LibraryLink ToToggle FramesPrintFeedback

Configuring WS-RM Persistence

The Fuse Services Framework WS-RM features already described in this chapter provide reliability for cases such as network failures. WS-RM persistence provides reliability across other types of failure such as an RM source or an RM destination crash.

WS-RM persistence involves storing the state of the various RM endpoints in persistent storage. This enables the endpoints to continue sending and receiving messages when they are reincarnated.

Fuse Services Framework enables WS-RM persistence in a configuration file. The default WS-RM persistence store is JDBC-based. For convenience, Fuse Services Framework includes Derby for out-of-the-box deployment. In addition, the persistent store is also exposed using a Java API. To implement your own persistence mechanism, you can implement one using this API with your preferred DB Developing Applications Using JAX-WS.

[Important]Important

WS-RM persistence is supported for oneway calls only, and it is disabled by default.

Fuse Services Framework WS-RM persistence works as follows:

To enable WS-RM persistence, you must specify the object implementing the persistent store for WS-RM. You can develop your own or you can use the JDBC based store that comes with Fuse Services Framework.

The configuration shown in Example 9.14 enables the JDBC-based store that comes with Fuse Services Framework.


The JDBC-based store that comes with Fuse Services Framework supports the properties shown in Table 9.4.


The configuration shown in Example 9.15 enables the JDBC-based store that comes with Fuse Services Framework, while setting the driverClassName and url to non-default values.