IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere Studio Application Developer Integration Edition > Additional migration information > Migrating to the SCA programming model > Migrating WebSphere Business Integration Server Foundation client code

Migrating the Business Process Choreographer generic EJB API client

This topic shows how to migrate clients that use the 5.1 Business Process Choreographer generic EJB API to invoke a BPEL service.

There is a new version of the Generic EJB API that uses DataObjects as its message format. The client must change how the message is constructed. Previously, the messages were based on the WSIFMessage class, but now they should be based on the commonj.sdo.DataObject class. If that the Generic EJB API has not changed significantly, as the ClientObjectWrapper still provides a message wrapper around the particular message format.

Ex: DataObject dobj = myClientObjectWrapper.getObject();
String result = dobj.getInt("resultInt");

The JNDI name of the old Generic EJB that takes WSIFMessage objects is:

GenericProcessChoreographerEJB
JNDI Name: com/ibm/bpe/api/BusinessProcessHome
Interface: com.ibm.bpe.api.BusinessProcess

There are two generic EJBs in which the human task operations are available as a separate EJB. The JNDI names of these Generic EJBs are:

GenericBusinessFlowManagerEJB
JNDI Name: com/ibm/bpe/api/BusinessFlowManagerHome
Interface: com.ibm.bpe.api.BusinessFlowManager

HumanTaskManagerEJB
JNDI Name: com/ibm/task/api/TaskManagerHome
Interface: com.ibm.task.api.TaskManager

: Migrating WebSphere Business Integration Server Foundation client code