application server server1 Service integration bus wasA = Message flows JMS activationSpec PPAS MyMDB application JNDI Figure 7. MDB application scenario after replacing the Version 5.1 JMS resources with Version 7.0 JMS resources Chapter 7. Migrating Messaging resources 47
6. Redeploy the MDB application to use the JMS activation specification, as described in Deploying and administering enterprise applications. Ensure you select the Do not overwrite existing bindings option. Accept the defaults for all installation steps except for the following: v Delete the Listener Port binding v Set the activation specification binding to jms/SamplePPAS . 7. Click OK . 8. If no other Version 5.1 applications use the WebSphere MQ client link, delete it. a. Display the list of WebSphere MQ client links for the messaging engine. Click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional Properties] WebSphere MQ client links , where bus_name is wasA and engine_name is wasA.server1-wasA . b. Select the check box next to the link, Default.MQClientLink. c. Click Delete d. Click OK 9. Save your changes to the master configuration. Results You should now be able to use the MDB application with the JMS resources in the later version. On the Enterprise Applications panel ( Applications -> Application Types -> WebSphere enterprise applications ) ensure that the MDB application is started. There should be no errors displayed in the administrative console at this point. If there are any errors, check the SystemOut log for more information about the problem. Using a Version 5.1 JMS client There are certain limitations and restrictions to bear in mind when deciding whether to use a JMS client developed for WebSphere Application Server Version 5.1 with a later version of the product. About this task You can use a JMS client application developed for WebSphere Application Server Version 5.1 with a later version of the product without needing to recompile the application client. However, consider the following points: Procedure v A JMS client developed for WebSphere Application Server Version 5.1 can access JMS resources on a later version, which can be assigned to resources on a service integration bus, but cannot access directly default messaging JMS resources on that later version. Consider the JMS interoperation scenario, of a Version 5.1 JMS application that uses JMS resources provided by the default messaging provider on a node on a later version. The Version 5.1 JMS queue is backed by a bus queue, which is normal for a JMS queue on the later version, but there is no configured link between the Version 5.1 JMS queue and bus queue. The JMS application communicates with the bus queue through a WebSphere MQ client link and the messaging engine. To send messages to the bus queue or receive messages from the queue, the JMS application opens a connection on the WebSphere MQ client link. This is all invisible to the JMS application, but can be displayed and managed by the administrator.
You've reached the end of your free preview.
Want to read all 123 pages?
- Fall '19
- IBM WebSphere Application Server, Java Platform, Enterprise Edition, Java Community Process