Two scenarios of invoking asychronous service from BPEL

OrderService is one asynchronous service. When invoking it from one BPEL process we can have the different behaviour by using different activities: in one scenario OrderService is invoked and then BPEL process will wait for the callback response from OrderService. If the specified timeout occurs the notification is sent off but BPEL process continues the waiting for the response. However in another scenario after invoking OrderService BPEL will wait for the callback response. If the specified timout occurs BPEL will handle the timeout and will not wait for the callback response any more.

The first scenario can be implemented by using the activity invoke, receive wrapped in the scope with which onAlarm is attached.

The second scenario is implemented using pick activity. One branch of pick is onMessage to wait for the callback and another branch is onAlarm.

Using MDS in JDeveloper

When using WSDL in MDS in Oracle SOA 11g, JDeveloper uses .adf\META-INF\adf-config.xml to decide where MDS is.

For example, in the following component.xml the WSDL's location is defined as:
oramds:/apps/SOInterfaces-2.3.9.8/BSC/OrderAndActivation/Activation/ServiceProvisioning-v1.wsdl.


When building the SOA application JDeveloper will look up the MDS from adf-config.xml in order to load the WSDL. From adf-config.xml we know that for /apps/SOInterfaces-2.3.9.8 it uses the metadata-store-usage is mstore-usage-2 which is a database-based MDS. Its database details is defined in metadata-store-usage with id="mstore-usage-2".

Persistent Context vs. Entity Manager vs. Transaction

These definitions are from the link: http://docs.jboss.org/hibernate/entitymanager/3.6/reference/en/html/architecture.html

"Entity Manager
The EntityManager API is used to access a database in a particular unit of work. It is used to create and remove persistent entity instances, to find entities by their primary key identity, and to query over all entities. This interface is similar to the Session in Hibernate.

Persistence context

A persistence context is a set of entity instances in which for any persistent entity identity there is a unique entity instance. Within the persistence context, the entity instances and their lifecycle is managed by a particular entity manager. The scope of this context can either be the transaction, or an extended unit of work."