Versions Compared

Old Version 4

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section describes how to configure the WSO2 ESB's JMS transport with Microsoft Message Queuing (MSMQ). 

...

1. Download axis2-transport-msmq-1.1.0-wso2v6wso2v9.jar for jar for 64x or 32x, and place that in <ESB_HOME>/repository/components/dropins directory. MSMQ bridging requires JNI invocation, and WSO2 ships two dlls for 64bit and 32bit O/S respectively. Therefore, make sure you download the correct file suitable for your environment.

...

4. If you haven't already, download and install WSO2 ESB as described in Getting Started . 

Setting up the JMS Listener

5. Add the following configuration to <ESB_HOME>/repository/conf/axis2/axis2.xml file.

Code Block
languagehtml/xml
<transportReceiver name="msmq" class="org.apache.axis2.transport.msmq.MSMQListener">
     <parameter name="msmq.receiver.host" locked="false">localhost</parameter>
</transportReceiver>

Setting up the JMS Sender

6. To enable the JMS transport sender, add the following JMS transport listener configuration in <ESB_HOME>/repository/conf/axis2/axis2.xml file. 

Code Block
languagehtml/xml
<transportSender name="msmq" class="org.apache.axis2.transport.msmq.MSMQSender"/>
Info

If you get an error message similar to the following when you start the server after configuring WSO2 ESB's JMS transport with MSMQ, you must check whether the msvcr100d.dll file is available in the C:\Windows\System32 directory. If the file is not available, you need to download the file and copy it to the C:\Windows\System32 directory.

Code Block
ERROR - NativeWorkerPool Uncaught exception
java.lang.UnsatisfiedLinkError: no msmq_native_support in java.library.path


Tip

For details on the JMS configuration parameters used in the code segments above, see JMS Connection Factory Parameters.

 

You now have instances of MSMQ and WSO2 ESB configured, up and running. Next, refer to section JMS Usecases for implementation details of various JMS use cases.