High Quality JMS Messaging.

Deploy the Resource Adapter

The first action is to deploy SwiftMQ's JCA 1.5 Resource Adapter.

The Resource Adapter is located as RAR archive in the "j2ee" directory of the SwiftMQ distribution. It is provided in 2 versions. One (swiftmq.rar) is to access a remote SwiftMQ Router and the other (swiftmq-ivm.rar) is to start a SwiftMQ Router intraVM. Both only differ in the default configuration of the Resource Adapter. We will use "swiftmq-ivm.rar".

Start WebSphere Application Server and connect with the administration console and log in. On the left side expand the node "Resources" and click on "Resource Adapters":

On the right panel you will now see the list of installed Resource Adapters:

Click on "Install RAR". This will open another panel in which you can choose the RAR file you want to install. Choose "Local Path" and use the "Browse" button to locate the file "swiftmq-ivm.rar" in the "j2ee" directory of your SwiftMQ distribution:

Click on "Next". The next panel allows you to configure the Resource Adapter. This is not necessary so click "Ok":

Now we are back to the list of installed Resource Adapters and you will see SwiftMQ's Resource Adapter in the list. Don't save the configuration because you have to configure the Resource Adapter.

Click on "SwiftMQ JMS Resource Adapter". This brings you back to the "Configuration" panel. But now you see a list of links to configure additional properties:

Click on "Custom Properties" to configure the properties of the Resource Adapter:

Now you will see all properties you can configure for SwiftMQ's Resource Adapter. The only property you need to configure is the "RouterWorkingDirectory". Click on "RouterWorkingDirectory" and enter the full path of the directory where the "smqr1" script is located. In our example this is "D:/temp/ttt9/swiftmq_5_2_0_jmsplus/scripts/win32":

Click "Ok". Now you can save the configuration:

Everything is now properly configured. You need to restart WebSphere in order to start the Resource Adapter. After restart please have a look in WebSphere's SystemOut.log to verify that the SwiftMQ Router is started from the Resource Adapter.