| Author |
Message
|
| kriersd |
 Posted: Tue Oct 29, 2002 6:46 am Post subject: How is the listener starting. |
 |
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Folks
We have installed Workflow on the AIX server. After I start up the Workflow service I can't see the listener running. I do know that the MQ Listener is in fact running, but I do not see it when I run the command "ps -ef | grep fmc". I see everything else except the listener. I faintly remember some documentation stating that the listener is started automaticly, but how? I would like to find where this is set and remove it. I would like to start the listener via a shell script.
Can anyone tell me what file Workflow modified at install to start up the listener?
Thanks..
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Oct 29, 2002 7:24 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Dave:
I'm not really a Unix guy, so this may be totally off base, but I seem to recall something about INETD.
Also, from the Install guide:
Starting MQSeries on UNIX
For any of the UNIX based operating platforms, all MQSeries services except the TCP/IP listener program must be started manually by entering MQSeries commands at a command prompt. The TCP/IP listener program is started automatically.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kp |
| Posted: Tue Oct 29, 2002 10:27 am Post subject: |
|
|
Novice
Joined: 16 Oct 2002
Posts: 15
Location: Belgium
|
Check /etc/inetd.conf and /etc/services.
As Workflow uses MQseries as middleware, it follows those standards.
In /etc/services the following line is added
fmcl <MQQueueManager><MQPort> <MQPort>/tcp #MQSeries
Where:
<MQQueueManager>
is the name for the MQSeries queue manager.
<MQPort>
is the TCP/IP port number (default 5010)
In /etc/inetd.conf you ll find
fmcl <MQQueueManager><MQPort>stream tcp nowait mqm
/usr /mqm/bin/amqcrsta amqcrsta -m <MQQueueManager>
You can delete that entry if you want. Don't forget to run refresh -s inetd to activate your changes.
You can now run your listener via a script using runmqlsr
Good luck,
KP |
|
| Back to top |
|
|
| olan022 |
| Posted: Tue Oct 29, 2002 12:17 pm Post subject: |
|
|
Acolyte
Joined: 17 Apr 2002
Posts: 50
|
After defining via RUNMQLSR or INETD, If you want to VERIFY that a listener is actually running, simply telnet to it. For instance, under Windows type
telnet MYSERVER 1414
If the listener is running, you will get a blank screen. Pressing several keys will eventually kill the connection.
If the listener is not running, you will get a connection failure message immediately. |
|
| Back to top |
|
|
| jc_squire |
| Posted: Tue Oct 29, 2002 1:04 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
fyi - if you successfully telnet to the host on the correct port and enter any sequence of characters it will generate ffst reports.
ctrl C will also kill the connection
regards
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| leongor |
| Posted: Wed Oct 30, 2002 1:40 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Listener when configured with INETD is amqcrsta process. It also can run with mqm user.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Oct 30, 2002 1:54 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Thanks a bunch guys..
I found the command used to start up the listener in the INETD file. This whole UNIX stuff is quite new to me..
Dave :lol:
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
