Oracle E-Business Suite SOA Implementation: Customer Success Story

3. Presentation Agenda SOA Principles Of Oracle E-Business Suite Key Features Of Oracle EBS Adapter Leveraging SOA Suite SLA / KPI Monitoring Demo Forsythe Technology � Success Story PO Automation Demo Customer Benefits Q & A Here is the list of agenda items: First will touch upon SOA principles followed by Oracle E-Business Suite. We will cover Integration Architecture Next I�ll cover Key features of E-Business Suite Adapter with special emphasis on Security. We�ll also go though Function Security Demo. Next We�ll look at how we can leverage SOA Suite in E-Business Suite Service enablement. We�ll discuss order fulfillment case study Finally we�ll cover native SOA enablement and demo for the same followed by Q & AHere is the list of agenda items: First will touch upon SOA principles followed by Oracle E-Business Suite. We will cover Integration Architecture Next I�ll cover Key features of E-Business Suite Adapter with special emphasis on Security. We�ll also go though Function Security Demo. Next We�ll look at how we can leverage SOA Suite in E-Business Suite Service enablement. We�ll discuss order fulfillment case study Finally we�ll cover native SOA enablement and demo for the same followed by Q & A

4. SOA PrinciplesOracle E-Business Suite As you might already be that in a typical SOA interaction scenario where we have 3 roles Provider, Consumer and Broker E-Business Suite also follows the generic SOA Principles. Here as you can see the Service Provider role is played by EBS Adapter and the Service Broker role is played by the Integration Repository. Service Consumer is end user who locates the service from Integration Repository and invokes it by providing necessary input parameters. At the run-time, EBS adapter services the request. As you might already be that in a typical SOA interaction scenario where we have 3 roles Provider, Consumer and Broker E-Business Suite also follows the generic SOA Principles. Here as you can see the Service Provider role is played by EBS Adapter and the Service Broker role is played by the Integration Repository. Service Consumer is end user who locates the service from Integration Repository and invokes it by providing necessary input parameters. At the run-time, EBS adapter services the request.

5. Integration RepositorySource of truth An integral part of Oracle E-Business Suite Catalog of all public integration interfaces Oracle EBS Adapter introspects the public interfaces to expose them as web services An integral part of Oracle E-Business Suite, 11i10 has hosted version and R12 has integrated with EBS Catalog of all public integration interfaces, these are annotated by the product teams and published by oracle for external integration Oracle EBS Adapter introspects the public interfaces to expose them as web services An integral part of Oracle E-Business Suite, 11i10 has hosted version and R12 has integrated with EBS Catalog of all public integration interfaces, these are annotated by the product teams and published by oracle for external integration Oracle EBS Adapter introspects the public interfaces to expose them as web services

6. Oracle E-Business Suite Adapter Schematic Architecture Let�s understand the schematic architecture of EBS adapter. On left of Adapter you can see various interfaces from Oracle E-Business Suite like PL/SQL APIs, Business Events, XML Gateway Transactions, eCommerce Gateway transactions, Open Interface Tables and Concurrent Programs. These interface are the integration points which are published in integration repository as a catalogue to the outside world. On right of adapter we�ve various fusion middleware components like BPEL Process Manager for process orchestration, Enterprise Service Bus to deliver event driven architecture, Business Activity Monitoring for real-time dashboards and Integration B2B for transacting with business partners. In the middle we have EBS adapter which exposes the integration interfaces of Oracle EBS as services, so that they become accessible to FMW SOA components. Let�s understand the schematic architecture of EBS adapter. On left of Adapter you can see various interfaces from Oracle E-Business Suite like PL/SQL APIs, Business Events, XML Gateway Transactions, eCommerce Gateway transactions, Open Interface Tables and Concurrent Programs. These interface are the integration points which are published in integration repository as a catalogue to the outside world. On right of adapter we�ve various fusion middleware components like BPEL Process Manager for process orchestration, Enterprise Service Bus to deliver event driven architecture, Business Activity Monitoring for real-time dashboards and Integration B2B for transacting with business partners. In the middle we have EBS adapter which exposes the integration interfaces of Oracle EBS as services, so that they become accessible to FMW SOA components.

