Service Oriented Architecture for EBS

3. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

4. Service Enabling E-Business SuiteNishit RaoGroup Product ManagerFusion Middleware@NorCal OAUG Jan 17th 08

5. Service Oriented Architecturefor EBS

6. What is Service Enablement? Service Broker • It’s all about… • Capability to Provide Services • Ability to Consume Services • Abstracted Re-Usable Interfaces • Standard Based Web Services • Documented Services & API Find Register Service Contract Service Consumer Service Provider Client Service

7. Why Service Enablement?Business Drivers • Leveraging the investment of existing Applications • Rapid time to design and deploy new solutions • Interoperability in a heterogeneous ecosystem • Integrated View of business processes • Maximize ROI by re-usability of services • Low TCO for implementation and deployment

8. Service Oriented Architecture Integration Repository Find Register Service Contract Service Consumer E-Business Suite Adapter Client Service

9. Integration RepositorySingle Source of Truth • PL/SQL APIs (2650+) • Open Interface Tables (147+) • Concurrent Programs (214+) • XML Gateway (170+) • eCommerce Gateway (24+) • Interface Views • Java • Web Service

10. Integration Repositoryhttp://irep.oracle.com • Catalog of all Public Interfaces – the single source of truth for Integration • Common User Interface to search and browse E-Business Suite interfaces • Embedded within the core E-Business Suite schema to leverage the standard security system • Preconfigured for exposing & administering Interface Points as Web Services • Automatically kept in step with source code, via standard patching technology

11. Integration Repository Oracle Apps Adapter PL/SQL API, Views, Business Events XML & eCommerce Gateway Open Interface Table & Concurrent Programs B2B ESB Oracle SOA Suite BPEL PM BAM Oracle E-Business Suite AdapterSchematic Architecture

12. Oracle Adapter Architecture Generates WSDL / JCA Service definition Adapter Design-time (JDeveloper) Oracle Adapters (JCA1.5 Resource Adapter) Adapter Framework WSDL/JCA JCA 1.5 Technology ESB Backend Native Interfaces Legacy Application Exposes WSDL/JCA Services Package Application BPEL PM J2EE Application Server (Oracle AS, BEA Weblogic, JBoss, IBM Websphere)

13. Salient FeaturesOracle Applications Adapter • Leverages Integration Repository for 11.5.10 • Expose only recommended public interfaces • Version aware design-time • Packaged IREP content for 11.5.10 • Direct Application connectivity for pre 11.5.10 • Completely standards based product • XA Support • Automatic Application Context Initialization

14. Oracle Apps AdapterStandards Based • Based on J2CA 1.5 standards • Deployed as a resource adapter in the same Oracle AS Server Containers for J2EE (OC4J) • Supports open standards, such as • J2EE Connector Architecture (J2CA) • Extensible Markup Language (XML) • Web Service Invocation Framework (WSIF) • Web Service Inspection Language (WSIL) • Web Service Definition Language (WSDL) • Uses JDeveloper based design-time environment • Generates Adapter metadata as WSDL files with J2CA extension

15. Supported Interfaces • Business Events • Seeded and custom events for outbound • Only custom events for inbound • PL/SQL APIs • Packaged IREP annotated for 11.5.10 (public APIs) • All for pre-11.5.10 • Custom + Ones still not annotated in IREP • XML Gateway Interfaces • Seeded + custom maps • Open Interface Tables & Concurrent Programs • ECommerce Gateway Interfaces

16. Oracle E-Business Suite Adapter Benefits • Exposes E-Business Suite Integration Interfaces as standard Web Services for 1.5.x versions • Supports multiple versions of Oracle Apps in a heterogeneous ecosystem • Supports most-used interface types • Intuitive UI • Simplifies design-time experience • Faster design to deploy time • Declarative development of integration solutions

17. About Integration Interfaces

18. Business Event System • Events as business documents • Component of the Oracle Workflow • Based on Oracle Advanced Queues (Oracle AQ) • Allows Apps modules and external systems to raise events • Facilitates event subscriptions • Subscriptions can be synchronous or asynchronous • Provides hooks into the E-Business Suite for, • Messaging Integration • Workflow Business Processes • Code Extensions • Supports non-invasive changes

19. Business Events System Workflow Engine AQ AQ AQ • Business Events • New Order • Update Order • Cancel Order AQ AQ AQ Business Events (XML) Oracle Applications Business Event System Component Architecture

20. PL / SQL APIs • Public PL/SQL are used for inserting and updating Oracle Applications data • Multiple operations can be performed by the procedures for a Business Service • The PL/SQL APIs are typically used for A2A integration purposes

