Tuning the eWAS heap size for TDWC

You are having issues with performance of the embedded WebSphere Application Server (eWAS), especially during massive object queries from TDWC, or during planner activity.

A typical error message that is seen in the SystemOut.log is an OutOfMemory message.

Change the maximumHeapSize for eWAS, then restart the WebSphere Application Server.

The change can be done in this file:

<TWSHome>/appserver/profiles/twsprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/server1/server.xml

Edit the following line at the bottom of the server.xml file:

"verboseModeClass="false" verboseModeGarbageCollection="false" verboseModeJNI="false" initialHeapSize="256" maximumHeapSize="1024"

Change the maximumHeapSize, then restart the WebSphere Application Server.

If you install TWS v8.6 on a 64 bit platform, you can increase the heapsize to 2048.

If you install TWS v8.5.1 on a 64 bit platform, check the operating system. This release of TWS still uses a 32-bit version of eWAS for some platforms (for example AIX, HP, and Solaris). In this case, the suggestion is to set the maximum heapsize value to 1536.

Server.xml location by product version:

TWS v8.3 and v8.4: <TWSHome>/appserver/profiles/twsprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/server1/server.xml

TWS 8.5x:
<TWAHome>/eWAS/profiles/twaprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/<servername>/server.xml

TWS 8.6:
<TWAHome>/eWAS/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1/server.xml

The same considerations are valid for Tivoli Dymanic Workload Console (TDWC) and the z/OS connector, and not only for TWS.