By Rekha Ayothi-Oracle on Apr 24, 2015
Oracle XML Gateway allows you to generate, consume and transport business transaction documents via XML messages from Oracle E-Business Suite (EBS). It uses Oracle Workflow, Business Event System, Oracle Advanced Queuing, and other database components.
Leaving aside the network latency, the performance of XML Gateway’s inbound and outbound message processing depends on sizing and resource allocation of various components on the EBS application and database tiers.
In Oracle E-Business Suite Release 12.2, we enhanced XML Gateway’s core execution engine for inbound message processing. Now, inbound transactions are mainly processed on the application tier. Outbound transactions are processed on the database tier.
Our Applications Performance team executed performance tests on XML Gateway R12.2. The test cases involved payloads of varying sizes and concurrent messages. Based on our tests, we have published new performance tuning recommendations for Oracle XML Gateway. It includes sizing of Oracle Workflow listeners, updates of XML Gateway properties, and tuning of memory and cache settings of OAFM Managed Servers:
Oracle XML Gateway Sizing and Performance Guidelines (Note 1988982.1)
- Oracle XML Gateway User’s Guide
- Oracle Workflow Administrator’s Guide
- Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Note 1905593.1)
- Getting Optimal Performance from Oracle E-Business Suite
- OAUG/Collaborate Recap: Best Practices for E-Business Suite Performance Tuning
- New Whitepaper: Primer on Integrating with EBS 12 with Other Applications