Use the mqsichangebroker command on Windows systems to modify your integration node.
>>-mqsichangebroker--integrationNodeName------------------------> >--+---------------------------------------------------+--------> '- -a --servicePassword --+-----------------------+-' '- -i -- serviceUserId -' >--+------+--+------------------------+-------------------------> +- -t -+ '- -q --queueManagerName-' '- -n -' >--+-------------------+----------------------------------------> '- -l --userLilPath-' >--+----------------------------------+-------------------------> '- -g --configurationChangeTimeout-' >--+------------------------------------+-----------------------> '- -k --internalConfigurationTimeout-' >--+------------------------+-----------------------------------> '- -P --httpListenerPort-' >--+-------------------------------+----------------------------> '- -v --statisticsMajorInterval-' >--+------------------------------------------+-----------------> '- -y--ldapPrincipal-- -z--ldapCredentials-' >--+--------------------------+--+--------------------+---------> '- -c --ICU converter path-' '- -x --userExitPath-' >--+-----------------------+--+----------------------+----------> '- -e --activeUserExits-' '- -f --function level-' >--+--------------------+--+---------------------+--------------> '- -s --+-active---+-' '- -d --+-defined---+-' '-inactive-' '-undefined-' >--+-------------------+--+----------------------+------------->< '- -b --cachePolicy-' '- -r --cachePortRange-'
(Required) This parameter must be the first parameter. Specify the name of the integration node to modify.
You can specify the serviceUserId in any valid user name syntax:
username
.\username
username@domain
domain\username
\\server\username
If you use the unqualified form for this user ID (username), the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.
The serviceUserId that you specify must be a direct or indirect member of the mqbrkrs local group. The serviceUserId must also be authorized to access the home directory (where IBM® Integration Bus has been installed), and the working directory (if specified by the -w parameter).
If you specify that the integration node is to run as a WebSphere® MQ trusted application (-t parameter), you must also add the service user ID to the mqm group.
The security requirements for the serviceUserId are described in Security requirements for Windows systems.
For more details about using WebSphere MQ trusted applications, see the
Intercommunication section of the WebSphere MQ Version 7.5 product documentation
online.
(Optional) The integration node ceases to run as a WebSphere MQ trusted application.
If you specify the -q parameter without a queue manager name (in quotation marks, ""), no queue manager is associated with the integration node, and any association with a previously specified queue manager on the integration node is removed. You cannot remove the queue manager association if the integration node was created as multi-instance by using the -e parameter. Similarly, you cannot change the queue manager name if -d was defined.
If a queue manager is specified on the integration node and administration security is active, the queue-based (mq) mode of security is used by default, and the required queues that are used for setting authorization are created automatically when the integration node is created. If the queue-based mode of security is set and the queue manager is subsequently removed from the integration node, all access to the integration node is denied until a queue manager is specified on the integration node again, or until the authorization mode is changed to file and the required permissions are set. For information about using the mqsichangeauthmode command to specify the mode of administration security, see Configuring administration security to use file-based or queue-based authorization.
If you want to use the IBM Integration Bus functions that require access to WebSphere MQ queues, you can use the script iib_queues_create.mqsc to define them. The script is in the directory install_dir/server/sample/wmq or install_dir\server\sample\wmq. To learn which features require access to WebSphere MQ, see IBM Integration features and Enhanced flexibility in interactions with WebSphere MQ.
Create your own directory for storing your .lil or .jar files. Do not save them in the IBM Integration Bus installation directory.
If you specify more than one additional directory, each directory must be separated by the default platform-specific path separator.
A message flow cannot respond to a configuration change while it is processing an application message. An integration server returns a negative response to the deployed configuration message if any one of its message flows does not finish processing an application message and apply the configuration change within this timeout.
Specify the value in seconds, in the range 10 - 3600. The default is 300.
For information about how to set the value for this timeout, see Setting configuration timeout values.
The response time of each integration server differs according to system load and the load of its own processes. The value must reflect the longest response time that any integration server takes to respond. If the value is too low, the integration node returns a negative response, and might issue error messages to the local error log.
Specify the value in seconds, in the range 10 - 3600. The default is 60.
For information about how to set the value for this timeout, see Setting configuration timeout values.
The integration node starts this listener when a message flow that includes HTTP nodes or web services support is started; the default is 7080.
Ensure that the port that you specify has not been specified for any other purpose.
mqsichangebroker <brokername> ""
This command does not disable all new features, and it is not possible to use this flag to run the integration node at a different major version.
This option is an alternative to starting a multi-instance integration node in standby mode using the mqsistart command.
If you specify -d defined, the MQ Service is defined to the queue manager, and the integration node starts and stops when the queue manager starts and stops.
If you specify -d undefined, the MQ Service is not defined to the queue manager, and the integration node does not start and stop when the queue manager starts and stops. This is the default setting.
For more information about running the integration node as an MQ Service, see Creating a multi-instance integration node.
To change other integration node properties, first delete and re-create the integration node, and then use the IBM Integration Toolkit to redeploy the integration node configuration. If you want to update the user ID credentials that the integration node uses to access one or more databases from deployed message flows, use the mqsisetdbparms command. For more information, see Accessing databases from message flows.
mqsichangebroker IBNODE -x /opt/3rdparty/wmbexit
mqsichangebroker IBNODE -f 9.0.0.3
mqsichangebroker IBNODE -q IBQMGR
mqsichangebroker IBNODE -d defined
mqsichangebroker IBNODE -d undefined
mqsichangebroker IBNODE -i wbrkuid -a wbrkpw
mqsichangebroker IBNODE -g 500