7. Oracle Adapter Framework Oracle EBS Adapter is part of the larger ecosystem of Adapters from Oracle FMW. These adapters are technologically based on the Adapter Framework which in turn is based on Oracle Application Server. The technology, legacy, packaged application interfaces are exposed as services with the adapters from Adapter Framework. These adapters are based on the JCA standards. The consumers of the services on the right hand side are the FMW SOA Suite components like BPEL PM, ESB, BAM or B2B which are serviced via the WSIF. In a typical integration flow in a business scenario will utilize one or more of these adapters. JDev is the single design time IDE for all adapters including EBS Adapter. Oracle EBS Adapter is part of the larger ecosystem of Adapters from Oracle FMW. These adapters are technologically based on the Adapter Framework which in turn is based on Oracle Application Server. The technology, legacy, packaged application interfaces are exposed as services with the adapters from Adapter Framework. These adapters are based on the JCA standards. The consumers of the services on the right hand side are the FMW SOA Suite components like BPEL PM, ESB, BAM or B2B which are serviced via the WSIF. In a typical integration flow in a business scenario will utilize one or more of these adapters. JDev is the single design time IDE for all adapters including EBS Adapter.

8. Service Oriented ArchitectureOracle E-Business Suite Adapter � Life Cycle This is a typical life cycle of EBS adapter. As an end user you develop adapter artifacts using JDeveloper. Behind the scenes it uses adapter framework as integration technology and IREP for bringing content into the Adapter. You choose the EBS integration interface to which you want to integrate with. Now if you require to orchestrate, use BPEL PM and for event-driven architecture use ESB for creating the integration flow. Services artifacts will be deployed in either the BPEL PM or ESB Server based on the design-time component used. Once deployed you are ready to invoke your intended Oracle EBS interface. During invocation, EBS adapter ensures that you�ve required privilege to execute that interface through the implementation of EBS Security model. And finally you can monitor your web services using Enterprise Manager. This is a typical life cycle of EBS adapter. As an end user you develop adapter artifacts using JDeveloper. Behind the scenes it uses adapter framework as integration technology and IREP for bringing content into the Adapter. You choose the EBS integration interface to which you want to integrate with. Now if you require to orchestrate, use BPEL PM and for event-driven architecture use ESB for creating the integration flow. Services artifacts will be deployed in either the BPEL PM or ESB Server based on the design-time component used. Once deployed you are ready to invoke your intended Oracle EBS interface. During invocation, EBS adapter ensures that you�ve required privilege to execute that interface through the implementation of EBS Security model. And finally you can monitor your web services using Enterprise Manager.

9. Oracle E-Business Suite Adapter Key Features Leverages Integration Repository Supports widest range of interfaces Secured and Trusted Connection Functional Security Enabled Application Context Ready Transaction Support Supports Multiple Oracle EBS versions Let�s look at some of the key features of Oracle EBS Adapter Leverages Integration Repository for R12 and 11i10 You can choose your integration point from a large number of interfaces like PL/SQL APIs, Open Interface Tables, Concurrent Programs, XML Messages, ECommerce Transactions etc. The connection between EBS and FMW SOA Suite is secured and trusted EBS adapter implements Functional Security as an authorization mechanism for end users Implicit Application Context initialization which is necessary for invoking some of the interfaces from Oracle E-Business Suite. Using 2 phase commit Transaction is maintained From the same EBS Adapter you can connect to Multiple versions of Oracle EBS And last but not the least it�s Standards Based Now lets cover these features in detail:Let�s look at some of the key features of Oracle EBS Adapter Leverages Integration Repository for R12 and 11i10 You can choose your integration point from a large number of interfaces like PL/SQL APIs, Open Interface Tables, Concurrent Programs, XML Messages, ECommerce Transactions etc. The connection between EBS and FMW SOA Suite is secured and trusted EBS adapter implements Functional Security as an authorization mechanism for end users Implicit Application Context initialization which is necessary for invoking some of the interfaces from Oracle E-Business Suite. Using 2 phase commit Transaction is maintained From the same EBS Adapter you can connect to Multiple versions of Oracle EBS And last but not the least it�s Standards Based Now lets cover these features in detail:

