LibraryLink ToToggle FramesPrintFeedback

Configuring Standard WS-RM Policy Attributes

You can configure standard WS-RM policy attributes in one of the following ways:

Table 9.3 shows the elements defined in the http://schemas.xmlsoap.org/ws/2005/02/rm/policy namespace:


For more detailed reference information, including descriptions of each element’s sub-elements and attributes, please refer to http://schemas.xmlsoap.org/ws/2005/02/rm/wsrm-policy.xsd.

You can configure standard WS-RM policy attributes by adding an RMAssertion within a Fuse Services Framework rmManager Spring bean. This is the best approach if you want to keep all of your WS-RM configuration in the same configuration file; that is, if you want to configure Fuse Services Framework-specific attributes and standard WS-RM policy attributes in the same file.

For example, the configuration in Example 9.5 shows:

  • A standard WS-RM policy attribute, BaseRetransmissionInterval, configured using an RMAssertion within an rmManager Spring bean.

  • An Fuse Services Framework-specific RM attribute, intraMessageThreshold, configured in the same configuration file.


You can configure standard WS-RM policy attributes within features, as shown in Example 9.6.


If you use the WS-Policy framework to enable WS-RM, you can configure standard WS-RM policy attributes in a WSDL file. This is a good approach if you want your service to interoperate and use WS-RM seamlessly with consumers deployed to other policy-aware Web services stacks.

For an example, see WS-Policy framework—implicitly adding interceptors where the base retransmission interval is configured in the WSDL file.

You can configure standard WS-RM policy attributes in an external attachment file. This is a good approach if you cannot, or do not want to, change your WSDL file.

Example 9.7 shows an external attachment that enables both WS-A and WS-RM (base retransmission interval of 30 seconds) for a specific EPR.