Valores de WS-ReliableMessaging

For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the option to use the WS-MakeConnection protocol for synchronous two-way message exchange, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery. El producto fuerza estas políticas en mensajes de entrada y las aplica en mensajes de salida.

Para ver este panel en la consola, pulse en la vía de acceso siguiente: Servicios > Conjuntos de política > Conjuntos de políticas de aplicación > nombre_conjunto_políticas > 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.

Pestaña Configuración

Estándar
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.
Nota: If you plan to invoke a .NET-based Web service or host a Web service that is compatible with reliable .NET clients, you must select WS-ReliableMessaging Version 1.0.
Entregar los mensajes en el orden en el que se han enviado

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

Si habilita la entrega en orden, también debe asegurarse de que la aplicación receptora efectúe un sondeo para obtener los mensajes en el orden en el que desea recibirlos. Para obtener más información, consulte Configuring the WS-ReliableMessaging policy.

Si se especifica la entrega en orden se aumentará ligeramente la fiabilidad si utiliza la calidad de servicio persistente gestionada. Para obtener más información, consulte A message is not recovered after a server becomes unavailable, even with the managed persistent quality of service.

Calidad de servicio
Seleccione una de las siguientes calidades de servicio:
No persistente y no gestionada - Tolera anomalías de red y sistema remoto
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. El valor predeterminado es No persistente y no gestionada.
Gestionada no persistente - Tolera anomalías de sistema, red y sistema remoto, pero se descarta el estado después del reinicio del motor de mensajería
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, if a server becomes unavailable you will lose messages. This option supports clusters as well as single servers.
Gestionada persistente - Tolera anomalías de sistema, red y sistema remoto
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.
Nota:
  • 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. Especifique un enlace a un bus y mensaje de mensajería en el formulario Enlace de política WS-ReliableMessaging. Si la calidad de servicio seleccionada es No persistente y no gestionada, que no utiliza un enlace con un motor de enlace, se ignoran todos los enlaces que especifique.



Los enlaces marcados (en línea) requieren acceso a Internet.

Conceptos relacionados
Tareas relacionadas
Referencia relacionada


Nombre de fichero: uwbs_wsspsrmd.html