Hasitha's Tech Blessings

The WebSphere installation directory will be reffered to as

1. Go to the /Java/bin directory and open the JSAdmin.config file with a text editor.
2. Comment out the existing INITIAL_CONTEXT_FACTORY and add a INITIAL_CONTEXT_FACTORY named com.sun.jndi.fscontext.RefFSContextFactory
3. Comment the default PROVIDER_URL and use a directory path instead. Make sure that directory is created in the file system (ex: C:/JNDI-Directory).

Note: If exists, delete any earlier versions of the .bindings files from that folder.



ex: After changing your JSAdmin.config file should look like this.

#  appropriate one should be uncommented.
#
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WMQInitialContextFactory
#
#  The following line specifies the URL of the service provider's initial
#  context. It currently refers to an LDAP root context. Examples of a
#  file system URL and WebSphere's JNDI namespace are also shown, commented
#  out.
#
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/C:/JNDI-Directory
#PROVIDER_URL=iiop://localhost/
#PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN
......

26. 
    

26. 4. Restart the IBM WebSphere service

1. Open the WebSphere MQ explorer and right click on Queue Manager and select New >Queue Manager.
2. Provide a name for the Queue Manager (myQueueManager) and Make it default. Press Next.
3. Select the options to Start Queue Manager, Autostart Queue Manager and Create server connection channel. Then press on Next.
4. Select the option to Create listener configuration for TCP/IP and provide a port number (1415).
5. Once the Queue Manager is created, right click on the Queues icon belonging to the queue manager (myQueueManager) and select New->Local Queue.
6. Provide a name for the Queue (myQueue) and press on Next. Go with the default configurations and press on Finish.
7. Right click on the Channels icon under the Advanced icon and select New > Server-connection Channel. Provide a name for the channel (myChannel) and press on Next. Set the transmission protocol as TCP and press on Finish.
8. Once these steps are completed, a listener will be created running on port 1415 and you should be able to view it by clicking on the listeners icon.

Generating .bindings file

1. RefFSContextFactory uses a file system url as the provider url. We are going to create a .bindings file inside C:/JNDI-Directory folder using JSAdmin.config file we prepared. Navigate to /Java/bin directory and run JMSAdmin.bat file.
2. create bindings as appropriate. You have to use the names of resources you have defined. You can choose JNDI names as you want.

Following is an example commands that goes with configs we have made under “Creating a queue on WebSphere MQ”. You can check created objects by display ctx command.

Welcome to the Admin Tool's command-line interface

InitCtx> def qcf(MQ_JMS_MANAGER) qmgr(myQueueManager) tran(client) chan(myChannel) host(175.157.120.102) port(1415)

InitCtx> def q(JMS_QUEUE) qmgr(myQueueManager) queue(myQueue)

InitCtx> display ctx

 Contents of InitCtx

     .bindings                 java.io.File

  a  JMS_QUEUE                 com.ibm.mq.jms.MQQueue

  a  MQ_JMS_MANAGER            com.ibm.mq.jms.MQQueueConnectionFactory

 3 Object(s)

   0 Context(s)

   3 Binding(s), 2 Administered

InitCtx> end

Stopping Websphere MQ classes for Java(tm) Message Service Administration

C:\IBM\WebSphere MQ\Java\bin>

Now go to C:/JNDI-Directory . You should be able to view .bindings file there.

The following configuration changes were made on the ESB for it to be able to remotely
communicate with WebSphere MQ.
The ESB installation directory will be reffered to as .

1. Copy C:/JNDI-Directory from above machine to a suitable place in new machine. We will consider this place in Ubuntu machine as /home/user/JNDI-Directory.
2. Copy all the jars found in the jar_files.zip attachment to the /repository/ components/lib directory. In addition, you have to copy fscontext.jar file found in /Java/lib directory as well.
3. Add the following jms transport receiver configuration to the /repository/ conf/axis2.xml file.

 <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="myQueueConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial" locked = "false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">file:/home/user/JNDI-Directory</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">MQ_JMS_MANAGER</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
<parameter name="transport.jms.Destination">JMS_QUEUE</parameter>
<parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
</parameter>

<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial" locked = "false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">file:/home/user/JNDI-Directory</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">MQ_JMS_MANAGER</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
<parameter name="transport.jms.Destination">JMS_QUEUE</parameter>
<parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
</parameter>
</transportReceiver>

The architecture which was decided and implemented is  as below. We used Apache  Cassandra as the Message Store and Apache Zookeeper for cluster synchronization. 

WSO2 MB 2.0 is am implementation of AMQP 0-91 specification with fully JMS support.

Apache Cassandra is an open source distributed database management system. It is designed to handle very large amounts of data spread out across many commodity servers while providing a highly available service with no single point of failure. It has very fast search schemes built in. Thus Cassandra is a good choice for WSO2 MB with clustering support. 

Zookeeper is used in WSO2 MB 2.0 to synchronize information among nodes of MB cluster when running in clustered mode. Zookeeper is lightweight and fast for communicating critical data.