Use this command to change properties of a WebSphere® MQ link.
This command provides only a subset of the properties available. If you want to modify other properties, you need to use the administrative console or wsadmin and JACL
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 the topic "Configure Qshell to run WebSphere Application Server scripts".
This command is only valid when used with WebSphere Application Server Version 6.1 and later application servers. Do not use it with earlier versions.
Command-line help is provided for service integration bus commands:
wsadmin> $AdminTask help SIBAdminCommands
wsadmin> $AdminTask help command_name
For additional details of the command properties, see the related reference topic.
This command modifies the properties of a WebSphere MQ link.
To save the changes made by the command, invoke the "save" command on the AdminConfig object.
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 considerations when choosing the number for batch size, see the description of the Batch size (BATCHSZ) property in the WebSphere MQ Intercommunication book.
Default | 50 |
Range | 1 through 9999 |
For considerations when choosing the number for message size, see the description of the Maximum message length (MAXMSGL) property in the WebSphere MQ Intercommunication book.
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 considerations when choosing the number for this property, see the WebSphere MQ Intercommunication book.
Default | 300 seconds |
Range | 0 through 999999 |
This is the highest number the message sequence number reaches before it restarts at 1.
For considerations when choosing the number for this property, see the WebSphere MQ Intercommunication book.
Default | 999999999 |
Range | 1 through 999999999 For considerations when choosing the number for this property, see the description of the Sequence Numberwrap (SEQWRAP) property in the WebSphere MQ Intercommunication book. |
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 considerations when choosing channel names, see the description of the Channel name (CHANNEL) property in the WebSphere MQ Intercommunication book.
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 2147483647 |
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 excessive overhead in constantly starting up the channel. A very large value (more than an hour) could 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 considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
Default | 60 seconds |
Range | 0 through 999999 |
For considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
Default | 999999999 |
Range | 0 through 999999999 |
For considerations when using retry mechanisms with WebSphere MQ, see the WebSphere MQ Intercommunication book.
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 |
|
wsadmin>$AdminTask showSIBMQLink {-bus myBus -messagingEngine myHostNode01.server1-myBus -mqLink myMQLink} {sequenceWrap=999999999, uuid=88096617A1EE8A4C, name=myMQLink, initialState=STARTED, senderChannelAttribut es={senderChannelName=mySenderChannel, shortRetryInterval=60, protocolName=OutboundBasicMQLink, port=1414, longRetryCount=999999999, longRetryInterval=1200, shortRetryCount=10, senderChannelInitialState=STARTED, d iscInterval=900}, targetUuid=39B3369E108F4A77C1EAF57A, heartBeat=300, adoptable=true, nonPersistentMessage Speed=FAST, receiverChannelAttributes={inboundPersistentReliability=ASSURED, receiverChannelInitialState=S TARTED, receiverChannelName=myReceiverChannel, inboundNonPersistentReliability=RELIABLE}, batchSize=50, qm Name=myQueueManager, maxMsgSize=4194304} wsadmin>$AdminTask modifySIBMQLink {-bus myBus -messagingEngine myHostNode01.server1-myBus -name myMQLin -batchSize 100} myMQLink(cells/myHostCell01/nodes/myHostNode01/servers/server1|sib-engines.xml#SIBMQLink_1132608724468) wsadmin>$AdminTask showSIBMQLink {-bus myBus -messagingEngine myHostNode01.server1-myBus -mqLink myMQLink} {sequenceWrap=999999999, uuid=88096617A1EE8A4C, name=myMQLink, initialState=STARTED, senderChannelAttribut es={senderChannelName=mySenderChannel, shortRetryInterval=60, protocolName=OutboundBasicMQLink, port=1414, longRetryCount=999999999, longRetryInterval=1200, shortRetryCount=10, senderChannelInitialState=STARTED, d iscInterval=900}, targetUuid=39B3369E108F4A77C1EAF57A, heartBeat=300, adoptable=true, nonPersistentMessage Speed=FAST, receiverChannelAttributes={inboundPersistentReliability=ASSURED, receiverChannelInitialState=S TARTED, receiverChannelName=myReceiverChannel, inboundNonPersistentReliability=RELIABLE}, batchSize=100, q mName=myQueueManager, maxMsgSize=4194304}