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 JMS client

Clients that communicated with a 5.1 service via the JMS API (sending a JMS message to a queue) might require manual migration. This topic shows how to migrate clients that use JMS APIs (sending a JMS message to a queue) to invoke a service.

You must ensure that the Export with JMS Binding created in a previous step will be able to accept this text or object message with no changes. You might need to write a custom data binding to accomplish this. See the section "Migrating the JMS and the JMS process bindings" for more information.

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. See the section "Migrating WSIFMessage API calls to SDO APIs" for more details on how to perform this manual migration.

: Migrating WebSphere Business Integration Server Foundation client code