mediateSIBDestination command
Use the mediateSIBDestination 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.
如果要執行這個指令,請使用 wsadmin Scripting 用戶端的 AdminTask 物件。
wsadmin Scripting 用戶端是從 Qshell 執行.
如需相關資訊,請參閱利用 wsadmin Script 配置 Qshell 來執行 WebSphere Script.
- 如需 Jython 中可用的服務整合匯流排指令清單,以及每個指令的簡要說明,請在 wsadmin 提示下,輸入下列指令:
print AdminTask.help('SIBAdminCommands')
- 如需給定指令的概觀說明,請在 wsadmin 提示下,輸入下列指令:
print AdminTask.help('command_name')
AdminConfig.save()
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 IBM MQ server, and create the corresponding mediation execution point on a cluster or a server.
Target object
None.
Required parameters
- -bus bus_name -destinationName destination_name
- 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 mq_server_name -wmqQueueName mq_queue_name
- [Queue or web service destination] To assign the mediation point to a IBM MQ queue, specify both the name of the IBM MQ server bus member where the mediation point is to be assigned, and the name of the IBM MQ queue to be used to store messages ready for mediation. mq_server_name is the name of the IBM MQ server as specified in the -name parameter when creating the IBM MQ server. mq_queue_name is the name allocated to the IBM MQ queue by IBM MQ administration.
- -node node_name -server server_name
- [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_name
- [Not topic space] To mediate the bus destination to a cluster bus member, specify the name of the cluster.
Optional parameters
- -nonPersistentReliability
Specify the service integration quality of service to use with nonpersistent IBM MQ messages that are received by service integration from a IBM MQ network. IBM MQ 網路中的訊息有它們自己的服務品質層次。這是持續性或非持續性。 當服務整合應用程式收到這些訊息時,它們會被指派服務整合的服務品質層次,這會隨著它們的 IBM MQ 服務品質層次而不同。
For nonpersistent IBM MQ messages received, the default service integration quality of service is RELIABLE_NONPERSISTENT. If you choose to override this default, you will probably choose one of the other nonpersistent service integration qualities of service BEST_EFFORT_NONPERSISTENT or EXPRESS_NONPERSISTENT. However, you can choose any of the five possible service integration qualities of service:- BEST_EFFORT_NONPERSISTENT
- 傳訊引擎停止或失效時捨棄的訊息。訊息也可能因為用來傳送訊息的連線無法使用,或系統資源受到限制,而遭到捨棄。
- EXPRESS_NONPERSISTENT
- 傳訊引擎停止或失效時捨棄的訊息。如果用來傳送訊息的連線無法使用,也可能捨棄訊息。
- RELIABLE_NONPERSISTENT
- 傳訊引擎停止或失效時捨棄的訊息。
- RELIABLE_PERSISTENT
- 當傳訊引擎失敗時,可能會捨棄訊息。
- ASSURED_PERSISTENT
- 不捨棄訊息。
Note: 可靠性層次越高,效能影響越大。For more information, see Mapping the JMS delivery option and message reliability to and from the IBM MQ persistence value.
- -persistentReliability
Specify the service integration quality of service to use with persistent IBM MQ messages that are received by service integration from a IBM MQ network. IBM MQ 網路中的訊息有它們自己的服務品質層次。這是持續性或非持續性。 當服務整合應用程式收到這些訊息時,它們會被指派服務整合的服務品質層次,這會隨著它們的 IBM MQ 服務品質層次而不同。
For persistent IBM MQ messages received, the default service integration quality of service is ASSURED_PERSISTENT. If you choose to override this default, you will probably choose the other persistent service integration quality of service RELIABLE_PERSISTENT. However, you can choose any of the five possible service integration qualities of service:- BEST_EFFORT_NONPERSISTENT
- EXPRESS_NONPERSISTENT
- RELIABLE_NONPERSISTENT
- RELIABLE_PERSISTENT
- ASSURED_PERSISTENT
For more information, see Mapping the JMS delivery option and message reliability to and from the IBM MQ persistence value.
- -useRFH2
- Determines whether service integration technologies includes
an RFH2 header in messages it places on the mediation point. Possible
values are:
- TRUE
- FALSE
- -maintainStrictMessageOrder
- 維護嚴格訊息次序.
Possible values are:
- Selected
- Maintains the order in which a producer sends
messages to the destination.
At run time, this property has priority over other configuration property values. For information on the configuration properties that are overridden at run time, see Strict message ordering for bus destinations.
- Cleared
- Message order is not preserved for this destination.
Example
- Using Jython:
wsadmin>AdminTask.mediateSIBDestination("-bus abus -destinationName myqueue -mediationName filterMed -cluster cluster1")
- Using Jacl:
wsadmin>$AdminTask mediateSIBDestination {-bus abus -destinationName myqueue -mediationName filterMed -cluster cluster1}