Table of Contents

Title and Copyright Information

About AuraPlayer Rapid Adapter

Introduction

Restrictions

Supported versions

Capabilities

Common Use Cases

Install the AuraPlayer adapter in your OIC instance

Create an AuraPlayer Connection

Create a REST connection

Create an OIC Integration Flow

Invoke the Integration Flow

Troubleshooting your AuraPlayer Adapter

 

 

AuraPlayer Oracle Integration Cloud Adapter

Using the AuraPlayer Oracle EBS / Forms Adapter with Oracle Integration 3

Feb. 2024

Documentation that describes how to configure and add the AuraPlayer Oracle EBS / Forms Adapter to an integration in Oracle Integration.

About AuraPlayer Rapid Adapter

Introduction

The AuraPlayer adapter is a rapid adapter available as part of Oracle Integration Cloud, enabling on-premises EBS and Forms systems to plug into OIC for automation and integration purposes. To utilize the AuraPlayer adapter, you must already be utilizing OIC and have the necessary configurations for adapters.

 

AuraPlayer is a specialized software platform for mobilizing, automating, and integrating on-premises EBS/Forms applications. In order to use this adapter, you must have a valid installation and license of AuraPlayer’s server (“ServiceManager”) at your organization. The ServiceManager will be used to create your custom APIs to your EBS/Forms. These created APIs can later be invoked using the AuraPlayer adapter and used within OIC for automation and integration.

 

Restrictions

Users must have a valid AuraPlayer license and installation of the solution.

The AuraPlayer service manager will then be used to automatically create REST APIs from the Oracle EBS / Forms systems. These APIs serve as the basis for the connections. To learn more on how to create the APIs, feel free to review AuraPlayer’s training library.

 

To get started, reach out to AuraPlayer at sales@auraplayer.com

 

Supported versions

AuraPlayer’s solution can be installed and utilized on the following versions:

Oracle EBS 12.1, 12.2 and above; Oracle Forms 10g, 11, 12c and above

 

Capabilities

AuraPlayer's adapter for Oracle Integration Cloud makes it seamless to plug in on-premise or cloud hosted E-Business Suite applications and Oracle custom Oracle Forms applications to next-generation cloud third party applications through the OIC orchestration capabilities. AuraPlayer allows you to easily unlock the business logic trapped within your Forms/ E-Business Suite systems to integrate it to the world of SaaS. Utilizing OIC, you are able to connect to several AuraPlayer instances, set up connections, and extend and expose Rest API's through the Oracle Integration Cloud interface.

 

The AuraPlayer solution can be used for integrations, RPA automation, mobile apps, automated testing, and monitoring, and provides these unique capabilities:  

AuraPlayer’s capabilities

1. AuraPlayer provides the ability to integrate any Oracle EBS or Oracle Forms application via OIC, whether it is located on-premise or hosted in the cloud.
2. Allows for automation and integration of any Oracle Forms/ EBS workflow by recording the steps and wrapping it as a REST API.
3. Creates RPA automation flows that can be called as a REST API.  
4. AuraPlayer captures workflows as a user steps through a session, enabling workflows to be recorded as an API in a matter of hours.
5. There are no restrictions or limitations on workflows. Even the most customized workflows can be captured and made into APIs.
6. AuraPlayer can integrate as many Oracle EBS and Oracle Forms systems as needed.
7. AuraPlayer can integrate as many workflows/APIs as needed.
8. AuraPlayer runs all workflows/APIs in parallel on the server side (does not render the UI).
9. All AuraPlayer APIs are immediately activating a session in Oracle Forms/EBS on the server side.
10. All internal actions are handled and supported in AuraPlayer APIs/ RPAs, such as customizations, validations, flexfields, triggers, and stored procedures. 
11. AuraPlayer has built-in support for dynamic fields, dynamic flows, dynamic popups, dynamic error messages, and various permissions.
12. AuraPlayer delivers Oracle error messages in real time for easy error resolution. 
13. AuraPlayer does not directly connect to the database, but captures and automates the front end of the application to ensure all business logic is covered and applied. This eliminates risk and ensures system stability.

Common Use Cases

AuraPlayer can be used to create any custom API or RPA automation. 

Some common use cases are: 

• Create a sales order - streamline the creation of sales orders automatically from POs delivered by email
• Retrieve a list of sales orders - retrieve a list of all existing sales orders to be able to integrate data between systems
• Subinventory transfer -  transfer inventory in between sub inventories, warehouses or lots
• Check on-hand availability - Check on hand availability of items for streamlined purchasing
• Absences (get list)t - Get a list of employee absences to be able to integrate with cloud based HR or time Reporting systems.
• Purchase order (get details) - Get purchase order details to be able to integrate with Cloud ERP systems
• Approvals (get worklist) - Get a worklist of all open to-do action items for approvals from EBS
• Approvals (get expense details) - get a list of expense details to be able to look at existing expense workflows from your i-Expense application