10. Oracle E-Business Suite Adapter Leverages Integration Repository Oracle EBS Adapter is version aware and able to detect version of E-Business Suite instance. For 11.I.10 it uses content meta data file where as in R12 it uses live content from Integration Repository to be displayed in Object Module Browser visible in right hand side of the slide. It show the published E-Business Suite interface points from Integration Repository. In this case we are looking at the Process_Order_Header PL/SQL API. This API is under PL/SQL interfaces which is under Business Entity called Sales Order which is under Order Management which belongs to Order Management Suite. The wizard shows each of the input and output parameters associated with the API. All of the artifacts needed to convert this API into web service are created automatically by the EBS Adapter.Oracle EBS Adapter is version aware and able to detect version of E-Business Suite instance. For 11.I.10 it uses content meta data file where as in R12 it uses live content from Integration Repository to be displayed in Object Module Browser visible in right hand side of the slide. It show the published E-Business Suite interface points from Integration Repository. In this case we are looking at the Process_Order_Header PL/SQL API. This API is under PL/SQL interfaces which is under Business Entity called Sales Order which is under Order Management which belongs to Order Management Suite. The wizard shows each of the input and output parameters associated with the API. All of the artifacts needed to convert this API into web service are created automatically by the EBS Adapter.

11. Oracle E-Business Suite Adapter Widest Range of Integration Interfaces PL/SQL APIs Business Events Open Interface Tables Concurrent Programs XML Messages eCommerce Gateway Messages Interface Views More than 2500+ integration points� EBS Adapter enables widest range of integration interfaces. 1200+ pl/sql APIs are there to choose from, these are primarily used for inline integration Similarly we have 147+ OIT for batch data integration Concurrent Programs (214+) are primarily associated with OITs XML Messages (170+) for B2B messages eCommerce Gateway Interface(24+), for EDI integration transaction Business Events (1400+), for event driven integration EBS Adapter enables widest range of integration interfaces. 1200+ pl/sql APIs are there to choose from, these are primarily used for inline integration Similarly we have 147+ OIT for batch data integration Concurrent Programs (214+) are primarily associated with OITs XML Messages (170+) for B2B messages eCommerce Gateway Interface(24+), for EDI integration transaction Business Events (1400+), for event driven integration

12. Oracle E-Business Suite Adapter Secured and Trusted Connection FND Username / Password works APPS Schema name / Password not required FMW, a trusted client Connection Managed by the EM In order to connect oracle EBS adapter from FMW SOA Suite, only FND user password is required. All you need to do is to register FMW SOA Suite as trusted node. For configuring connection and managing the same EM is used In order to connect oracle EBS adapter from FMW SOA Suite, only FND user password is required. All you need to do is to register FMW SOA Suite as trusted node. For configuring connection and managing the same EM is used

13. Oracle E-Business Suite Adapter Function Security Enabled Function Security is the authorization mechanism used in Oracle E-Business Suite to restricts user access to individual menus and menu options Enforces User Authorization for execution Implemented for EBS R12 as well as EBS 11i10 Profile Option EBS ADAPTER FUNCTION SEC ENABLED By Default it will be set to N To implement Function Security set to Y Available via Metalink Note: 464164.1 Before we look into this feature let�s understand what�s function security: Function Security is the authorization mechanism used in Oracle E-Business Suite. Granularity of The protection provided is at menus and menu options level but not at data level. You can enforce function security for any E-Business Suite protected resource which can be represented as function. Function can be as low level as individual PL/SLQ or java API or it be as high level as whole application. You can control access of UI Components and a collection of functions called Menus. EBS Adapter implements the function security model of EBS. To run the EBS Adapter service the user should have right execution privileges to execute the interface. This functional security feature is available for both 11i10 and R12 versions of oracle EBS. For using function security you need to enable it by setting corresponding profile option to yes and grant execute privileges to user. For more details you can refer to metalink note 464164.1 Before we look into this feature let�s understand what�s function security: Function Security is the authorization mechanism used in Oracle E-Business Suite. Granularity of The protection provided is at menus and menu options level but not at data level. You can enforce function security for any E-Business Suite protected resource which can be represented as function. Function can be as low level as individual PL/SLQ or java API or it be as high level as whole application. You can control access of UI Components and a collection of functions called Menus. EBS Adapter implements the function security model of EBS. To run the EBS Adapter service the user should have right execution privileges to execute the interface. This functional security feature is available for both 11i10 and R12 versions of oracle EBS. For using function security you need to enable it by setting corresponding profile option to yes and grant execute privileges to user. For more details you can refer to metalink note 464164.1

