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 --ConfigurableService---+ '- -e --integrationServerName-' >-- -n --PropertyName--+- -v --PropertyValue-+--+-----+-------->< +- -p --Path.FileName-+ '- -f-' '- -d ----------------'
The valid resource types are listed in Configurable services properties.
You must also specify -b, -e, or -c with -o, except if you specify the object name BrokerRegistry, or the object name ComIbmJVMManager to change a property related to the heap size.
For compatibility with previous versions, you can also specify the value ComIbmXmlParserFactory for the ObjectName.
The property names for predefined configurable services are described in Configurable services properties.
If you specify a Configurable Service 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 IBNODE -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 configurable services 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 configurable services 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 IBNODE -b httplistener -o HTTPListener
-n startListener -v false
mqsichangeproperties IBNODE -b httplistener -o HTTPListener
-n startListener -v true
mqsichangeproperties IBNODE -b httplistener -o HTTPListener
-n enableSSLConnector -v true
mqsichangeproperties IBNODE -b httplistener -o HTTPSConnector
-n sslProtocol -v TLS
mqsichangeproperties IBNODE -b httplistener -o HTTPSConnector
-n crlFile -v file_path
mqsichangeproperties IBNODE -b securitycache -o SecurityCache
-n cacheTimeout -v 200
mqsichangeproperties IBNODE -b webadmin -o server
-n enabled -v false
mqsichangeproperties IBNODE -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 IBNODE -o ComIbmJVMManager
-n jvmMaxHeapSize -v size_in_bytes
mqsichangeproperties IBNODE -b pubsub -o OperationalEvents/MQ
-n enabled -v true
mqsichangeproperties IBNODE -b pubsub -o OperationalEvents/MQ
-n enabled -v false
mqsichangeproperties IBNODE -b pubsub -o OperationalEvents/MQ
-n policyUrl -v /apiv1/policy/MQEndpoint/example_mq_policy
mqsichangeproperties IBNODE -b pubsub -o OperationalEvents/MQ
-n format -v none
The following examples include the -e parameter to specify the integration server to change.
mqsichangeproperties IBNODE -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 IBNODE -e integrationServerName -o ExecutionGroup
-n httpNodesUseEmbeddedListener -v false
mqsichangeproperties IBNODE -e integrationServerName -o ExecutionGroup
-n soapNodesUseEmbeddedListener -v false
mqsichangeproperties IBNODE -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 IBNODE -e integrationServerName -o HTTPSConnector
-n explicitlySetPortNumber -v 7777
mqsichangeproperties IBNODE -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 IBNODE -e integrationServerName -n crlFile -v file_path
mqsichangeproperties IBNODE -e integrationServerName -o ComIbmJVMManager -n enableCRLDP -v true
mqsichangeproperties IBNODE -e integrationServerName -o ComIbmJVMManager
-n jvmDebugPort -v 8018
mqsichangeproperties IBNODE -e integrationServerName -o ComIbmJVMManager
-n jvmMaxHeapSize -v size_in_bytes
mqsichangeproperties IBNODE -e AddressSampleProvider
-o ComIbmJVMManager
-n keystoreType -v JKS
mqsichangeproperties IBNODE -e integrationServerName
-o FTEAgent -n coordinationQMgr -v QM2
mqsichangeproperties IBNODE -e integrationServerName
-o ComIbmGenericXmlParserFactory -n invalidCharacterEscapeType -v character_type
where
character_type specifies how to render the
character:mqsichangeproperties IBNODE -e default
-o ComIbmMQConnectionManager -n expiryCompensation -v option
where option specifies
if the expiry compensation is active or not:mqsichangeproperties IBNODE -o BrokerRegistry
-n httpConnectorPortRange -v 7777-8888
mqsichangeproperties IBNODE -o BrokerRegistry -n crlFileList -v file_path
mqsichangeproperties IBNODE -o BrokerRegistry
-n mqCCDT -v "C:\Program Files (x86)\IBM\WebSphere
MQ\Qmgrs\QM1\@ipcc\AMQCLCHL.TAB"
mqsichangeproperties IBNODE -o BrokerRegistry -n mqKeyRepository -v C:\SSL\key
The
SSL key repository is created using the WebSphere MQ GSKit.The following examples include the -c parameter to specify the type of configurable service to change.
mqsichangeproperties IBNODE -c Aggregation
-o myAggregationService
-n timeoutSeconds -v 120
This command changes all nodes
that are configured to use the myAggregationService configurable service
by setting the timeout of an aggregation to 120 seconds.mqsichangeproperties IBNODE -c CICSConnection -o myCICSConnectionService
-n connectionTimeoutSecs -v 120
This command changes the CICSRequest node that is configured to use the myCICSConnectionService configurable service by setting the Connection timeout to 120 seconds.
mqsichangeproperties IBNODE -c Collector
-o myCollectorService
-n collectionExpirySeconds -v 120
This command changes
all nodes that are configured to use the myCollectorService configurable
service by setting the expiry time of collections to 120 seconds.mqsichangeproperties IBNODE -c CORBA -o myCORBAService -n namingService,objectReferenceName -v localhost:2809,Europe.region/Market.object
mqsichangeproperties IBNODE -c EmailServer -o
myEmailConfigurableServiceName -n securityIdentity -v
myNewSecurityIdentityObjectName
This command changes the EmailInput node that is configured to use the myEmailConfigurableServiceName configurable service by renaming the securityIdentity object to myNewSecurityIdentityObjectName.
Note that you can use any string for the -o Objectname parameter.
mqsichangeproperties IBNODE -c CDServer -o myCDServer -n brokerPathToStagingDir
-v /tmp/cdtransfer
mqsichangeproperties IBNODE -c EISProviders -o SAP
-n jarsURL,nativeLibs
-v c:\sapjco\jars,c:\sapjco\bin
mqsichangeproperties IBNODE -c FtpServer -o TEST1
-n protocol,serverName,scanDelay,remoteDirectory,securityIdentity,
cipher,compression,strictHostKeyChecking
-v SFTP,winlnx58,30,.,chbatey,blowfish-cbc,9,no
mqsichangeproperties IBNODE -c IMSConnect
-o myIMSConnectService
-n Hostname -v production.ims.ibm.com
mqsichangeproperties IBNODE -c JDBCProviders -o Oracle
-n securityIdentity -v OracleDSN
OracleDSN is the DSN
with which you have associated a user ID and password using the mqsisetdbparms command.mqsichangeproperties IBNODE -c JDBCProviders -o myJDBCProvider
-n databaseSchemaNames -v mySchemaName
mqsichangeproperties IBNODE -c JDBCProviders -o myJDBCProvider
-n databaseSchemaNames -v myTableNameA:mySchemaName01
mqsichangeproperties IBNODE -c JDBCProviders -o myJDBCProvider
-n databaseSchemaNames -v myDefaultSchemaName;myTableNameA:mySchemaName01
mqsichangeproperties IBNODE -c JMSProviders -o WebSphere_MQ
-n jarsURL -v file://D:\SIBClient\Java
mqsichangeproperties IBNODE -c JMSProviders -o BEA_Weblogic
-n proprietaryAPIAttr2, proprietaryAPIAttr3
-v t3://9.20.94.16:7001,BEAServerName
mqsichangeproperties IBNODE -c JMSProviders -o myJMSprovider
-n jndiEnvironmentParms
-v domainName=myDomain;timeout=6000
mqsichangeproperties IBNODE -c MonitoringProfiles -o mp1
-n profileProperties -p mp1.xml
mqsichangeproperties IBNODE -c PeopleSoftConnection
-o myPeopleSoftAdapter.outadapter -n hostName
-v "my.peoplesoft.production.com"
Import a policy set to an integration node from a file:
mqsichangeproperties IBNODE -c PolicySets -o Policy_2
-n ws-security -p policyset.xml
This command
reads file policyset.xml and sets its contents
as Policy_2 in integration node IBNODE. The command
is used to move policy sets between integration nodes, or to
restore from a backup.mqsichangeproperties IBNODE -c PolicySetBindings -o Bindings_2
-n ws-security -p bindings.xml
This command
reads file bindings.xml and sets its contents
as Bindings_2 in integration node IBNODE. The command
is used to move policy set bindings between integration nodes,
or to restore from a backup.mqsichangeproperties IBNODE -c Resequence -o myResequenceService
-n missingMessageTimeoutSeconds -v 120
This command changes
all nodes that are configured to use the myResequenceService configurable
service, by setting them to propagate message sequences that have
missing messages after waiting for 120 seconds.mqsichangeproperties IBNODE -c SAPConnection -o mySAPAdapter
-n applicationServerHost -v production.sap.ibm.com
mqsichangeproperties IBNODE -c SecurityProfiles
-o TFIMv62MapSecProfile
-n mapping,mappingConfig
-v "WS-Trust v1.3 STS",
http://wstrusthost1.ibm.com:9080/TrustServerWST13/services/RequestSecurityToken
mqsichangeproperties IBNODE -c ServiceRegistries -o DefaultWSRR
-n connectionTimeout -v 180
mqsichangeproperties IBNODE -c SiebelConnection
-o mySiebelAdapter.outadapter
-n connectString
-v "siebel://my.siebel.production.com/SBA_80/SSEObjMgr_enu"
mqsichangeproperties IBNODE -c TCPIPClient
-o ClientPort1452HostnameJsmith
-n MinimumConnections -v 0
mqsichangeproperties IBNODE -c TCPIPServer -o ServerPort1452
-n ExpireConnectionSec -v 30
mqsichangeproperties IBNODE -c TCPIPClient -o MyTCPIPClient
-n AlternativeAddresses -v smith6:1111;jones7
mqsichangeproperties IBNODE -c TCPIPClient -o MyTCPIPClient
-n UseUniqueConnectionPool -v true
mqsichangeproperties IBNODE -e integrationServerName -o TCPIP/start/Server -n port -v 1445
mqsichangeproperties IBNODE -e integrationServerName -o TCPIP/stop/Server -n port -v 1445
mqsichangeproperties IBNODE -e integrationServerName -o TCPIP/quiesce/Server -n port,quiesceTimeoutSec -v 1445,30
mqsichangeproperties IBNODE -c Timer -o myTimerService
-n timeoutIntervalSeconds -v 1
This command changes all TimeoutNotification nodes that
are configured to use the myTimerService configurable service, by
configuring them to generate events every second if the node is configured
in Automatic mode.mqsichangeproperties IBNODE -e default -o ContentBasedFiltering
-n cbfEnabled -v true
mqsichangeproperties IBNODE -e default -o ContentBasedFiltering
-n validationThreads -v 5
mqsichangeproperties IBNODE -c JavaClassLoader
-o myJavaClassLoader
-n sharedJarPath
-v /var/app2/jars
mqsichangeproperties IBNODE -c UserDefined
-o MyService1 -n VerifyRequestTimeout -v 60
mqsichangeproperties IBNODE -c UserDefined
-o HTTP_Timeout -n VerifyRequestTimeout -d