In order to ensure proper shutdown of IIB servers during the shutdown phase of the Linux Operating system, during maintenance releases, patches, quick-fixes, and other routine restarts, it works best if they are kept under the control of the systemd. It is recommended not to use mqsistart and mqsistop to start or stop the broker.
Do you know?
IBM Integration Bus is a middleware product that enables the integration of different applications and services within an enterprise.
The mqsistart and mqsistop commands are typically used in a command-line interface or script to initiate the start or stop of an IBM Integration Bus (IIB) or WebSphere Message Broker integration nodes.
Example superuser: mqbrkr
Step-by-Step Instructions for Stopping, and Starting an Integration Node
Checking on the Integration Node
Login to the MQ Server via your credentials (Caution: don't sudo to mqbrkr).
Execute the command: "ps -aef|egrep -i mqbrkr|egrep -v egrep" [To see if the Integration Node is running].
If you don't receive any processes, then it means the service is not running.
If you receive output with processes, then it means the service is running.
Use the command to see if the Integration Broker is running as a systemd service: "systemctl status mqbroker".
If the service is not running as a systemd service, you will get a response like, Active: inactive (dead) since Wed 2023-12-22 11:24:00 EDT; 1 weeks 1 days ago.
If the service is running as a systemd service, you will get a response like, Active: active (running) since Wed 2023-12-22 11:24:00 EDT; 1 weeks 1 days ago.
Stopping an Integration Node
Login to the server, but don't sudo to the superuser: mqbrkr.
Use the above steps to make sure the status of an Integration Node.
If it is running as a service, use the following command to stop the service:
sudo -u root systemctl stop mqbroker.
Starting an Integration Node
Login to the server, but don't sudo to the superuser: mqbrkr.
Use the above steps to make sure the status of an Integration Node.
If you want it to run as a service, use the following command to stop the service:
sudo -u root systemctl start mqbroker.
Restarting an Integration Node
Login to the server, but don't sudo to the superuser: mqbrkr.
Use the above steps to make sure the status of an Integration Node.
If the services are running as a systemd service, use the following commands to restart the services.
sudo -u root systemctl restart mqbroker.
Do you know?
The use of systemctl will run the commands in the background and there are built-in delays in the process, so it may take time to execute. When you execute the command, you won't see any output on the terminal. For this, you may want to open an additional terminal window and run "tail -f /var/log/messages" to monitor the progress of the commands.
This way of stopping and starting the Integration Nodes doesn't work on servers running RHEL 6.0.
Comments