Link: Added: This issue depends JBESB-2500

Link: Added: This issue is a dependency of SOA-1247

Additional input from Jirka:

We also need to document adding the WSMQ datasource (to enable the JNDI provider integration)

An example is here:  

   http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-it-jms-providers/JMS_PROVIDER=wsmq,jdk=java15,label=soa3-RHEL5-x86/ws/jbosssoa/jboss-
as/server/oracle/deploy/wsmq-jms-ds.xml

Assigning to Darrin to fix the docs

And - we have to have the same information written here (in the Admin guide):
     1.3.4.2. JCA Adapter

1.3.4.2. JCA Adapter 

The default installation of IBM Websphere MQ Version 6 does not include the WMQ JCA Adapter. 

Procedure 1.1. Setting up the WMQ JCA Adapter 
1 - Update IBM Websphere MQ V6 
You need to update your Websphere MQ installation to at least version 6.0.2.1 to get the JCA Adapter. 

2 - Deploy the adapter to the SOA Platform server 
The WMQ JCA Adapter, wmq.jmsra.rar, is found in the Java/lib/jca/ directory of your WebSphereMQ installation. To deploy the adapter, copy this file to the deploy directory of your SOA Platform server, ${SOA_ROOT}/server/${CONFIG}/deploy/. 

3 - Create a JCA Connection Factory configuration 
To configure the SOA Platform server to use the WMQ JCA Adapter you have to create a JCA Connection Factory configuration file. The filename does not matter but should be descriptive, e.g. wsmq-jms-ds.xml. This configuration has to be copied into the deploy directory of the SOA Platform Server, ${SOA_ROOT}/server/{CONFIG}/deploy/. 

      [FIRST CODE SAMPLE] 

The JCA Adapter is now available and can be accessed using the configured connection factory. 

In your ESB configuration, you can now use this connection factory through the JCA Provider configuration to provide transactional context. The following example does this in ${SOA_ROOT}/server/${CONFIG}/deploy/jbpm.esb/META-INF/jboss-esb.xml. 

      [SECOND CODE SAMPLE] 

Closing this - received feedback from Tom F. that the updated text for the docs is correct.