isclite.ear | Santosh Nair's WebSphere And Unix Study Notes

There may be a requirement for changing the Inactive Session Timeout for the Websphere Admin Console .
The default Session timeout of WAS Console is 30 minutes.

We cannot change the session timeout from directly from the Admin console but there are two methods to do it

Method 1 : Using the wsadmin Script

This is the Recommended way to change the Session Expiration timeout value

Step 1 : The session timeout is saved in the deployment.xml file within the isclite.ear
a) Navigate to the <ProfileHome>/cells/CellName/applications/isclite.ear/deployments/isclite

[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Cell01/applications/isclite.ear/deployments/isclite

b) Check the Existing Session timeout value in the deployment.xml
Open the file deployment.xml and search for the parameter “invalidationTimeout”
Here “invalidationTimeout=30” Indicates the session timeout is 30 minutes

Step 2 : Copy the below following script into a file in the server in any location . I have saved this script in /root/sessiontimeout.jacl

set dep [$AdminConfig getid /Deployment:isclite/]
set appDep [$AdminConfig list ApplicationDeployment $dep]
set sesMgmt [$AdminConfig list SessionManager $appDep]# check if existing sesMgmt there or not, if not then create a new one, if exist then modify it
if {$sesMgmt == “”} {
# get applicationConfig to create new SessionManager
set appConfig [$AdminConfig list ApplicationConfig $appDep]
if {$appConfig == “”} {
# create a new one
set appConfig [$AdminConfig create ApplicationConfig $appDep {}]
# then create a new SessionManager using new Application Config just created
set sesMgmt [$AdminConfig create SessionManager $appConfig {}]
} else {
# create new SessionManager using the existing ApplicationConfig
set sesMgmt [$AdminConfig create SessionManager $appConfig {}]}
}# get tuningParams config id
set tuningParams [$AdminConfig showAttribute $sesMgmt tuningParams]
if {$tuningParams == “”} {
# create a new tuningParams
$AdminConfig create TuningParams $sesMgmt {{invalidationTimeout <timeout value>}}} else {
#modify the existing one
$AdminConfig modify $tuningParams {{invalidationTimeout <timeout value>}}}# saving the configuration changes
$AdminConfig save

Step 3 : Change the on the two lines of this file to the new session expiration value which you want and save the changes to the file. I have specified10 min as session expiration

This number specifies the number of minutes the console preserves the session during inactivity

Step 4 : Run the wsadmin.sh ( you may have to specify the credentials if security is enabled )

bash-3.2$[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

Execute wsadmin.sh -lang jacl -f FileName

bash-3.2$[root@mercury bin]# ./wsadmin.sh -lang jacl -f /root/sessiontimeout.jacl

Step 5 : Once the script is run check the deployment.xml to ensure the changes are reflected in it

Here the changes ie invalidationTimeout=”10″ is updated in deployment.xml file of isclite.ear

Step 6 : Restart the Dmgr or the Appserver ( in case of Stand Alone Server)

bash-3.2$[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

Stop Deployment Manager

bash-3.2$[root@mercury isclite]# ./stopManager.sh

Start Deployment Manager

bash-3.2$[root@mercury isclite]# ./startManager.sh

Step 7 : Test the session expiry after 10 min of Inactivity in the Websphere Admin console
Method 2: Modifying the deployment.xml

Step 1 : The session timeout is saved in the deployment.xml file within the isclite.ear
a) Navigate to the <ProfileHome>/cells/CellName/applications/isclite.ear/deployments/isclite

[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Cell01/applications/isclite.ear/deployments/isclite

b) Check the Existing Session timeout value in the deployment.xml
Open the file deployment.xml and search for the parameter “invalidationTimeout”
Here “invalidationTimeout=30” Indicates the session timeout is 30 minutes

Step 2 : Logout of the WAS admin console if you are allready logged in .

Step 3: Backup the existing deployment.xml file within the isclite.ear to some other location outside the WAS directory structure. This will ensure you wll be able to revert to the original setting if any issues occurs.

[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Cell01/applications/isclite.ear/deployments/isclite

I have saved the deployment.xml.org in /root as deployment.xml.org

[root@mercury isclite]# cp deployment.xml /root/deployment.xml.org

Step 4: Navigate to Go to the following directory,
<ProfileHome>/cells/CellName/applications/isclite.ear/deployments/isclite

Step 5 : Modify the deployment.xml file any editor and update setting the value of the “invalidationTimeout” parameter to the desired value (In minutes)

Here the I have update the invalidationTimeout=”10″ in deployment.xml file

Step 6 : Restart the Dmgr or the Appserver ( in case of Stand Alone Server)

bash-3.2$[root@mercury isclite]# cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

Stop Deployment Manager

bash-3.2$[root@mercury isclite]# ./stopManager.sh

Start Deployment Manager

bash-3.2$[root@mercury isclite]# ./startManager.sh

Step 7 : Test the session expiry after 10 min of Inactivity in the Websphere Admin console

In this Post i will share how to change the Background Image of the Admin console and also one you login change the Banner

Why is it needed sometimes
a) Some customers there may be many Websphere Instances
b) Confusing between different Admin console
c) Prevent Mistake of sometimes working on a Production Admin console instead of the UAT or DEV or any other env
d) This helps to identify the environment which we intent to work with .

