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


mqsicreateexecutiongroup command

Use the mqsicreateexecutiongroup command to add a new integration server to an integration node.

Supported platforms

  • Windows
  • Linux and UNIX systems

Purpose

You must start the integration node before you run the mqsicreateexecutiongroup command.

Syntax

Some parameters have alternative long names; for example: -p and --admin-port are alternative parameter names of the port number for the administration REST API. The long names available are listed in the Parameters section.

Read syntax diagramSkip visual syntax diagram
>>-mqsicreateexecutiongroup------------------------------------->

>--+-integrationNodeName-----------+---------------------------->
   +- -n --integrationNodeFileName-+   
   +- -i --ipAddress-- -p --port---+   
   '-+- -i --ipAddress-+-----------'   
     '- -p --port------'               

>-- -e --integrationServerName---------------------------------->

>--+----------------------------------------+------------------><
   '- -w --timeoutSecs-- -v --traceFileName-'   

Parameters

integrationNodeName
This parameter identifies the name of a specific integration node. To connect to a remote integration node by name, you must also specify -i and (optionally) -p.
-n integrationNodeFileName | --integration-node-file integrationNodeFileName
This parameter identifies the name of a .broker file that contains the connection details for an integration node. Include the location (path) and file name when you specify this parameter. You must ensure that the location is accessible when you run this command.

Use this option if multiple users want to connect to the same integration node or integration server, or if you are using advanced connection parameters such as SSL. To learn more about creating and using a .broker file, see Connecting to an integration node by creating a .broker file.

-i ipAddress, -p port | --admin-host ipAddress, --admin-port port
These parameters identify a host and port for an integration node, for connections that do not require advanced connection parameters.

To connect to a specific remote integration node by name, you can additionally prefix integrationNodeName. You cannot use -n integrationNodeFileName in the same command.

For an integration node, any parameters that you omit assume default values.

  • -i ipAddress: The host name or IP address of the computer on which the integration node is running. If you do not specify this parameter, a value that represents the local computer is used.

    If you want to connect to a secured integration node as a specific user, provide the security credentials as a URI in the following format: tcp://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format.

  • -p port: The port on which the web user interface HTTP connection listener is listening. If you do not specify this parameter, the value 4414 is used.

Other parameters:

-e integrationServerName
(Required) The name of the integration server to create.
-w timeoutSecs
(Optional) This parameter specifies the time in seconds that the utility waits to ensure that the command completed; the default value is 60.
-v traceFileName
(Optional) This parameter sends internal debug trace information about a command to the specified file.

Authorization

For information about platform-specific authorizations, see the following topics: If you have enabled integration node administration security, you must also set up the authority that is detailed in Tasks and authorizations for administration security.

Responses

This command returns the following responses:
0
The command completed successfully.
2
(Failure) The integration node received the deployment request but was unable to process it successfully. See the messages issued from the utility (or the Administration log) for more information.
9
(Failure) The request has been submitted to the integration node, but no response was received before the timeout expired.
10
(Failure) Another user or application canceled the request operation before the integration node was able to process it.
98
The integration node is not running.
99
One or more of the parameters that you specified is invalid.

Examples

Create an integration server called IS1 on the integration node, which is listening on fred.abc.com:4414.

  mqsicreateexecutiongroup -i fred.abc.com -p 4414 -e IS1

Create an integration server called IS2 on the integration node that is defined by the connection parameters in file BROKER.broker

  mqsicreateexecutiongroup -n BROKER.broker -e IS2 

Create an integration server IS3 on the integration node that is defined by the connection parameters in file FRED.broker. Wait 5 minutes for the integration node to respond, and send output to trace.txt.

  mqsicreateexecutiongroup -n FRED.broker -e IS3 -w 300 -v trace.txt

an26000_.htm | Last updated 2018-11-02 14:45:59