a. Open the Weblogic Console by hitting the URL
b.Enter the valid credentials and click on Login button.
c. On the home page click on the deployments located on extreme left side of the page
d.In the deployments click on the MQSeriesAdapter.
e.On the SettingsforMQSeriesAdapter click on the Configuration tab.
f.In the configuration tab click on the OutboundConnectionPools. Here we will specify Outbound connection properties JNDI to connect to MQ.
g.On the OutboundConnectionsPools tab you will be able to see javax.resource.cci.ConnetionFactory under which eis/MQ/MQAdapter Connection Factory is already created.
h.Click on the new button to create the connection factory to connect to your MQ.
i.It will open Create a New Outbound Connection dialogue. In Outbound Connection Groups select javax.resource.cci.ConnectionFactory and click on next
j.In next screen you need to give the JNDI name for your connection. It should be same as you configured in JDEV which is eis/MQ/MQSeriesAdapter. Please have a look at step k of section 2.2. After entering the JNDI name click on Finish.
k.You will and to Outbound Connection Pools tab and you will find your connection factory listed there.
l.Click on your connection factory and you will land to Properties tab.
Configure the following properties:
•channelName – MQChannel name configured on MQ server for your QueueManager. In our case it is MYCHANNEL.
•connectionFactoryLocation - MQAdapter.ConnectionFactory
•hostname – Hostname of the server where MQ is installed.
•portNumber – Port Number where the MQlistener configured for QueueManager is listening. In our case it is 7001.
•QueueManagerName - Name of the QueueManager.
•SSLEnable – false
•XATransaction - false.
m.Now go to Deployments and click check MQSeriesAdapter and click on update button present at the top of the deployment table.
n.After that in Update Application Assistant Window keep the default values
o. Copy com.ibm.mq.jar in domain/lib folder and restart the server.
p. On next page click on finish button. You are ready to use the MQAdapter
b.Enter the valid credentials and click on Login button.
c. On the home page click on the deployments located on extreme left side of the page
d.In the deployments click on the MQSeriesAdapter.
e.On the SettingsforMQSeriesAdapter click on the Configuration tab.
f.In the configuration tab click on the OutboundConnectionPools. Here we will specify Outbound connection properties JNDI to connect to MQ.
g.On the OutboundConnectionsPools tab you will be able to see javax.resource.cci.ConnetionFactory under which eis/MQ/MQAdapter Connection Factory is already created.
h.Click on the new button to create the connection factory to connect to your MQ.
i.It will open Create a New Outbound Connection dialogue. In Outbound Connection Groups select javax.resource.cci.ConnectionFactory and click on next
j.In next screen you need to give the JNDI name for your connection. It should be same as you configured in JDEV which is eis/MQ/MQSeriesAdapter. Please have a look at step k of section 2.2. After entering the JNDI name click on Finish.
k.You will and to Outbound Connection Pools tab and you will find your connection factory listed there.
l.Click on your connection factory and you will land to Properties tab.
Configure the following properties:
•channelName – MQChannel name configured on MQ server for your QueueManager. In our case it is MYCHANNEL.
•connectionFactoryLocation - MQAdapter.ConnectionFactory
•hostname – Hostname of the server where MQ is installed.
•portNumber – Port Number where the MQlistener configured for QueueManager is listening. In our case it is 7001.
•QueueManagerName - Name of the QueueManager.
•SSLEnable – false
•XATransaction - false.
m.Now go to Deployments and click check MQSeriesAdapter and click on update button present at the top of the deployment table.
n.After that in Update Application Assistant Window keep the default values
o. Copy com.ibm.mq.jar in domain/lib folder and restart the server.
p. On next page click on finish button. You are ready to use the MQAdapter
hi, Can OSB service call IBM JMS directly or not ?
ReplyDelete