| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| channel configuration - non-standard ports |
« View previous topic :: View next topic » |
| Author |
Message
|
| bduncan |
 Posted: Mon Jun 11, 2001 1:15 pm Post subject: |
 |
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
While setting up multiple queue managers on a single linux box (redhat 7.1) I learned a few things I thought I'd share.
First, redhat 7.1 does away with inetd.conf which is where I used to set up the channel listener (amqcrsta) service. It turns out that the updated Quick Beginnings guide for MQ on Linux actually says that the best way to manage the channel listeners is with the runmqlsr command. Aside from being more efficient, it also works nicely with redhat 7.1. You can also specify a port number when running the listener. Therefore, if you have 2 queue managers on the same box, they need to use different ports, which requires running two copies of the channel listener program.
When defining channels between the two queue managers, I assumed that I could specify the non-standard ports appending to the IP address much like I would when telneting into a box on a non-standard port. So my CONNAME attribute would look something like CONNAME(192.168.1.1:5000) where 5000 is my port number. Unfortunately MQSeries uses a slightly different syntax, and it took me a while to track this down, so I figured I'd share it. The port number is specified in parenthesis: CONNAME('192.168.1.1(5000)')
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
[ This Message was edited by: bduncan on 2001-08-17 09:05 ] |
|
| Back to top |
|
 |
| kolban |
| Posted: Mon Jun 11, 2001 5:10 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
In Redhat 7.1, it would appear that inetd has been replaced with a more sophisticated replacement called "xinetd". I am guessing that the "x" is for extended. As noticed, it has a different configuration set (not the old /etc/inetd.conf) but there appears to be a tool for converting an /etc/inetd.conf file to the new format (opinion: not needed since the new format is pretty clear). For basic information and sample configs, see the web site at
http://www.xinetd.org/
Neil |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jun 12, 2001 5:08 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
You are correct about xinetd. I should have mentioned that in my post - it looks like I stated inetd was completely done away with. It is relatively straightforward to configure MQ in redhat 7.1. Within the xinetd.d directory, you just need to create a new file called MQSeries (the structure of which is specified in the URL Kolban provided) in order to instruct the OS to launch amqcrsta. The quick beginnings guide for MQ5.2 on Linux says however, that this is not the optimal way to start the channel listener (which is a change from the quick beginnings guide for MQ v5.1) and that you should use the runmqlsr program. To make this program run constantly and start during bootup, add an entry to the inittab file, and give it the respawn parameter...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
