This appendix contains sizing and performance tuning recommendations for Oracle XML Gateway. Performance sizing and performance recommendations are provided for Oracle Workflow listeners of Oracle E-Business Suite and the oafm managed server (memory parameters and java cache settings).
This appendix includes the following topics:
Recommendations for Inbound Messages and Transactions
Recommendations for Outbound Messages and Transactions
Please note that all the recommendations mentioned here are based on Performance Testing in internal lab environments. The actual numbers may have to be considered based on load in production instances.
Recommendations for Improving the Performance
When multiple inbound transactions are submitted concurrently, you may see high elapsed time for a transaction. You can fine tune parameters controlling Oracle Workflow listeners to improve the performance of inbound transaction in such scenario.
The following recommendations are applicable when the approximate number of concurrent transactions is more than 1,000 with a payload size of 20KB or more. These changes increase CPU consumption on the server.
Increase the value of the parameter “Inbound Thread Count” from 1 to 5 for the following listeners:
ECX Inbound Agent Listener
ECX Transaction Agent Listener
Workflow Java Deferred Agent Listener
To do this, perform the following steps:
Log in to Oracle Applications Manager as a user who has the System Administrator responsibility.
Navigate to OAM Setup from the navigation menu and select the Site Map link.
Select the Service Components link under Workflow.
Select the corresponding listener and click the Edit button.
Click the Next button.
Update the parameter value and click the Finish button.
Restart the Agent Listener.
Decrease the value of the parameter “Processor Min Loop Sleep” from 120 seconds to 5 seconds for the following listeners:
Note: Ensure the parameter “Processor Min Loop Sleep” is set to the default value (5 seconds) for the Workflow Java Deferred Agent Listener.
ECX Inbound Agent Listener
ECX Transaction Agent Listener
To do this, perform the following steps:
Log in to Oracle Applications Manager as a user who has the System Administrator responsibility.
Navigate to OAM Setup from the navigation menu and select the Site Map link.
Select the Service Components link under Workflow.
Select the corresponding listener and click the Edit button.
Click the Next button.
Update the parameter value and click the Finish button.
Restart the Agent Listener.
Refer to the Oracle Workflow Administrator's Guide for more information.
When multiple inbound transactions are submitted concurrently, an out of memory exception may occur at two different levels during the processing of inbound transactions. Initially an out of memory exception may occur at the oafm managed server level even if it has significant amount of default JVM size, such as 1 GB, which is sufficient to handle a payload size of up to 50MB. Consequently, an out of memory exception may occur at the Workflow Java Deferred Agent Listener level when the agent listener is contained within the Generic Service Component Container, which has sufficient default JVM size, such as 384MB, to handle a payload size of up to 50MB.
These recommendations are applicable when an out of memory exception is encountered with a payload size more than 50MB.
Note: The default JVM size of the oafm managed server may cause an out of memory exception for payloads larger than 50MB.
Recommendations
The following table shows the maximum JVM size required for the oafm managed server and Workflow Java Deferred Agent Listener for a particular size of payload with a single transaction to avoid an out of memory exception. The Workflow Java Deferred Agent Listener is contained within the Generic Service Component Container; therefore, we must increase its JVM size to increase the listener's JVM size.
| Payload Size | OAFM Server JVM Size | Generic Service Component Container JVM Size | Default or Recommended Values? |
|---|---|---|---|
| Up to 50MB | "-Xmx1024" | "-Xmx384m" | default |
| 51MB-150MB | "-Xmx2048m" | "-Xmx1536m" | recommended |
| 200MB | "-Xmx3072m" | "-Xmx2048m" | recommended |
Perform the following steps to change JVM sizes:
For the oafm manager server:
Log in to the WebLogic Server Administration Console.
Click Servers and then <oafm-server-name>.
Click the "Server Start" tab.
Click the Lock & Edit button on the left top corner.
Change the JVM size in the "Arguments:" text box, from "-Xms512m -Xmx512m" to "-XmsNm -XmxNm".
Please note that "N" determines the size to be, for example, 2048, 3072, and so on.
Click the Save button.
Click Release Configuration.
Restart the oafm managed server.
For the Generic Service Component Container:
Log in to Oracle Applications Manager as a user who has the System Administrator responsibility.
Navigate to Overview and then AutoConfig.
Click Edit Parameters under Applications.
Select the Environments tab.
Expand "oa_environment:adovars".
Change the value of parameter "AFJSMARG" and set the required size after “-server” option, for example, to set size to 3584m:
-server -Xmx3584m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc
Similar to inbound transactions, when multiple outbound transactions are submitted concurrently, the elapsed time of transactions escalates with an increase in number of transactions. To improve the performance of outbound transactions, fine tune the outbound parameter settings and the parameters controlling Oracle Workflow listeners.
Recommendations
The following recommendations are applicable when the approximate number of concurrent transactions is more than 1,000 with a payload size 100KB or more. These changes increase CPU consumption on the server.
Decrease the "OXTAOutDequeueRate" parameter time from 12000 msecs (2 minutes) to 1000 msecs (1 second)
For instructions on how to change this value, refer to My Oracle Support Knowledge Document 829449.1, Preserve System Properties Customized For Your ECX (XML Gateway).
Increase the "OXTAOutThreads" parameter value from 1 to 2
For instructions on how to change this value, refer to My Oracle Support Knowledge Document 829449.1, Preserve System Properties Customized For Your ECX (XML Gateway).
Decrease the value of parameter “Processor Min Loop Sleep” for Workflow Deferred Agent Listener from 120 seconds to 2 seconds
To do this, perform the following steps:
Log in to Oracle Applications Manager as a user who has the System Administrator responsibility.
Navigate to OAM Setup from the navigation menu and select the Site Map link.
Select the Service Components link under Workflow.
Select the corresponding listener and click the Edit button.
Click the Next button.
Update the parameter value and click the Finish button.
Restart the Agent Listener.
Increase the value of parameter “Inbound Thread Count” for the Workflow Deferred Agent Listener from 1 to 5 for a map size up to 100KB and from 1 to 8 for a map size greater than 100KB.
To do this, perform the following steps:
Log in to Oracle Applications Manager as a user who has the System Administrator responsibility.
Navigate to OAM Setup from the navigation menu and select the Site Map link.
Select the Service Components link under Workflow.
Select the corresponding listener and click the Edit button.
Click the Next button.
Update the parameter value and click the Finish button.
Restart the Agent Listener.
If the destination server is Oracle E-Business Suite, then it should have the optimal settings mentioned in the previous section for inbound transactions.