Abhi2271/tech-qa huggingface dataset:
IBM Setting a big session time-out value in DASH causes session lock-out - United States DASHL2; session; time-out; timeout; cannot login; locked out ; 2147483647; security.xml TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Using a big value (2147483647) for the session timeout setting in DASH, to achieve the maximum time between timeouts, is causing users to be locked out completely. 

SYMPTOM
After entering the user ID and password in the login page, and then pressing the "continue" button,
the login page does not change, stuck at "processing" and then returns to the login page again." 

All users get essentially locked out completely from DASH sessions.


CAUSE
In order to maximize the time between session timeouts, the customer is setting the timeout parameter in the security.xml file to 2147483647.

This timeout parameter used in the security.xml file is a WAS setting, but DASH is using a javascript call (settimeout), which causes a condition that prevents a login, if the timeout value is really big. 


Note: 2147483647 is the maximum positive value for a 32-bit signed binary integer in computing.


RESOLVING THE PROBLEM
This condition that prevents logins can be averted by setting the custom property LTPAFIX in the consoleProperties.xml to "false". 


Please follow this steps: 

1. On DASH server, navigate to <JazzSM Home>/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF 

 
2. Take a backup of consoleProperties.xml 

 
3. Open consoleProperties.xml in edit-mode. 

 
4. Search for "LTPAFIX" and change the value from "true" to "false". 


Example: 

Before 
===== 
<consoleproperties:console-property id="LTPAFIX" value="true"/> 
</consoleproperties:ibm-portal-consoleproperties> 

After 
==== 
<consoleproperties:console-property id="LTPAFIX" value="false"/> 
</consoleproperties:ibm-portal-consoleproperties> 

5. Save the file. 

 
6. Restart DASH server.

Question: Why are the users unable to login to Web GUI 8.1 after I modify timeout to 2147483647 in security.xml file ? 

I followed the Web GUI 8.1 reference guide here to switching off the session timeout

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/webtop/wip/task/web_adm_settimeout.html

After I edited /config/cells/JazzSMNode01Cell/security.xml file, modified timeout setting to 2147483647, users are not able to login anymore.

Answer: 1. On DASH server, navigate to <JazzSM Home>/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF


2. Take a backup of consoleProperties.xml


3. Open consoleProperties.xml in edit-mode.


4. Search for "LTPAFIX" and change the value from "true" to "false".
IBM How to Proxy SSL request from DataPower to Remote Proxy Server? - United States Forward Proxy XMLFW MPGW CONNECT TUNNEL TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 How to configure an IBM WebSphere DataPower SOA Appliance Service to proxy an SSL request to a remote proxy server using the CONNECT method for SSL tunneling? 

CAUSE
Many common forward proxy servers expect requests in different formats depending on if they are proxying non-SSL or SSL requests.

For example, a non-SSL request to be proxied may come in the form of GET hostname:port/URI.

For SSL requests to be proxied, remote proxy servers are commonly configured to tunnel the request from the client to the backend server.

In the SSL request scenario, remote proxy servers will typically expect a CONNECT request and then tunnel the SSL request from the client to the backend server.

Users configuring DataPower may need a way to implement this CONNECT method for SSL tunneling to a remote Proxy Server.




RESOLVING THE PROBLEM
Non-SSL Proxy requests will work using either:

a) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port

b) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent

SSL Proxy requests will work using the CONNECT method for SSL Tunneling when using a Multi-Protocol Gateway when configuring in a User Agent's HTTP Proxy Policy.

The XML Firewall service is not designed to use the CONNECT method for SSL Tunneling.

Question: Does IBM DataPower Gateway Appliance support the HTTP CONNECT method? Does IBM DataPower Gateway Appliance support the HTTP CONNECT method for SSL proxy requests? 

Answer: SSL Proxy requests will work using the CONNECT method for SSL Tunneling when using a Multi-Protocol Gateway when configuring in a User Agent's HTTP Proxy Policy.

The XML Firewall service is not designed to use the CONNECT method for SSL Tunneling.
IBM How do I adjust the number of batches that DotEdit displays in IBM Datacap Taskmaster Capture? - United States batch; list TECHNOTE (FAQ)

QUESTION
 I want to increase the number of batches that IBM Datacap DotEdit displays. It only displays 100 and there are more than 100 batches available. What needs to be done to increase the list? 

CAUSE
The default limit is 100 rows, but this number can be modified by editing the file \Datacap\DotEdit\apps.ini file.

ANSWER
Please do the following: 

 1. Backup the \Datacap\DotEdit\apps.ini file. If the file does not exist, create a new one or copy it from \Datacap\tmweb.net. 
 2. Open it in notepad.exe or other editor. 
 3. Find the app to be modified (for example [APT]). If it does not exist, create a new section with the application name listed between square brackets. 
 4. Add a new line containing BatchLimit=xxx, where xxx is the number of batches to be displayed. 
 5. Save the file.


Additional information: 
 * For version 8.1, Fix Pack 1 or newer must be installed. 
 * Increasing the number of batches displayed is known to cause a slowdown in perceived response time due to gathering and formatting of the batch list. 
 * The optimum number will vary due to system conditions, infrastructure and user expectation. 
 * The DotEdit batch list will be slower to display than the batch list in Taskmaster Web, due to architectural differences between the applications.

Question: Unable to view batches in DotEdit 

Hi all,

Is there any limitation to view batches in Dot Edit client application, because I am unable to see batches with QID more than 1119.

Also unable to see batches with status as "Pending". 


Answer: Backup the \Datacap\DotEdit\apps.ini file. If the file does not exist, create a new one or copy it from \Datacap\tmweb.net. 
 2. Open it in notepad.exe or other editor. 
 3. Find the app to be modified (for example [APT]). If it does not exist, create a new section with the application name listed between square brackets. 
 4. Add a new line containing BatchLimit=xxx, where xxx is the number of batches to be displayed. 
 5. Save the file.