Oracle Fusion Applications Integration using Oracle SOA Suite

Oracle Fusion Applications Integration using Oracle SOA Suite

1. Obtain the WSDL from the Oracle Enterprise Repository for Fusion Applications cloud hosted instance (http://fusionappsoer.oracle.com ) – This requires a free Oracle login. Search for Asset Type = “ADF Service” and enter the name of the service, such as Account. From the results list, pick the desired service, such as Trading Community Account. Clicking on the Details tab will provide a link to the Abstract WSDL as well as the URL pattern for finding the Concrete WSDL in your Fusion Applications environment. Simply replace the hostname and port and download the WSDL.

Note that not all the services are available in SaaS mode since some services
are “internal” and not exposed on the external virtual host; that is, they are inside the “firewall”. To ensure that the service you have selected can be invoked from external clients, click on the Taxonomy tab of the service definition and ensure that Keyword=External is present.

2. In Oracle JDeveloper, create a SOA project with a BPEL process that needs to integrate with Oracle Fusion Applications. Create a partner link based on the WSDL obtained in step 1.

3. Apply a compatible security policy to this partner link. If your environment has an SSL enabled environment, you can use the out-of-the-box oracle/wss_username_token_over_ssl_client_policy. You can also choose the
equivalent SAML policies (for identity propagation) or WS-Security message protection enabled policies if these have been enabled in your environment.

 

To get invoked via outbound services from Oracle Fusion Applications, you would follow these steps:

4. Set up a Receive activity in a BPEL process with a SOAP endpoint and implement the process based on the WSDL and XSD documented by Oracle Fusion Applications in the Application Composer Object Workflow Outbound Message page. This can be considered as an intermediary web service that understands the Fusion objects and mediates the requests to other on-premise or cloud applications as needed—for example, to synchronize new customers created with the on-premise Master Data Management system or to create them as Contacts in the Oracle RightNow CX cloud service.

5. Deploy the composite and obtain the endpoint URL.


6. In Oracle Fusion Applications,
register the endpoint URL in the Application Composer Object Workflow page in the Outbound Message page activity for the object. You can now receive this outbound message in your SOA composite and process it as per your required business process.

——————————————————————————————————————

Advertisements

One comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s