Exploring ODE Part IV: BpelServer API

If you look at the ODE source code, the BpelServer API is a very important one. In this entry, we will look at the class that how we use the BpelServer, for the ODE, lets look at the ODEServer source code.

 __log.debug("Initializing transaction manager");
__log.debug("Creating data source.");
__log.debug("Starting DAO.");
EndpointReferenceContextImpl eprContext = new EndpointReferenceContextImpl(this);                
__log.debug("Initializing BPEL process store.");
__log.debug("Initializing BPEL server.");
 __log.debug("Initializing HTTP connection manager");

// Register BPEL event listeners configured in axis2.properties file.
registerContextInterceptors();        .....

As above code shown:

  • Initialized the TransactionManager, which will be used in the datasource and scheduler service.
  • Created the data source.
  • Created the DAOConnectionFactory, the extension API is BpelDAOConnectionFactory.
  • Created the EndpointReferenceContext, which takes care of resolving EndpointReference.
  • Created the Process Store, it takes care of process deploying, undeploying, list etc.
  • Initializing the BpelServer, includes following actions: setMessageExchangeContext, setDaoConnectionFactory, setBindingContext, the BindingContext and the MessageExchangeContext are the extension points for communicating with partner services.
  • Register the EventListners, MexInterceptors etc, these are all the APIs in BpelServer.

You also could see how we initialize the BpelServer in the MockBpelServer class. In the Riftsaw project,it is in the BpelEngineImpl class. In the Riftsaw project, we are adding another implementation for the ProcessStore that leverages the JBoss Application Server’s Deployer mechanism, also we adding another implementation for the BindingContext that use the JAXWS based approach, which used the JBossWS to accomplish.