WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Example: Migrating an MDB application from Version 5 embedded messaging - stage 2

This topic provides an example of the migration of an MDB (message-driven bean) application on a version 6 node, from using Version 5 default messaging JMS resources and listener port to version 6 default messaging provider JMS resources including JMS activation specification.

This topic provides a contextual description of the migration, then a summary of the steps involved.

This example follows on from the example described in Example: Migrating an MDB application from Version 5 embedded messaging - stage 1.

Consider the example scenario, before replacing the Version 5 JMS resources with version 6 JMS resources, shown in the following figure Figure 1.
Figure 1. MDB application scenario before replacing the Version 5 JMS resources with version 6 JMS resources. The migrated scenario still uses the Version 5 JMS resources: a JMS queue connection factory, PPQCF; two JMS queues, InQ and OutQ; and a listener port, MDBPort. These resources are to be replaced by equivalent version 6 resources.
This scenario shows the Version 5 JMS resources to be replaced by version 6 equivalents.  For more information this scenario, see the description that accompanies this figure.

To replace the Version 5 default messaging JMS resources with equivalent version 6 default messaging provider JMS resources, complete the following steps:

  1. Delete the Version 5 JMS resources:
    1. Display the collection list of Version 5 JMS queue connection factories. Click Resources > JMS Providers > V5 Default Messaging > [Additional Properties] WebSphere queue connection factories
    2. Select the check box next to the queue connection factory, PPQCF.
    3. Click Delete
    4. Click OK.
    5. Display the collection list of Version 5 JMS queues. Click Resources > JMS Providers > V5 Default Messaging > [Additional Properties] JMS queue destinations
    6. Select the check box next to the queues, INQ and OUTQ.
    7. Click Delete
    8. Click OK
    9. Save your changes to the master configuration.
  2. Create a version 6 JMS queue connection factory to replace the Version 5 JMS queue connection factory. [If you want to use a unified JMS connection factory instead of the domain-specific JMS queue connection factory, you would need to rewrite the MDB application to use JMS 1.1 interfaces.] For example, use the version 6 WebSphere administrative console to complete the following steps:
    1. Display the collection list of JMS queue connection factories for the default messaging provider. Click Resources > JMS Providers > Default messaging provider > [Connection factories] JMS queue connection factory
    2. Click New
    3. On the New JMS queue connection factory page, set the following properties:
      Name: PPQCF
      JNDI Name: jms/SamplePPQCF
      Bus name wasA
      All other properties have default settings. The name and JNDI name properties match the same properties on the Version 5 JMS queue connection factory. The connection factory creates connections to the service integration bus called wasA.
    4. Click OK.
    5. Save your changes to the master configuration.
  3. Create version 6 JMS queues to replace the Version 5 JMS queues For example, use the version 6 WebSphere administrative console to complete the following steps for the input JMS queue:
    1. Display the collection list of JMS queues for the default messaging provider. Click Resources > JMS Providers > Default messaging provider > [Destinations] JMS queue
    2. Click New
    3. On the New JMS queue page, set the following properties for the JMS queue called InQ that is backed by the existing bus destination also called InQ:
      Name: InQ
      JNDI Name: jms/SampleInputQueue
      Queue name: InQ
      All other properties have default settings. The Queue name property specifies the name of the bus queue that is used to store and process messages for the JMS queue.
    4. Click OK This returns you to the collection list of JMS queues.
    5. Click New
    6. On the New JMS queue page, set the following properties for the JMS queue called OutQ that is backed by the existing bus destination also called OutQ:
      Name: OutQ
      JNDI Name: jms/SampleOutputQueue
      Queue name: OutQ
      All other properties have default settings. The Queue name property specifies the name of the bus queue that is used to store and process messages for the JMS queue.
    7. Click OK.
    8. Save your changes to the master configuration.
  4. Create a JMS activation specification to replace the Version 5 listener port. The JMS activation specification is used to deploy the MDB application as a JCA 1.5-compliant resource, as a listener on the JMS queue InQ. For example, use the version 6 WebSphere administrative console to complete the following steps:
    1. Display the collection list of JMS activation specifications for the default messaging provider. Click Resources > JMS Providers > Default messaging provider > [Activation Specifications] JMS activation specification
    2. Click New
    3. On the New JMS activation specification page, set the following properties:
      Name: PPAS
      Name: jms/SamplePPAS
      Destination JNDI Name: jms/SampleInputQueue
      All other properties have default settings.
    4. Click OK This returns you to the collection list of JMS activation specifications.
    5. Save your changes to the master configuration.
  5. Save your changes to the master configuration. After replacing the Version 5 JMS resources with version 6 equivalents, the MDB application scenario becomes as shown in the following figure:
    Figure 2. MDB application scenario after replacing the Version 5 JMS resources with version 6 JMS resources. The migrated scenario still uses the Version 5 JMS resources, but equivalent version 6 resources have been created for use by the MDB application when it has been redeployed as a JCA 1.5-compliant resource with the JMS activation specification. The version 6 resources are: a JMS queue connection factory, PPQCF; two JMS queues, InQ and OutQ; and a JMS activation specification, PPAS.
    This scenario shows the version 6 JMS resources.  For more information about this scenario, see the description that accompanies this figure.
  6. Redeploy the MDB application to use the JMS activation specification, as described in Deploying and managing applications. Ensure you select the Do not overwrite existing bindings option.
    Accept the defaults for all installation steps except for the following:
    • Delete the Listener Port binding
    • Set the activation specification binding to jms/SamplePPAS
  7. Click OK.
  8. If no other Version 5 applications use the WebSphere MQ client link, delete it.
    1. Display the list of WebSphere MQ client links for the messaging engine. Click Buses > wasA > Messaging engines > wasA.server1-wasA > WebSphere MQ client links
    2. Select the check box next to the link, Default.MQClientLink.
    3. Click Delete
    4. Click OK
  9. Save your changes to the master configuration.
You should now be able to use the MDB application with the version 6 JMS resources. On the Enterprise Applications panel, ensure that the MDB application is started. There should be no errors displayed in the console at this point. If there are any errors, check the SystemOut log for more information about the problem.
Related tasks
Migrating Version 5.x messages using the WebSphere message migration utility
Migrating a single node from Version 5 embedded messaging
Migrating a network deployment from Version 5 embedded messaging
Example: Migrating an MDB application from Version 5 embedded messaging - stage 1
Related reference
General considerations for migrating from Version 5 embedded messaging

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjn0044_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)