WebSphere Application Server 8.5.5: Changing the console session expiration

The idle period, before the administrative console session expires, is referred to as session timeout. The default session timeout value for the administrative console is 15 minutes. The timeout value can be modified by using a JACL script that is available at the information center. [From: WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile]

Run this JACL script to set how long Integrated Solutions Console can be used until the login session expires.

About this task

The following JACL script serves as an example of how to set the duration that an Integrated Solutions Console can be used until the login session expires. Other scripting types, such as JYTHON, could be used.

Procedure

  1. Copy the following script into a file.
    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
    
  2. Change the <timeout value> on the two lines of this sample to the new session expiration value. This number specifies the number of minutes the console preserves the session during inactivity.
  3. Save the file to any directory using, for example, the filename timeout.jacl.
  4. Start the wsadmin scripting client from the <WAS-install>/profiles/<profile_name>/bin directory.
  5. Issue the following command.
    wsadmin -f <path to jacl file>/timeout.jacl

Source: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Fisc%2Fcons_sessionto.html

Inaccessible WebSphere Application Server 7.0

You may have experienced that you cannot access your WAS installation anymore for whatever reason. If you are sure that you haven’t changed the credentials or something like that, there’s still a way to fix it.

I tried to inspect the services.msc on Windows. You can see there the WebSphere Application Server service. If its startup type is Automatic, change it to Manual. Then restart the machine. Start the deployment manager or server (depends on your environment) manually. Based on my experience, this should be okay now. If WAS is inaccessible again, change the startup type to Automatic and then restart the machine.

If you still cannot login, there must be some problem with your WAS configuration.

If anyone know the exact solution, please comment! 😀