IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Creating an integration node by using the command line

On Linux, UNIX and Windows, you can create integration nodes on the command line.

Before you begin

About this task

When you create an integration node, you can optionally specify a queue manager for the integration node. If you do not specify a queue manager, features that require access to WebSphere MQ will be unavailable. For more information about using WebSphere MQ with IBM App Connect Enterprise, see Enhanced flexibility in interactions with IBM MQ and Installing IBM MQ.

When you create an integration node, you can optionally use the -w workPath parameter to specify a working directory within which work files for the integration node are stored. If you do not specify this parameter, the files are stored in a subdirectory of the IBM App Connect Enterprise working directory, which was set when the product was installed.

To create an integration node by using the command line, complete the following steps:

Procedure

  1. Ensure that you have the authority to create an integration node by following the steps for your operating system:
    • Linux platformUNIX platformOn Linux and UNIX, ensure that you are logged in using a user ID that has authority to run the mqsicreatebroker command.

      Run the mqsiprofile script to set up the command environment for the integration node:

      install_dir/server/bin/mqsiprofile

      You must run this script before you can run the IBM App Connect Enterprise commands.

      For more information, see Setting up a command environment.

    • Windows platformOn Windows, open an IBM App Connect Enterprise command prompt for the runtime installation in which you want to create the integration node. For more information about initializing the runtime environment, see Setting up a command environment.

      On Windows systems, you must open a command console with elevated privileges.

  2. Use the mqsicreatebroker command to create the integration node.
    For example, if you want to create an integration node that is called INODE with a queue manager that is called ACEQMGR, enter the following command:
    mqsicreatebroker INODE -i wbrkuid -a wbrkpw -q ACEQMGR
    Where wbrkuid and wbrkpw are the user name and password under which the integration node runs.
    Note: You can specify a queue manager name that does not exist, but the specified queue manager must be running before you start your integration node.

    When you create your first integration node, the web user interface uses the default port 4414, and the port number increments by one for each integration node created after. You can disable the web user interface or change the port on which it runs by using the mqsichangeproperties command. If administration security is not enabled, web users can access the web user interface as a default user with unrestricted access to data and integration node resources.

    For more information about the command parameters, see mqsicreatebroker command.

Results

You have created an integration node.

What to do next

  1. Start the integration node by using the mqsistart node_name command. See Starting and stopping an integration node on Windows and Linux systems.
  2. If you want to work with the integration node in the IBM App Connect Enterprise Toolkit (or a custom integration application), connect the toolkit to the integration node. For example, connect to the integration node before you can use the Enterprise Toolkit to start the node's web user interface or create integration servers associated with the integration node. See Connecting the Enterprise Toolkit to an integration node.
  3. If you want to use the web user interface to manage the integration node's integration servers and their resources, start the web user interface using the administration URI (hostname and port) configured for the integration node. The hostname and port are reported by the mqsilist command; for example:
    mqsilist
    ...
    BIP1325I: Integration node 'NODEIPL101' with administration URI 'http://<host>:4417' is running.

    For more information about using the web user interface to manage integration servers and their resources, see Managing integration servers and Managing integration solution resources that are deployed to an integration server.


ae12720_.htm | Last updated 2018-11-02 14:45:49