This chapter explains how to configure reliable messaging in web service providers and clients.
This chapter covers the following topics:
Table 6–1 describes the reliable messaging configuration options.
Table 6–1 Endpoint Reliable Messaging Configuration Options
Examples and detailed instructions on how to create web service providers and clients that use reliable messaging are provided in the following chapters:
For an example of creating a web service and a client using a web container and NetBeans IDE, see Chapter 3, WSIT Example Using a Web Container and NetBeans IDE.
For an example of creating a web service and a client using only a web container, see Chapter 9, WSIT Example Using a Web Container Without NetBeans IDE.
If Secure Conversation is enabled for the web service endpoint, the web service acquires a Security Context Token (SCT) for each application message sequence, that is, each message sequence is assigned a different SCT. The web service then uses that token to sign all messages exchanged for that message sequence between the source and destination for the life of the sequence. Hence, there are two benefits in using Secure Conversation with Reliable Messaging:
The sequence messages are secure while in transit between the source and destination endpoints.
If there are different users accessing data at the source and destination endpoints, the SCT prevents users from seeing someone else’s data.
Secure Conversation is a WS-Security option, not a reliable messaging option. If Secure Conversation is enabled on the web service endpoint, Reliable Messaging uses Security Context Tokens.
For more information on how to use Secure Conversation, see Chapter 7, Using WSIT Security.