Use the mqsicreatebroker command to create an integration node on a z/OS® system.
>>---mqsicreatebroker----integrationNodeName--------------------> >--+------------------------+--+-------------------+------------> '- q= --QueueManagerName-' '- l= --UserLilPath-' >--+------------------------+-----------------------------------> '- P= --HTTPListenerPort-' >--+----------------------------------+-------------------------> '- g= --ConfigurationChangeTimeout-' >--+------------------------------------+-----------------------> '- k= --InternalConfigurationTimeout-' >--+-------------------------------+----------------------------> '- v= --StatisticsMajorInterval-' >--+-------------------------------------------+----------------> '- y= --LdapPrincipal-- -z--LdapCredentials-' >--+------------------------+--+--------------------+-----------> '- c= --ICUConverterPath-' '- x= --UserExitPath-' >--+--------------------+--+-------------------+----------------> '- s= --+-active---+-' '- b= --cachePolicy-' '-inactive-' >--+----------------------+--+-------------+------------------->< '- r= --cachePortRange-' '- C= --CCSID-'
For restrictions on the character set that you can use, see Characters allowed in object names.
If you specify a queue manager that does not exist, you must create it before the flow is deployed.
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.
The queue manager attribute MAXMSGLEN (the maximum length of messages that can be put to queues) is updated to 100 MB. This attribute is updated regardless of whether the queue manager is created by this command.
For restrictions on the character set that you can use, see Characters allowed in object names.
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.
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.
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.
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.
mqsicreatebroker IBNODE q= IBQMGR
mqsicreatebroker IBNODE s= active