Use this option if multiple users want to connect to the same integration node, 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.
If you want to run a command that uses SSL to administer a remote integration node over a secured channel, you must specify the keystore and truststore password for the connection that is using the IBM_JAVA_OPTIONS environment variable. For more information, see Resolving problems when running commands.
Use this option for connections to remote integration nodes that do not require advanced connection parameters.
If you are connecting to a remote integration node, you can additionally prefix integrationNodeName to explicitly set which integration node to connect to. You cannot use -n integrationNodeFileName in the same command.
Parameters that you omit assume default values:
If you want to connect to a secured integration server 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. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.
Use this option if multiple users want to connect to the same integration node, or if you are using advanced connection parameters such as SSL.
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.
If you are connecting to a remote integration node, you can additionally prefix integrationNodeName to explicitly set which integration node to connect to. You cannot use -n integrationNodeFileName in the same command.
Parameters that you omit assume default values:
If you want to connect to a remote host name, provide the security credentials as a URI in the following format: protocol://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.
If you specify -e without -m or -j, the integration server is started. Message flows are started only if they were running when the integration server was stopped.
If you specify -e with -m or -j, the integration server must be running. If the integration server is stopped, the request is rejected.
If you specify -e without -m or -j, the integration server is stopped. The state of every message flow (stopped or started) is retained, and started message flows are started when the integration server is started again.
If you specify -e with -m or -j, the integration server must be running. If the integration server is stopped, the request is rejected.
If you do not specify -e, resource statistics collection is started or stopped for all integration servers on the integration node.
If you do not specify -e, resource statistics status is reported for all integration servers on the integration node.
If you specify -g without -m or -j, all integration servers are started, but message flows are started only if they were running when the integration server was stopped.
If you specify -g with -m or -j, the specified message flow or flows are started only if the integration server is running. The request checks all integration servers, and starts message flows on integration servers that are currently running. Error BIP2851 is reported for each integration server that is not running.
If you specify -g without -m or -j, all integration servers are stopped. The state of every message flow (stopped or started) is retained for each integration server, and started message flows are started when the integration server is started again.
If you specify -g with -m or -j, the specified message flow or flows are stopped only if the integration server is running. The request checks all integration servers, and stops message flows on integration servers that are currently running. Error BIP2851 is reported for each integration server that is not running.
You can specify only one message flow in a single command. If you want to stop all message flows deployed to the integration node, or to the integration server identified by -e, specify -j.
integrationNodeSpec |--+- integrationNodeName ---------+----------------------------| +- -n --integrationNodeFileName-+ +- -i --ipAddress-- -p --port---+ '-+- -i --ipAddress-+-----------' '- -p --port------' integrationNodeSpec |--+- integrationNodeName ---------+----------------------------| +- n= --integrationNodeFileName-+ +- i= --ipAddress-- -p --port---+ '-+- i= --ipAddress-+-----------' '- p= --port------'
If you try to connect to a remote integration node by specifying the i or p 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 integration node (name)
The reported reason code is MQRC_ENVIRONMENT_ERROR. You must specify a local queue manager.
In previous versions of IBM® Integration Bus, you might have used the -q parameter for this command to define a connection to a queue manager. A queue manager connection is no longer used to connect to an integration node. The -q parameter is now deprecated, and is ignored if used. If you use the -q parameter, a BIP1922 warning is displayed.
In previous versions of IBM Integration Bus, you might have used the q= parameter for this command to define a connection to a queue manager. A queue manager connection is no longer used to connect to an integration node. The q= parameter is now deprecated, and is ignored if used. If you use the q= parameter, a BIP1922 warning is displayed.