Prashant's JD Edwards CNC Blog: October 2015

This topic explains about setting of session timeout for JAS Server for WebLogic server

Session timeout is a crucial setting. Setting the timeout value more than 30 minutes may cause high memory usage and out of memory error. Following setting is for 30 minutes timeout

1 Session Timeout Settings for Oracle WebLogic Server (WLS)

The web.xml file is missing the session-timeout descriptors. The session defaults to 1 hour.

Locate the two web.xml files for the weblogic installation as given below:

>> web.xml in the Server Manager Agent installation directory on the JAS Server:

......targets/webinstance name/owl_deployment/webclient.ear/app/webclient.war/WEB-INF/web.xml

>> web.xml in the Weblogic installation directory:

......user_projects/domains/.../servers/machine name/stage/webinstance name/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>30</session-timeout>

</session-config>

Bounce the web instance once.

Additionally, the E1 parameter that comes into play is the UserSession in the JAS.INI file:

[CACHE]

UserSession=1800000

UserSession=1800000 this value is equivalent to 30 minutes.
This will expire the JDE user session after 20 minutes of inactivity despite a higher setting in the Weblogic XML files.
NOTE: The UserSession inactivity is checked in fixed intervals set by the variable cachecheck from the same section in JAS.INI. This means that if the UserSession is 30min and cachecheck 5min, the session will actually be expired at any time between the 30min and 34min59sec, this means the first time the cachecheck runs after the idletimeout is exceeded.

Here is additional information on timeouts:

The user session for WebLogic needs to timeout before the user session for JAS. For instance, if the user sessions for WebLogic are set to timeout after 60 minutes of inactivity, then the user sessions for JAS needs be set to timeout to somewhat more than 60 minutes (like 70 minutes).

If the timeout is set to 60 minutes, the user’s session will be cleaned up (removed) the next time a cachecheck task is executed and the session has 60+ minutes of INACTIVITY, hence upon clicking any application users are taken to the login page for a new session to be created (this is how it will work). Note: If the cachecheck interval is 10min, the session idle time could go from 60min to 59min59sec before it's expired.

The UserSession will only be active for as much time as mentioned in the JAS.INI file or the WLS session timeout value whichever is LOWER. Note: the UserSession must also take into account the variability of the expiration time depending on the cachecheck intervals.

If the session needs to be active for upto/beyond 2 hours it is necessary to increase this to 2 hours (120 minutes) in both the WLS session timeout settings and the JAS.INI file and bounce the JAS Server for the setting to take effect.

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.

This step-by-step guide is done on SOLARIS system

Following component is needed to Install Self Service.

Please go thru oracle link http://docs.oracle.com/cd/E24705_01/doc.91/e21052/toc.htm before starting setup

Install and Configure Oracle Database [11.2.0.1]
Install Repository Creation using [RCU] – V37395-01
Install jdk 1.7.0_79
Installing Oracle WebLogic [10.3.6.0] Server
Installing WebCenter Portal 11g [11.1.1.8.0]
Configuring WebCenter
Installation of required patches
Starting nodeManager.sh & startWeblogic.sh
Portal Login details
Creation of new instance in Server Manager
Register Portal

Install and Configure Oracle Database [11.2.0.1]

Install Oracle Database [Pre-installation task]

a) Create necessary groups and a user. [Following instruction is to be done using root user id]

[code]

groupadd oinstall

groupadd dba

useradd -g oinstall -G dba -d /export/home/oracle -s /usr/bin/bash oracle

passwd oracle

[/code]

b) Create necessary folder for the installation

[code]

mkdir -p /u01/oracle/product/11.2.0/db_1

mkdir /export/home/oracle/tmp

[/code]

[code]

chown -R oracle:oinstall /export/home/oracle

[/code]

c) Change kernel parameters

[code]

projadd -U oracle -K "project.max-shm-memory=(priv,4g,deny)" oracle

projmod -sK "project.max-sem-nsems=(priv,256,deny)" oracle

projmod -sK "project.max-sem-ids=(priv,100,deny)" oracle

projmod -sK "project.max-shm-ids=(priv,100,deny)" oracle

echo "set maxuprc=16384" >> /etc/system

echo "set max_nprocs=30000" >> /etc/system

echo "set shmsys:shminfo_shmmax=4294967295" >> /etc/system

[/code]

Now reboot the machine and login with an oracle user. Now change the .profile file of the oracle user and set necessary environment variables:

