|
Problem(Abstract) |
The timeouts for the Deployment Manager server are
described separately because they are different than the Application
Server. Also, our best practice recommendation is different for deployment
manager server than for Applications Servers. Best practice for Deployment
Manager is to set the following timeouts to zero, which means no timeout.
To disable the timeouts in the Deployment Manager, set the HTTP and WLM
timeouts to zero. There are 7 settings:
HTTP non-SSL transport (3 settings)
input timeout
output timeout
keepalive timeout
HTTP SSL transport (3 settings)
input timeout
output timeout
keepalive timeout
WLM timeout (1 setting)
|
|
|
|
Resolving the
problem |
Setting HTTP transport timeout settings for Deployment Manager
Version 5.0
In Version 5.0 you cannot access the Deployment Manager's HTTP Transport
configuration through the administrative console. Edit the Deployment
Manager's server.xml file. If your Deployment Manager's directory is:
/WebSphere/V5R0M0/DeploymentManager
the server.xml file is located here:
/WebSphere/V5R0M0/DeploymentManager/config/cells/<cell
name>/nodes/<dmgr node name>/servers/dmgr/server.xml
Edit the following stanzas (server.xml is an ASCII file) :
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_1" sslEnabled="false">
<address xmi:id="EndPoint_1" host="" port="9090" />
<properties xmi:id="Property_1082999396779"
name="ConnectionIOTimeout" value="0" description="Disable
HTTP input timeout" required="false" />
<properties xmi:id="Property_1082999457062"
name="ConnectionResponseTimeout" value="0"
description="Disable HTTP output timeout" required="false"/>
<properties xmi:id="Property_1082999484327"
name="ConnectionKeepAliveTimeout" value="0"
description="Disable session keep alive timeout" required="false" />
</transports>
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_2" sslEnabled="true"
sslConfig="PLEX1Manager/DefaultHTTPS">
<address xmi:id="EndPoint_2" host="" port="9443" />
<properties xmi:id="Property_1082999396779"
name="ConnectionIOTimeout" value="0" description="Disable
HTTP input timeout" required="false" />
<properties xmi:id="Property_1082999457062"
name="ConnectionResponseTimeout" value="0"
description="Disable HTTP output timeout" required="false"/>
<properties xmi:id="Property_1082999484327"
name="ConnectionKeepAliveTimeout" value="0"
description="Disable session keep alive timeout" required="false" />
</transports>
Important: After saving the changes to server.xml, run the
WebSphere® Application Server for z/OS® configuration preprocessor
utility:
- cd /WebSphere/V5R0M0/DeploymentManager/bin
- wsc2n.sh -X
The purpose of running this utility is to copy certain configuration
values from your xml configuration documents to the dmgr's was.env file.
These settings are used by some of the native code that comprise the
implementation of the WebSphere Application Server for z/OS product.
Restart the Deployment Manager server to pick up these changes.
Version 5.1
- On the left side of the Administrative Console under System
Administration, select Deployment Manager > HTTP Transports.
- Click on host value for transport that is SSL Enabled = false,
then add the following custom properties:
ConnectionIOTimeout = 0
ConnectionResponseTimeout=0
ConnectionKeepAliveTimeout=0
- Repeat for SSL Enabled = true transport.
- Click OK until you receive a prompt to save the configuration.
- Save configuration.
- Restart Deployment Manager to pick up change.
How to set WLM timeout for Deployment Manager
For both Version 5.0 and 5.1, the WLM timeout is set the same way for the
Deployment Manager server as for an Application Server.
- On the left side of the Administrative Console under System
Administration, select Deployment Manager > ORB Service > Advanced
Settings
- Set the WLM Timeout to zero (ignore field description of
1-2147040 range).
- Click OK, then follow instructions to save the configuration.
- Restart Deployment Manager server to pick up this change.
|
|
|
|
|
|
|