For restrictions on the character set that you can use, see Characters allowed in object names.
For compatibility with existing systems, you can specify <password>. However, if you do not specify a password with this parameter when you run the command, you are prompted to enter a password. You must enter the password a second time to verify that you have entered it correctly.
For compatibility with existing systems, you can specify <password>. However, if you do not specify a password with this parameter when you run the command, you are prompted to enter a password. You must enter the password a second time to verify that you have entered it correctly.
To complete a password change successfully:
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.
You can specify the serviceUserId in any valid user name syntax:
Do not use a domain name as part of the serviceUserId parameter.
If you use the unqualified form for this user ID (username), the operating system searches for the user ID throughout its domain. This search, which starts with the local system, 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). If you specified the -w parameter, it must be able to access the working directory.
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.
The queue manager specified on the integration node is also required for message flow nodes that use system queues to store state information about messages, such as the CD and FTE nodes, and for event-driven processing nodes that are used for aggregation and timeout flows, message collections, and message sequences. These nodes require a queue manager to be specified on the integration node, and they also require a set of system queues to be created. For information about creating the system queues, see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. For more information about the IBM Integration Bus features that require system queues, see Installing WebSphere MQ.
If you specify a queue manager that does not exist, you must create it before the flow is deployed.
If the -q parameter is not specified, some features that require access to WebSphere MQ will be unavailable. For more information about using WebSphere MQ with IBM Integration Bus, see Enhanced flexibility in interactions with WebSphere MQ.
crtmqm -md /<integration node sharedWorkPath>/mqm/qmdata
-ld //<integration node sharedWorkPath>/mqm/qmlog queueManagerName
If this shared queue manager path is not appropriate, create the multi-instance queue manager on the server before you run this command. For more information, see Creating a multi-instance integration node.
For restrictions on the character set that you can use, see Characters allowed in object names.
The queue manager specified on the integration
node is also required for message flow nodes that use system queues
to store state information about messages, such as the CD and FTE
nodes, and for event-driven processing nodes that are used for aggregation
and timeout flows, message collections, and message sequences. These
nodes require a queue manager to be specified on the integration node,
and they also require a set of system queues to be created. You create
the queues by running the script iib_createqueues.bat in
the install_dir\server\sample\wmq directory.
Alternatively, you can create the queues by running the WebSphere MQ define qlocal command.
For more information about using the define qlocal command,
see the WebSphere MQ product
information. For more
information about the IBM Integration Bus features
that require system queues, see mqsicreatebroker command.
If you specify a queue manager that does not exist, you must create it before the flow is deployed.
If the -q parameter is not specified, some features that require access to WebSphere MQ will be unavailable. For more information about using WebSphere MQ with IBM Integration Bus, see Enhanced flexibility in interactions with WebSphere MQ and Installing WebSphere MQ.
crtmqm -md \<integration node sharedWorkPath>\mqm\qmdata
-ld \\<integration node sharedWorkPath>\mqm\qmlog queueManagerName
If this shared queue manager path is not appropriate, create the multi-instance queue manager on the server before you run this command. For more information, see Creating a multi-instance integration node.
For restrictions on the character set that you can use, see Characters allowed in object names.
mqsichangebroker IB10NODE -q ""
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.
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.
When an integration node has been enabled for multi-instance mode using the -e flag, the integration node workPath is divided between data that is specific to this integration node instance, and that which is shared between this integration node and any of its instances created using the mqsiaddbrokerinstance command. Data specific to the multi-instance enabled integration node is stored in the workPath directory on the local server, whereas the shared data is held in a directory on network storage at the location that is specified using the -e flag.
This directory is also used for trace records that are created when tracing is active. These records are written to a subdirectory, log, which you must create before you start the integration node.
Error logs that are written by the integration node when a process ends abnormally are stored in this directory.
The error log is unbounded and continues to grow. Check this directory periodically and clear out old error information.
You cannot change this parameter by using the mqsichangebroker command. To specify or change the work path, delete and re-create the integration node.
Specifying this parameter creates a separate working directory for the integration node. This working directory is a subset of the default working directory structure that contains fewer subdirectories and no common\profiles subdirectory.
You must ensure the integration node has access to this network storage location before you start the integration node, and that the queue manager for the integration node has been configured as a WebSphere MQ multi-instance queue manager.
Specify this parameter if you require either authentication services or publish/subscribe access control. If you do not specify this parameter, the integration node assumes that no User Name Server is defined. To enable publish/subscribe access control, specify the -s and -j parameters.
To remove topic-based security, specify an empty string (two single quotation marks ").
If you specify this parameter on HP-UX and Solaris, specify the serviceUserId as mqm.
If you specify this parameter, add the serviceUserId (identified by the -i parameter) to the mqm group.
If you specify this parameter on Windows systems, add the serviceUserId (identified by the -i parameter) to the mqm group.
If you specify this parameter on HP-UX and Solaris, specify the serviceUserId as mqm.
For more details about using WebSphere MQ trusted applications, see the
Intercommunication section of the WebSphere MQ Version 7.5 product
documentation online.
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.
An interval of zero minutes indicates that the operating system has an external method of notification (the ENF timer), and is not using an internal timer within IBM Integration Bus.
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.
On Linux and UNIX systems, directory names are case-sensitive. You must include the names in single quotation marks if they contain mixed case characters.
Do not include environment variables in the path; the integration node ignores them.
Directory names are case-sensitive, and you must include the names in single quotation marks if they contain mixed case characters.
Do not include environment variables in the path; the integration node ignores them.
Do not include environment variables in the path; the integration node ignores them.
This name is case-sensitive; enclose the names in single quotation marks if they are in mixed case.
Do not include environment variables in this path; IBM Integration Bus ignores them.
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 directory, separate directories by using a colon (:).
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 directory, separate directories by using a semicolon (;).
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 directory, separate directories by a semicolon (;) on Windows systems, or a colon (:) on Linux and UNIX systems.
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 a colon (:).
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 a semicolon (;).
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.
For 64-bit integration servers, which are the default in WebSphere Message Broker Version 6.1, you must append the corresponding library path to the environment variable MQSI_LILPATH64.
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.
Specify the administrative security status for the integration node. If you specify -s active, administration security is enabled. Only user IDs that you authorize are permitted to complete actions on the integration node. Read, write, and execute authority is always granted on the integration node to all user IDs that belong to the security group mqbrkrs. When the integration node has been created, you can add further user ID authorizations.
If you are using queue-based security, the queue SYSTEM.BROKER.AUTH.integration_server_name is created when you create an integration server on an integration node for which administrative security is enabled. Populate the queue with the appropriate user authorization.
If you specify -s inactive, or omit this parameter, integration node administration security is not enabled. All users are able to complete all actions against the integration node and all integration servers.
If integration node administration security is not enabled, web users can access the web user interface as the default user, with unrestricted access to data and integration node resources.
If you do not specify this option, the security queues are retained and can be reused if you re-create the integration node.
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.
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.