As an Apps technical or functional consultant, it is essential for you to understand what options EBS gives you to if you want to talk to a SOA component like BPEL or ESB. The selection depends upon the interaction pattern you are looking for - invoking the SOA component from EBS or invoking EBS components from SOA components, whether the communication needs to be in real time, batch, complexity and technical feasibility. Following are the options that Oracle provides:
Interface Tables and Views:
The most common strategy to insert data into the Oracle Apps' tables is to first insert the data into some intermediate tables (called Interface tables) and then run some validations over the data. Once the data is validated, it is then transferred to the base tables which are the real application tables that reside in the application database. This transfer from interface tables to base tables along with the validations is usually achieved by calling a concurrent program after insertion into the interface tables.
We also have interface views. These provide a way to retrieve data from Oracle Applications. By using views, you can get synchronous data access to Oracle Applications.
Concurrent Programs:
A concurrent program is essentially an executable file (more technically, it's an instance of an executable). They are termed concurrent because several copies of the same concurrent program can run simultaneously, each having different parameter values.
PL/SQL APIs:
These are stored procedures that can be used to query, update or add data to Oracle's base tables.
Oracle XML Gateway:
XML gateway can be used to create messages to be sent out of Oracle Apps, as well as deliver messages to Oracle Apps sent by outside systems. In order to provide standardized messages, XML gateway uses OAGIS standard messages.
Oracle e-Commerce (EDI) Gateway:
There may be suppliers who don't yet understand XML and are still running systems that understand EDI (EDI predates XML as the de facto standard for message exchange). For these kind of messages that are not based on XML, we have the Oracle e-Commerce Gateway. It enables Oracle Applications to talk to EDI based systems, both in inbound and outbound directions.
Business Events:
Events are yet another way of message communication. If you ever want to utilize events in Oracle Apps, you need to use the Oracle Workflow Business Event System. This system essentially uses AQ to communicate business events between systems. Events can be raised locally or received from an external system or the local system through AQ. There are more than 1000 built in events within EBS that can be leveraged for event-based integration of business processes.
For more info visit http://soatraining.hpage.com
Comments
No one has commented yet.