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.
About this task
Use this task to complete the following broad actions:
- Attach a reliable messaging policy set (either a default policy set or one that you have created) to an aspect of your application (that is, application level or web service level). Policy sets define the reliability level (quality of service) and other configuration options that you want to apply to your reliable messaging application.
- 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 by using the administrative console, complete the following
steps:
Procedure
- 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.
- 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 .
To
define the bindings for a WebSphere Application Server Version 7.0 or later provider or client
policy set, navigate to or
To
define the bindings for an application that you have attached to a
service provider policy set, navigate to 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
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:
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:
This panel also gives you links to the associated service integration
bus and WS-Notification service.
- 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.