vi /export/home/oracle/.profile

[code]

export ORACLE_SID=portal

export JAVA_HOME=/u01/jdk/jdk1.7.0_79

export ORACLE_BASE=/u01/db

export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1

export PATH=$ORACLE_HOME/bin:$PATH

export TMP=/export/home/oracle/tmp

export TMPDIR=/export/home/oracle/tmp

export DISPLAY=:0.0

export PATH=$JAVA_HOME/bin:$PATH

[/code]

Now create an “installation” directory under /u01/installable. Extract downloaded files using unzip utility & start the installation.

[code]

cd/u01/oracle/installable/OracleDB/database

./runinstaller.

[/code]

1	$C:\Temp\db\1$ Uncheck the checkbox and click next.	2	$C:\Temp\db\2$ Click second option & click on Next button
3	$C:\Temp\db\3$ Click Next	4	$C:\Temp\db\4$ Click Next
5	$C:\Temp\db\5$ Select standard edition & click Next	6	$C:\Temp\db\6$ Enter Software installation directory & click on Next
7	$C:\Temp\db\7$ Enter Inventory directory & click on Next	8	$C:\Temp\db\8$ Click Next
9	$C:\Temp\db\9$ Save response file & click on Finish	10	$C:\Temp\db\10$ This will complete Oracle Database software installation part.

Configure Database (Creation of database using DBCA)

[code]

Cd /u01/oracle/product/11.2.0/db_1/bin

./dbca

[/code]

$C:\Temp\db\db1$

1	$C:\Temp\db\db2$ Click Next	2	$C:\Temp\db\db3$ Select create a database & click on next
3	$C:\Temp\db\db4$ Select option 1 & click on Next	4	$C:\Temp\db\db5$ Enter db name as portal & click on Next
5	$C:\Temp\db\db7$ De-select enable auto maintenance task - click next	6	$C:\Temp\db\db8$ Enter password as 0rac1e & click on Next
7	$C:\Temp\db\db9$ Click on Next	8	$C:\Temp\db\db10$ Remove all check box & click on Next
9	$C:\Temp\db\db11$ De-select sample schemas & click on Next	A	$C:\Temp\db\db11$ Enter 2048 MB as memory Size, select use automatic memory management & click on Next
B	$C:\Temp\db\db13$ Select AL32UTF8 as character set & click on next	C	$C:\Temp\db\db15$ Select 100 processes and click on next
D	$C:\Temp\db\db16$ Click on Next	E	$C:\Temp\db\db17$ Select create database and click on Finish button

After completion start listner. This will complete the process for oracle database installation.

Install Repository Creation using [RCU] – V37395-01

