Change E1 timeout on wls (WebLogic) and explanation of multiple copies of jdbj.ini and jas.ini

Remember that JDE maintains a couple of copies of many of the main files that you are dealing with in WLS.  There is a couple of copies in the SM directories.  This is the copy that you change when you are editing the file with SM.   For web.xml It’s in a path something like:

/u01/app/oracle/jde_home_1/SCFHA/targets/JDE91DV/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/web.xml

How to find them for your site (on linux) a cheeky find command like the one below [for jdbj.ini):

find  . -name jdbj.ini -exec ls -l {} \;

This will tell you that the two “Server Manager” copies are actually:

-rwxrwxrwx 1 oracle oinstall 1720 Jun  1 16:19 ./SCFHA/targets/JDE91DV/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/classes/jdbj.ini
-rwxrwxrwx 1 oracle oinstall 1720 Jun  1 16:20 ./SCFHA/targets/JDE91DV/config/jdbj.ini

So, there are two copies of jdbj.ini in the SM tree, there is also another in the WEB-INF classes dir for the runtime JVM.

-rw-r----- 1 oracle oinstall 3387 Jun 5 16:20 ./domains/mydomain/servers/JDE91DV/stage/JDE91DV/app/webclient.war/WEB-INF/classes/jdbj.ini

When you change a value in SM, you get a message like:

and you see the physical file that is changed is below:

-rw-r--r-- 1 oracle oinstall 3387 Jun  1 16:19 ./SCFHA/targets/JDE91DV/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/classes/jas.ini
-rwxrwxrwx 1 oracle oinstall 3387 Jun  5 11:10 ./SCFHA/targets/JDE91DV/config/jas.ini

The one that is read in by the wls JVM is still unchanged:

-rw-r----- 1 oracle oinstall 3387 Jun  1 16:19 ./domains/mydomain/servers/JDE91DV/stage/JDE91DV/app/webclient.war/WEB-INF/classes/jas.ini

So, when I hit synch, it makes 2 copies of the file.  One to the owl_deployment location and the second to the runtime location for WLS  Note the times highlighted.

-rw-r----- 1 oracle oinstall 3387 Jun  5 11:14 ./domains/mydomain/servers/JDE91DV/stage/JDE91DV/app/webclient.war/WEB-INF/classes/jas.ini

-rw-r--r-- 1 oracle oinstall 3387 Jun  5 11:14 ./SCFHA/targets/JDE91DV/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/classes/jas.ini
-rwxrwxrwx 1 oracle oinstall 3387 Jun  5 11:10 ./SCFHA/targets/JDE91DV/config/jas.ini

 

This is turning into quite a saga.  I guess the reason I’ve explained the above is to tell you WHY you are changing two copies of the web.xml for the timeout.  1 for the runtime and 2 incase there is some sort of redeployment from SM triggered.

edit the web.xml file and add the following before the last line of the file.  This is for a 30 minute timeout.  Please don’t type the quotes, my blog post is not working with RAW xml.

• <session-config>
    <session-timeout>30</session-timeout>
• </session-config>