MQ setup in websphere

1        Run ActiveMQ Server

1.1      Download ActiveMQ 5.4.3 and Extract

http://www.apache.org/dyn/closer.cgi?path=%2Factivemq%2Fapache-activemq%2F5.4.3%2Fapache-activemq-5.4.3-bin.zip

1.2      Run the Server

In command line:

cd [ActiveMQ_extracted_directory]/bin

activemq

Now the ActiveMQ server is running.

1.3      Monitor Queues and Topics in ActiveMQ AdminConsole

The default URL of ActiveMQ admin console is: http://localhost:8161/admin/

2        Configure ActiveMQ as the WebSphere Generic JMSProvider

2.1      Put the Three Attached JAR Files under Directory[WAS6.1_RUNTIME_ROOT]/lib/ext/

2.2      Open WAS Admin Console

2.2.1      Resources àJMSàJMS providersàselect a scopeàNew

Name: ActiveMQmessaging provider (or any other name you want)

External initialcontext factory: com.sft.gec.activemq.jndi.ActiveMQWASInitialContextFactory

External providerURL: tcp://localhost:61616

2.2.2      In the page of ActiveMQ messaging provider, click“Custom properties” and add properties as below

Property Name	Property Value
java.naming.connectionFactoryNames	QueueConnectionFactory
java.naming.queue.GEC.SLE.EQLQ1	GEC.SLE.EQLQ1
java.naming.queue.GEC.SLE.EQLQ2	GEC.SLE.EQLQ2
java.naming.queue.GEC.SLE.EQLQ3	GEC.SLE.EQLQ3
java.naming.queue.GEC.SLE.EQLREJECT	GEC.SLE.EQLREJECT
java.naming.queue.SLE.GEC.EQLQ1	SLE.GEC.EQLQ1
java.naming.queue.SLE.GEC.EQLQ2	SLE.GEC.EQLQ2
java.naming.queue.SLE.GEC.EQLQ3	SLE.GEC.EQLQ3

In the property name java.naming.queue.xyz, xyz is the queue’sname, e.g. GEC.SLE.EQLQ1. It should be consistent with the correspondingproperty value.

If you want to create a topic, use java.naming.topic.xyz similarly.

If there’re multiple connection factory names, use comma to separatethem.

2.2.3      Back to the page of ActiveMQ messaging provider,click “Queue connection factories” and add the connection factory as below

Name: ActiveMQqueue connection factory (or any other name you want)

JNDI name: jms/gecEqlConnectionFactory(this should be consistent with the connection factory JNDI name configured inGEC Spring context file)

External JNDI name:QueueConnectionFactory (this should be consistent with the java.naming.connectionFactoryNamesproperty value you just added for ActiveMQ messaging provider)

2.2.4      Back to the page of ActiveMQ messaging provider,click “Queues” and add queues as below

Name (or any other name you want)	JNDI Name	External JNDI name
gecEqlQ1In	jms/gecEqlQ1In	GEC.SLE.EQLQ1
gecEqlQ2In	jms/gecEqlQ2In	GEC.SLE.EQLQ2
gecEqlQ3In	jms/gecEqlQ3In	GEC.SLE.EQLQ3
gecEqlQRIn	jms/gecEqlQRIn	GEC.SLE.EQLREJECT
gecEqlQ1Out	jms/gecEqlQ1Out	SLE.GEC.EQLQ1
gecEqlQ2Out	jms/gecEqlQ2Out	SLE.GEC.EQLQ2
gecEqlQ3Out	jms/gecEqlQ3Out	SLE.GEC.EQLQ3

2.3      Save All the Changes and Restart the Server

After GEC started, in the ActiveMQ admin console, you shouldbe able to see the four inbound queues (Q1, Q2, Q3 and QR) with one consumer oneach. It means that GEC is now listening on the four inbound queues.

The outbound queue won’t be visible until GEC sends messagesto it.