Mediating a bus destination using the wsadmin tool

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.

[iSeries] 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:

For additional details of the command properties, see the related reference topic.

Purpose

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.

Command name
mediateSIBDestination
Target
None.
Result
A bus destination object.

To save the changes made by the command, invoke the "save" command on the AdminConfig object.

Required parameters

-bus busname-destinationName destname
The destination to be mediated.
-mediationName mediation_name
The name of the mediation to be applied to the bus destination. This mediation must exist before this command can be used.

Conditional parameters

-wmqServer Servername -wmqQueueName Queuename
[Queue or WebService destination] To assign the mediation point to a WebSphere MQ queue, specify both the name of the WebSphere MQ server bus member where the mediation point is to be assigned, and the name of the WebSphere MQ queue to be used to store messages ready for mediation. Servername is the name of the WebSphere MQ server as specified in the -name parameter when creating the WebSphere MQ server definition. Queuename is the name allocated to the WebSphere MQ queue by WebSphere MQ administration.
-node nodename -server servername
[Not topic space] To mediate the bus destination to a server bus member, specify both the name of the node on which the server runs and the name of the server.
-cluster cluster
[Not topic space] To mediate the bus destination to a cluster bus member, specify the name of the cluster.

Optional parameters

-nonPersistentReliability BEST_EFFORT | EXPRESS | RELIABLE_NON_PERSISTENT

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:

BEST_EFFORT_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.

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.

EXPRESS_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
RELIABLE_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails.
RELIABLE_PERSISTENT
Messages may be discarded when a messaging engine fails.
ASSURED_PERSISTENT
Messages are not discarded.
The default is RELIABLE_NONPERSISTENT.
-persistentReliability RELIABLE_PERSISTENT | ASSURED

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:

BEST_EFFORT_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable and as a result of constrained system resources.

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.

EXPRESS_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails. Messages may also be discarded if a connection used to send them becomes unavailable.
RELIABLE_NONPERSISTENT
Messages are discarded when a messaging engine stops or fails.
RELIABLE_PERSISTENT
Messages may be discarded when a messaging engine fails.
ASSURED_PERSISTENT
Messages are not discarded.
The default is ASSURED_PERSISTENT.
-useRFH2 TRUE | FALSE
Determines whether or not service integration technologies includes an RFH2 header in messages it places on the mediation point. Possible values are:
TRUE
FALSE
The default is TRUE.
-maintainStrictMessageOrder TRUE | FALSE
Maintain strict message order
Selected
Maintains the order in which a producer sends messages to the 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.

Cleared
Message order is not preserved for this destination.

Example

wsadmin>$AdminTask mediateSIBDestination {-bus abus -destinationName myqueue
 -mediationName filterMed -cluster cluster1}



Related concepts
WebSphere MQ queue points and mediation points
WebSphere MQ server and mediated exchange scenarios
Mediations
Related tasks
Creating the queue-type destination and assigning it to a WebSphere MQ queue
Mediating a destination using a WebSphere MQ queue as the mediation point
Related reference
Destinations administrative commands
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=rjo_cli_dest_mediate
File name: rjo_cli_dest_mediate.html