[jboss-svn-commits] JBL Code SVN: r36411 - in labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US: extras/configuration and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Dec 15 06:13:32 EST 2010
Author: tfennelly
Date: 2010-12-15 06:13:32 -0500 (Wed, 15 Dec 2010)
New Revision: 36411
Added:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-adapter-trace-enabled.txt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-01.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-02.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jms-provider-config-01.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-config.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt
Modified:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/websphere_msq_series.settings
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-xa-config.xmlt
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-xa-config.xmlt
Log:
https://issues.jboss.org/browse/JBESB-3497
Investiage Websphere MQ issue highlighted in SOA-2117
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml 2010-12-15 09:30:23 UTC (rev 36410)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml 2010-12-15 11:13:32 UTC (rev 36411)
@@ -386,31 +386,146 @@
</para>
</important>
- <orderedlist>
- <listitem>
<para>
- Set the main JNDI parameters for the <application>IBM
- Websphere MQ Series</application> to the following:
+ From a JBoss ESB perspective, configuring Websphere MQ providers is simple enough. You have 2 options:
+ <orderedlist>
+ <listitem><para>As a JCA Provider using the Websphere MQ JCA Adapter through the <jms-jca-provider> configuration.</para></listitem>
+ <listitem><para>As a Standard JMS Provider through the <jms-provider> configuration.</para></listitem>
+ </orderedlist>
</para>
+ <section id="websphere_mq_series_providers">
+ <title>
+ Websphere MQ JMS Provider Configurations
+ </title>
+ <para>
+ The following is an example of a <jms-jca-provider> configuration:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config-01.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ The above configuration is an example of how to configure a gateway provider through the <jms-jca-provider> configuration. The main
+ things to note of specific relevance to Websphere MQ are:
+ <orderedlist>
+ <listitem><para>The adapter name "wmq.jmsra.rar". This rar file must be present in the server's deploy folder.</para></listitem>
+ <listitem><para>The initial context factory "com.ibm.mq.jms.context.WMQInitialContextFactory".</para></listitem>
+ <listitem><para>The "queueManager" configuration in the <activation-config>. You need to configure a Queue Manager
+ in your Websphere MQ installation. All your Queues (all destinations) are configured under your Queue Manager.</para></listitem>
+ <listitem><para>The "channel" configuration in the <activation-config>. A Queue Manager can be configured with
+ a number of different types of "channels". Clients connect through "Server Connection" channels. A default server connection channel
+ is added as part of the Websphere MQ installation ("SYSTEM.DEF.SVRCONN"), but it is a good idea to specify your own dedicated channels, especially if
+ you are using extended (XA) transations. More on this later.
+ </para></listitem>
+ <listitem><para>The "transportType" configuration in the <activation-config>. Websphere MQ supports transport types "Client" and "Binding".</para></listitem>
+ </orderedlist>
+ </para>
+ <para>
+ We said that the above <jms-jca-provider> configuration is an example of how to configure a gateway provider. That's not strictly true; it's just
+ a provider configuration. It is the <jms-listener> configuration that determines the gateway/message-aware characteristics of a listener. What is true
+ to say about the above configuration however is that, as far as Websphere MQ is concerned, it is only of use as a provider to a gateway listener i.e. would not
+ work as a Message-Aware listener for Websphere MQ . This is because it does not specify an appropriate JNDI Provider URL (that can be used by the ServiceInvoker)
+ for routing ESB messages to the destinations (buses) defined on the provider. Note the <activation-config> configures the JCA adapter for getting messages
+ from the destinations. It does not specify any information used for delivering messages to the destinations. An example of a configuration that could be used as
+ a provider for a Message-Aware listener would be:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config-02.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ Creating a standard JMS provider configuration is more or less the same:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jms-provider-config-01.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ What you should note with the standard provider is that there's no adapter and <activation-config> configurations. Listeners getting messages from the destinations defined in
+ a standard provider do not use a JCA Adapter Inflow to receive the messages. Instead, they need to use JNDI to lookup the destination and get the messages. This
+ effectively means that for Websphere MQ, the jndi-URL must always be specified (remember that for JCA it is only required for destinations that service a Message-Aware
+ listener).
+ </para>
+ </section>
+ <section id="websphere_mq_series_jmsrouter">
+ <title>
+ JMSRouter Configuration for Websphere MQ
+ </title>
+ <para>
+ The following is an example of a JMSRouter configuration for routing messages to Websphere MQ from inside an ESB action pipeline:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jmsrouter-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </section>section>
+ <section id="websphere_mq_series_xa_transactions">
+
+ <title>
+ Websphere MQ and XA Transactions
+ </title>
+
+ <para>
+ If your Websphere MQ endpoint is to participate in JTA/XA Transactions you will need to install the "Extended Transactional Client" bundle from IBM.
+ This bundle may not be part of the default set of client jars provided with your Websphere MQ installation. If not, contact your IBM representative to get these jar files.
+ Once you have the Extended Client bundle, install the .jar files on your ESB/Application Server's classpath, as well as on the classpath of any
+ external client applications.
+ </para>
+ <para>
+ Before you can use extended transactions in WMQ, you need to
+ <ulink url="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/umj_pjcfm.html">configure XA Connection Factories in your WMQ JNDI namespace</ulink>.
+ Once you have configured the XA Connection Factories, you can reference them using their JNDI name in the "connection-factory" property of the JNDI connection property.
+ </para>
+ <para>
+ The following is an example showing how the <link linkend="jms_and_jca"><jms-jca-provider></link> configuration
+ would look for an Extended Transaction Client configuration, where the XA Connection Factory configured in the WMQ JNDI namespace is
+ called "WMQXAConnectionFactory". Inflow related configurations (adapter, <activation-config> etc) were intentionally omitted as
+ they are not relevant to the Extended Client configuration:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-xa-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ The following is an example of using an the same XA Connection Factory on the JMSRouter:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jmsrouter-xa-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+ <important>
+ <para>
+ An important point to note about Websphere MQ and XA is that it does not support both getting and putting messages concurrently on the same Queue Manager Channel. For this reason,
+ it is a good idea to configure a dedicated channel for each component that gets or puts messages into a Websphere MQ destination in the context of XA transactions.
+ </para>
+ </important>
+
+ </section>
+
+ <section id="websphere_mq_jca_tracing">
+
+ <title>
+ Enabling Tracing for Websphere MQ JCA Adapter
+ </title>
+
+ <para>
+ The WebSphere MQ resource adapter lets you configure diagnostic trace as a property on the resource adapter, or by setting JVM system properties.
+ With the JBoss ESB/Application, the recommended method is to use JVM system properties. On systems that use run.sh, you can set these by editing
+ the JBoss run.conf file (in the /bin directory) and appending the following onto the end of the file:
+ </para>
+ <programlisting><xi:include parse="text" href="extras/configuration/wmq-jca-adapter-trace-enabled.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+ <para>
+ Client logging can also be enabled by setting the additional MQJMS_TRACE_LEVEL property:
+ </para>
+ <programlisting><xi:include parse="text" href="extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+ </section>
+
+ <section id="websphere_mq_java_client_tracing">
+
+ <title>
+ Enabling Tracing for Websphere MQ Java Client
+ </title>
+
+ <para>
+ This is done programmatically by calling the "enableTrace" static method on the com.ibm.mq.MQEnvironment class.
+ </para>
+
+ </section>
- <programlisting><xi:include parse="text" href="extras/configuration/websphere_msq_series.settings" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <note>
- <para>
- <application>Websphere</application> queue names must be
- written in capitals and without any slashes (an example is
- <literal>QUEUEA</literal>). The <systemitem>queue
- manager</systemitem>'s name should match the value of
- <property>connection-factory</property> (one could also bind
- this name to JNDI.) In this example, the <systemitem>queue
- manager</systemitem> is named
- <property>ConnectionFactory</property>.
- </para>
- </note>
-
-</listitem>
+ <section id="websphere_mq_checklist">
+
+ <title>
+ Websphere MQ Gotchas and Checklist
+ </title>
-<listitem>
+ <orderedlist>
+ <listitem>
<para>
If using <systemitem>XA connections</systemitem>, set
the <property>max-xa-sessions-per-connection</property>
@@ -418,8 +533,23 @@
information on how to configure this property, see the
"Maximum Sessions per Connection" section of this chapter.)
</para>
-</listitem>
-<listitem>
+ </listitem>
+ <listitem>
+ <para>
+ If using <systemitem>XA connections</systemitem>, be sure to configure
+ a dedicated Queue Manager Channel for each component that gets or sets
+ messages into a Websphere MQ destination. See earlier section titled
+ "Websphere MQ and XA Transactions".
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Make sure the GET and PUT properties on all your Websphere MQ destinations
+ is not set to Inhibit. This can be set by default when the destination is created
+ and results in the ESB not being able to put/get messages.
+ </para>
+ </listitem>
+ <listitem>
<para>
Check that the following items are present on the class-path:
</para>
@@ -439,9 +569,15 @@
<listitem>
<para>
- <filename>com.ibm.mq.jar</filename> (client <filename>JAR</filename>
+ <filename>dhbcore.jar</filename>
</para>
</listitem>
+
+ <listitem>
+ <para>
+ <filename>com.ibm.mq.jar</filename> (client <filename>JAR</filename>)
+ </para>
+ </listitem>
<listitem>
<para>
@@ -455,6 +591,24 @@
</listitem>
</itemizedlist>
+ If using the Websphere MQ v7.0 Client jar files you will also need to add the following jar files to your classpath:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>com.ibm.mq.commonservices.jar</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>com.ibm.mq.headers.jar</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>com.ibm.mq.jmqi.jar</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
<note>
<para>
The client jars differ between MQ 5.3 and MQ 6.0. However the
@@ -482,47 +636,7 @@
</listitem>
</orderedlist>
- <para>
- If using JCA Inflow, you will need to configure the "adapter" attribute on the
- <jms-jca-provider> configuration and ensure that the JCA Adapter RAR file is
- in the ESB/Application Server's deploy folder:
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- Also, be sure to read the <link linkend="jms_and_jca">section on JMS and JCA</link>, as well as how to configure JCA <connection-factories> and AdminObjects for your JMS Destinations
- on JBoss Application Server.
- </para>
-
- <section id="websphere_mq_series_xa_transactions">
-
- <title>
- IBM Websphere MQ Series and XA Transactions
- </title>
-
- <para>
- If your Websphere MQ endpoint is to participate in JTA/XA Transactions you will need to install the "Extended Transactional Client" bundle from IBM.
- This bundle is not part of the default set of client jars for WMQ and is licensed separately. Contact your IBM representative to get these jar files.
- Once you have the Extended Client bundle, install the .jar files on your ESB/Application Server's classpath, as well as on the classpath of any
- external client applications.
- </para>
- <para>
- Before you can use extended transactions in WMQ, you need to
- <ulink url="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/umj_pjcfm.html">configure XA Connection Factories in your WMQ JNDI namespace</ulink>.
- Once you have configured the XA Connection Factories you can now reference them using their JNDI name in the "connection-factory" property of the JNDI connection property.
- </para>
- <para>
- The following is an example showing how the <link linkend="jms_and_jca"><jms-jca-provider></link> configuration
- would look for an Extended Transaction Client configuration, where the XA Connection Factory configured in the WMQ JNDI namespace is
- called "WMQXAConnectionFactory". Inflow related configurations (adapter, <activation-config> etc) were intentionally omitted as
- they are not relevant to the Extended Client configuration:
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-xa-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- These configurations are also relevant to a JMSRouter action configuration, using the same "WMQXAConnectionFactory":
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jmsrouter-xa-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-
- </section>
+ </section>
</section>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/websphere_msq_series.settings
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/websphere_msq_series.settings 2010-12-15 09:30:23 UTC (rev 36410)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/websphere_msq_series.settings 2010-12-15 11:13:32 UTC (rev 36411)
@@ -1,4 +1,4 @@
-jndi-URL="localhost:1414/SYSTEM.DEF.SVRCONN”
+jndi-URL="localhost:1414/SYSTEM.DEF.SVRCONN"
jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory"
connection-factory="ConnectionFactory"
destination-type="queue"
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-adapter-trace-enabled.txt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-adapter-trace-enabled.txt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-adapter-trace-enabled.txt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,3 @@
+# Settings to enable WebSphere MQ resource adapter trace
+JAVA_OPTS="$JAVA_OPTS -DtraceEnabled=true -DtraceDestination=wmq_jca.trc
+ -DtraceLevel=10 -DlogWriterEnabled=false"
\ No newline at end of file
Property changes on: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-adapter-trace-enabled.txt
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Name: svn:keywords
+ Id Revision
Name: svn:eol-style
+ LF
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-01.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-01.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-01.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,18 @@
+<jms-jca-provider name="WMQ-JCA" connection-factory="MyAppXAConnectionFactory" adapter="wmq.jmsra.rar"
+ jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
+
+ <property name="max-xa-sessions-per-connection" value="1" />
+
+ <jms-bus busid="quickstartGwChannel">
+ <jms-message-filter dest-type="QUEUE" dest-name="QUEUE1_JMS" transacted="true"/>
+ </jms-bus>
+
+ <activation-config>
+ <property name="queueManager" value="TQM" />
+ <property name="channel" value="Q1CONN" />
+ <property name="hostName" value="localhost" />
+ <property name="port" value="1414" />
+ <property name="transportType" value="CLIENT" />
+ </activation-config>
+
+</jms-jca-provider>
\ No newline at end of file
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-02.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-02.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-rar-config-02.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,19 @@
+<jms-jca-provider name="WMQ-JCA" connection-factory="MyAppXAConnectionFactory" adapter="wmq.jmsra.rar"
+ jndi-URL="localhost:1414/CHANX"
+ jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
+
+ <property name="max-xa-sessions-per-connection" value="1" />
+
+ <jms-bus busid="quickstartEsbChannel">
+ <jms-message-filter dest-type="QUEUE" dest-name="QUEUE2_JMS" transacted="true"/>
+ </jms-bus>
+
+ <activation-config>
+ <property name="queueManager" value="TQM" />
+ <property name="channel" value="Q2CONN" />
+ <property name="hostName" value="localhost" />
+ <property name="port" value="1414" />
+ <property name="transportType" value="CLIENT" />
+ </activation-config>
+
+</jms-jca-provider>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-xa-config.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-xa-config.xmlt 2010-12-15 09:30:23 UTC (rev 36410)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jca-provider-xa-config.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -1,5 +1,5 @@
<jms-jca-provider name="WMQ" connection-factory="WMQXAConnectionFactory"
- jndi-URL="wmqserver:1414/SYSTEM.DEF.SVRCONN"
+ jndi-URL="wmqserver:1414/CHANXA_SEND"
jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
<property name="max-xa-sessions-per-connection" value="1" />
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jms-provider-config-01.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jms-provider-config-01.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jms-provider-config-01.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,9 @@
+<jms-provider name="JMS" connection-factory="MyAppConnectionFactory"
+ jndi-URL="localhost:1414/CHAN1"
+ jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory">
+
+ <jms-bus busid="quickstartGwChannel2">
+ <jms-message-filter dest-type="QUEUE" dest-name="QUEUE3_JMS" />
+ </jms-bus>
+
+</jms-provider>
\ No newline at end of file
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-config.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-config.xmlt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-config.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,6 @@
+<action name="routeToORDERSQueue" class="org.jboss.soa.esb.actions.routing.JMSRouter">
+ <property name="jndi-context-factory" value="com.ibm.mq.jms.context.WMQInitialContextFactory"/>
+ <property name="jndi-URL" value="wmqserver:1414/CHANX"/>
+ <property name="connection-factory" value="WMQConnectionFactory"/>
+ <property name="jndiName" value="ORDERS"/>
+</action>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-xa-config.xmlt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-xa-config.xmlt 2010-12-15 09:30:23 UTC (rev 36410)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmq-jmsrouter-xa-config.xmlt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -1,6 +1,6 @@
<action name="routeToORDERSQueue" class="org.jboss.soa.esb.actions.routing.JMSRouter">
<property name="jndi-context-factory" value="com.ibm.mq.jms.context.WMQInitialContextFactory"/>
- <property name="jndi-URL" value="wmqserver:1414/SYSTEM.DEF.SVRCONN"/>
+ <property name="jndi-URL" value="wmqserver:1414/CHANXA_SEND"/>
<property name="connection-factory" value="WMQXAConnectionFactory"/>
<property name="jndiName" value="ORDERS"/>
<property name="max-xa-sessions-per-connection" value="1"/>
Added: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt (rev 0)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt 2010-12-15 11:13:32 UTC (rev 36411)
@@ -0,0 +1,3 @@
+# Settings to enable WebSphere MQ resource adapter and client trace
+JAVA_OPTS="$JAVA_OPTS -DtraceEnabled=true -DtraceDestination=wmq_jca.trc
+ -DtraceLevel=10 -DlogWriterEnabled=false -DMQJMS_TRACE_LEVEL=base"
\ No newline at end of file
Property changes on: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/extras/configuration/wmqjca-adapter-and-client-trace-enabled.txt
___________________________________________________________________
Name: svn:mime-type
+ text/plain
Name: svn:keywords
+ Id Revision
Name: svn:eol-style
+ LF
More information about the jboss-svn-commits
mailing list