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.


  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


IBM Content Navigator 2.0.2 Ping page


To access the Ping page to find version information for IBM Content Navigator:

Enter the URL from any browser with the following format:


By default, the context root is navigator.

Tip: If you are using SSL, the protocol of the URL is HTTPS:




Source: http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.1.0/com.ibm.installingeuc.doc/eucts019.htm?lang=en

Cannot load Search Designer (Workplace XT) in Internet Explorer

Workplace XT version: 1.1.5

IE version: 10


When accessing Search Designer in IE, it says that it needs Java to run the applet. Although the Java is installed, IE still does not load the page.


Make sure that the site is added to the Trusted sites zone.


  1. Go to Tools > Internet Options.
  2. Under Security tab, click Trusted sites and click the Sites button.
  3. Enter the site in the “Add this website to the zone” field.


Process Engine Workflow Terminologies

Each workflow step is created in the Process Designer.  The step specifies what needs to be accomplished and included in order for the business process to continue.

A workflow step has:

Participants who are individually assigned to complete part of the workflow.

Workflow groups to which work is assigned when it is to be completed by the first available worker in that group.

Responses that can be used to direct routing.

Attachments that provide participants with information they need to complete work.

Data fields, which can be Boolean, Float, Integer, String, or Time.  Whether the suit fits is a Boolean field, which means it can be either True or False.

Types of steps

General step: General steps represent an activity that will be processed by a participant or sent to a work queue for processing by participants.

System step: System steps represent built-in functions that will be performed by the system software. The built-in system functions perform logic-control and other functionality in the workflow, such as setting time limits for specific activities in the workflow.

Submap step: Submap steps represent calls to another workflow map.

Component step: Through the Component Integrator, the component step automatically performs actions on the Content Engine, or through custom code, can perform a variety of requests through 3rd party applications.

source: IBM Corporation

FileNet Process Engine Terminologies

The Process Engine Database is a Microsoft SQL or Oracle database that manages the process data.

Workflows are data in the Process Engine Database. If the database is not working or properly configured, workflow activity is impossible.

Isolated Region – a logical subdivision or partition of the Process Engine Database that separates work according to organizational boundaries. Each Process Engine Database must contain at least one isolated region.

Roster – a table that contains information about all currently running workflows that is used primarily to search for active workflows.

Queue  a table that holds work items.

Workflow – an instance of a workflow definition.

Work Item – a single unit of work; a task.

The Process Engine Database is administered through the Process Configuration Console (PCC), which is available through FileNet P8 Workplace. The PCC is used to create and initialize isolated regions, and create queues and rosters.

source: IBM Corporation

Datacap Studio Application Error


When developing an application in Datacap Studio, the Datacap Studio window just closes and a message box is displayed saying something like “external component has thrown an exception…”.


Just open Datacap Studio again. I don’t know the exact cause of the problem… If anyone has additional knowledge about this, feel free to comment! 🙂

Datacap Studio 8.1 UI Bug

We have experienced bugs in the user interface of Datacap Studio 8.1, particularly on the Test tab.


First, the Test tab displays the content of the Rulemanager tab. Second, it displays NOTHING. Yes, just nothing. Just white background without anything on it.


We just reinstalled Datacap and everything went fine as it should be. Restarting the machine does not solve it. If anyone knows an alternative solution, feel free to comment! 🙂