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 > Create SCA exports to access the migrated service
Migrating the EJB and the EJB process bindings
The EJB and EJB process bindings can be migrated to the recommended SCA construct.
In WebSphere Studio Application Developer Integration Edition, this binding type enabled clients to communicate with a BPEL process or other service type by invoking an EJB. If that this binding type was not optional for microprocesses – it was always selected because the generated EJB was used internally by the other binding types.
The JNDI name of the generated EJB was automatically generated as a combination of the BPEL’s name, target namespace, and valid-from timestamp.
For example, these attributes can be found by examining the BPEL process’s properties in the BPEL editor on the Description and Server content tabs:
| Process name | MyService |
|---|---|
| Target namespace | http://www.example.com/process87787141/ |
| Valid From | Jan 01 2003 02:03:04 |
The generated namespace for this example is then com/example/www/process87787141/MyService20030101T020304.
In WebSphere Studio Application Developer Integration Edition, when the EJB binding was selected as the deployment type there were no options given.
There are four options for migrating the WebSphere Studio Application Developer Integration Edition process binding. The type of client(s) that access the service will determine which of the migration option(s) below to perform:
After the manual migration steps have been completed, the client must be migrated to the new programming model as well. See the appropriate topic for the following client types:
| Client type | For further information see |
|---|---|
| EJB client that invokes the generated session bean. Such a client would invoke an EJB method corresponding to the BPEL operation to invoke | "Migrating the EJB client" |
| WSIF client that uses the EJB process binding | "Migrating the EJB process binding client" |
| Generic Business Process Choreographer EJB API | "Migrating the Business Process Choreographer generic EJB API client" |
| Generic Business Process Choreographer Messaging API | "Migrating the Business Process Choreographer generic Messaging API client" |
| Another BPEL process in the same module | N/A: Wire BPEL components together using Assembly Editor |
| Another BPEL process in a different module | N/A: Create an Import with SCA Binding in the referencing module, and configure its binding to point to the Export with SCA Binding created below in Option 1 |
Migration option 1 for the EJB and EJB process binding
The first migration option for the WebSphere Studio Application Developer Integration Edition EJB process binding is to make business processes accessible to another component in the same module.- Migration option 2 for the EJB and EJB process binding
The second migration option for the WebSphere Studio Application Developer Integration Edition EJB process binding is to make business processes accessible to other SCA modules and clients. - Migration option 3 for the EJB and EJB process binding
The third migration option for the WebSphere Studio Application Developer Integration Edition EJB process binding is to make modules accessible by a non-SCA entity (for example, a JSP or a Java client). - Migration option 4 for the EJB and EJB process binding
The fourth migration option for the WebSphere Studio Application Developer Integration Edition EJB process binding is to make business processes accessible by a web services client.