[開発][JMS] Listener Port

env:
WAS + MQ

All the listener port really does is take the factory and bind it to the destination, and then manage the two. To create a port, go to Application Servers - (your server's name) - Message Listener Service. Here you'll create a port and assign it a JNDI name. This JNDI name will be used by your application to talk to the port. The guts of the port is pretty straightforward, just give it the JNDI names for the Connection Factory and Destination. The rest should work with the default values. Once you have that created, go back to the Listener Ports screen.

It's here that you'll probably want to add a little extra info in case your queue manager ever needs to be rebooted or taken down for short periods. We're going to add two custom properties: "MAX.RECOVERY.RETRIES" and "RECOVERY.RETRY.INTERVAL." This will let the Listener Port retry for the specified number of tries, and wait for however long you've set the interval to between tries. The interval value is in seconds.

tag:
Listener Port, WAS, MQ, MAX.RECOVERY.RETRIES, RECOVERY.RETRY.INTERVAL

ref:
Jonathan Forck, Message-Driven Beans in WebSphere -Use MQ Messaging for Many Processes-, October 3, 2005 11:00 AM EDT
http://websphere.sys-con.com/node/136459

tag : Message Listener Service Port WAS MQ MAX.RECOVERY.RETRIES RECOVERY.RETRY.INTERVAL

2009-12-05 17:51 : 開発 : コメント : 0 : トラックバック : 0 :
コメントの投稿
非公開コメント

« next  ホーム  prev »

search

ad



counter


tag cloud

category cloud