1. For OAS 10.1.3:
修改OAS Session timeout value
Log in to the Oracle Enterprise Manager
Select your OC4J containerClick on "Applications" Link
Click on link for your E1 JAS OC4J, Ex: "EA_JS_81"
Click on the link for webmodule, "webclient"
Click on link for "Administration"
Under "Go to Task" column, click on icon for "Configuration Properties"
Set the Session timeout value in Seconds
Restart the OC4J instance
Session timeout value => 3600
Update the UserSession value in the relevant JAS.INI:
EnterpriseOne HTML Server -> Instance Name -> Configuration -> Web Runtime -> Cache Configuration -> User Session Cache Timeout -> 5400000修改Http Server Timeout值
修改Http Server Timeout值 => 5400
/u01/OracleAS_1/Apache/Apache/conf/httpd.conf
2. For Oracle WebLogic Server (WLS)
Modify the web.xml and restart the instance - default 60mins
The web.xml file is missing the session-timeout descriptors. The session defaults to 1 hour.
[root@e1wls04 u01]# find . -name 'web.xml'|grep webclient.war
./oracle/Middleware/user_projects/domains/PD_e1wls04/servers/PD900_e1wls04/stage/PD_e1wls04/app/webclient.war/WEB-INF/web.xml[root@e1wls04 u01]# find . -name 'web.xml'|grep webclient.war
./JDE_HOME/targets/PD_e1wls04/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/web.xml
Make a backup of the above two web.xml files. Add the following stanza at the end (right before </web-app>) of both these web.xml files:
<session-config>
<session-timeout>60</session-timeout>
</session-config>
NOTE:
The DOWNSIDE of this extensive timeout value is that the user session will be kept in memory for a longer time which in turn the JVM will support fewer sessions. If more sessions get created (more users login) and remain in memory for a longer time there is a chance that an OutOfMemory condition will be reached. Consider fewer users per (JVM) JAS instance if user sessions are going to be "alive" for a longer time. Oracle Support recommends a timeout value of 30 minutes with 60 minutes being the high end.
沒有留言:
張貼留言