Use this command to mediate a bus destination for a service integration bus.
Mediating a destination associates a mediation with a selected bus destination. At run-time, the mediation applies some message processing to the messages handled by the bus destination. Note that you can only mediate a destination with a single mediation at a time. You can mediate more than one destination with the same mediation.
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 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 mediates a bus destination for a service integration bus. There are parameters that you can use to create a mediation queue point on a WebSphere MQ server, and create the corresponding mediation execution point on a cluster or a server.
To save the changes made by the command, invoke the "save" command on the AdminConfig object.
Determines the service integration quality of service level property for WebSphere MQ messages that are received by service integration from a WebSphere MQ network. The messages in a WebSphere MQ network have their own quality of service level which is determined by WebSphere MQ. However when these messages are received by a service integration mediation, they are accorded a service integration quality of service level property that depends on their WebSphere MQ quality of service level.
For example, if a WebSphere MQ message is nonpersistent, using this attribute, you can specify that a service integration mediation which examines the quality of service level will observe best effort nonpersistent, express nonpersistent, reliable nonpersistent, reliable persistent or assured persistent (the default is reliable nonpersistent). If the mediation places the message on a service integration queue point without changing the quality of service level, service integration uses this quality of service level for the message.
Possible values are:
For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.
Determines the service integration quality of service level property for WebSphere MQ messages received by service integration from a WebSphere MQ network. The messages in a WebSphere MQ network have their own quality of service level which is determined by WebSphere MQ. However when these messages are received by a service integration mediation, they are accorded a service integration quality of service level property which is dependent on their WebSphere MQ quality of service level.
For example, if a WebSphere MQ message is persistent, using this attribute, you can specify that a service integration mediation which examines the quality of service level will observe best effort nonpersistent, express nonpersistent, reliable nonpersistent, reliable persistent or assured persistent (the default is assured persistent). If the mediation places the message on a service integration queue point without changing the quality of service level, service integration uses this quality of service level for the message.
Possible values are:
For non-transactional JMS message-driven beans and MessageListeners that use a JMS destination configured on the default messaging provider, best-effort nonpersistent messages are not recoverable. In this case, if a message is unlocked because the message-driven bean or MessageListener threw an exception, then the message is not redelivered or sent to the exception destination because it was deleted from the message store when it was passed to the listener. If you require higher message reliability for non-transactional JMS message-driven beans and MessageListeners, configure a different option for the Maximum reliability property of the bus destination.
At runtime, this property has priority over other configuration property values. For information on the configuration properties that are overridden at runtime, see Strict message ordering for bus destinations.
wsadmin>$AdminTask mediateSIBDestination {-bus abus -destinationName myqueue -mediationName filterMed -cluster cluster1}