Use the modifySIBMQLink command to modify the properties of a WebSphere® MQ link.
To run the command, use the AdminTask object of the wsadmin scripting client.
The wsadmin scripting client is run from Qshell. For more information, see Configuring Qshell to run WebSphere Application Server scripts using wsadmin scripting.
print AdminTask.help('SIBAdminCommands')
print AdminTask.help('command_name')
AdminConfig.save()
The modifySIBMQLink command modifies the properties of a WebSphere MQ link.
A WebSphere MQ link.
None.
The queue manager name must conform to the WebSphere MQ naming conventions; for example, the name must be a maximum of 48 characters.
The batch size does not affect the way the sender and receiver channels for this link transfer messages. Messages are always transferred individually, but are committed or backed out as a batch.
For more information about choosing the batch size, see the description of the batch size (BATCHSZ) property in the Intercommunication section of the WebSphere MQ information center.
Default | 50 |
Range | 1 through 9999 |
For information about how to choose an appropriate number, see the description of the Maximum message length (MAXMSGL) property in the Intercommunication section of the WebSphere MQ information center.
Default | 4194304 bytes (4MB) |
Range | 0 through 104857600 Specify 0 to use the largest value that the target queue manager will honor. |
Heartbeats give the receiving channel the opportunity to quiesce the channel connection.
For more information about choosing the value for this property, see the Intercommunication section of the WebSphere MQ information center.
Default | 300 seconds |
Range | 0 through 999999 |
For more information about choosing the value for this property, see the description of the Sequence Number wrap (SEQWRAP) property in the Intercommunication section of the WebSphere MQ information center.
Default | 999999999 |
Range | 100 through 999999999 |
Default | Fast |
Range |
|
If you set this option to True, the WebSphere MQ sender channels might reestablish a connection to this WebSphere MQ link in the event that a communications failure has occurred and the link has not yet detected the failure condition.
Default | True |
Default | Started |
Range |
|
This name must be the same as the name of the receiver channel on WebSphere MQ.
For more information about choosing channel names, see the description of the channel name (CHANNEL) property in the Intercommunication section of the WebSphere MQ information center.
Type the host name or IP address of the host on which the gateway queue manager runs.
If this field is blank, the gateway queue manager is assumed to be running on the same host as the messaging engine on which the WebSphere MQ link is defined.
Default | 1414 |
Range | 0 through 65535 |
The connection names must be given as a comma separated list in the following format:
Dnsname1(portnumber1) , Dnsname2(portnumber2)
Type the DNS name or the IP address of the host on which the gateway queue manager is running. Type the port number in the range 0 through 65535.
If you do not specify the connection name list parameter, the gateway queue manager is assumed to be running on the same host as the messaging engine on which the WebSphere MQ link is defined.
If you do specify the connection list parameter, you must have already specified a value for the sender channel name parameter, otherwise the value that you specify for the connection name list parameter is ignored.
If you specify the host name and port parameter as well as the connection name list parameter, then at runtime the connection name list takes precedence and host name and port values are ignored.
The default value is a reasonable interval. Change this value only if you understand the implications for performance, and you need a different value for the requirements of the traffic flowing down your channels.
Performance is affected by the value specified for the disconnect interval. A very low value (a few seconds) can cause an unacceptable amount of processing in constantly starting up the channel. A very large value (more than an hour) might mean that system resources are unnecessarily held up.
If you want your channels to be active only when there are messages for them to transmit, you should set the disconnect interval to a fairly low value. Note that the default setting is quite high and so is not recommended for channels where this level of control is required. Because it is difficult to interrupt the receiving channel, the most economical option is to have the channel automatically disconnect and reconnect as the workload demands. For most channels, the appropriate setting of the disconnect interval can be established heuristically.
Default | 900 seconds |
Range | 0 through 999999 A value of 0 (zero) means never disconnect; the channel waits indefinitely for messages. |
Default | 10 |
Range | 0 through 999999999 |
For more information about using retry mechanisms with WebSphere MQ, see the Intercommunication section of the WebSphere MQ information center.
Default | 60 seconds |
Range | 0 through 999999 |
For more information about using retry mechanisms with WebSphere MQ, see the Intercommunication section of the WebSphere MQ information center.
Default | 999999999 |
Range | 0 through 999999999 |
For more information about using retry mechanisms with WebSphere MQ, see the Intercommunication section of the WebSphere MQ information center.
Default | 1200 seconds |
Range | 0 through 999999 |
Default | Started |
Range |
|
This name must be the same as the name of the sender channel on WebSphere MQ.
This reliability delivery option is assigned to all WebSphere MQ nonpersistent messages flowing over this receiver channel.
Default | Reliable |
Range |
|
Default | Assured |
Range |
|
Default | Started |
Range |
|
This option is supported only when used by a JMS application that is running with a WebSphere Application ServerVersion 7.0 or later server or client, and that is connected to a messaging engine running on WebSphere Application ServerVersion 7.0 or later server. Use on previous versions of WebSphere Application Server will result in an exception to the application.
Default | TRUE |
Range |
|
Show the properties of a WebSphere MQ link, modify the link to change the batch size, then show the properties of the link again.
wsadmin>AdminTask.showSIBMQLink('[-bus myBus -messagingEngine myHostNode01.server1-myBus -mqLink myMQLink]') '{nonPersistentMessageSpeed=FAST, qmName=myBus, adoptable=false, sequenceWrap=999999999, name=myMQLink, targetUuid=738AE126B908E5451A3D4691, initialState=STARTED, senderChannel=null, brokerProfile=[], receiverChannel=null, preferLocalQueuePoints=true, batchSize=50, uuid=6B89C4F08AB072C5, heartBeat=300, description=null, maxMsgSize=4194304, exceptionDestination=_SYSTEM.Exception.Destination.myHostNode01.server1-myBus}' wsadmin> wsadmin>AdminTask.modifySIBMQLink('[-bus myBus -messagingEngine myHostNode01.server1-myBus -name myMQLink -batchSize 100]') 'myMQLink(cells/cell01/nodes/node01/servers/server1|sib-engines.xml#SIBMQLink_1132608724468)' wsadmin>AdminTask.showSIBMQLink('[-bus myBus -messagingEngine myHostNode01.server1-myBus -mqLink myMQLink]') '{nonPersistentMessageSpeed=FAST, qmName=myBus, adoptable=false, sequenceWrap=999999999, name=myMQLink, targetUuid=738AE126B908E5451A3D4691, initialState=STARTED, senderChannel=null, brokerProfile=[], receiverChannel=null, preferLocalQueuePoints=true, batchSize=100, uuid=6B89C4F08AB072C5, heartBeat=300, description=null, maxMsgSize=4194304, exceptionDestination=_SYSTEM.Exception.Destination.myHostNode01.server1-myBus}' wsadmin>
Modify a WebSphere MQ link so that the link has no preference for which queue points to use.
wsadmin>AdminTask.modifySIBMQLink('[-bus Bus1 -messagingEngine node1.node1server1-Bus1 -name MQLink -queueManagerName QM2 -preferLocal FALSE]') wsadmin>