Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Start mq on Solaris
- Thread starter venom666
- Start date
- Thread starter
- #3
Thanks Dilber
But the quick beggings only shows a manual process for starting everthing.
What I need is an automated way of starting everything up
Do I just put the following in an .rc script in the following order ???
1. strmqm
2. Start a WebSphere MQ listener as a background task by entering the following
command: runmqlsr -t tcp &
3. On the sender workstation, start the sender channel as a background task by
entering the following command:
runmqchl -c FIRST.CHANNEL -m saturn.queue.manager &
4. strmqcsv ...qmanager name
But the quick beggings only shows a manual process for starting everthing.
What I need is an automated way of starting everything up
Do I just put the following in an .rc script in the following order ???
1. strmqm
2. Start a WebSphere MQ listener as a background task by entering the following
command: runmqlsr -t tcp &
3. On the sender workstation, start the sender channel as a background task by
entering the following command:
runmqchl -c FIRST.CHANNEL -m saturn.queue.manager &
4. strmqcsv ...qmanager name
Dont think you are going to achieve anything out of writing a script for this, other than avoiding each time to manually type these commands and execute them. What is that you wish to achieve off this anyways.
Otherwise, you should also include the queue manager name unless you have a default queue manager created. Also include the port number on runmqlsr command so as to avoid confusion as to which port your listener is listening at. By default it listens on 1414 though. No point in having a channel run in the background. You need the command server only if you are doing any PCF activity or client connections.
Hope this helps.
Cheers
KK
Otherwise, you should also include the queue manager name unless you have a default queue manager created. Also include the port number on runmqlsr command so as to avoid confusion as to which port your listener is listening at. By default it listens on 1414 though. No point in having a channel run in the background. You need the command server only if you are doing any PCF activity or client connections.
Hope this helps.
Cheers
KK
- Thread starter
- #5
If you like to start everything up after a reboot,
1. Create a script under /etc/init.d which will take start,stop parameter to start/stop queue manager,listerner,channel inititor,etc.
2. Under /etc/rc1.d, create Kxxmqm to link to the script of /etc/init.d. (xx is two digit number).
3. Under /etc/rc3.d, create Sxxmqm file to link to the script under /etc/init.d. (xx is two digit number).
Usually you need put all these into SystemV package and install them automatically as root.
1. Create a script under /etc/init.d which will take start,stop parameter to start/stop queue manager,listerner,channel inititor,etc.
2. Under /etc/rc1.d, create Kxxmqm to link to the script of /etc/init.d. (xx is two digit number).
3. Under /etc/rc3.d, create Sxxmqm file to link to the script under /etc/init.d. (xx is two digit number).
Usually you need put all these into SystemV package and install them automatically as root.
- Status
Similar threads
- Locked
- Question