The following documentation outlines how to configure and use the AuraPlayer adapter for OIC.

 

Install the AuraPlayer adapter in your OIC instance

Find the AuraPlayer adapter in the integration store and install it in your OIC instance. After installation, In the OIC environment, search under “Adapters” to find the AuraPlayer adapter. 

 

Once you’ve verified it is available, continue to the next step.

 

Create an AuraPlayer Connection

 

Using the AuraPlayer adapter, you can create a connection between OIC and a specific AuraPlayer ServiceManager instance.

(Note that if you have several installed ServiceManagers that need to be integrated with OIC, you will need to create a specific connection for each one of them.)

 

Go to the “Connections” tab and press the “Create” button.

 

Select “AuraPlayer”

 

Give the connection a name.

Set the URL of the specific ServiceManager, and in the security section, put the username and password of the ServiceManager administrator. 

 

Test and Save the AuraPlayer connection you have just created.

The AuraPlayer ServiceManager is now configured as a new connection.

 

Create a REST connection 

 

To create a REST connection, go to the “Connections” tab, press the “Create” button, and select REST.

 

Give it a name and make sure to select the “Trigger” role. 

 

 

Select “Basic Authentication”.

 

Test and Save the REST connection you have just created.

 

Now that the AuraPlayer connection and the REST Trigger connections are created in the OIC platform, you can create OIC Integration Flows that will invoke AuraPlayer ServiceManager APIs.

Create an OIC Integration Flow

 

Select the “Integrations” tab to create a new Integration Flow, and select the “Create” button”.

 

Select the Integration type. In this example, we have selected “Application”.

Give a name to the Integration Flow and press the “Create” button.

Select the REST Trigger you have created.

Name your endpoint for the Integration Flow.

 

Set a name for the path URL, select POST as a method, and define the input and output options for this endpoint by checking the boxes as appear below. Press “Continue”.

 

Set the input parameters of the Integration Flow and click “Continue”.

 

Select the response format “JSON Sample” and click the “inline” link to define the outputs.

 

Enter Sample JSON. In our example, we expose the entire output of the AuraPlayer API with all its output parameters.

Select “Continue” and then select “Finish”. Now the Integration Flow wrapper is defined.

 

The flow chart will be opened. It will flag an error for this Integration Flow and will require you to set a primary business identifier. This is an OIC requirement, and requires you to give the Integration Flow a unique name to identify and track it wherever it runs. Save the name in order to continue.

 

 

Now you can add the invocation of the API. To do so, you must add a new node between the “Trigger” node and the existing “Map” object. Hover on the line between the two points and click on the “+” sign. Select the desired AuraPlayer connection.

 

Set its name in the OIC flow chart.

 

Now, you will be able to view all the available APIs/services on the ServiceManager associated with this connection, and you can select the API that you want to invoke. Set the service name, path, and select “POST” method. 

Next, you must map the inputs and the outputs of the Integration Flow to those of the API.

Begin mapping the inputs by selecting the first mapping object. 

 

 

We begin by mapping the left side, where you will find the query parameters that you have set for the Integration Flow. With the right side, where you will find the parameters of the API that you are invoking from the AuraPlayer ServiceManager. To perform the mapping, simply draw a line to link between the parameters on both sides. For example, the input “Customer” should be mapped to a parameter called “Order Sold To”, the “item ID” to “Line Ordered Item”, etc. 

 

When finished, press the “Validate” button.

 

 

Below the “Invoke” node, select the second mapping object in order to map the outputs. 

 

On the left side, you will find the outputs that are available from the AuraPlayer API. And on the right side, you will find the outputs that you have defined for this Integration Flow. 

Draw a line to the corresponding parameters, like above. For example, map the “Success” API output parameter to the “AP Status” flow output, etc.

 

Press the “Validate” button. Press the “Save” button to save the newly created Integration Flow and to go back to the integrations list.

 

 

Invoke the Integration Flow

 

Select the “Activate” button. It cannot be invoked without first activating it.

 

Once the flow is activated, you can run it to validate that all is working correctly.

 

 

To run the flow, you will need to enter the data values for the parameters. (In this example, we will enter the customer, the price, the quantity and an item ID.) Select “‘Run”.

 

 

This will invoke the Integration Flow, which will invoke Oracle EBS/Forms using the API of the ServiceManager. It will return a response from the API.

 

Once an integration Flow is set up, you can invoke it from inside the OIC environment or from any REST client.

 

 

Troubleshooting your AuraPlayer Adapter

For troubleshooting and technical assitance, please visit our support site or open a support ticket. For additional assistance, contact us at support@auraplayer.com.