Download the RCU from oracle (link: http://www.oracle.com/technetwork/middleware/downloads/fmw-11-download-092893.html ) Part # V37394-01 is for Linux & V37395-01 is for Windows platform [We have downloaded Windows RCU].

Oracle WebCenter requires that certain schemas exist in the database prior to installation. You must run the Repository Creation Utility (RCU) in order to create the schemas in the database.

Before begin adjust the following database parameters before running RCU

alter system set processes=500 scope=spfile;

alter system set open_cursors=800 scope=spfile;

shutdown immediate;

startup;

You must unzip the file and put it in a easy to access folder. We can consider this folder as an Oracle Home (rcu Home). In our case we have installed it in C:\Temp\rcu\rcuHome\BIN

The following screen will appear:

Create OBIEE schemas with RCU : Create repository . Choose "Create and load component schemas into a database." and press "Next".

The following screen will appear: select the “WebCenter Suite” & change prefix to “OW” from “DEV”

Create OBIEE schemas with RCU : Select Components

Click on "Next". The following screen will appear

Click on Next

Click on Create

When the schemas/ tablespaces are created the following screen will appear:

Create OBIEE schemas with RCU : Completion Summary Click on "Close" and all the stuff is done. Now you are ready to install the OBIEE Server.

Installing jdk 1.7

Before installation weblogic server Jdk 1.7 component is needed. Installable dk-7u79-solaris-sparc.gz and jdk-7u79-solaris-sparcv9.gz has been downloaded from oracle.

Installation steps are as follows

zcat jdk-7u<version>-solaris-sparc.tar.Z | tar xf -

zcat jdk-7u<version>-solaris-sparcv9.tar.Z | tar xf -

Restarted the server & verified new version of java

Installing Oracle WebLogic [10.3.6.0] Server

Download following part number from e-delivery for weblogic installation, extract these zip files and copy to portal server

Extract V29856-01 & run following command in /u01/installable/WebLogic

java -d64 -jar wls1036_generic.jar

Following screen will appear

1	$C:\Temp\jrockit\Screenshot\2$ Click on Next	2	$C:\Temp\jrockit\Screenshot\3$ Enter path to install and Click on Next
3	$C:\Temp\jrockit\Screenshot\4$ Select custom and Click on Next	4	$C:\Temp\jrockit\Screenshot\5$ Click on Next
5	$C:\Temp\jrockit\Screenshot\6$ Verify java version & click on next	6	$C:\Temp\jrockit\Screenshot\7$ Click on Next
7	$C:\Temp\jrockit\Screenshot\8$ Click on Next	8	$C:\Temp\jrockit\Screenshot\9$ Deselect Run Quickstart & click on Done

Installing WebCenter Portal 11g [11.1.1.8.0]

Installer requires the location of Java Runtime Environment [JRE]. Location has been given while running ./runinstaller

$C:\Temp\weblogic\screenshot\1$

$C:\Temp\weblogic\screenshot\2$

$C:\Temp\weblogic\screenshot\3$

$C:\Temp\weblogic\screenshot\4$

$C:\Temp\weblogic\screenshot\5$

$C:\Temp\weblogic\screenshot\6$

$C:\Temp\weblogic\screenshot\7$

$C:\Temp\weblogic\screenshot\8$

Configuring Web Center

$C:\Temp\weblogic\screenshot\9$

$C:\Temp\weblogic\screenshot\10$

$C:\Temp\weblogic\screenshot\11$

$C:\Temp\weblogic\screenshot\12$

$C:\Temp\weblogic\screenshot\13$

$C:\Temp\weblogic\screenshot\14$

$C:\Temp\weblogic\screenshot\15$

$C:\Temp\weblogic\screenshot\16$

$C:\Temp\weblogic\screenshot\17$

$C:\Temp\weblogic\screenshot\18$

$C:\Temp\weblogic\screenshot\19$

$C:\Temp\weblogic\screenshot\20$

$C:\Temp\weblogic\screenshot\21$

$C:\Temp\weblogic\screenshot\22$

$C:\Temp\weblogic\screenshot\23$

Installation of Required patches

Patch: 6880880 This is latest opatch

Downloaded p6880880_111000_SOLARIS64.zip patches from patches and update tab of oracle support.

>mv p6880880_111000_SOLARIS64.zip /u01/Middleware/Oracle_WC1

>cd /u01/Middleware/Oracle_WC1

>mv OPatch OPatch_28042015

>unzip p6880880_112000_SOLARIS64.zip

Apart from patch following patches has been applied

Patch : 18633874 - p18633874_111180_Generic.zip

Patch 20425442 - p20425442_111180_Generic.zip

Starting nodeManager.sh & startWeblogic.sh

Now we need to start WebCenter WebLogic Admin Server and Managed Servers (WLS_Spaces, WLS_Portlet and WLS_Services)

Post Configuration Tasks

Starting Node Manager
Starting the WebLogic Administration Server
Starting Managed Servers from the Administration Console
Verify the installation

Starting WebLogic Node Manger

1. Run this script to start the Node Manager once. This process will create the Node Manager

properties file.

MW_Home/wlserver_10.3/server/bin/startNodeManager.sh

2. Shut down the Node Manager process.

3. Run this script to set the Node Manager properties. This process will update the

nodemanager.properties file.

MW_Home/oracle_common/common/bin/setNMProps.sh

4. Re-Run this script to start the Node Manager:

MW_Home/wlserver_10.3/server/bin/startNodeManager.sh

Starting WebLogic startWeblogic

1.Before starting server create boot.properties in

/u01/Middleware/user_projects/domains/portal_domain/servers/AdminServer/security

The boot.properties should contain following entries

username=weblogic

password=oracle123

2. Start server with running startWeblogic.sh script in the directory /u01/Middleware/user_projects/domains/portal_domain/bin

Portal Login Details

SR #	Description	Link
1	Web Logic Admin	http://prtlserver:7001/console
2	Web Center Login	Http://prtlserver:8888/webcenter
3	Web Center Console / Enterprise Manager	http://prtlserver:7001/em