14. Application Context Application Context: Organization ID Username Responsibility NLS

15. Passing the Application Context Retains Application Context across multiple invokes

16. Multi-Org support in R12.0

17. Support for NLS

18. Oracle E-Business Suite AdapterGlobal Transaction EBS Adapter uses the two-phase commit (2pc) protocol to arrive at consensus among multiple participants in a global transaction. This diagram shows a BPEL process where we use EBS adapter to invoke two partner links. In case invocation of first partnerlink goes through fine but second invocation fails then it�ll rollup even first partnerlink execution and there by maintain the transaction. EBS Adapter uses the two-phase commit (2pc) protocol to arrive at consensus among multiple participants in a global transaction. This diagram shows a BPEL process where we use EBS adapter to invoke two partner links. In case invocation of first partnerlink goes through fine but second invocation fails then it�ll rollup even first partnerlink execution and there by maintain the transaction.

19. Connects to multiple EBS InstancesFlexibility in deployment Supports multiple version of Oracle EBS Works seamless across multiple versions in the ecosystem Version aware design-time Live Connection and Cache for IREP in R12 Packaged IREP content for 11.5.10 Direct Application connectivity for pre 11.5.10 No run-time configuration required Supports multiple version of Oracle EBS Works seamless across multiple versions in the ecosystem Version aware design-time Live Connection and Cache for IREP in R12 Packaged IREP content for 11.5.10 Direct Application connectivity for pre 11.5.10 No run-time configuration required

20. Visual and Declarative DevelopmentFaster development to implementation time

21. Let�s learn how do we leverage the SOA Suite using EBS Adapter. And before we jump into the case study to learn about, let me first throw some light on Oracle FMW SOA Suite from a technology stack perspective.Let�s learn how do we leverage the SOA Suite using EBS Adapter. And before we jump into the case study to learn about, let me first throw some light on Oracle FMW SOA Suite from a technology stack perspective.

22. Oracle BPEL PM Process Orchestration Oracle BPEL Process Manager enables enterprises to orchestrate disparate applications and Web services into business processes. The ability to quickly build and deploy these processes in a standards-based manner delivers critical functionality for developing a Service-Oriented Architecture (SOA). Oracle E-Business Suite Adapter enables E-Business Suite to expose its business services as standard web services and participate into the business process orchestration in a heterogeneous IT ecosystem. For example, Consider �Order to Receipt� is one of the most common business processes that any company requires. The PeopleSoft CRM application may be used to capture the order; the JDE EnterpriseOne application may be used to fulfill (pick/ship) the order; and Oracle E-Business Suite may be used to Invoice the customer. Oracle BPEL PM will be the key integration platform to orchestrate the Order to Receipt business process between these three applications and Oracle E-Business Suite is enabled for this process orchestration via the E-Business Suite Adapter Oracle BPEL Process Manager enables enterprises to orchestrate disparate applications and Web services into business processes. The ability to quickly build and deploy these processes in a standards-based manner delivers critical functionality for developing a Service-Oriented Architecture (SOA). Oracle E-Business Suite Adapter enables E-Business Suite to expose its business services as standard web services and participate into the business process orchestration in a heterogeneous IT ecosystem. For example, Consider �Order to Receipt� is one of the most common business processes that any company requires. The PeopleSoft CRM application may be used to capture the order; the JDE EnterpriseOne application may be used to fulfill (pick/ship) the order; and Oracle E-Business Suite may be used to Invoice the customer. Oracle BPEL PM will be the key integration platform to orchestrate the Order to Receipt business process between these three applications and Oracle E-Business Suite is enabled for this process orchestration via the E-Business Suite Adapter

