mqsichangeproperties command

Use the mqsichangeproperties command to modify broker properties and properties of broker resources.

Supported platforms

  • Windows® systems.
  • Linux® and UNIX® systems.
  • z/OS®. Run this command by customizing and submitting the BIPCHPR utility; see Contents of the broker PDSE.

Purpose

Use the mqsichangeproperties command to change properties that are associated with a broker and relate to inter-broker communications, the JVM, and the HTTP listener component (which includes the HTTP and HTTPS (SSL) support for the HTTPInput and HTTPReply nodes). You can also use the Configuration Manager Proxy (CMP) API to change properties.

Start of changeUse the mqsireportproperties command to view properties that are associated with a broker.End of change

Usage notes

  • Before you run the mqsichangeproperties command, ensure that the broker is running.
  • If you change any value, stop and restart the broker for the change to take effect.
  • Start of changeWhen a message flow that includes HTTP nodes is started, the broker starts the HTTP listener.End of change

Syntax

Parameters

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

 

-b httplistener
(Optional) The name of the component.

Start of changeYou must specify either -b httplistener or -c ConfigurableService.End of change

-c ConfigurableService
(Optional) The type of configurable service. The type is predefined; for example, JMSProviders. You can define additional services of any defined type by using the mqsicreateconfigurableservice command.

Start of changeYou must specify either -b httplistener or -c ConfigurableService.End of change

-o ObjectName
(Required) The name of the object for which you want to change the properties.

For compatibility with previous versions, you can also specify the value ComIbmXmlParserFactory for the ObjectName.

-n PropertyName
(Required) The name of the property to be changed. All property names start with a lowercase character.
-v PropertyValue
(Required) The value that is assigned to the property that is specified by the -n parameter.

Start of changeYou can specify more than one property name together with a corresponding value, using commas as separators, provided that you use a valid value for the corresponding property; for example, -n Name1,Name2 -v Value1,Value2. End of change

Start of changeDo not leave a space after each comma in the list of names and corresponding values.End of change

Use "" to specify an empty PropertyValue string.

mqsichangeproperties WBRK_BROKER -c JDBCProviders -o DB2EXTRA -n connectionUrlFormat 
-v "jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];"

 

Start of changeFor detailed information about valid components, configurable services, object names, properties, and values, select the appropriate topic: End of change

Authorization

On Windows systems, the user ID that is used to run this command must be a member of the Administrators group on the local computer.

On Linux and UNIX systems, the user ID that is used to run this command must be a member of the mqbrkrs group.

Additionally, the broker requires the following authority for the supported multicast protocols:
PGM/IP
The broker requires:
  • Linux platformUNIX platform root authority on Linux and UNIX systems
  • Windows platform Administrator authority on Windows systems
  • z/OS platform root authority (UNIX System Services only) on z/OS
PGM/UDP
The broker requires User authority on all supported platforms.
PTL
The broker requires User authority on all supported platforms.

Examples

Always enter the command on a single line; in some examples, a line break has been added to enhance readability.

Changes to broker components

The following examples specify the -b parameter to identify a particular broker component.

  • Enable the HTTPSConnector for the HTTP nodes deployed to the specified broker:
     mqsichangeproperties TEST -b httplistener -o HTTPListener -n enableSSLConnector -v true
  • Change the default SSL protocol from SSLv3 to TLS for the HTTP nodes that are deployed to the specified broker:
    mqsichangeproperties TEST  -b httplistener -o HTTPSConnector -n sslProtocol -v TLS 

Changes to properties associated with execution groups

The following examples include the -e parameter to specify the execution group to change.

  • Change the clientPingInterval to 200 for a cloned broker:
    mqsichangeproperties TEST -e default -o DynamicSubscriptionEngine -n clientPingInterval -v 200 
  • Enable multicast for a cloned broker:
    mqsichangeproperties TEST -e default -o DynamicSubScriptionEngine -n multicastEnabled -v true
  • Set the JVM port number to activate message flow debugging:
    mqsichangeproperties TEST -e exgroup1 -o ComIbmJVMManager -n jvmDebugPort -v 8018 
  • Set the type of server keystore:
    mqsichangeproperties TEST -e AddressSampleProvider -o ComIbmJVMManager -n keystoreType -v JKS

Changes to configurable services

The following examples include the -c parameter to specify the type of configurable service to change.

  • Change the location of the JAR files for the IBM® WebSphere® MQ JMS client:
    mqsichangeproperties WBRK6_DEFAULT_BROKER -c JMSProviders -o WebSphere_MQ  
    -n jarsURL -v file://D:\SIBClient\Java
Related concepts
Broker domains
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:34

an09140_