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
Migration option 5 for the JMS and JMS process binding
The fifth migration option for the WebSphere Studio Application Developer Integration Edition JMS process binding is to make business processes accessible by a JMS client.
The Export with JMS binding makes an SCA component accessible by an external JMS client. To create an Export with JMS binding, follow these steps:
Procedure
- For BPEL services, you will need to create and reference new queue resources, because the 5.1 JMS process binding was quite different from the standard 5.1 JMS binding. For non-BPEL services, you can find the values you selected for the JMS deployment code in WebSphere Studio Application Developer Integration Edition 5.1 by finding the WSDL file named JMSBinding.wsdl and JMSService.wsdl in the appropriate package underneath the ejbModule/META-INF folder of the generated EJB project, and inspecting the binding and service information captured there. From the binding, you can determine whether text or object messages were used and whether any custom data format bindings were used. If there were any, consider writing a custom data binding for your 6.x or later Export with JMS Binding as well. From the service, you can find the initial context factory, JNDI connection factory name, JNDI destination name, and destination style (queue).
- Open the assembly editor for the module created by the migration wizard.
- Create an export with JMS binding for each BPEL process interface that had a JMS binding generated for it in WebSphere Studio Application Developer Integration Edition by right-clicking the BPEL component in the Assembly Editor.
- Select Generate Export… > Messaging Binding > JMS Binding .
- If there are multiple interfaces for the process, select the interface(s) to export with this binding type.
- On the next panel (JMS Export Binding attributes), select JMS messaging domain. Define this attribute as Point-to-Point.
- Select how data is serialized between Business Object and JMS Message. It is recommended that you select UTF8XMLDataHandler, because XML is independent of the runtime environment and enables service integration between disparate systems.
- Specify the function selector to use for mapping message to operation.
- For accessing JMS header properties, wire the JMS export to a mediation flow component.
- When the Export with JMS binding has been created, select the export in the Assembly Editor and view its properties.
