To begin administering the system, you must start all necessary components of IBM WebSphere InterChange Server Express.
The recommended order for starting up the system is: IBM WebSphere MQ Listener, IBM WebSphere InterChange Server Express, and IBM WebSphere System Manager. Connectors are automatically started when you start InterChange Server Express.
There is some flexibility for starting components. MQ Listener can be started later, however, the connectors that depend on it are started in a paused state. System Manager can be open at any time, but you must connect to the server instance again after WebSphere InterChange Server Express is started. The only required order for starting components is if you are using IBM Java Object Request Broker (ORB) located on a different machine than WebSphere InterChange Server Express, you must start the ORB before starting WebSphere InterChange Server Express.
When shutting down an instance of WebSphere InterChange Server Express, you have two choices. You can shut down the system gracefully or immediately. A graceful shutdown allows the system to complete work that is in progress before shutting down, whereas an immediate shutdown stops the system without allowing pending events to process.
Before you can start the InterChange Server Express system, make sure all of the necessary third-party software is running. This includes the database on which the InterChange Server Express repository resides. This section assumes that you have already started the system and loaded the repository. If you are starting the system for the first time, refer to the WebSphere Business Integration Server Express installation guide for Windows, for Linux, or for OS/400.
When starting up the system, all connectors and collaborations start in the state they were in at the time they were last shut down. For example, if a collaboration was paused at shutdown, it is paused when the system is started again.
The following tasks describe the recommended order to start the system:
(For OS/400 MQ Listener is started automatically when the server is started.)