Starting and stopping an integration node on Windows, Linux, and UNIX systems

Use the mqsistart or mqsistop commands to start or stop an integration node.

Before you begin

Ensure that your user ID has the correct authorizations to perform the task. Refer to Security requirements for administrative tasks.
On Linux®, UNIX, and Windows systems, you must set up your command prompt environment before you perform this task, by running the product profile or console; see Setting up a command environment.
When you start an integration node, all integration servers under that node are started automatically unless one of the following conditions applies:
1. The integration node was stopped by using the mqsistop command, the Enterprise Toolkit, or the web user interface.
2. You specified that an integration server must not be started. To specify that an integration server must not be started automatically, add an empty file that is named .stopped into the server's directory; for example:
```
C:\myACEwork\components\NODEIPL101\servers\ISDEVIPLAA\.stopped
```
If you use the mqsistop command or the Enterprise Toolkit or web user interface to stop an integration server, a .stopped file is added to the server's directory. When the integration node is next restarted, the integration server is not started automatically (unless the .stopped file is deleted before the integration node is started).

Procedure

Optional: On Windows, if the integration node is configured to use an IBM® App Connect Enterprise vault, copy the .mqsivaultrc file into the directory that is referenced by the environment variable MQSI_WORKPATH. The default value for MQSI_WORKPATH is C:\ProgramData\IBM\MQSI.
For more information about IBM App Connect Enterprise vaults and the .mqsivaultrc file, see mqsicreatebroker command - Windows systems and mqsivault command.
To start an integration node, enter the following command on the command line:
```
mqsistart INODE
```
Substitute your own integration node name for INODE.

To start an associated queue manager for the integration node, use the strmqm command. For more information, see the topic Starting and stopping a queue manager in the IBM MQ documentation.
The integration node is started. If you are using Windows, the command initiates the Windows service for the integration node.
You can check that the integration node is running by using the mqsilist command; for example:
```
mqsilist
...
BIP1325I: Integration node 'NODEIPL101' with administration URI 'http://<host>:4417' is running.
```
You can also check that the integration node initialized successfully by reviewing the following logs:
- On Windows, check the Application Log in the Event Viewer.
- On Linux and UNIX, check the system log.
The log contains messages about verification procedures. If all tests are successful, only an initial start message is recorded. If one or more verification tests are unsuccessful, the log also includes messages that provide details of the tests that failed. If errors are reported, review the messages, and take the suggested actions to resolve these problems.
To stop an integration node, enter the following command on the command line:
```
mqsistop INODE
```
Substitute your own integration node name for INODE.

To stop the associated queue manager, run the endmqm command. For more information, see the topic Starting and stopping a queue manager in the IBM MQ documentation.
You can check that the integration node is stopped by using the mqsilist command; for example:
```
mqsilist
...
BIP1326I: Integration node 'ACE02NODE' is stopped.
```

What to do next

For more information about verifying the status of an integration node, see Verifying an integration node.