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 Components and SCA Imports for the services in the application for rewiring

Migrating a JMS service

If the Migration wizard did not fully migrate all of your service projects, you can migrate a JMS service to an SCA Import with JMS binding.

If the JMS message is being sent to a WebSphere Business Integration Adapter, see the section "Migrating Interactions with WebSphere Business Integration Adapter" in the link below.

To migrate a JMS service project for an outbound service migration, follow these steps:

  1. Import the workspace using the Migration wizard. This will result in the creation of a Business Integration module with the WSDL Messages, PortTypes, Bindings, and Services generated in WebSphere Studio Application Developer Integration Edition.

  2. In the Business Integration perspective, expand the module so that you can see its contents. Open the Assembly Editor by double-clicking the first item under the module project (it will have the same name as the project).

  3. Add an Import that will allow the application to interact with a JMS queue according to the SCA programming model.

  4. In the Assembly Editor, expand the migrated module project and expand the Interfaces category. Find the WSDL PortType that describes the web service that the application will invoke. Drag it onto the Assembly Editor.

  5. A Component Creation window will allow you to select the type of component to create. Choose Import with No Binding.

  6. You will see that a new Import was created in the Assembly Editor.

    If you select it and go to the Properties view, on the Description tab you can change the import's name and display name to something more meaningful.

  7. You can refer to the 5.1 WSDL binding and service files to find details about the JMS service that you are migrating and use them to enter the details of the 6.x or later "Import with JMS Binding". Locate the 5.1 JMS binding and service WSDL files within the 5.1 service project (they are often named *JMSBinding.wsdl and *JMSService.wsdl). Inspect 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 "Import 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).
  8. Right-click the import and select Generate Binding > Messaging Binding > JMS Binding. You will be prompted to enter the following parameters:

    Select JMS messaging domain:

    • Point-to-Point
    • Publish-Subscribe

    Specify the end point configuration.

    You can have the messaging provider resources created for you on deployment or you can specify the messaging resources to use.

    Specify the Default data format to specify how the data is serialized between Business Object and JMS Message.

    If your application needs to set any JMS header properties that are not normally available in the JMS Import Binding, they can be set using a mediation flow.

    For security, if you are using a Java Authentication and Authorization Services alias, you can specify that, too. Click OK.

    Inbound connectivity is using default JMS function selector class:

    <selected> or <deselected>

  9. Select the import that you just created. In the Properties view, go to the Binding tab. You can manually enter all the binding information listed there to the same values that you specified before in WebSphere Studio Application Developer Integration Edition. The binding information that you may specify is:

    • JMS Import Binding (you can specify the default message type here)
    • End-Point Configuration
    • Method Bindings
    • Faults Configuration
    • Security Attributes
    • Message Configuration
    • Propagation
    • Summary

Once you have completed this, rewire the service:

: Create SCA Components and SCA Imports for the services in the application for rewiring