Versions Compared

Old Version 5

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 Enterprise Integrator's JMS transport with Microsoft Message Queuing (MSMQ). 

Info

The setup instruction here are only applicable for Windows environments since we invoke Microsoft C++ API for MSMQ via JNI invocations.

Note

From the below configurations, do the ones in the axis2.xml file based on the profile you use as follows:

  • To enable the JMS transport in the Integration profile, edit the <EI_HOME>/conf/axis2/axis2.xml file.
  • To enable the JMS transport in other profiles, edit the <EI_HOME>/wso2/<PROFILE_HOME>/conf/axis2/axis2.xml file. <PROFILE_HOME> refers to the main directory of the profile inside the WSO2 EI distribution. For example, to enable the JMS transport in the Business Process profile, edit the <EI_HOME>/wso2/business-process/conf/axis2/axis2.xml file

The msmq: component in WSO2 EI is a transport for working with MSMQ. This component natively sends and receives directly allocated ByteBuffer instances, allowing access to the JNI layer without memory copying. Using the ByteBuffer created with the method allocateDirect, the native code can directly access the memory. URI format is msmq:msmqQueueName.

Follow the steps below to set up and configure WSO2 EI with MSMQ. 

1. Download  Download the axis2-transport-msmq-12.10.0-wso2v6wso2v2.jar for 64x or 32x, and place that in  file and add it to the <EI_HOME>/dropins 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. This file provides the JNI invocation required by MSMQ bridging. 

2. Install Visual C++ 2008 (VC9). It works with Microsoft Visual Studio 2008 Express.

...

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

Setting up the JMS Listener

5. Add the following configuration to <EI_HOME>/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 <EI_HOME>/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 Integration Profile after configuring the 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.

...