23. Oracle Business Activity MonitoringReal-Time Dashboards Oracle Business Activity Monitoring (Oracle BAM) is a complete solution for building interactive, real-time dashboards and proactive alerts for monitoring business processes and services. Oracle BAM gives business executives and operation managers the information they need to make better business decisions and take corrective action if the business environment changes. Oracle E-Business Suite Adapter enables to implement Oracle BAM solutions. For example, Oracle BAM can monitor the business event raised by Oracle Order Management for triggering Sales Order and this particular business event is propagated outbound from Oracle E-Business via Oracle E-Business Suite AdapterOracle Business Activity Monitoring (Oracle BAM) is a complete solution for building interactive, real-time dashboards and proactive alerts for monitoring business processes and services. Oracle BAM gives business executives and operation managers the information they need to make better business decisions and take corrective action if the business environment changes. Oracle E-Business Suite Adapter enables to implement Oracle BAM solutions. For example, Oracle BAM can monitor the business event raised by Oracle Order Management for triggering Sales Order and this particular business event is propagated outbound from Oracle E-Business via Oracle E-Business Suite Adapter

24. Leveraging Oracle BAMOrder Fulfillment Use Case Sales Order book in Oracle E-Business Suite Business Event Raised (Order Entered) Business Event propagated to Oracle BPEL PM Process BAM Sensors pickup the Business Event Order Number and Order Status � Data Order Number and Order Status process by BAM Server Data viewed on the BAM Monitor Entire Order Fulfillment process tracked for KPIs/SLAs

27. About Forsythe

28. Forsythe Vision

29. Forsythe�s Growth is Through Our Clients� Growth KEY TAKEAWAY: We have evolved through our relationships with our customers and our core expertise. We grew our business because our customers trusted us and asked us to do this. Our growth comes from your growth. ================== Today, we are unique: We are IT infrastructure strategists with core competencies in IT economics and execution Technical depth across the infrastructure, Single point of contact in a complex IT marketplace Our Company Evolved From A Financial/Business Foundation To understand how we help our customers, it�s important to understand where we came from and how we evolved with our customers. The success we generate for our customers is rooted in our history. We started with a financial and mainframe legacy world, where we learned mission critical, highly available, and highly redundant economic disciplines. Our evolution took place based on the mutual trust between us and our customers. They asked us to be a greater part of their technology investments, and now we apply our foundational disciplines to the interdependencies between multiple technologies. The next stage has been to help our customers gain greater strategic alignment out of their technology investment. Our customers are asking us to support them internationally, and we�re making the initial investments for that next step in our evolution. Summary We stay really close to our customers�We have a lot of customers today that have been doing business with us for over twenty years because we continue to evolve with our clients. We are looking forward to providing more, increasingly impactful solutions to our customer base. It�s the culmination of our deep and proven history that allows us to generate results that deliver economic impact and pragmatic execution. Our business model is validated by 38 consecutive years of profitability�including post-2000. It was difficult to find a profitable technology firm post 2000. The reason we were profitable is because many of our customers were contracting, and they needed help reducing their operating expenses and we were there to help them. Our model is focused on the economics and execution of optimizing the IT infrastructure. KEY TAKEAWAY: We have evolved through our relationships with our customers and our core expertise. We grew our business because our customers trusted us and asked us to do this. Our growth comes from your growth. ================== Today, we are unique: We are IT infrastructure strategists with core competencies in IT economics and execution Technical depth across the infrastructure, Single point of contact in a complex IT marketplace Our Company Evolved From A Financial/Business Foundation To understand how we help our customers, it�s important to understand where we came from and how we evolved with our customers. The success we generate for our customers is rooted in our history. We started with a financial and mainframe legacy world, where we learned mission critical, highly available, and highly redundant economic disciplines. Our evolution took place based on the mutual trust between us and our customers. They asked us to be a greater part of their technology investments, and now we apply our foundational disciplines to the interdependencies between multiple technologies. The next stage has been to help our customers gain greater strategic alignment out of their technology investment. Our customers are asking us to support them internationally, and we�re making the initial investments for that next step in our evolution. Summary We stay really close to our customers�We have a lot of customers today that have been doing business with us for over twenty years because we continue to evolve with our clients. We are looking forward to providing more, increasingly impactful solutions to our customer base. It�s the culmination of our deep and proven history that allows us to generate results that deliver economic impact and pragmatic execution. Our business model is validated by 38 consecutive years of profitability�including post-2000. It was difficult to find a profitable technology firm post 2000. The reason we were profitable is because many of our customers were contracting, and they needed help reducing their operating expenses and we were there to help them. Our model is focused on the economics and execution of optimizing the IT infrastructure.

