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. The managed qualities of service, managed persistent and managed non-persistent, are supported by the service integration bus. Use this page to select the bus and messaging engine to use for the reliable messaging protocol state.
To view this pane in the console, click the
following path: .
Note:
- You only need to specify a binding to a bus and messaging engine if you
are using a managed quality of service. If your chosen quality of service
is Unmanaged Non-Persistent, any binding that you specify is ignored. The
quality of service is defined on the WS-ReliableMessaging settings form
for your chosen policy set. For more information, see Configuring the WS-ReliableMessaging policy.
- When many applications use the same messaging engine, it can impact performance. Before you bind a reliable messaging application to a particular messaging engine, check how many other applications are already binding to that messaging engine and, if necessary, create a new messaging engine to bind to your application. In order to make the reliable message application environment more scalable in a cluster, increase the number of messaging engines associated with the cluster.