• Perform a data volume/frequency analysis to predict likely adapter memory consumption. To establish a baseline, measure the memory consumption of an idle adapter instance.

• Assess the latency in your environment as this is critical when integrating end-systems.

• Minimize the number of unused, idling process engine jobs in BusinessWorks, as they needlessly consume memory.

• Consider the option of tuning the Java Virtual Machine (JVM) using these suggestions:

◦ Apply the latest JVM patches for your operating system

◦ Tune heap and stack size to optimize garbage collection, including selecting an optimal value for the TIBCO BusinessWorks engine’s thread stack size deployment setting.

◦ Adjust operating system kernel parameters to match the characteristics of the application.

◦ Set the -Xms and -Xmx parameters on the JVM, which are operating system independent and control the amount of memory allocated to the JVM at startup (-Xms) and the maximum amount of memory the JVM is allowed to consume (-Xmx). At a minimum, these should both be set to 256 MB. If the application generates java.lang.OutOfMemoryErrors during testing or production runs, then you must increase the -Xmx parameter to larger values.

◦ Investigate other JVM parameters and tuning options. Depending on the JVM and operating system, there may be other tuning options available. The following web sites should be helpful:

▪ http://www.javaperformancetuning.com/tips/rawtips.shtml

▪ http://java.sun.com/docs/hotspot/VMOptions.html

◦ Investigate later versions of the JRE; these may provide better performance. However they are not supported.