Oracle EBS with Mule AnyPoint Connector

1. Oracle EBS with Mule AnyPoint Connector The Oracle E-Business Suite 12.2 (EBS 12.2 Connector) AnyPoint Connector allows connections between the integration of the Mule runtime engine (Mule) and Oracle E-Business Suite 12.2 applications. About the Architecture of the Connector To solve different types of integrations, Oracle EBS offers various technologies or products. For business applications, the most commonly used integrations are as follows. ●Integration of data-centric ●Integration using Oracle E-Business Suite Integrated SOA Gateway via Web Services (ISG) The following example illustrates the MuleSoft Oracle EBS connector's integration architecture. Pre-Requirements For this connector to be used, you must: ●Get to know Oracle E-Business Suite, Anypoint Connectors, Anypoint Studio, Mule concepts, Mule flow components, and global elements ●To test your link to your target resource, have Oracle EBS login credentials to see the Connector Release Notes for the software specifications and compatibility details. Details about POM file <dependency> <groupId>com.mulesoft.connectors</groupId> <artifactId>mule-oracle-ebs-122-connector</artifactId> <version>RELEASE</version> <classifier>mule-plugin</classifier> </dependency> RELEASE is converted to the new version by Mule. To define a version, go to Anypoint Exchange's Oracle EBS 12.2 Connector and select Snippets for dependency. Configure the Design Center Input Source Trigger The connector can be used as a trigger, or the HTTP Listener or Scheduler can be used as a trigger. As a signal, use the Connector By using the connector as the trigger, you can create a global feature. ●Then press Build in the Design Middle. ●To open the Flow Designer, press Build a New Program. ●Enter a value for the name of the project, and then press Build. ●To exit from Let's Get Started, press Go Straight to Canvas. ●Tap the card for the ignition. ●Find the connector.

2. ●Please fill out these fields for the connector. HTTP listener as a trigger The types of connections to be given for this configuration. ●Read Timeout for Receive ●Default 30000 by default ●Using the Trigger HTTP Listener ●Tap the card for the ignition. ●HTTP Listener Searching. ●Enter the relative path from the path set in the HTTP Listener set up in the General tab. ●Click Alter. ●Enter the configuration name and base path (where your Mule application listens for requests) for the HTTP listener in HTTP Listener Configuration, then press Add Link. ●Enter the name of the connection and pick the type of connection. ●Specify the values for the HTTP link: in Configure Connection. ●Configuration of HTTP Listener ●The Definition Sector ●To protocol The chosen HTTP or HTTPS protocol for the HTTP endpoint ●The Host IP address where requests are being listened to by your Mule application ●PORT The port address where requests are listened to by your Mule application ●Click Save. Save. ●To add a part, click the plus sign. ●Fifty percent As a part, select the connector. ●Configure the global feature for the connector: configuration: ●Configuration Connector ●The Definition Sector ●The Host ●The host of an instance of Oracle EBS ●PORT ●The Oracle EBS Web Services Port ●Activated SSL ●Calls to Web Services are attempted using HTTPS instead of HTTPS if tested. ●Username ●Name to use for Oracle EBS Web Services login Login Password The username's password Alias Rest Operation Locator Name assigned to oracle.apps.find.rep.ws.service.EbsRestLocator Internal Name Web Service when deployed Alias of the FND Site Sec alias

3. Name assigned when deployed to the PL/SQL Web Service with the internal name FND WEB SEC Name of transparency The name of the Oracle EBS liability that is necessary to conduct the procedure. This area embraces key-responsibility. Application Name for Accountability The short name of the application that is required to execute the operation Name of the security community (Optional) The protection group key of an instance of Oracle EBS (STANDARD by default) Language NLS (Optional) The NLS language of an instance of Oracle EBS (AMERICAN by default) Org. Org. ID ●(Optional) The company ID of an instance of Oracle EBS ●Select an action. ●Connector Working ●About PL/SQL ●Get the WADL configured. ●A surgery ●Get the operation installed. ●To test the link, click Test. ●Add a Studio Project Connector ●Two ways to link the connector to your Studio project are supported by Anypoint Studio: ●From the Exchange button in Taskbar Studio ●From the View of the Mule Palette ●Add the Exchange Use Connector Creating a Mule project in the Studio. In the upper-left corner of the Studio taskbar, press the Swap icon (X). Click Login in Exchange and provide your username and password for the Anypoint platform. Check for "ebs" in Trade. Pick the connector, and then press Project Add. To mount the connector, obey the prompts. In Studio, Install a Connector Creating a Mule project in the Studio. In the Mule Palette view, under Trade, press (X) Scan. Type 'ebs' into the search field in Add Modules to Project. Click the name of this connector under Available Modules.

