Login
Register

Home

Trainings

Fusion Blog

EBS Blog

Authors

CONTACT US

SOA
  • Register

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

webinar new

Search Courses

Asynchronous BPEL Process

 

A Asynchronous Process is one which you call and need not wait for the response before proceeding further. You may just initiate the Asynchronous process and receive the response when you require it as a part of your process, hence you are not forced to wait for response.

For analogy sake, let me give you an example for better understanding. I have chosen simplicity of the analogy above technical similarity.

Real life example of a Synchronous process: You call a friend and ask him to give you some information. While your friend is finding out the information for you, you are on the call waiting for his response. Note that connection is not dropped

Real life example of an Asynchronous process: You call a friend and ask him to give you some information. You ask him to call you back when the information is ready and you disconnect the call. When your friend is ready with the information, he calls you and gives you the information. Note that you don’t wait for a response from your friend and connection is lost. When your friend is ready, he has to establish a new connection and then provide you the information

By now, you have already got a SOA Server up & Running, and also, you have now successfully connected your jDeveloper to BPEL Server.
In this article, you will see the steps for
    a) Creating a new Business Event which will be raised in EBS to initiate BPEL Process
    b) Creating a BPEL Process that listens to Business Events from an Oracle eBusiness Suite environment.
You will also find an overview of how event message is propagated from Oracle eBusiness Suite to BPEL Server.

Oracle BPEL Tables in the perspective of Oracle Workflow Tables.

In this article you will learn about the main tables used by the BPEL Server/Engine. For these tables, you will also see the corresponding tables in good old Oracle Workflow.

The reason I write this article is because I believe in next 5 Years time , many of the current Oracle Workflow Consultants will be working on Oracle BPEL Instead.

PROCESS_LOG [ Similar to wf_item_types in Oracle Workflows ]

This is the table in BPEL where the any activity related to changes to the process are stored.

For example, if you wish to know how many time the BPEL process was deployed onto server or revised, then this is the table to look into.

 

A higher level that this table are tables PROCESS and PROCESS_DEFAULT.

These table contain the BPEL Process name and their revision information.

CUBE_INSTANCE [ Similar to wf_items in Oracle Workflows ]

For each BPEL process instance an entry gets created in this table.

This will tell you the data on which this instance started, and the last updated date of the instance.

To purge records from this table, you can use collaxa.delete_ci, using primary key value from cikey.

State 5 or more means that the process instance is complete.

If state is less than 5, then it means that process instance is ongoing.

 

INVOKE_MESSAGE

Stores the information regarding the message that invoke a BPEL Process.

For example a Business Event can invoke a BPEL Process via WebService, as shown in image below.

Of course this table will also tell you the timestamp at which the BPEL process was invoked.

WORK_ITEM [ Similar to WF_ACTIVITIES in Oracle Workflow ]

This table contains the activities against the BPEL Process Instance.

 

DOCUMENT

If a variable with XML document has size bigger than 5MB[configurable], then variables XML data gets stored into this table.

 

AUDIT_TRAIL

This is the table that gets used to display the audit flow from BPEL Console.

This has a column named LOG which is a Large Object RAW Column, each step in BPEL process gets logged into LOG Column in XML zipped form.

 

Integration Repository [ iRep ] in Release 11i is perhaps meaningless unless your customer has Oracle SOA Suite and of course unless the developer decides to use the Oracle Apps Adapter in their BPEL flow. 
To work with integration repository in Release 11i, not only you are enforced to use Oracle's Oracle Apps Adapter, but also there is another major restriction in Integration Repository of Release 11i. 
This second limitation exists because the Integration Repository in Release 11i is not extensible. These limitations however are elegantly overcome in Release 12. This article discusses the comparison and R12 SOA features in details.

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Apr 2024  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
  1  2  3  4  5  6  7
  8  91011121314
15161718192021
22232425262728
2930     

Enquire For Training

Fusion Training Packages

Get Email Updates


Powered by Google FeedBurner