BW6.X - BWCE - How to ensure stable TEA response times in a BusinessWorks 6.X environment

This article explains what to do to make the TEA response times stable in a BusinessWorks 6.X environment.

The approach depends from the BusinessWorks version and the underlying Java version.

If you are using MS SQL Server to manage the bwagents database there is also a JDBC driver option that can be used to improve performances.

# BusinessWorks 6.4, 6.5, 6.6 and 6.7 (Java 😎

Configure the bwagent to use G1GC and possibly increase the Max Heap Size

Edit the bwagent.tra file and, to remove the Java CMS garbage collector configuration options and enable the G1GC garbage collector, update the following line :

java.extended.properties=-Xmx1024m -Xms256m -XX:+HeapDumpOnOutOfMemoryError -XX:SurvivorRatio=128 -XX:MaxTenuringThreshold=0 -XX:+UseTLAB -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled

with

java.extended.properties=-Xmx1024m -Xms256m -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC

In a large environment you may also increase the Java Heap Max Size with the following:

java.extended.properties=-Xmx2048m -Xms256m -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC

Configure the TEA to use G1GC and possibly increase the Max Heap Size

Edit the tea.tra file and, to enable the G1GC garbage collector, update the following line :

java.extended.properties=-Xms64m -Xmx512m -XX\:MaxPermSize=64m -XX:-HeapDumpOnOutOfMemoryError %TEA_START_PARAMS%

with

java.extended.properties=-Xms64m –Xmx512m -XX:+UseG1GC -XX:-HeapDumpOnOutOfMemoryError %TEA_START_PARAMS%

In a large environment you may also increase the Java Heap Max Size with the following:

java.extended.properties=-Xms64m -Xmx1024m -XX:+UseG1GC -XX:-HeapDumpOnOutOfMemoryError %TEA_START_PARAMS%

# BusinessWorks 6.8 and 6.9 (Java 11)

G1GC is the default garbage collector in Java 11.

Edit the bwagent.tra file and, to remove the Java CMS garbage collector configuration options, update the following line :

java.extended.properties=-Xmx1024m -Xms256m -XX:+HeapDumpOnOutOfMemoryError — illegal-access=deny — add-opens java.management/sun.management=ALL-UNNAMED — add-exports java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED — add-exports java.base/com.sun.net.ssl.internal.ssl=ALL-UNNAMED — add-exports java.base/com.sun.crypto.provider=ALL-UNNAMED -XX:SurvivorRatio=128 -XX:+UseTLAB -XX:+CMSClassUnloadingEnabled

with

java.extended.properties=-Xmx1024m -Xms256m -XX:+HeapDumpOnOutOfMemoryError — illegal-access=deny — add-opens java.management/sun.management=ALL-UNNAMED — add-exports java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED — add-exports java.base/com.sun.net.ssl.internal.ssl=ALL-UNNAMED — add-exports java.base/com.sun.crypto.provider=ALL-UNNAMED

In a large environment you may also increase the Java Heap Max Size with the following:

java.extended.properties=-Xmx2048m -Xms256m -XX:+HeapDumpOnOutOfMemoryError — illegal-access=deny — add-opens java.management/sun.management=ALL-UNNAMED — add-exports java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED — add-exports java.base/com.sun.net.ssl.internal.ssl=ALL-UNNAMED — add-exports java.base/com.sun.crypto.provider=ALL-UNNAMED

Possibly increase the Max Heap Size of the TEA

In a large environment you may increase the TEA Java Heap Max Size with the following:

Edit the tea.tra file and update the following line:

java.extended.properties=-Xms64m -Xmx512m -XX:-HeapDumpOnOutOfMemoryError — add-opens java.base/java.lang=ALL-UNNAMED %TEA_START_PARAMS%

with

java.extended.properties=-Xms64m -Xmx1024m -XX:-HeapDumpOnOutOfMemoryError — add-opens java.base/java.lang=ALL-UNNAMED %TEA_START_PARAMS%

# Performances improvement when MS SQL Server is used to manage the bwagents database

The property sendStringParametersAsUnicode managed by the Microsoft JDBC driver for MS SQL Server have an impact on bwagents performances when it is disabled.

To implement this solution you have to update the bwagent.ini file on all machines of the target environment:

. Edit the bwagent.ini file

. Update the following line :

bw.agent.technology.dbems.db.connectionURL=jdbc:sqlserver://esbserver1:1433;databaseName=BW681

with

bw.agent.technology.dbems.db.connectionURL=jdbc:sqlserver:// esbserver1:1433;databaseName=BW681;sendStringParametersAsUnicode=false

. Restart the bwagent

Additional elements

In a BusinessWorks 5.X environment you can also configure the TIBCO Administrator server and the Hawk agents to use the G1GC garbage collector (note that in a BW 5.15 environment Java 11 is used so G1GC is enabled by default).