You can gradually introduce JAX-WS based client and provider entities such that a migrated Version 6.1 WS-Notification configuration is ready to be configured for reliable notification.
For reliable notification, you apply policy sets that include WS-ReliableMessaging to your WS-Notification configuration. You can only use policy sets with Java™ API for XML-based Web Services (JAX-WS) applications, and with Version 7.0 WS-Notification services and service points.
The WS-Notification implementation in WebSphere Application Server Version 6.1 uses service integration bus-enabled web services to expose the WS-Notification service endpoint, so that it can be invoked by applications and configured with specific attributes such as WS-Security or JAX-RPC handlers. However, the Version 6.1 implementation is not compatible with JAX-WS handlers or applications, and it cannot compose with WS-ReliableMessaging.
To prepare a migrated Version 6.1 WS-Notification configuration for reliable notification, you must recreate your Version 6.1 WS-Notification services and service points as Version 7.0 WS-Notification services and service points, and recreate each JAX-RPC client application to which you want to apply a policy set as a JAX-WS application. Note that you can continue to use JAX-RPC applications with Version 7.0 WS-Notification services and service points, and that you only have to recreate those applications that must work with policy sets.
For information about coding JAX-RPC and JAX-WS client applications to perform specific WS-Notification tasks, see Developing applications that use WS-Notification. You might also find it useful to learn about JAX-WS and the JAX-WS client programming model. This should help you to determine the effort involved in porting client code from JAX-RPC to JAX-WS, or to validate JAX-WS client to JAX-RPC web service interoperability.
To support a phased approach to preparing for reliable notification, and to describe the four main configurations that you might want to achieve, this task is divided into four subtasks: