The following figure shows the message flow when the WS-RM 1.2 functionality is used:

Figure 34-2 Message flow when the WS-RM 1.2 functionality is used

1. Exchanging the WS-RM Policy
   Exchange the availability and the WS-RM Policy of the WS-RM 1.2 functionality between the message source and the destination. Exchange the WS-RM Policy by coding the WS-RM Policy specifications in the WSDL file.
   
2. Generating a sequence
   Before sending the application message, generate a sequence and share RMS and RMD. A sequence is a context related to a set of a series of application messages that are sent by using the WS-RM 1.2 functionality. The sequence generation processing is automatically executed when the Web Service method is invoked for the first time for a port object.
   
3. Sending application messages
   After the sequence is generated, RMS sends the application messages to RMD. A sequence identifier and a message number are added to the application messages to be sent.
   
4. Closing the sequence
   When the sending of the application messages is completed, RMS can close the sequence. Once the sequence is closed, RMS cannot send and receive new application messages. Even if the sequence is closed, the related resources are saved and not destroyed. The sequence closing operation is executed when the close method is invoked on the Web Service client side.
   
5. Terminating the sequence
   When the sending of the application messages is completed, RMS terminates the sequence. When the sequence is terminated, the related resources are destroyed. To generate the sequence again, reacquire the port object and invoke the Web Service method.
   

Hereafter, the messages related to the sequence generation, the sequence closure, and the sequence termination are collectively called Sequence life cycle messages.