Propagating eBusiness Suite business events through Enterprise Service Bus
Propagating eBusiness Suite Business Events with Enterprise
Service Bus
Purpose
This OBE tutorial describes and shows you how to perform
propagation of eBusiness Suite events with Oracle Enterprise Service. This process
involves configuring the eBusiness Suite and setting up the ESB to capture events
that are written to a file. This OBE tutorial also lists the preinstallation
requirements.
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor
over each individual icon in the following steps to load and view only the screenshot
associated with that step.
The screenshots will not reflect the specific environment
you are using. They are provided to give you an idea of where to locate specific
functionality in Oracle Identity Manager.
Overview
In an environment comprising of heterogeneous services and
applications, managing integration of various components in a point-to-point
approach is complex. By using ESB the communication between such components
become easily manageable. An ESB provides a messaging infrastructure, which
lets you communicate in different ways, such as synchronously or asynchronously.
By using ESB, Quality of Service aspects such as guaranteed delivery is also
ensured. The ESB infrastructure provides a common communications backbone by
integrating directly with the Oracle Adapter for Oracle Applications.
In such environments, eBusiness Suite outbound business events can be propagated
through ESB. By using adapters, you can expose underlying these business events
as Web Services. These Web services can then be integrated with ESB by propagating
the events to other applications or systems.
Linda is an eBusiness suite user in Mydo Main Corporation.
She creates and approves a purchase order (PO) for a business task. By doing
this, a PO approved business event is raised. Linda needs to propagate this
PO approved business event to ESB and save the details to an xml file.
When the PO is approved, the business event raised is oracle.apps.po.evnt.xmlpo.
To setup the XML Gateway trading partner, perform the following
steps:
1.
Open the browser and enter the URL to access Oracle Applications in the
following format:
http://<hostname>.<domainname>:<port>
The URL can be of the type http://ap6065rt.us.oracle.com:8095/OA_HTML/AppsLocalLogin.jsp
.
2.
Enter the username as OPERATIONS
and password as welcome
and then click Login.
3.
Click XML Gateway from the left panel and then click Define
Trading Partners from the right panel. Notice that the Trading Partner
Setup application is displayed. This is an Oracle Forms based application.
4.
On the Trading Partner form, press F11 to launch the Trading Partner
Setup form.
.
5.
For creating the Trading Partner, provide the following parameters and
press CTRL+F11. Notice that the form is populated with existing
transaction details for the Advance Network Devices trading partner.
Parameter
Value
Trading Partner Type
Supplier
Trading Partner Name
Advanced
Network Devices
6.
For creating the Trading Partner details, provide the following parameters
and then click File > Save to store the partner details.
Note: Retain the values as is incase if some of them are populated
by default to the values mentioned in the table above.
7.
To generate the PO, click File > Switch Responsibility and
type Purchasing, Vision Operations (USA). Notice that the Purchasing
form is displayed.
8.
From the right panel, under the Top Ten List
section, click Purchase Orders.
9.
Notice that the Purchase Order form is displayed. Details of the
Trading Partner is already existing in the Oracle XML Gateway. To create
the PO with the details of the Trading Partner provide the following parameters:
Parameter
Value
Supplier Name
Advanced Network Devices
Site
SANTA CLARA-ERS
Item
CM13139
Quantity
1
Promised
<any future date on dd-month name-yyyy format>
10.
To save the PO, click the Save icon from the toolbar.
11.
Notice that the status of the PO is Incomplete. However, the Approve
option is enabled.
To approve the PO, click OK.
Note: The valid Trading Partner set up is available so the Transmission
Method is enabled by default to the XML option.
12.
Notice that the status of the PO is approved. You can save the
PO, Rev value for future reference. Once the PO is approved the
oracle.apps.po.event.xmlpo business event is raised. This event
is propagated to the ESB and saved to a file.
13.
The WF_Deferred Agent Listener should be running on the target
database. To check this, login to the Oracle Applications using the following
URL:
To create the datasource, perform the following steps:
1.
Open a browser window and enter the URL to access the
Enterprise Manager 10g Application Server Control in the following format:
http://<hostname>.<domainname>:<port>/em
Note: The default port is 8888. The username
is oc4jadmin and password is welcome1.
2.
On the Cluster Topology page, click home.
3.
On the OC4J: home page, click Administration.
4.
In the Task Name column, click to expand the Properties icon
if it is not already expanded. Then, under Services section, in the JDBC
Resources row, click the Go to Task icon.
.
5.
In the Connection Pools section, click Create and then click Continue.
Retain the values as is.
6.
Enter ebiz_pool in the Name section and select the Generate
URL from Connection Information radio button.
7.
For the connection data, provide the following information:
Parameter
Value
Driver Type
Thin
DB Hostname
ptc-apps01.us.oracle.com
DB Listner port
1521
DB Identifier Type
SID
SID/Service Name
VIS
8.
In the Credentials section, enter the username as apps and password
as apps. Next, click Finish.
9.
Under the JDBC resources, click Create and then click Continue.
Retain the values as is.
10.
For the data source, provide the following information and then Click
Finish to create the data source.
Parameter
Value
Name
ebizDataSource
JNDI Location
jdbc/ebizDataSource
Database SID
orcl
Connection Pool
ebiz_pool
11.
To create the Oracle Applications adapter, click OC4J:home.
12.
Click Applications, and then click the default application.
13.
Under Modules, click AppsAdapter.
14.
Click Connection Factories and click Create.
15.
Accept the default values and click Continue.
16.
Enter JNDI Location as eis/Apps/appsSample and Configuration Properties
as jdbc/ebizDataSource.
Note: the Configuration Properties values is for xADataSourceName.
17.
Retain other entries as default and click Finish.
18.
Open the command prompt, navigate to C:\SOASuite10131\opmn\bin and
execute the following commands:
To build the ESB sample application, perform the following
steps:
1.
Navigate to C:\<JDeveloper_Home> and double-click
jdeveloper.exe.
2.
Click View > Connection Navigator.
3.
In the left pane, double click on Database. Notice that the Create
Database Connection wizard is displayed.
4.
InCreate Database ConnectionwizardStep 1 of 4,
type theConnection Nameas ebiz and click Next.
.
5.
InCreate Database ConnectionwizardStep 2 of 4,
type theUsername as apps and password as apps
and then click Next.
6.
InCreate Database ConnectionwizardStep 3 of 4,
enter the following values and then click Finish.
Parameter
Value
Driver
thin
Host Name
ptc-app01.us.oracle.com
JDBC Port
1521
SID
vis
Note: Retain the defaults incase the same values
get populated.
7.
InCreate Database ConnectionwizardStep 4 of 4,
click Test Connection. Notice that the status is shown as Success!
Note: Similarly, you can create connections to (i) Application
Server (SOA) instance (ii) Integration Server and test them. Use the following
values for each of them:
Parameter - for Application Server (SOA) instance
Value
Connection Name
AppServerConnection1
Connection Type
Oracle
Application Server 10g 10.1.3
Username
oc4jadmin
Password
welcome1
Connect To
Single Instance
Host Name
localhost
OPMN Port
6003
OC4J Instance Name
home
Parameter - for Integration Server
Value
Connection Name
ServerConnection1
Application Server
AppServerConnection1
Host Name
localhost
Port
8888
8.
To create a new ESB project, click File
> New.
9.
Notice that the New Gallery box is displayed.
10.
Select Application and provide the application name as OBE.
11.
Right click on the created Application workspace and click Create
New Project.
12.
Next, click ESB Project and click OK.
13.
Type Project name as CaptureBusinessEvent and click OK.
14.
To define the Application adapter GetEvent, under Adapter Services,
from the Component Palette, drag and drop Application Adapter to ESB design
console.
15.
Notice that the Adapter Configuration Wizard is displayed. Select
the established Database Connection to Vision Database and click
Next. The JNDI name corresponding to the database connection appears
in the Database Server JNDI Name field.
16.
Once you have completed creating a new connection for the service, you
can add an XML Gateway map by choosing through the maps available in Oracle
Applications. Navigate to Product Families > Other Interfaces >
Business Events > Outbound (Listen to Business Events from Oracle
Apps) and click oracle.apps.po.event.xmlpo and then click OK.
17.
The business event is captured with all in the wizard file and Click
Next.
18.
To define the schema for the business event, click Browse.
19.
Notice that the Type Chooser dialog
box appears. Click the Import Schema icon.
20.
Notice that the Import Schema File dialog box appears. Click the
Browse icon.
21.
Notice the Import Schema dialog box appears. Click the APPS_WF_EVENT_T.xsd
and click Open.
22.
Click the WF_EVENT_T schema for the business event and Click OK.
23.
Click Finish to complete the steps of creating the Adapter Service.
24.
You need to create File Adapter Service to write outbound business event
data into a XML file. Click the Adapter Service from the Component
Palette. Click the File Adapter.
25.
The Adapter Configuration Wizard appears. Enter the name of the
File Service Adapter as WriteEvent. Next, click configure adapter
service icon for the WSDL file entry.
26.
Notice that the Adapter Configuration Wizard is displayed. In
theAdapter Configuration Wizard Step 1 of 4 Service Name, retain
the default service name as WriteEvent.
27.
In theAdapter Configuration Wizard Step 2 of 4 Operation, Click
the WriteFile radio button, and type the Operation Name as Write.
28.
In theAdapter Configuration Wizard Step 3 of 4 File Configuration,
provide the following values:
Parameter
Value
Directory for Outgoing files (physical path)
C:\tmp
File Naming Convention
EventAck%SEQ%.xml
29.
Notice the Popup TypeChooser window is displayed. Click to expand and
select Project Schema Files > APPS_WF_EVENT_T.xsd > WF_EVENT_T
and then click OK.
30.
Click Finish.
31.
In ESB design console, click the Transformation icon on GetEvent_RS
Routing Service.
32.
In the GetEven_RS Routing service details design page, click Add
under the Routing Rules section.
33.
In the Browse Target Service Operation Dialog box, click Write
operation under WriteEvent and then Click OK.
34.
In ESB design console, click the Transformation icon on GetEvent_RS
Routing Service.
35.
Click Create New Mapper file radio button option. This creates a Transformation
Mapping File WF_EVENT_T_To_WF_EVENT_T.xsl
36.
In the above created Transformation mapping file design window, establish
default transformation mapping between Source WF_EVENT_T ( GetEvent.wsdl)
and WF_EVENT_T Target (WriteEvent.wsdl) by drawing link.
37.
In the Auto Map Preferences, select the default mappings.
38.
Notice the established default mapping is displayed.
Bookmark
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