30. Recent Client Engagements $93M storage cost savings for a business unit of one of the largest US banks $22.6M server consolidation savings over three years for a client with global database complexity. $6.5M storage savings annually for a large insurance company. $2.5M annual savings strategy to address 200% year-over-year storage growth, for a financial institution. $1M savings per month for a 10,000 handset IPT deployment at a national risk services and staffing consulting company. $20M savings annually by optimizing and consolidating maintenance contracts at a $50B pharmaceutical company

31. Forsythe Partners

33. Business Problem Back-office Procurement volume increasing dramatically Workloads increasing Total number of data errors increasing Order error tracking remediation more difficult due to increasing volumes Response/turnaround time slow

34. The IT Ecosystem at Forsythe Heterogeneous Environment Mini Solaris, HP-UX OEL, Red Hat Oracle E-Business 11.5.10.2 HR Financials OM, CRM Projects Custom Applications, Third Party Packages Oracle Fusion Middleware BPEL B2B

35. Solution Highlights Connectivity RNIF 2.0 SSL 1024 bit Certificates Transactions RosettaNet Standard 3A4 � Purchase Order 3A4c � PO Acknowledgement 3A6 � Order Status 3B2 � Ship Notice Multiple Web Services Calls

36. Business Process Flow

37. Logical Architecture

38. Let�s now experience various steps involved in function security implementation. In this demo we�ll be calling a PL/SQL API from BPEL. First we will run the process without enabling the Function Security and check out how the process go through. Then we will enable the Function Security and check out the results and exceptions. And Finally we�ll see what need to be done to overcome these exceptions. Let�s now experience various steps involved in function security implementation. In this demo we�ll be calling a PL/SQL API from BPEL. First we will run the process without enabling the Function Security and check out how the process go through. Then we will enable the Function Security and check out the results and exceptions. And Finally we�ll see what need to be done to overcome these exceptions.

39. Purchase Order AutomationDesign View

40. Purchase Order Automation Design View

41. Purchase Order AutomationDesign View

42. Purchase Order Automation Design View

43. Purchase Order Automation Run Time View

44. Purchase Order Automation Run Time View

45. Purchase Order AutomationRun Time View

46. Solution Benefits Create B2B connection to a top vendor to achieve back-office efficiencies Transactions PO Order Status Ship Notice Business Benefits Automated Population of Data Faster Problem Resolution Decreased Time to Create Customer Invoices More Timely Order Status Information Increased Visibility into Business Processes

47. Transaction Volume / Processing Time

48. Lessons Learned Leverage BPEL Adapters Oracle EBS Adapter Database Adapter Direct table access � Selects XML Gateway Use BPEL for linking B2B into the User�s existing process Leverage Workflow Worklists Instead of Emails

49. Customer Benefits Agile and Flexible Integration Architecture Service Enablement of E-Business Suite Low Cost of Ownership Standards based integration Faster development to implementation time Visual and Declarative development of integration solutions High Value Proposition Enables Business Insight by leveraging Oracle BAM

51. Key Take Aways Integration Architectures Secured Integrations Leveraging Oracle BAM Success story � PO Automation with BPEL, B2B, EBS Adapter & XML Gateway

52. Let�s take up any question you might be having.Let�s take up any question you might be having.