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 JMS and the JMS process bindings

The JMS and JMS process bindings can be migrated to the recommended SCA construct.

In WebSphere Studio Application Developer Integration Edition, this binding type gave clients the ability to communicate with a BPEL process or other service type by sending a message to an MDB. If that this binding type was not optional for long-running processes and it was always selected. In fact, this binding type was the only binding type allowed for request-response interfaces of long-running processes. For the other service types, an MDB would be generated and it would invoke the appropriate service.

The JNDI name used by the JMS binding was a combination of the BPEL’s name, target namespace, and valid-from timestamp.

In WebSphere Studio Application Developer Integration Edition, when the JMS binding was selected as the deployment type for a BPEL process, the following options were given:

There are five options for migrating the WebSphere Studio Application Developer Integration Edition JMS process binding. The type of client(s) that access the service will determine which 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:

Further information for migrating clients
Client type For further information see
WSIF Client that uses the JMS process binding "Migrating the Business Process Choreographer generic Messaging API client and the JMS 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 "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.

: Create SCA exports to access the migrated service