21. Simple Data Type Design Time WSDL Apps Context Info IREP JPub PL/SQL Wrappers Complex Data Type Shopping Cart Add Apps.Initialize <soap:envelope> <payload> <data> </data> <payload> <soap:envelope> Remove List Run Time PL/SQL APIs Architecture Data

22. Oracle XML Gateway • Typically used to integrate with trading partners using XML Document formats that conform to OAG standards • Messaging platform for transmitting XML documents • Repository-based message designer • Event-Driven message processing using Workflow

23. XML Gateway E-Business Suite API Consume XML Message* In Workflow SalesOrder • XML Messages defined byOAG Message Queues PurchaseOrder Business Event Business Event Create XML Message* Out Workflow XML GatewaySchematic Transactional Diagram

24. Open Interface Tables • Intermediate staging tables when the data is inserted / updated. • The data from these tables is posted into the base tables via the concurrent programs • The Open Interface Tables can be exposed as web service based integration interfaces • The Open Interface Tables are typically used for internal and A2A integration purposes

25. 3rd Party Adapter EAI Solution Validation using the systems application logic SQL*Loader Flat File Oracle Form Database Oracle Database Non Oracle Database Gateway Technology Interface Tables EDI Gateway / XML Gateway Import Program EDI or XML Open Interface TablesSchematic Diagram

26. Design Time Create JOIN (optional) WSDL Apps Context Info IREP Interface Tables Shopping Cart Add Apps.Initialize <soap:envelope> <payload> <data> </data> <payload> <soap:envelope> Remove List Run Time Data Open Interface TablesArchitectural Diagram

27. Concurrent Programs • An Execution file that can be an operating system file or database stored procedure which contains application logic (Example: PL/SQL, Java) • Typical use is to move data from staging tables to base tables • The concurrent program can be exposed as a web services based integration interface • The concurrent program is typically used for internal and A2A integration purposes

28. Design Time WSDL Apps Context Info Concurrent Program IREP Base Tables Interface Tables Concurrent Program Apps.Initialize Run Time Concurrent ProgramsArchitectural Diagram, Example Apps.Initialize

29. Leveraging Fusion Middleware

30. Oracle BPEL PM Process Orchestration Oracle EBusiness Suite Adapter Integration Repository Web Service Interface in Oracle BPEL PM Open Interface Tables, View, PL/SQL APIs XML & eCommerce Gateway Business Events Concurrent Programs Oracle E-Business Suite Integration Interfaces Oracle BPEL PM Apps Adapter

31. Oracle EBusiness Suite Adapter Integration Repository Open Interface Tables, View, PL/SQL APIs XML & eCommerce Gateway Business Events Concurrent Programs Oracle E-Business Suite Integration Interfaces Apps Adapter Oracle ESB Oracle ESB Event Driven Architecture

32. Integration Repository Oracle EBusiness Suite Adapter Open Interface Tables, View, PL/SQL APIs XML & eCommerce Gateway Business Events Concurrent Programs Oracle E-Business Suite Integration Interfaces Oracle BAM Apps Adapter Oracle Business Activity MonitoringReal-Time Dashboards

33. Oracle DB Adapter vis-à-vis Oracle Applications Adapter

34. EBS Adapter Demo

35. Order Visibility Case Study

36. Business Problem • The Business Use Case • Move to automated Quote-to-Order Processing. • Faster rampup of additional B2B partners. • Increased RN PIPs interactions (new message types being added) • Partners are demanding faster turnaround, forcing Company to upgrade I.e. – stop being the bottleneck • What is expected from BPEL/BAM • Event driven integration and orchestration for Order Status, ASN, and Invoice from ERP (EBS) to B2B • Create RosettaNet documents for PO, ASN, and Invoice • Order Processing Dashboard

37. Technical Issues/Requirements • Technical Requirements • Integrate EBS with 3rd Party B2B using JMS. • Order Processing was heavily customized with custom PL-SQL validation. • The Order for EMEA has different validation from Order for APAC. • SLA from trading partners (15m – 1h) turnaround for order processing. • Software versions • EBS for Order Processing. • 3rd Party for B2B. • BPEL for Integration and BAM for Visibility. • Siebel for Order Capture.

38. Order Processing Workflow events generated at Key Transaction Points Logical Architecture Events published to single generic Q BPEL dequeues using correlation ID and enqueue to JMS Generic Queue ASN Invoice Order Status Siebel Captures Order and matches to Quote sends order to EBS

39. BAM Usage • Information available: • Order status • Volume counts • Cycle times • B2B service level • Errors • Search capability: • Date range • Error • Customer • Quote number • PO number • SO number • Last state

40. Q & A