This chapter describes tips for tuning Oracle B2B performance. It contains the following sections:
Oracle B2B (Business to Business) is an e-commerce gateway that enables the secure and reliable exchange of business documents between an enterprise and its trading partners. Oracle B2B supports business-to-business document standards, security, transports, messaging services, and trading partner management. With Oracle B2B used as a binding component within an Oracle SOA Suite composite application, end-to-end business processes can be implemented.
For more information about Oracle SOA Suite, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
The following sections describe basic tuning configurations that you should also consider while tuning:
Tuning the B2B_DATA_STORAGE table attributes can improve performance in some deployments. Review your use case scenarios and then consider the following to improve performance:
If the B2B_DATA_STORAGE table logging attribute is set to NOLOGGING, consider changing it to LOGGING.
When performing DML operations using NOLOGGING option, the unrecoverable System Change Number (SCN) in the control files are recorded and this can lead to "control file contention" under heavy data load.
Consider migrating LOB columns in the B2B_DATA_STORAGE table to SecureFiles
Partition the table B2B_DATA_STORAGE by HASH(ID) with 128 partitions
Partition the PK index by GLobal HASH(ID) with 64 partitions
Changing the value of the Metadata Service (MDS) instance cache size can improve performance. A ratio of 5:1 is recommended for the xmx-to-mdsCache values. For example, if the xmx size is 1024, maintain mdsCache at 200 MB.
These settings can be modified using Oracle Enterprise Manager Fusion Middleware Control. For more information, see "Configuring Oracle B2B" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
Changing the value of b2b.inboundThreadCount and b2b.outboundThreadCount can improve Oracle B2B message processing. The recommended value depends on your system. For a 2 GB computer, for example, a setting of 3 to 5 is recommended. The b2b.inboundThreadSleepTime and b2b.outboundThreadSleepTime properties put a thread to sleep after message processing. A setting between 10 and 1000 (milliseconds) is recommended.
These settings can be modified using Oracle Enterprise Manager Fusion Middleware Control. For more information, see "Configuring Oracle B2B" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
The JMS Out Queue component is the element that enables B2B to receive data from a JMS queue. To maximize performance, consider enabling the Multiple JMSOUTQUEUES and create the corresponding listening channels in B2B.