IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsicreateexecutiongroup command

Use the mqsicreateexecutiongroup command to add a new integration server to a broker.

Supported platforms

Purpose

You must start the broker before you run the mqsicreateexecutiongroup command.

Syntax

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

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

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

brokerSpec

|--+- brokerName ----------------+------------------------------|
   +- -n --brokerFileName--------+   
   | .-------------------------. |   
   | V                         | |   
   '-----+- -i --ipAddress-+---+-'   
         +- -p --port------+         
         '- -q --qMgr------'         

Parameters

brokerSpec
(Required) You must specify at least one parameter to identify the target broker for this command, in one of the following forms:
brokerName
This parameter identifies the name of a locally defined broker. You cannot use this option if the broker is on a remote computer.
-n brokerFileName
This parameter identifies the name of a file that contains the connection details for a local or remote broker.

Use this option if multiple users want to connect to the same broker, or if you are using advanced connection parameters such as SSL.

To create this file, right-click the broker in the IBM® Integration Explorer and select Export *.broker file. When prompted, navigate to the location in which you want to save the file and enter the file name; the extension .broker is appended automatically when you click Save. 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.

If you want to run a command that uses SSL to administer a remote broker over a secured channel, you must specify the keystore and truststore password for the connection using the IBM_JAVA_OPTIONS environment variable. See Resolving problems when running commands for further information.

-i ipAddress, -p port, -q qMgr
These parameters identify the connection details for the broker.

Use this option for connections to remote brokers that do not require advanced connection parameters.

If you choose this option, you must specify at least one of these three parameters; the order in which you specify them is insignificant. You cannot specify each parameter more than once.

Parameters that you omit assume default values:

  • -i ipAddress: The host name or the IP address of the computer on which the broker is running. If you do not specify this parameter, a value that represents the local computer is used.
  • -p port: The TCP port on which the broker's queue manager is listening. If you do not specify this parameter, the value 1414 is used.
  • -q qMgr: The name of the broker's queue manager. If you do not specify this parameter, a value that represents the default queue manager on the local computer is used.
You cannot connect to a remote queue manager on z/OS; see Usage note.
-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 to the specified file.

Usage note

If you try to connect to a remote broker by specifying the i, p, and q parameters, or by using a connection parameter file (.broker), the command attempts to use WebSphere® MQ Java™ client code. This option is not supported on z/OS, and returns the following error:

BIP1046E: Unable to connect with the broker (name)

The reported reason code is MQRC_ENVIRONMENT_ERROR. You must specify a local queue manager.

Authorization

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

Responses

This command returns the following responses:
0
The command completed successfully.
2
(Failure) The broker 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 broker, but no response was received before the timeout expired.
10
(Failure) Another user or application canceled the request operation before the broker was able to process it.
98
The broker is not running.
99
One or more of the parameters that you specified is invalid.

Examples

Create an integration server called IS1 on the broker that is hosted by the queue manager QMGR, which is listening on fred.abc.com:1414.

  mqsicreateexecutiongroup -i fred.abc.com -p 1414 -q QMGR –e IS1

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

  mqsicreateexecutiongroup –n BROKER.broker –e IS2 

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

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

an26000_.htm | Last updated Friday, 21 July 2017