This article introduces how the Oracle SOA-Suite can be used to conveniently integrate Oracle Fusion Applications with other business applications such as the Oracle E-Business Suite. It is the first article in a series that will cover all important aspects of the integration in depth.
The following topics will be explored to give a bird’s eye view of the integration setup:
- The example scenario used to demonstrate the scope of the integration
- The SOA-Suite
- The concept of event-driven interaction with SOA
- Implementation of loose coupling to provide the flexibility to use various target systems
One of the most common tasks in customer relationship management – the creation of a new customer account – will serve to demonstrate the integration. Figure 1 shows, how a person from the CRM creates a new account in the corresponding Fusion Apps form.
After it is started you should see a window similar to the one in figure 2.
Before you start building SOA applications, you need to install the SOA Composite Editor. In order to do so, click on ‘Help’ in the menu bar and then on ‘Check for Updates…’ in the drop-down menu.
Using the Update Center caused problems so we manually installed the extension. To do so, you first need to download it from Oracle at the following location:
We used Version 184.108.40.206.8.02.22 since this is the latest version for JDeveloper 220.127.116.11. To perform the actual installation you simply need to choose ‘Install From Local File’ on the next page (figure 5) and then browse to the just downloaded zip archive.
After restarting JDeveloper, you are eventually ready to develop SOA composites.
Connect to application server (optional)
In this step we show how to connect JDeveloper to your WebLogic server so that you are able to directly deploy your SOA composites to it. Since SOA applications can also be exported and deployed via the Enterprise Manager (what is described in the next article), this step is optional.
Click on ‘View’ in the menu bar and select ‘Resource Palette’ from the drop down menu to open a new view where you can manage your application server connections.
In the “Resource Palette” view right click ‘Application Server’ and create a new connection from the context menu.
In the opening windows, enter a name for your connection. We chose ‘Fapps01s1’ since it is the hostname of our specific server.
On the next page, enter the login credentials for your application server.
On the following page, enter the hostname of your application server, the domain you want to connect to, and the corresponding ports. An overview of all configured domains and ports you can find in a summary file, which is located below the home directory of your OFA Provisioning installation:
Subsequently, you can test if your connection can be established.
All tests should finish successful to guarantee a proper working. If this is not the case you should recheck the configuration. Afterwards, you can finish the process. Now you should be able to open the established connection and navigate to the SOA server(s) running in your WebLogic environment.
After successfully setting up JDeveloper, you can start developing your applications. Select ‘File’ and ‘New…’ from the drop down menu. In the opening window, choose to create a ‘SOA Application’.
Find a name for your whole Application…
…and for the project that belongs it.
Now select the service component you would like to start the project with. The BPEL Process component is used in our sample application therefore we will select this one here.
After finishing the wizard, you should face the newly created project quite similar to figure 19.
Abbildung 19 – Neu erstellte Composite
From here you can start developing your SOA application by just dragging the service components or adapters you need from the Component Palette on the right side to the composite.xml tab in the center.
After showing you how to essentially build up your SOA development environment, we describe in the following article how to actually deploy your application to a SOA server. For this purpose, we will use the sample application which was already mentioned in the first article. Additionally we will show how to debug the execution of a deployed composite.