Deploying the Connection Factories and Destinations (SAP Library

Deploying the Connection Factories and Destinations

All the work you did with the JMS Connector service, can also be done by passing the deployment framework of the AS Java two XML descriptors, meaning that you can deploy your connection factories and destinations. One way of achieving this is to package these descriptors in the Enterprise Archive (EAR) file of the application, if your JMS client is residing on the server. The descriptors (jms-destinations.xml and jms-factories.xml) must be put under the META-INF directory of the EAR file.

For more information about how to deploy the connection factories and destinations, see: Deploying, Updating and Undeploying a J2EE Application.

Example jms-factories.xml

<jms-factories>

<application-name>

JMSTestApplication

</application-name>

<connection-factory>

<factory-name>

QueueConnFactory

</factory-name>

<context-factory-type>

<link-factory-name>

jmsfactory/default/QueueConnectionFactory

</link-factory-name>

<initial-context-factory>

com.sap.engine.services.jndi.InitialContextFactoryImpl

</initial-context-factory>

<provider-url>

localhost

</provider-url>

<security-principal>

</security-principal>

<security-credentials>

</security-credentials>

</context-factory-type>

<user-name>

Administrator

</user-name>

abc123

</password>

</connection-factory>

</jms-factories>

Example for jms-destinations.xml

<jms-destinations>

<application-name>

JMSTestApplication

</application-name>

<connection-factory>

QueueConnFactory

</connection-factory>

<destination-name>

JMSTestQueue

</destination-name>

</destination>

</jms-destinations>

Next Step

JMS Client Example