Oracle method requires to install APEX application to the SAME EBS database. The OA Framework page of creation Menu Function needs to access the APEX tables in local database to retrieve the APEX App and Page information.
APEX2EBS framework can be used in any APEX-installed database, either a separate database or the same EBS database (not recommanded). Database link is created to connect APEX data and EBS data.
Since ORDS needs JDK11 or higher to run, the Weblogic Server used for EBS app server cannot be used. ORDS can use the embedded Jetty server to run, but it is not production-ready to handle heavy workload. So it's better to use separate stand-alone app server (Tomcat + Apache) to serve the APEX web pages.
Navigation
Oracle method is one-way: users need to log on to EBS side first, then through the responsibility's menu items to access APEX pages.
APEX2EBS framework is two-way: users can log on to APEX and access those APEX pages, and also log on to EBS side to access the same APEX pages. The availability and security of the custom APEX pages is controlled on the APEX side.

For schema usage, all schema (APPS, APEX, custom) are resided in the same database. For the APEX2EBS framework, the APEX workspace (APEX2EBS) connect to EBS custom schema by DB link.

© 2026 by Christopher Ho. All Rights Reserved