Applications that you want to integrate using Oracle BPEL or Oracle ESB are likely use different values to represent the same information. For example, one application might represent a state with the long name (California) while another application may represent the state with an abbreviation (CA). A domain-value map enables you to associate values from one application with values from another.

Read more: BPEL Tutorials : Domain Value Maps

Capturing an event can be done in ESB as well as BPEL. We have already seen how to capture an event in BPEL.Now let us see in ESB.

Read more: Capturing a Business Event in a ESB Process

It is important to understand different integration components available within EBS to make informed decision about using one or more for your SOA integration project. Selecting one or more of them depends upon the requirements and the interaction pattern determined to be best fit for the service oriented architecture based integration. Following are the integration mechanisms available within e-Business suite.

Oracle XML Gateway:

E-Business Suite utilizes the Oracle Workflow Business Event System to support event-based XML message creation and consumption. It can consume events raised by the Oracle E-Business Suite and can subscribes to inbound events for processing. It can be leveraged for Business-to-Business (B2B) and Application-to-Application (A2A) integration scenarios. Majority of messages delivered with the Oracle E-Business Suite are mapped using the Open Application Group (OAG) standard.

Business Events:

The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems. There are more than 1000 built in events with in EBS that can be leveraged for event-based integration of business processes.

Concurrent Programs:

A concurrent program is an instance of an execution file. Concurrent programs use a concurrent program executable to locate the correct execution file. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults.

Interface Tables:

Interface tables are intermediate tables into which the data is inserted first. Once the data gets inserted into the interface tables, the data is validated, and then transferred to the base tables. Base tables are real application tables that reside in the application database. The data that resides in the interface tables is transferred to the base tables using concurrent programs. Interface views provide a way to retrieve data from Oracle Applications. By using views, you can get synchronous data access to Oracle Applications.

PL/SQL APIs:

These are stored procedures that enable you to insert and update data in Oracle Applications. Oracle e-Commerce (EDI) Gateway: Oracle e-Commerce Gateway provides a common, standards-based approach for Electronic Data Interchange (EDI) integration between Oracle Applications and third party applications. It is the EDI integration enabler for Oracle Applications.

 

Many of our learners asked us to show how can we capture an Oracle Applications Business event in the BPEL process.

Read more: Capturing a Business Event in the BPEL Process