mqsichangebroker command - Linux and UNIX systems

BrokerName

(Required) This parameter must be the first parameter. Specify the name of the broker to modify.

-t

(Optional) The broker runs as a WebSphere® MQ trusted application.

For more details about using WebSphere MQ trusted applications, see the Intercommunication section of the WebSphere MQ Version 7 product documentation online.

-n

(Optional) The broker ceases to run as a WebSphere MQ trusted application.

-l userLilPath

(Optional) A list of paths (directories) from which the broker loads Loadable implementation libraries (LIL files) for user-defined message processing nodes.

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 broker 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 additional directory, each directory must be separated by the default platform-specific path separator.

-g configurationChangeTimeout

(Optional) The maximum time (in seconds) that is allowed for a user configuration request to be processed. It defines the length of time taken within the broker to apply to an integration server a configuration change that you have initiated. For example, if you deploy a configuration from the IBM Integration Toolkit, the broker must respond to the Configuration Manager within this time.

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.

-k internalConfigurationTimeout

(Optional) The maximum time (in seconds) that is allowed for an internal configuration change to be processed. For example, it defines the length of time taken within the broker to start an integration server.

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 broker 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.

-P httpListenerPort

(Optional) Enter the number of the port on which the Web services support is listening.

The broker 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.

-v statisticsMajorInterval

(Optional) The time interval (in minutes) at which statistics and accounting archive records are written. The valid range is from 1 minute to 43200 minutes; the default value is 60.

-y ldapPrincipal

(Optional, but mandatory when ldapCredentials is provided.) The user principal for access to an optional LDAP directory that holds the JNDI administered Initial Context for the JMS provider.

-z ldapCredentials

(Optional, but mandatory when ldapPrincipal is provided.) The user password for access to LDAP.

-c ICU converter path

(Optional) A set of directories to search for additional code page converters, delimited by a colon (:).

The code page converters must be either of the form codepagename.cnv, or in an ICU data package called icudt48.dat. The code page converters must be located in a sub-directory named icudt48_<platform_suffix> of the specified directory where <platform_suffix> is one of the following values:

• l for little-endian ASCII platforms
• b for big-endian ASCII platforms
• e for EBCDIC platforms

-x userExitPath

(Optional) The path that contains the location of all user exits to be loaded for integration servers in this broker. This path is added to the system library search path (PATH,LIBPATH,LD_LIBRARY_PATH,SHLIBPATH) for the integration server process only.

-e activeUserExits

(Optional) Active user exits. By default, user exits are inactive. Adding a userExit name to this colon-separated list changes its default state to active for this broker. You can use the mqsichangeflowuserexits command to override the default state at the integration server or message flow level. If you specify a user exit name, and no library is found to provide that user exit when the integration server starts, a BIP2314 message is written to the system log. The integration server fails to start.

-f function level

(Optional) Use this parameter to enable function that becomes available in IBM Integration Bus fix packs. Valid values that you can set are all, which enables all functions, or a version string of the form V.R.M.F (for example, 9.0.0.3), which indicates the maximum level of feature function to enable. You can use this parameter to revert to a prior fix pack level, but you must first remove any flows that are using the new functions.

This command does not disable all new features, and it is not possible to use this flag to run the broker at a different major version.

-s security_status

(Optional) Specify this parameter to change the administrative security status of the broker.

• If you specify active, administrative security is enabled for the broker. The command creates authorization queues that are required, if they do not exist.
• If you specify inactive, administrative security is disabled for the broker. The command does not delete or clear the security queues that are associated with this broker and its integration servers.

If you omit this parameter, the security status is unchanged.

For further information about using security, see Administration security overview and Authorizing users for administration.

-d

(Optional) Enables a broker to be started and stopped as a WebSphere MQ service when the queue manager starts and stops.

This option is an alternative to starting a multi-instance broker in standby mode using the mqsistart command.

If you specify -d defined, the WebSphere MQ service is defined to the queue manager and the broker starts and stops when the queue manager starts and stops.

If you specify -d undefined, the WebSphere MQ service is not defined to the queue manager and the broker does not start and stop when the queue manager starts and stops. This is the default setting.

-b cachePolicy

(Optional) The policy to use for the cache manager. Set this parameter to default, disabled, none, or the fully qualified name of an XML policy file.

• If you specify default, the default cache policy is used.
• If you specify disabled, the global cache components in the broker are disabled. The cache is disabled by default.
• If you specify none, the cache manager in each integration server uses the values that you set. The integration server properties that were set most recently by the broker-level policy are retained as a starting point for customization.
• If you specify the fully qualified name of a policy file, the brokers listed in the policy file are configured to share the data in the global cache. The path must be absolute, not relative.

-r cachePortRange

(Optional) The range of ports to be used by the cache manager. Set this parameter to generate or to a specific range of ports.

• If you specify a range of ports, the value of this parameter must be in the format xxxx-yyyy, and the range must contain at least 20 ports.
• If you specify generate, the broker generates a range of ports that are not being used by another broker on that computer. The broker chooses a range that starts from 2800. If, for example, another broker is using ports 2800 to 2819, the broker generates a range from 2820 to 2839.

-4 integrationRegistryHostname

The host name of the Integration Registry. If this parameter is not set, the host name of the machine is used. Use this parameter only to configure multi-instance brokers. For more information, see Integration Registry configuration for multi-instance integration nodes.

To change other broker properties, first delete and re-create the broker, and then use the IBM Integration Toolkit to redeploy the broker configuration. If you want to update the user ID credentials that the broker 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 IB9NODE -s active

mqsichangebroker IB9NODE -d defined

mqsichangebroker IB9NODE -d undefined