IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Stopping an integration server using the IBM Integration Toolkit or IBM Integration Explorer

You can stop all the message flows in an integration server by using the IBM® Integration Toolkit or IBM Integration Explorer.

If resources are deployed to your integration server, the started or stopped state of the message flows is remembered when you stop the integration server. You can use the menu to start or stop all message flows before the integration server has been stopped.

If you prefer, you can stop integration servers by using the mqsistopmsgflow command.

The broker processes all inflight messages and associated transactions for each message flow before stopping it. See Message flow transactions for information on how outstanding units of work are handled in this situation.

Stopping an integration server with the IBM Integration Toolkit

To stop an integration server by using the IBM Integration Toolkit:

Open the IBM Integration Toolkit, and switch to the Integration Development perspective.
In the Integration Nodes view, expand your broker.
Right-click the integration server, and click Stop.

A message is sent to the broker to stop the selected integration server.

Stopping an integration server with the IBM Integration Explorer

To stop an integration server by using the IBM Integration Explorer:

Open the IBM Integration Explorer.
In the Navigator view, expand the Integration Nodes folder.
Expand your broker.
Right-click the integration server, and click Stop > Integration Server.

A message is sent to the broker to stop the selected integration server.

Stopping an integration server with the mqsistopmsgflow command

To stop an integration server by using the mqsistopmsgflow command:

Open a command prompt that has the environment configured for your current installation.
Enter the mqsistopmsgflow command, specifying the parameters for the integration server that you want to stop.
- If the broker is local, specify the broker name. For example:
```
mqsistopmsgflow IB9NODE -e EGroup_2
```
- If the broker is remote, you can specify a configuration file. For example:
```
mqsistopmsgflow -n IB9NODE.broker -e EGroup_2
```
- If the broker is remote, you can alternatively specify one or more of the connection parameters -i, -p, -q. For example:
```
mqsistopmsgflow -q IB9QMGR -e EGroup_2
```

If you want to stop all the integration servers on a broker, specify the -g flag instead of -e.

See the mqsistopmsgflow command description for more details about these options.

be10150_.htm |

Last updated Friday, 21 July 2017