Attaching and binding a WS-ReliableMessaging policy set to a web service application by using the administrative console

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. Use the administrative console to attach the policy set to your application, and (for managed qualities of service) define bindings to a service integration bus and messaging engine.

1. Attach a policy set to your reliable messaging application at either application level or service level..
   Note:

   • You can attach one policy set at each level.
   • You can only apply a WS-ReliableMessaging policy at application level or service level.
   • If you apply reliable messaging at service level, then all services must use the same WS-ReliableMessaging policy and bindings values.
   • You can attach any policy set at operation level. For a policy set that includes the WS-ReliableMessaging policy, attachment at the operation level configures the other components of the policy set (for example WS-Security and WS-Addressing) but any WS-ReliableMessaging configuration at operation level is ignored.
2. If your chosen policy set specifies a managed quality of service, define bindings to a service integration bus and messaging engine.

   If the policy set instance specifies managed non-persistent or managed persistent quality of service, choose the service integration bus and messaging engine that is to manage the WS-ReliableMessaging state. Use the WS-ReliableMessaging policy binding panel to select or create the service integration bus and messaging engine that you want to use.

   Note: When many applications use the same messaging engine, it can impact performance. Factors to consider include the number of applications that are already binding to the messaging engine, the CPU utilization, and the message throughput. To improve performance for a single server configuration, create a new messaging engine to bind to your application.

   To define the default WS-ReliableMessaging policy binding for provider and client policy set attachments within WebSphere® Application Server Version 6.1 applications, and for attachments to service applications that are deployed to a Version 6.1 server, navigate to Services > Policy sets > Default policy set bindings > Version 6.1 default policy set bindings > WS-ReliableMessaging.

   To define the bindings for a WebSphere Application Server Version 7.0 or later provider or client policy set, navigate to Services > Policy sets > General provider policy set bindings > provider_policy_set_binding_name > WS-ReliableMessaging or Services > Policy sets > General client policy set bindings > client_policy_set_binding_name > WS-ReliableMessaging

   To define the bindings for an application that you have attached to a service provider policy set, navigate to Applications > Application Types > WebSphere enterprise applications > application_name > [Web Service Properties] Service provider policy sets and bindings and follow the instructions given in Managing policy sets and bindings for service providers at the application level using the administrative console.

   To define the bindings for an application that you have attached to a service client policy set, navigate to Applications > Application Types > WebSphere enterprise applications > application_name > [Web Service Properties] Service client policy sets and bindings and follow the instructions given in Managing policy sets and bindings for service clients at the application level using the administrative console.

   WS-Notification note: If the application that you have attached to a service client policy set is a Version 7.0 WS-Notification service client, you can instead use the context-specific version of the Service client policy sets and bindings panel that can be reached through either of the following paths:

   • Service integration > WS-Notification > Services > service_name > [Additional properties] Outbound request policy sets and bindings
   • Service integration > Buses > bus_name > [Services] WS-Notification services > service_name > [Additional properties] Outbound request policy sets and bindings

   If you want to configure policy set and binding details for a single Version 7.0 WS-Notification service client, rather than for all clients for the service, you can instead use the following panel:

   • Services > Service clients > ws-notification_service_client_name

   This panel also gives you links to the associated service integration bus and WS-Notification service.
3. Save your changes to the master configuration.

What to do next

If your chosen policy set specifies a managed quality of service, configure the sib.wsrm.tokenLockTimeout custom property on the messaging engine that you specified in the policy binding. Set the value of the property to be less than the amount of time that the control region waits before ending an inactive servant region. Setting this value ensures that the control region does not end the servant region while WS-ReliableMessages are locked. Refer to Service integration custom properties for more information.