Scope
: Change the Login Image
: Change the Banner Image post Login

Step1 :
The Images which are used with the Admin Console are available in the Path <WAS_ROOT>/AppServer/systemApps/isclite.ear/isclite.war/images

In my case its /apps/IBM/WebSphere/AppServer/systemApps/isclite.ear/isclite.war/images

List of the png Images

For the Login Image : login_image_175x175.png
Dimensions : 175X175 px
For the Banner Image : banner-swoosh.png
Dimensions : 577X45 px

IMP: Take the Backup of these files either in the same location as login_image_175x175.png.org & banner-swoosh.png.org or in your local machine

Step2: Once the Backup is done , download these two images in your local machine using Winscp from /apps/IBM/WebSphere/AppServer/systemApps/isclite.ear/isclite.war/images

Step3: Change the Login Image
We need to resize these New Images using any Image editor.. I use http://apps.pixlr.com/editor/
This is Online based, very light weight and User friendly But you can use any editor tool like MS Paint etc

NOTE :If you are going to use any other Image Ensure that the dimensions of the new Image is same as the one your are replacing in this case 175X175 px

I will be replacing the below Image (Original Dimension is 175X175 px)

With the one below

The dimensions are 175X175 px

Step4: Using Winscp move the New Image to /apps/IBM/WebSphere/AppServer/systemApps/isclite.ear/isclite.war/images and rename it as login_image_175x175.png

Step5: Clear the Browser Cookies and hit the admin console url . Now you can see the new Login Image instead of the old one

Step 6: You can Also modify the Image with pixlr / MS Paint to add the environment details

Similarly you can use any Image or the same login_image_175x175.png with the details of your environment details like PROD . Application server name etc

Modify the Banner Image
Step 1: Copy the banner-swoosh.png from /apps/IBM/WebSphere/AppServer/systemApps/isclite.ear/isclite.war/images to your local machine

Step 2: Edit it using pixlr tool to mention the details of the Environment

In My case i have mentioned the “PROD MYAPP WAS-v8.5.5 ”
NOTE: You can use any image but enure the dimension of the Image is 577X45 px and can experiment with the Font , color

Save the image as banner-swoosh.png

Step 3: Upload the banner-swoosh.png to /apps/IBM/WebSphere/AppServer/systemApps/isclite.ear/isclite.war/images
Overwrite the existing one

Step4: Clear the browser cookies and retry to login
Now we will see the details in the Banner once we login

NOTE : You could use different colors for each environment , for eg : Yellow — DEV , Green – UAT , RED – PROD

To get regular mail updates on my Posts , Please subscribe to the site http://webspherepundit.com and also like the Facebook Page https://www.facebook.com/webspherepundit

Santosh Nair's WebSphere And Unix Study Notes

Tag Archive | isclite.ear

Changing Inactive Session TimeOut for WAS Admin console

Change the Background Image of Admin Console

To get regular mail updates on my Posts , Please subscribe to the site http://webspherepundit.com and also like the Facebook Page https://www.facebook.com/webspherepundit