Параметры WS-ReliableMessaging

For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery.Данный программный продукт применяет эти стратегии к входным и выходным сообщениям.

Для просмотра этой панели консоли выберите следующий путь: Службы > Наборы стратегий > Наборы стратегий приложений > набор-стратегий > WS-ReliableMessaging.

With WebSphere Application Server, you can use WS-ReliableMessaging with Java API for XML-Based Web Services (JAX-WS) 2.0 Web services applications that use a SOAP over HTTP binding. To configure a Web service application to use WS-ReliableMessaging, you attach a policy set that contains a WS-ReliableMessaging policy type. This policy type offers a range of qualities of service: managed persistent, managed non-persistent, or unmanaged non-persistent.

Do not edit the policies associated with the provided default policy sets. If you need to modify the reliable messaging policy settings, use a copy of a default policy set or create a new policy set.

Конфигурация

Стандартный

Select the WS-ReliableMessaging specification to use for reliable transmission of your messages. WS-ReliableMessaging Version 1.1 is the default value. Details of the supported WS-ReliableMessaging specifications are available at the following Web addresses:

The WS-ReliableMessaging specification Version 1.0, February 2005.
The OASIS WS-ReliableMessaging specification Version 1.1, February 2007.

Прим.: If you plan to invoke a .NET-based Web service, you must select WS-ReliableMessaging Version 1.0.

Доставлять сообщения в порядке их отправки

Select this option if the sender of a request has to receive a response before it sends the next request.

Если вы используете упорядоченную доставку, убедитесь, что приложение, делающее запрос, принимает сообщения в правильном порядке. Дополнительная информация приведена в разделе Configuring the WS-ReliableMessaging policy.

При использовании постоянного управляемого QoS включение упорядоченной доставки несколько увеличивает надежность. Дополнительная информация приведена в разделе A message is not recovered after a server becomes unavailable, even with the managed persistent quality of service.

Качество службы

Выберите один из следующих QoS:

Неуправляемый непостоянный — выдерживает сбои сети и удаленной системы.: You can configure Web service applications to use WS-ReliableMessaging with a default in-memory store. This quality of service requires minimal configuration. However it is non-transactional and, although it allows for the resending of messages that are lost in the network, if a server becomes unavailable you will lose messages. This quality of service is for single server only and does not work in a cluster. This quality of service is not supported on the z/OS platform. Используется по умолчанию.
Управляемый непостоянный — выдерживает сбои системы, сети и удаленной системы; но его состояние сбрасывается после перезапуска модуля обмена сообщениями.: This in-memory quality of service option uses a messaging engine to manage the sequence state, and messages are written to disk if memory is low. This quality of service allows for the re-sending of messages that are lost in the network, and can also recover from server failure. However, state is discarded after a messaging engine restart so in this case you will lose messages. This option supports clusters as well as single servers.
Управляемый постоянный — выдерживает сбои системы, сети и удаленной системы.: This quality of service for asynchronous Web service invocations is recoverable. This option also uses a messaging engine and message store to manage the sequence state. Messages are persisted at the Web service requester server and at the Web service provider server, and are recoverable if the server becomes unavailable. Messages that have not been successfully transmitted when a server becomes unavailable can continue to be transmitted after the server restarts.

Прим.:

All three qualities of service are supported when applications are deployed to the application server. Thin client and client container applications use the first option only.
For the unmanaged non-persistent quality of service, the messages are stored only in memory. For both of the managed qualities of service, the messages are managed by a messaging engine backed by a message store.Укажите в форме Привязка стратегии WS-ReliableMessaging привязку к шине и модулю обмена сообщениями. Если выбран QoS "Неуправляемый непостоянный", не использующий привязку к модулю обмена сообщениями, то указанная привязка игнорируется.