Implementing the Oracle E-Business Suite for established customers sometimes involves interfacing with legacy applications or third party services. Interoperability scenarios can be classified into three levels:
Deployment Wide - these involve cross application services that can be interfaced transparently from the application. Example: integration with a single-signon server.
Application Specific - these involve special interoperability features that the application is directly aware of. Example: integration between Oracle iPayment and credit card processors. These are documented in the respective application implementation manuals.
Function Specific - these involve industry standards for publishing a variety of interfaces used to interoperate with third party applications and services. Such industry standards include Web Services, Enterprise Java Beans, MIME, and so on.
In addition to the above, the Oracle E-Business Suite technology stack is consolidating around the OA Framework technology stack. In the interim, some CRM applications are not migrated from the JTT technology stack. Instead, OA Framework has created interoperability solutions that allow for these technology stacks to coexist and facilitate a smooth user experience upon transition between technology stacks.