Deploying JMS application to connect to the Service Integration Bus running on WebSphere Application Server traditional

To deploy the messaging applications that use the Java™ Messaging Service (JMS) to connect to the messaging engine that is running on WebSphere® Application Server traditional, you must add the wasJmsClient-2.0 and jndi-1.0 features to the server.xml file. If you want to perform a JNDI lookup, then you must add the jndi-1.0 feature. You must also define the connection factory and destination properties.

Before you begin

Ensure that you created a Liberty server on which you want to deploy the messaging application that uses JMS. For more information, see Creación manual de un servidor de Liberty.

Important: La característica wasJmsClient-2.0 admite las características de las especificaciones JMS 1.1 y JMS 2.0. Sin embargo, puede decidir utilizar la característica wasJmsClient-1.1 si desea utilizar solamente las características que son compatibles con la especificación JMS 1.1.

About this task

The wasJmsClient-2.0 feature provides support for applications that use Java Messaging Service 1.1 specifications.

Procedure


Icono que indica el tipo de tema Tema de tarea



Icono de indicación de fecha y hora Última actualización: Tuesday, 6 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twlp_dep_msg_sibus
Nombre de archivo:twlp_dep_msg_sibus.html