Dynamic Workload Console - adjusting session timeout settings

About this task

The value assigned to the session timeout settings defines after how many minutes a user is automatically logged out from the WebSphere Application Server Liberty Base. If you plan to perform long running operations, or to have many users connected concurrently to the Dynamic Workload Console, or expect to have low performance on the system where the Dynamic Workload Console is installed, you might want to edit these values: httpSession invalidationTimeout="5h" and ltpa expiration="1440".

Perform these steps to change the values assigned to the timeout settings:

Stop WebSphere Application Server Liberty Base:
UNIX™
```
./stopAppServer.sh  [-direct]
```
Windows™
```
stopAppServer.bat [-direct]
                 
```
For more information about stopping WebSphere Application Server Liberty Base, see Application server - starting and stopping.

Create a .xml file with this content (i.e. timeout_config.xml):

<server description="http_timeout_config">    
 <httpSession invalidationTimeout="5h" invalidateOnUnauthorizedSessionRequestException="false"/>
 <ltpa expiration="1440"/> 
 </server>

Save the file in the following path:<DATA_DIR>/usr/dwcServer/configDropins/overrides
Start WebSphere Application Server Liberty Base:
UNIX™
```
./startAppServer.sh  [-direct]
```
Windows™
```
startAppServer.bat [-direct]
                 
```
Note: The desired time must be indicated in minutes
For more information, please refer to the WebSphere Application Server Liberty Base documentation at the following links https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.liberty.autogen.base.doc/ae/rwlp_config_httpSession.html. and https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.liberty.autogen.base.doc/ae/rwlp_config_ltpa.html

Configuring the DWC.timeout.expiration parameter

HCL Workload Automation V10.1 Fix Pack 5 introduced a new property named DWC.timeout.expiration within the ssl_config.xml file, enabling the Dynamic Workload Console to manage session timeouts more effectively.

If you are facing the OUTOFMEMORYERROR error, you can manually configure the DWC.timeout.expiration parameter.

The DWC.timeout.expiration setting must be defined in milliseconds within the ssl_config.xml file using the following format:
```
<jndiEntry jndiName="DWC.timeout.expiration" value="32400000"/>
```
The invalidationTimeout parameter, defined within the <httpSession> element, can be specified in minutes (m) or hours (h). For example:
```
<httpSession invalidationTimeout="30m"
invalidateOnUnauthorizedSessionRequestException="true"
accessOnTimeout = "false"/>
```
Note: It is recommended that the invalidationTimeout parameter be set between 30 minutes and 1 hour.
The ltpa.keys expiration setting, also within the ssl_config.xml file, is specified in minutes without the need for a unit symbol. For example:
```
<ltpa keysPassword="{xor}Ozo5PiozKw=="
keysFileName="${server.config.dir}/resources/security/ltpa.keys"
expiration="600"/>
```

Note: The sum of DWC.timeout.expiration and invalidationTimeout must be less than the ltpa.keys expiration value.