Use the mqsichangeproperties command to modify integration node properties and properties of integration node resources.
Use the mqsichangeproperties command to change properties that are associated with an integration node:
You can also use web user interface or the IBM® Integration API to change properties.
Use the mqsireportproperties command to view properties that are associated with an integration node.
>>-mqsichangeproperties--integrationNodeName--------------------> >--+-----------------------------+-- -o --ObjectName------------> +- -b --ComponentName---------+ +- -c --policy-type-----------+ '- -e --integrationServerName-' >-- -n --PropertyName--+- -v --PropertyValue-+--+-----+-------->< +- -p --Path.FileName-+ '- -f-' '- -d ----------------'
You must also specify the name of a policy on the -o parameter.
You must also specify -b, -e, or -c with -o, except if you specify the object name BrokerRegistry.
For compatibility with previous versions, you can also specify the value ComIbmXmlParserFactory for the ObjectName.
The property names for predefined policies are described in Policy properties.
If you specify a policy of type UserDefined, the PropertyName specified is created if it does not exist.
You can specify more than one property name together with a corresponding value, by using commas as separators, if you use a valid value for the corresponding property; for example, -n Name1,Name2 -v Value1,Value2.
Do not leave a space after each comma in the list of names and corresponding values. Use "" to specify an empty PropertyValue string.
If the property value contains a comma, enclose the value with escaped double quotation marks (\" and \"); for example, -n Name1,Name2 -v Value1,\"Value21,Value22\".
mqsichangeproperties INODE -c JDBCProviders -o DB2EXTRA -n connectionUrlFormat
-v "jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];"
If you set the -c parameter to EISProviders or JMSProviders, and the -n parameter to jarsURL, the expected value is a URL that specifies the file location of the EIS or JMS provider JAR files, but omits the file:// part of the URL. (On Windows, the file location cannot be a mapped network drive on a remote Windows computer; the directory must be local or on a Storage Area Network (SAN) disk.)
Use this parameter for policy sets and bindings.
Use this parameter for monitoring profiles; the XML file must conform to the monitoring profile schema.
If you specify this parameter for other policies or components, an error is generated.
You can use this parameter only when the integration server is in the stopped state. You can use the -f parameter when the integration node is running or stopped. You are advised to use this parameter only under the direction of IBM support to recover from integration server startup failures.
If you specify this parameter for other policies or components, an error is generated.
Always enter the command on a single line; in some examples, line breaks have been added to enhance readability.
The following examples specify the -b parameter to identify a particular integration node component.
mqsichangeproperties INODE -b NodeHttpListener -o HTTPListener
-n startListener -v false
mqsichangeproperties INODE -b NodeHttpListener -o HTTPListener
-n startListener -v true
mqsichangeproperties INODE -b NodeHttpListener -o HTTPListener
-n enableSSLConnector -v true
mqsichangeproperties INODE -b NodeHttpListener -o HTTPSConnector
-n sslProtocol -v TLSv1.2
mqsichangeproperties INODE -b NodeHttpListener -o HTTPSConnector
-n crlFile -v file_path
mqsichangeproperties INODE -b securitycache -o SecurityCache
-n cacheTimeout -v 200
mqsichangeproperties INODE -b webadmin -o server
-n enabled -v false
mqsichangeproperties INODE -b webadmin -o HTTPSConnector
-n port -v new_port_number
You can change this
property only when the integration node is running, and the change
takes effect when the integration node is restarted.mqsichangeproperties INODE -o ComIbmJVMManager
-n jvmMaxHeapSize -v size_in_bytes
mqsichangeproperties INODE -b pubsub -o OperationalEvents/MQ
-n enabled -v true
mqsichangeproperties INODE -b pubsub -o OperationalEvents/MQ
-n enabled -v false
mqsichangeproperties INODE -b pubsub -o OperationalEvents/MQ
-n policyUrl -v /apiv1/policy/MQEndpoint/example_mq_policy
mqsichangeproperties INODE -b pubsub -o OperationalEvents/MQ
-n format -v none
The following examples include the -e parameter to specify the integration server to change.
mqsichangeproperties INODE -e integrationServerName -o ExecutionGroup
-n httpNodesUseEmbeddedListener -v true
If you disable the integration node listener (as shown in a previous example), you do not have to change the integration server configuration as shown in this command; if the integration node listener is not active, all integration servers use the embedded listener by default for all HTTP message handling.
mqsichangeproperties INODE -e integrationServerName -o ExecutionGroup
-n httpNodesUseEmbeddedListener -v false
mqsichangeproperties INODE -e integrationServerName -o ExecutionGroup
-n soapNodesUseEmbeddedListener -v false
mqsichangeproperties INODE -e integrationServerName -o ExecutionGroup
-n soapNodesUseEmbeddedListener -v true
If you disable the integration node listener (as shown in a previous example), you do not have to change the integration server configuration as shown in this command; if the integration node listener is not active, all integration servers use the embedded listener by default for all HTTP message handling.
mqsichangeproperties integrationNodeName -e integrationServerName -o ComIbmIIBSwitchManager -n agentXConfigFile -p filepath\agentx.json
mqsichangeproperties INODE -e integrationServerName -o ExecutionGroup
-n failedMessageWaitTime -v wait_time
mqsichangeproperties INODE -e integrationServerName -o HTTPSConnector
-n explicitlySetPortNumber -v 7777
mqsichangeproperties INODE -e integrationServerName
-o HTTPSConnector -n ciphers
-v \"SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA\"
-v \"SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA\"
-v "SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA"
mqsichangeproperties INODE -e integrationServerName -n crlFile -v file_path
mqsichangeproperties INODE -e integrationServerName -o ComIbmJVMManager -n enableCRLDP -v true
mqsichangeproperties INODE -e integrationServerName -o ComIbmJVMManager
-n jvmDebugPort -v 8018
mqsichangeproperties INODE -e integrationServerName -o ComIbmJVMManager
-n jvmMaxHeapSize -v size_in_bytes
mqsichangeproperties INODE -e AddressSampleProvider
-o ComIbmJVMManager
-n keystoreType -v JKS
mqsichangeproperties INODE -e integrationServerName
-o FTEAgent -n coordinationQMgr -v QM2
mqsichangeproperties INODE -e integrationServerName
-o ComIbmGenericXmlParserFactory -n invalidCharacterEscapeType -v character_type
where
character_type specifies how to render the
character:mqsichangeproperties INODE -e default
-o ComIbmMQConnectionManager -n expiryCompensation -v option
where option specifies
if the expiry compensation is active or not:mqsichangeproperties INODE -e integrationServerName
-o ComIbmResourceStatsManager -n bluemixReporting -v active
mqsichangeproperties INODE -e integrationServerName
-o ComIbmResourceStatsManager -n fileReporting -v active
mqsichangeproperties INODE -o BrokerRegistry
-n httpConnectorPortRange -v 7777-8888
mqsichangeproperties INODE -o BrokerRegistry -n crlFileList -v file_path
mqsichangeproperties INODE -o BrokerRegistry
-n mqCCDT -v "C:\Program Files (x86)\IBM\WebSphere
MQ\Qmgrs\QM1\@ipcc\AMQCLCHL.TAB"
When
you have set the mqCCDT property, restart the
integration node for the changes to take effect.mqsichangeproperties INODE -o BrokerRegistry -n mqKeyRepository -v C:\SSL\key
The
SSL key repository is created using the WebSphere MQ GSKit.