4. Apply. Press Add. Select Terminate. The Connector To Use Deploy the location of the REST service so that your PL/SQL resources can be subsequently exposed for consumption by the connector. In the See Also section, see the Oracle Developer's Guide Tutorial link. The process for deploying the PL/SQL Modification API as a REST service is illustrated in the following steps. For every PL/SQL, the same guide applies. As a user that has the Integration Administrator function, log in to the Oracle E-Business Suite. From the navigation menu, choose Responsibility for the Integrated SOA Gateway and the Integration Repository connection. Click Search in the Integration Repository tab to access the main Search page. To access more search fields, press Show More Search Options. Type as the search criteria the following main search values: Category: Subtype Interface Quality category: PL/SQL FA ADJUSTMENT PUB Internal name: PL/SQL deploy - Search To perform the lookup, press Go.

5. Deploying PL/SQL - API Change To open the interface details tab, click the REST Service Locator interface name link. Enter the following information under the REST Web Service tab: Deploy PL/SQL - API Configuration Change Important: The alias of the web service deployed MUST be: 1) an internal name. 2) In minuscule shape. You will find the alias information under the label Service Alias. It is a fa adjustment pub in this case. To deploy the service to an Oracle E-Business Suite WebLogic environment, click Deploy. After a successful deployment of the REST service, Deployed appears along with the View WADL connection in the REST Service Status area. To view the deployed service's WADL overview, click the View WADL link. Deploy PL/SQL - Deployed Modification API In Studio to Configure Drag the connector operations to the canvas of Anypoint Studio. Configure the Global Connector Feature. Configuration Connector The Definition Sector The Host The host of an instance of Oracle EBS PORT The Oracle EBS Web Services Port Activated SSL If tested, the connector uses HTTPS instead of HTTPS to make calls to Web services. Username Username for Oracle EBS Web Services login Login Password The username's password Alias Rest Operation Locator Name assigned to the Web Service when deployed under the internal name oracle.apps.find.rep.ws.service.EbsRestLocator Alias of the FND Site Sec alias

6. Name assigned to the PL/SQL Web Service with the FND WEB SEC internal name when deployed Name of transparency The name of the Oracle EBS liability that is necessary to conduct the procedure. This area embraces key-responsibility. Application Name for Accountability The short name of the application that is required to execute the operation Name of the security community (Optional) The protection group key of an instance of Oracle EBS (STANDARD by default) Language NLS (Optional) The NLS language of an instance of Oracle EBS (AMERICAN by default) Org. Org. ID (Optional) Company ID of an instance of Oracle EBS Requests and Answers Log Configure a logger to log requests and answers while using the connector by adding this line to the Loggers element of the log4j2.xml configuration file for the Mule app:: The following example shows an aspect of Loggers with the added AsyncLogger line: The application log can be interpreted in the following ways: The performance is visible in the Anypoint Studio console window if you are running the software from the Anypoint Platform. If you are using Mule to run the program from the command line: In your OS console, the App Log is available. If the log file path in the app log file (log4j2.xml) has not been customized, you can also access the app log file at this default location: MULE HOME/logs/.logs/.log See Configuring Logging for more detail about the App Log. Use Case: Build an EBS 12.2 Global Element for Oracle To build a global Oracle EBS 12.2 element for Web Services and PL/SQL invocation, follow the steps below: Example Flow In Studio, create a new Mule Project and pick an HTTP Listener in the new flow as the source. Add the latest global element configuration of the HTTP Listener. Specify parameters for Host and Port with the following values:

7. Value parameter The Host 0.0.0.0 0.0.0 PORT 8081 8081 Click Save. Save. Assign your HTTP Listener to the latest global setup. Specify the HTTP Listener path as the value for /start. Drag an element of the Transform Message and add the following code to it: Percentage dw 2.0 Application/xml output Ns ns0 http:/xmlns.oracle.com/apps/per/rest/hr location api/create location/api/create location/apps/per/rest/hr location { Ns0#InputParameters: { InputParameters VALIDATE ns0#P: 0,0,, Ns0#P EFFECTIVE DATE: now, now, now, now ns0#P DESCRIPTION: "Description Office" } } Conclusion I hope you reach a conclusion about Oracle EBS connector with Mule Anypoint. You can use it in the integration of other applications and learn more through MuleSoft online training.