Download to read offline
Uploaded byPavan B
Service everywhere using oracle integration repository
The document outlines the architecture and capabilities of Oracle's integration repository and SOA gateway, emphasizing their roles in facilitating application-to-application and business-to-business integrations. It provides insights into service enablement processes, reengineering traditional integrations into a service-oriented architecture, and integration with Oracle SOA, Informatica, and ODI. Future trends in integration are discussed, highlighting the shift towards more flexible cloud and hybrid integration strategies.
More Related Content
Similar to Service everywhere using oracle integration repository
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Service everywhere using oracle integration repository
- 1. Session ID: Prepared by: ServiceEverywhere, Using Oracle Integration Repository 10276 Venkata Pavan Boyapati Wendys
- 2. Pavan Boyapati • ProfessionalSummary : – 9 years of experience in Oracle Applications – Financials & Supply Chain modules – Complex Integrations – Emerging technologies within Enterprise applications – Currently working at Wendys as a Oracle Senior Developer • Previous Experience: – Hitachi Consulting – Dell – Oracle Consulting – Worthington Industries 2
- 3. Agenda • Architecture ofOracle E-Business Suite Integrated SOA Gateway. • Steps to enable service end points in Oracle Integration Repository. • Reengineer Traditional and Custom PLSQL / Datafile integrations. • Integrate Services with Oracle SOA, Informatica & ODI • Future of Integrations and role of Service Based Approach. 3
- 4. 4 Oracle Integration Repositoryand SOA Gateway • Oracle Integration repository and Oracle SOA Gateway are Out Of Box from Oracle E-business Suite package with numerous service end points and can be leveraged for both application-to-application (A2A) and business-to- business (B2B) interfaces. • Oracle SOA Gateway is used to Invoke and Receive Web Services with in Oracle E-Business Suite.
- 5. 5 Oracle Integration Repositoryand SOA Gateway • Integration Repository is the source of truth for E-Business suite interfaces and also a console for service enablement. • Oracle E-Business suite connects to multiple applications and tools for data sharing and processing.
- 6. Architecture of OracleIntegrated SOA Gateway • Oracle Integrated SOA Gateway is a complete set of service infrastructure in Oracle EBS supporting all interface types including both standard and custom. • Following are the key components of SOA Gateway – Oracle Integration Repository and Service Enablement – Service Invocation Framework – SOA Monitor – Manage Security 6 Oracle Integrated SOA Gateway SOA Monitor Manage Security Service Invocation Framework Service Enablement
- 7. Oracle Integration Repository: • Oracle Integration Repository is a centralized location/Catalog with all interface endpoints exposed by applications in EBS. • To access within Oracle EBS, select “Integrate SOA gateway” responsibility and click “Integration Repository” • The Integration Repository allows us to discover and search on business interfaces from the catalog by – Product Family – Interface Type – Standard 7 Architecture of Oracle Integrated SOA Gateway
- 8. 8 Architecture of OracleIntegrated SOA Gateway
- 9. Oracle Integration Repositorysupports the following interface types: – PL/SQL – XML Gateway – Concurrent Programs – Business Events – Open Interface Tables/Views – EDI – Business Service Object (Service Beans) – Java APIs for Forms – Composite Services 9 Architecture of Oracle Integrated SOA Gateway
- 10. Integration Repository hassecurity rules to allow only authorized users to perform activities. Following are the roles available to assign based on user duties. – System Integration Analyst – System Integration Developer – Integration Repository Administrator 10 Architecture of Oracle Integrated SOA Gateway
- 11. Privileges System Integration Analyst System Integration Developer Integration Repository Administrator View PublicInterfaces Yes Yes Yes View Private/Internal Interfaces No Yes Yes Generate/Regenerate Web Services (WSDL) No No Yes Deploy/Re-deploy Web Services No No Yes Un-deploy Web Services No No Yes Subscribe to Business Events No No Yes Create Grants No No Yes Download Composite Service No Yes Yes 11 Architecture of Oracle Integrated SOA Gateway
- 12. Enable Service EndPoints within Integration Repository • Service Enablement allows us to transform packaged integration interface definitions into web services. • Following are the steps to perform. 12 Deploy Generate WSDL I rep – Access Interface Definition Architecture of Oracle Integrated SOA Gateway
- 13. • Open InterfaceDefinition 13 Architecture of Oracle Integrated SOA Gateway
- 14. • Generate WSDL 14 Architectureof Oracle Integrated SOA Gateway
- 15. • Deploy WSDL 15 Architectureof Oracle Integrated SOA Gateway
- 16. • Open WSDL 16 Architectureof Oracle Integrated SOA Gateway
- 17. 17 Architecture of OracleIntegrated SOA Gateway
- 18. 18 Architecture of OracleIntegrated SOA Gateway • ‘Regenerate’ and ‘Redeploy’ are required if interface definitions are changed.
- 19. 19 Architecture of OracleIntegrated SOA Gateway Service Invocation Framework • Oracle SOA gateway leverages Service Invocation Framework (SIF) to invoke integration services from Oracle EBS. • SIF contains Oracle Workflow Java Business Event System (JBES) and seeded Java rule function to provide infrastructure for web service Invocation. • SIF uses SSL-based Web service Invocation over HTTPS protocol. • SIF provides ability to test business event for service invocation.
- 20. 20 Architecture of OracleIntegrated SOA Gateway • Oracle Integrated SOA Gateway relies on Business Event System and Event Subscription to parse a given WSDL. • Seeded Java Rule function to Invoke Web service oracle.apps.fnd.wf.bes.WebServiceInvokerSubscription • Uses standard Business event error feature in case of exceptions.
- 21. 21 Architecture of OracleIntegrated SOA Gateway • SOA Monitor – Monitor Soap Requests and Responses – View error description of failed Request/Response – Purge web service monitoring log
- 22. 22 Architecture of OracleIntegrated SOA Gateway • Manage Security – Security is designed to guard service content from unauthorized access. – Enforces security at different levels • Specific User • Group of users • All Users
- 23. Reengineer Traditional /Custom Integrations 23 • Examine existing integrations with Oracle E-Business Suite • Ability of tools on using services to communicate • Identify reusable components Plsql Objects Packages Functions Procedures ETL or Custom Apps Staging tables/ File outputs ORACLE EBS Party Party Party Validations and Inserts Data Read / Write Send/ReceiveSend/Receive SQL
- 24. 24 • Architect Integrationsbased on service oriented approach • Develop and enable services for custom business logic • Enable Service end points for reusable processes Reengineer Traditional / Custom Integrations ORACLE EBS Send/Receive Send/Receive Party Party Party Custom Standard Oracle I Repository PL/SQL XML Gateway Concurrent Programs Business Events Open Interface Tables/Views EDI Business Service Object Java APIs for Forms
- 25. 25 Reengineer Traditional /Custom Integrations Steps to enable Custom PL/SQL code as a service end point using SOA gateway: • Create annotations in the PL/SQL Package Spec • Generate and Upload iLDT • Generate and Deploy in Integration Repository Annotations in PLSQL : • Oracle Integration Repository will recognize integration information through annotations in the code. • For PL/SQL packages, only package spec should be annotated.
- 26. • Example: Create orReplace <Package_Name> as /* $Header: $ */ /*# * @rep:scope public * @rep:product <Object Name> * @rep:lifecycle active * @rep:displayname <Name of the package> * @rep:compatibility S * @rep:category BUSINESS_ENTITY <Object> */ PROCEDURE <Procedure_Name>( p_input IN VARCHAR2, p_output OUT VARCHAR2, ) /*# * @param p_input <description of input> * @param p_output Return <output details> * @rep:displayname <procedure_name> */; END <Procedure_Name>; / Show Errors Exit 26 Reengineer Traditional / Custom Integrations
- 27. Generate iLDT – OncePackage spec is Annotated, Move the file to Unix server and run irep_parser.pl to generate iLDT. $IAS_ORACLE_HOME/perl/bin/perl $FND_TOP/bin/irep_parser.pl -g -v - username=<admin username> <Object name>:patch/115/sql:<Package Name>.pls:12.0=<pls file location>/<Package Name.pls> Upload iLDT – Once iLDT is generated upload using FNDLOAD $FND_TOP/bin/FNDLOAD <UNAME>/<PWD> 0 Y UPLOAD $FND_TOP/patch/115/import/wfirep.lct <pls file name>.ildt 27 Reengineer Traditional / Custom Integrations
- 28. Generate WSDL andDeploy – Once iLDT is uploaded we can generate and deploy from oracle Integration Repository or we can as well use the commands. $FND_TOP/bin/soagenerate.sh irepname=<internalname/packagename> $FND_TOP/bin/soadeploy.sh irepname=<internalname/packagename> – Verify Log in ServiceDeploy.log to check the status / any issues. 28 Reengineer Traditional / Custom Integrations
- 29. • Steps inEnabling Custom Integration and Interfaces 29 Validate Annotated Files Annotate Custom APIs View Custom Interface Details Generate Webservice Create Security Deploy Websevice Integration Repository 1 43 2 6 5 Publish Web serviceOracle Integrated SOA Gateway Upload iLDT Reengineer Traditional / Custom Integrations
- 30. Integrate Services withOracle SOA, Informatica & ODI Integration with Oracle SOA suite • Soa suite combined with Oracle Integrated Soa gateway gives us a greater flexibility and better control of web services than any other. • There are multiple ways to connect to Oracle EBS – – Using EBS Adapter – Using Db Adapter – Using AQ Adapter – Using File Adapter – Subscribe to EBS service 30
- 31. Cont. • Oracle EBSadapter gives us a strong connectivity with all applications in Oracle E-business Suite. 31 ORACLE EBS OracleIntegration Repository PL/SQL APIs, Views, Business Events XML & Ecommerce Gateway Concurrent Programs and Open Interface Tables BPEL PM BAM ESB B2B EBSAdapter Integrate Services with Oracle SOA, Informatica & ODI
- 32. Integration with ODIand Informatica • ODI and Informatica has a strong common platform, that is they both are primarily a strong relational database integration tools handling huge volumes of data. • ODI and Informatica both have the capability of invoking and receiving web services and can easily integrate with service based architecture. • However Oracle SOA suite and Oracle Data Integrator hand shake each other very well than with Informatica. 32 Integrate Services with Oracle SOA, Informatica & ODI
- 33. 33 Integration with ODI OracleData Integrator Provides below entry points for Web services : • Data Services • Oracle Data Integrator Runtime Services • Invoking Third Party Web services (OdiinvokeWebService Tool) Integrate Services with Oracle SOA, Informatica & ODI
- 34. Integration with Informatica •Informatica has capability to extract data from web service sources and write data to web service targets. • Webservices provider is the entity of powercenter framework that allows workflows and data integration functionality accessible through web services. – Web Services Hub – Batch Web Services – Real Time Web Services 34 Integrate Services with Oracle SOA, Informatica & ODI
- 35. Informatica Web servicesProvider Architecture 35 WebService Client Web Services Hub Realtime WS Batch WS Integration Service Web Service Workflow Workflow Repository Service SecurityGateway Integrate Services with Oracle SOA, Informatica & ODI
- 36. Future of Integrationsand Service Based Approach 36 • New Products and Acquisitions - Dramatic growth of Integration Requirements • Retire or Modernize Legacy Applications • Cloud and On-Premise Integration Hybrid Integration Architecture Cloud Applications On Premise Applications Mobile Clients Devices and Sensors Business process Outsourcing
- 37. 37 ON-Premises Integration API Management B2B, MFT Mobile IntegrationIntegration CloudService SOA Cloud Service SAAS,APPS Adapters Stream Explorer Future of Integrations and Service Based Approach • One Application cannot do everything • On Premise – leverage existing investment, Security, Compliance • Cloud - Future Investments for growing business
- 38. 38 Future of Integrationsand Service Based Approach Integration Cloud Service Soa/Suite Cloud Service Designed for LOB/Apps IT Designed for IT Oracle Cloud On Premise Or Oracle Cloud Common Architecture, Standards, Integration Components, Application Adapters, API Management. • Ease Of Use – Web based drag and drop Integration application • Pre- Built Integrations • Comprehensive – Full Suite of Developer tools • Flexible Deployment – Same Offering available on-Premise or in Cloud
- 39. Service Everywhere, UsingOracle Integration Repository
Editor's Notes
- #6 Integrations of Oracle EBS with other applications are often made complicated with custom code or by using third party tools for data communication. Existing Integrations can be made service oriented by exposing PL/SQL, XML Gateway, Concurrent Program and so on as Web Services.
- #9 Above are the different views of Oracle Integration Repository. The Product Family view is organized as follows: Product Family -> Product -> Business Entity. For example, Financials -> Payables -> Payables Invoice. The Interface Type view is organized as follows: Interface Type -> Product Family -> Product. For example, Web Service -> Financials -> Cash Management. The Standard view is organized as follows: Standard and Version -> Product Family -> Product. For example, OAG7.2 -> Financials -> Payables -> Process Invoice.
- #10 Above are all the types that are registered with Oracle Integration Repository.
- #11 Above roles are assigned from ‘User Management’ responsibility. ‘Integration Repository Administrator’ has the highest level of access in Integration Repository.
- #12 Above is the table listing the level of access for each role in Integration Repository.
- #19 After service generation, if the interface definition has been changed then we need to regenerate and deploy the service to see the changes. However, if interface definition is not changed, then regenerating the service will not change the service definition.
- #20 SIF was based on the Web Services Invocation Framework (WSIF) provided in Oracle Application Server 10g In WebLogic server (R12.2 release) SIF leverages JAX-WS (Java API for XML-based Web Services) Dispatch from Oracle JRF.
- #21 Service Invocation from PL/SQL Using PL/SQL, Busines Event is raised using API WF_EVENT.Raise. Oracle Workflow Business Event System (BES) identifies that the event has a subscription with Java Rule Function oracle.apps.fnd.wf.bes.WebServiceInvokerSubscription. The Business Event System enqueues the event message to WF_JAVA_DEFERRED queue. The Java Deferred Agent Listener then dequeues and executes the subscription whose Java rule function invokes the Web service. Service Invocation from Java Using Java business event is raised by calling Java method oracle.apps.fnd.wf.bes.BusinessEvent.raise either from OA Framework page or Java code running on the Concurrent Manager. If message requires transformation, then Java rule function performs XSL transformation on message by using a PL/SQL API ECX_STANDARD.perform_xslt_transformation.
- #22 Users with the Integration Repository Administrator role can only see ‘Administration’ link from the Navigator menu. This Administration link contains • SOA Monitor: SOA Monitor is where administrators can monitor and audit all SOAP messages in and out of Oracle EBS. • Log: Log allows administrators to access the centralized Log information.
- #23 Only users with the Integration Repository Administrator role can create and revoke security grants. Security can be enabled uniquely for each function contained in an interface.
- #24 Most of integration tools or third party applications connected to Oracle EBS, should have a capability of communicating using web services. By examining the existing code and architecture will help us leverage Oracle SOA gateway for service based approach and reusability.
- #26 Depending upon the business requirement, Integration developers will annotate the interface based on the standards and validate before making them available in I-repository.
- #31 SOA Suite combined with Integrated SOA gateway will open up lot of functionality that comes with products in SOA Suite. Oracle BPEL process Manager Oracle Service Bus Oracle Event Processing Oracle Business Activity Monitoring Oracle Enterprise Service Bus It will help us to manage and orchestrate services into composite applications and complex business processes, Improving efficiency and agility. Connection to EBS : There are multiple ways to connect to Oracle EBS from Oracle SOA, It depends up on the type of interface and existing business logic. If organization has license to use ‘Oracle E-Business Suite Adapter’ then in most cases that will be the best way to connect to Oracle EBS.
- #32 Oracle EBS Adapter is a standard JCA service comes with SOA suite in middle tier. It is provided via Oracle BPEL process or Oracle Service Bus. All the integrated transactions with Oracle EBS Adapter can be monitored via BPEL PM and OSB consoles. It supports connectivity with PLSQL APIs, XML gateway, Concurrent Programs, Open Interfaces and Views from all application modules in EBS. Integrated SOA gateway is out of box from EBS and it can generate SOAP Webservice by enabling it in Integration Repository and invoke using SIF. These services are monitored in SOA monitor. However it has some limitations with respect to complex integrations.
- #33 Oracle SOA offers lot of flexibility and works very well with application and component integrations, however when there is a demand for integration for large volumes of data and processing it, in those cases Oracle Data Integrator and Informatica does a better job then Oracle SOA. In some cases we need a hybrid approach i.e. a combination of ODI/Informatica with Oracle SOA for effective Data Driven integrations with high performance and increased productivity.
- #34 Data Services : Data Services provides access to data in source and target data stores along with changes captured in them. These web services are automatically generated by ODI and deployed in application server. ODI Runtime services : ODI runtime services are web services invoked by third party applications to start scenarios in Oracle Data Integrator to perform business logic. Invoking Third Party Web services (OdiinvokeWebService Tool) : OdiinvokeWebService Tool is used to invoke web services and capture responses, which can be xml or a full formed SOAP message. OdiinvokeWebService Tool provides an advanced editor for generating its code to connect to a WSDL, Specify parameters, Specify Operation…etc
- #35 Web Services Hub: Web Services Hub needs to be created from Informatica Administrator console like other services. It is an application service in PowerCenter Domain that is used to Receive Request and Send Responses to Web service Clients. It interacts with the Integration service and the Repository service to process requests and generate responses. A Web Services Hub contains a list of all Powercenter web services. Batch Web Services: Batch Web Services is a set of web service operations that allow access to the Integration Service processes and repository metadata. It contains Data Integration Web Service(DIWS) and Metadata Web Services (MWS). DIWS provides operations with respect to integration services like schedule/run/stop/start workflows/tasks. MWS provides the set of operations for repository objects such as folders/workflows/tasks, task source table, task target tables, etc. Real Time Web Services: Real Time Web Services are the workflows enabled as a web service and that can be invoked from other applications. Real Time Web Services are managed through the web service hub console.
- #36 Above is the architecture diagram of connection points in Informatica Web Service Provider.
- #37 Applications are moving to cloud rapidly, it is clear that web services will be the future of integrations. With Organizations acquiring new companies, new products and modernizing legacy applications , there is a dramatic growth for integration requirements in IT teams.
- #38 Companies adapting cloud based products for new functionalities and new implementations. However with existing technologies and investments “OnPremise”, Integrations are more Hybrid in nature.
- #39 ‘Oracle Integration Cloud Service’ and ‘Oracle SOA Cloud service’ are the integration related cloud products from oracle and above is the comparison and commonality between the products.