Content Platform Engine relies on the transaction timeout value. The default timeout value
might be too small for IBM® Enterprise
Records. Before you install IBM Enterprise
Records, increase the transaction timeout value.
About this task
Also, Content Engine and Content Platform Engine rely
on the transaction-timeout value, whose default might be too short
for some standard or administrative processes.
Procedure
To increase the transaction timeout value on your web
application server.
Complete appropriate procedure in the following table:
Option |
Description |
WebSphere® Application
Server |
- Log in to the WebSphere Application
Server administrative console and navigate to .
- Increase the values for total transaction lifetime timeout and
maximum transaction timeout to 600 seconds and save your changes.
- Navigate to .
- Set the Request timeout value to 150% of the transaction timeout
value you set. For example, if your Content Engine Transaction
Timeout value is 600, set the Request Timeout value to 900. Content Platform Engine transaction timeout is different from IBM Enterprise
Records ORB services transaction
timeout.
- Set the transaction timeout for all application servers and then
change the IBM Enterprise
Records ORB
services transaction timeout only for WebSphere Application
Server.
- Restart the WebSphere Application
Server.
|
WebLogic Server |
- Log in to the WebLogic Server Administration Console.
- Adjust transaction-timeout value by setting the JTA
node timeout in seconds value to at least 600 seconds.
- Restart the WebLogic Server.
|
JBoss Application Server |
- Log in to the JBoss Application Server
- Edit the JBOSS_HOME/server/default/conf/jboss-service.xml file.
- Locate the TransactionTimeout attribute tag and set its value
to at least 600 (seconds), for example:
<attribute name="Transaction
Timeout">600</attribute>
- Save and close the jboss-service.xml file.
- Restart the JBoss Application Server.
|