WSReliableMessaging policy and binding properties

Use the attributes parameter for the setPolicyType and setBinding commands to specify additional configuration information for the ReliableMessaging policy and policy set binding. The WSReliableMessaging quality of service (QoS) is only available for application policy sets.

WSReliableMessaging is an interoperability standard for the reliable transmission of messages between two endpoints. Use WSReliableMessaging to secure and verify transactions when using web services between businesses.

請利用 AdminTask 物件 PolicySetManagement 群組中的下列指令和參數來自訂您的原則集配置。
  • 利用 getPolicyType 和 getBinding 指令的 -attributes 參數來檢視原則和連結配置的內容。 如果要取得屬性,請將內容名稱傳給 getPolicyType 或 getBinding 指令。
  • 利用 setPolicyType 和 setBinding 指令的 -attributes 參數來新增、更新或移除原則和連結配置中的內容。 如果要新增或更新屬性,請指定內容名稱和值。 如果屬性存在,setPolicyType 和 setBinding 指令會更新值,如果屬性不存在,會新增屬性和值。 如果要移除屬性,請將值指定為空字串 ("")。 -attributes 參數會接受內容物件。
Note: 如果 -attributes 參數提供的內容名稱或值無效,setPolicyType 和 setBinding 指令會發生失敗,且出現異常狀況。 無效的內容會在 SystemOut.log 檔中,記載為錯誤或警告。 不過,指令異常狀況不一定包含造成異常狀況之內容的詳細資訊。 當 setPolicyType 和 setBinding 指令失敗時,請檢查 SystemOut.log 檔中,是否有任何錯誤和警告訊息指出 -attributes 參數的輸入包含一或多個無效的內容。
Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
適用於轉換使用者 適用於轉換使用者: 在 WebSphere Application Server 7.0 版及更新的版本中,安全模型已加強為以網域為中心的安全模型,而不是基於伺服器的安全模型。 另外,本產品的這個版本也變更了預設廣域安全 (Cell) 層次和預設伺服器層次連結的配置。 在 WebSphere Application Server 6.1 版 Feature Pack for Web Services 中,您可以為 Cell 配置一組預設連結,也可以選擇性地為每部伺服器配置一組預設連結。在 7.0 版及更新的版本中,您可以配置一或多個一般服務提供者連結,以及一或多個一般服務用戶端連結。 在配置一般連結之後,您可以指定其中一個連結作為廣域預設連結。您也可以選擇性指定作為應用程式伺服器或安全網域預設值的一般連結。trns

為了支援混合 Cell 的環境,WebSphere Application Server 支援 7.0 版和 6.1 版連結。 一般的 Cell 層次連結專用於 7.0 版及更新的版本,應用程式特定連結保持應用程式所需要版本。 當使用者建立應用程式專用連結時,應用程式伺服器會判斷供應用程式使用所需要的連結版本。

WSReliableMessaging policy properties

Configure the WSReliableMessaging policy by specifying the following properties with the setPolicyType command:
specLevel
Choose the WS-ReliableMessaging standard to use for reliable transmission of your messages. The WS-ReliableMessaging specification Version 1.1 is the default value. Use the following information to choose a specification level:
  • Specify 1.0 as the value for the specLevel attribute to use the WS-ReliableMessaging specification Version 1.0, February 2005 specification level.
  • Specify 1.1 as the value for the specLevel attribute to use the OASIS WS-ReliableMessaging specification Version 1.1, August 2006 specification level.
The following example code sets the specLevel property to the OASIS WS-ReliableMessaging specification Version 1.1, August 2006:
AdminTask.setPolicyType('[-policySet "CustomWSReliableMessaging"  -policyType 
 WSReliableMessaging -attributes "[[specLevel 1.1]]"]')
inOrderDelivery
Specifies whether to process messages in the order that they are received. If you use the inOrderDelivery property, then inbound messages might be queued while waiting for earlier messages.
The following example code enables the inOrderDelivery property:
AdminTask.setPolicyType('[-policySet "CustomWSReliableMessaging" -policyType WSReliableMessaging -attributes "[[inOrderDelivery true]]"]')
qualityOfService
Specifies the quality of the WSReliableMessaging service to use. Define one of the following three values for the qualityOfService attribute:
  • unmanagedNonPersistent

    This setting tolerates network and remote system failures. The unmanagedNonPersistent quality of service is non-transactional. With this setting configured, messages are lost if a server fails. This quality of service is supported for all environments only if the environment is configured as a web service requester.

  • managedNonPersistent

    This setting tolerates system, network, and remote system failures. However, the message state is discarded when the messaging engine restarts. The managedNonPersistent quality of service is non-transactional. This setting prevents message loss if a server fails. However, messages are lost if the messaging engine fails. Managed and thin client applications cannot use this quality of service.

  • managedPersistent

    This setting tolerates system, network, and remote system failures. With this setting, messages are processed within transactions, persisted at the web service requester and provider. Messages can be recovered if a server fails. Messages that are not successfully transmitted at the time of failure continue when the messaging engine or application restarts. Managed and thin client applications cannot use this quality of service.

The following example sets the qualityOfService property as unmanaged nonpersistent:
AdminTask.setPolicyType('[-policySet "CustomWSReliableMessaging" -policyType 
 WSReliableMessaging -attributes "[[qualityOfService unmanagedNonPersistent]]"]')
The following example uses the setPolicyType command to set a value for each policy property:
AdminTask.setPolicyType('[-policySet "CustomWSReliableMessaging" -policyType 
 WSReliableMessaging -attributes "[[specLevel 1.1][inOrderDelivery true][qualityOfService 
 unmanagedNonPersistent]]"]')

WSReliableMessaging binding configuration attributes

If you set the qualityOfService policy property to managedNonPersistent or managedPersistent, configure the WSReliableMessaging binding by specifying values for the following properties with the setBinding command:
busName
The name of the service integration bus that contains the messaging engine to use for the managedNonPersistent or managedPersistent Quality of Service options.
The following example sets the busName property as myBus:
AdminTask.setBinding('[-bindingLocation "" -bindingName cellWideBinding2 -policyType 
 WSReliableMessaging -attributes "[[busName myBus]]"]')
messagingEngineName
The name of the messaging engine to use for the managedNonPersistent or managedPersistent quality of service options.
The following example sets the messagingEngineName property as messagingEngine001:
AdminTask.setBinding('[-bindingLocation "" -bindingName cellWideBinding2 -policyType 
 WSReliableMessaging -attributes "[[messageEngineName messageEngine001]]"]')
The following code example demonstrates how to use the setBinding command to set values for each binding attribute:
AdminTask.setBinding('[-bindingLocation "" -bindingName cellWideBinding2 -policyType 
 WSReliableMessaging -attributes "[[busName myBus][messageEngineName messageEngine001]]"]')

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:14
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rxml_wsfpreliablemessaging
檔名:rxml_wsfpreliablemessaging.html