Configured Services - JMS
Jms In version 10.x, high-level JMS configuration is provided and grouped as distinct JMS Servers. This includes configuration like the persistence store for destinations —which are set individually for each destination in JBoss. JMS resources in WebLogic are configured by the insertion of XML snippets in the config.xml of the domain. An XML element called will specify which server or cluster the JMS resource is to be deployed to and the will point to the JMS configuration details, including connection factories and actual destinations. Configuration details for JMS resources are typically found under the jms directory of the domain’s config directory in WebLogic 10.x. In JBoss, JMS connection factories are typically configured in the deploy/jboss-messaging.sar/connection-factories-service.xml file of a JBoss server, but can generally be configured as part of any service archive deployment. It is more typically the destinations themselves — the queues and topics —which need to be configured and deployed to support each application. In JBoss, it is enough to create a JMS destination XML snippet for each queue or topic, which may be provided in its own destination-service.xml file or combined collectively in the same *-service.xml file. The content of such a destination XML file in JBoss will resemble that of any MBean deployment file, and the MBean code will be QueueService or TopicService as the case may require. Red Hat Consulting Strategic Migration Planning Guidewww.jboss.com 9 The destination configuration details can be found in the matching *-jms.xml file under the config/jms directory of the WebLogic domain. In WebLogic, each individual queue or topic is deployed to a server or cluster by specifying a XML element in the main config XML file. The corresponding destination XML file would be deployed to the JBoss server or cluster, possibly by dropping it in the server’s deploy directory or one of the cluster members’ farm directory