Starting an integration server

You can start an integration server and all the deployed resources in an integration server by using the IBM® Integration Toolkit, the web user interface, or a command.

About this task

If resources are deployed to your integration server, the started or stopped state of the resources is retained when you next start the integration server.

To start an integration server, you can use any of the following instructions:

Starting an integration server by using the IBM Integration Toolkit

About this task

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

Procedure

  1. Open the IBM Integration Toolkit, and switch to the Integration Development perspective.
  2. In the Integration Nodes view, expand your integration node.
  3. Right-click the integration server, and click Start.

Results

A message is sent to the integration node to start the selected integration server.

Starting an integration server by using the web user interface

About this task

To start an integration server by using the web user interface:

Procedure

  1. Start the web user interface for your integration node; see Accessing the web user interface.
    The navigator is displayed on the left side of the pane, showing the servers (integration servers), message flows, and other resources that are owned by your integration node.
  2. In the navigator, expand Servers.
  3. Click the down arrow beside the integration server to display the menu, and then click Start.

Results

A message is sent to the integration node to start the selected integration server.

Starting an integration server with the mqsistartmsgflow command

About this task

To start an integration server by using the mqsistartmsgflow command:

Procedure

  1. Open a command line for your current installation.
  2. Enter the mqsistartmsgflow command, specifying the parameters for the integration server that you want to start.
    • If the integration node is local, specify the integration node name. For example:
      mqsistartmsgflow IBNODE -e default
    • If the integration node is remote, you can specify a configuration file. For example:
      mqsistartmsgflow -n IBNODE.broker -e default
    • If the integration node is remote, you can alternatively specify one or more of the connection parameters -i or -p. For example:
      mqsistartmsgflow -e default
    • If you want to start all the integration servers on an integration node, specify the -g flag instead of -e.For example:
      mqsistartmsgflow IBNODE -g
    See the mqsistartmsgflow command description for more details about these options.

What to do next

Start or stop resources that are deployed on your integration server; see Starting or stopping deployed resources.