+

Search Tips   |   Advanced Search

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

To configure a web service application to use WS-ReliableMessaging, you attach a policy set containing 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 the application, and (for managed qualities of service) define bindings to a service integration bus and messaging engine.

We can attach a WS-ReliableMessaging policy set and define bindings using the administrative console as described in this task, or we can attach and bind a WS-ReliableMessaging policy set by .

This task assumes that we have already developed and installed the web service application to which to attach a policy set.

The following default policy sets work with WS-ReliableMessaging applications:

For more information, see WS-ReliableMessaging default policy sets.

If we can use any of these default policy sets, or we have configured our own reliable messaging policy set, then you are ready to complete this task.

Use this task to complete the following broad actions:

  1. Attach a reliable messaging policy set (either a default policy set or one that we have created) to an aspect of the application (that is, application level or web service level). Policy sets define the reliability level (quality of service) and other configuration options to apply to the reliable messaging application.

  2. Define the bindings for each attachment to a policy set that specifies a managed quality of service. That is, choose the service integration bus and messaging engine to use to maintain the state for the managed persistent and managed non-persistent qualities of service.

To attach a WS-ReliableMessaging policy set and define bindings using the administrative console...

  1. Attach a policy set to the reliable messaging application at either application level or service level..

    • We can attach one policy set at each level.

    • We can only apply a WS-ReliableMessaging policy at application level or service level.

    • If we apply reliable messaging at service level, then all services must use the same WS-ReliableMessaging policy and bindings values.

    • We 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 the 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 to use.

    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 the application.

    To define the default WS-ReliableMessaging policy binding for provider and client policy set attachments within WAS v6.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 WAS v7 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 we 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 Manage policy sets and bindings for service providers at the application level using the administrative console.

    To define the bindings for an application that we 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 Manage policy sets and bindings for service clients at the application level using the administrative console.

  3. WS-Notification note: If the application that we have attached to a service client policy set is a Version 7.0 WS-Notification service client, we 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:

    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, we 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.

  4. Save the changes to the master configuration.

(zos)


What to do next

If the chosen policy set specifies a managed quality of service, configure the sib.wsrm.tokenLockTimeout custom property on the messaging engine that 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.


Subtopics


Related tasks

  • Add assured delivery to web services through WS-ReliableMessaging
  • Manage policy sets using the administrative console
  • Define and manage policy set bindings
  • Attaching a policy set to a service artifact
  • WS-ReliableMessaging
  • Detecting and fixing problems with WS-ReliableMessaging

    (zos) Service integration custom properties