For B2B Suite Projects that process large messages and transactions, or large amounts of transactions, you can configure the Project in the following ways to increase throughput and improve performance:
To avoid memory errors on the Logical Host, increase the heap size for the Logical Host to at least 1024 MB as described below.
In the Environment Explorer tab in Enterprise Designer, right-click the Logical Host, and click Properties.
The Properties dialog box appears.
See Figure 8–1.
In the Heap Size box, enter the new heap size.
Click OK.
The eInsight engine has three properties that affect performance:
Max Concurrent Instances
Max Runtime Thread Pool Size
The Max Concurrent Instances property indicates the amount of inbound messages that each BP processes simultaneously. For example, if you set this property to 10, the BP processes up to ten inbound messages at the same time. When the eleventh message is received, the BP does not process the message until the processing of one of the ten messages has been completed.
The Max Runtime Thread Pool Size property defines how many threads BPs can invoke simultaneously.
These settings are a trade-off between performance and memory. Depending on how much memory your system has, you can specify these settings accordingly. Unfortunately it is impossible to recommend actual settings here because the memory capacity of your system is unknown. If you find your Project processes too slowly, or messages are lost, increase these settings as your system allows.
For instructions on configuring runtime properties of the eInsight engine, and more information about these properties, see the eInsight Business Process Manager User's Guide.
In the Environment Explorer tab of the Enterprise Designer, expand the Logical Host folder, right-click the Integration Server, and click Properties.
The Properties dialog box appears.
In the Properties dialog, expand the Configuration⇒eInsight Engine Configuration folders.
Increase the settings for the Max Concurrent Instances and Max Runtime Thread Pool Size properties.
Click OK.
If a Project that uses the SeeBeyond JMS IQ Manager needs to process messages or transactions over 8 MB (Windows) or 16 MB (UNIX), increase the Segment size property of the JMS IQ Manager as described in the eGate Integrator JMS Reference Guide.
To increase throughput performance, increase the Oracle number of processes to handle simultaneous database process requests, such as 500. For information, refer to your Oracle documentation.