Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Reliable messaging (WS-ReliableMessaging)
Develop a reliable web service application
Develop a JAX-WS provider or requester application that can compose with a WS-ReliableMessaging-enabled policy set.
At any stage - that is, before or after we have built your reliable web service application, or configured your policy sets - you can set a property that configures endpoints to only support clients that use reliable messaging. This setting is reflected by WS-Policy if engaged. We can develop a JAX-WS web service requester application that sends messages reliably, or a web service provider application that requires reliable messaging. Your client application can also take programmatic control of WS-ReliableMessaging sequences.
Procedure
- Develop your JAX-WS web service application.
For a Web service requester application that sends messages reliably:
- Get an implementation WSDL document, and select the SOAP over HTTP binding. The WSDL should be WS-I Basic Profile compliant.
- Build the JAX-WS application from the WSDL implementation document.
- (Optional) Enable transaction support for outbound (requester) one-way message sends. See Provide transactional recoverable messaging through WS-ReliableMessaging.
- (Optional) Use the waitUntilSequenceCompleted method on the sequenceManager to ensure that reliable messaging state is released after the client finishes messaging, as described in the Controlling WS-ReliableMessaging sequences programmatically topic.
- (Optional) To use in-order delivery (that is, you want WS-ReliableMessaging to make messages available to your requester application in the order that they were sent), then also configure your requester application to poll for the messages in the order in which it should receive them. See Configure the WS-ReliableMessaging policy.
For a web service provider application that requires reliable messaging:
- Write or get an interface WSDL document that describes the service interface. The document should be compliant with the WS-I Basic Profile.
- Write or get an implementation WSDL document, and select the SOAP over HTTP binding. The WSDL should remain WS-I Basic Profile compliant.
- Build the JAX-WS application from the WSDL implementation document.
- Enable your client application to take programmatic control of WS-ReliableMessaging sequences.
This helps manage resources on the server, for example by removing sequences after a client application has finished messaging. We can add code to create sequences, send acknowledgement requests, close sequences, terminate sequences and wait until sequences are complete. For more information, including example code, see Controlling WS-ReliableMessaging sequences programmatically.
What to do next
You are now ready to configure a policy set instance to enable WS-ReliableMessaging.
Related
Controlling WS-ReliableMessaging sequences programmatically
Provide transactional recoverable messaging through WS-ReliableMessaging
JAX-WS application deployment model
Add assured delivery to web services through WS-ReliableMessaging
WS-ReliableMessaging
Configure endpoints to only support clients that use WS-ReliableMessaging
Detecting and fixing problems with WS-ReliableMessaging
Related
WS-ReliableMessaging - requirements for interaction with other implementations