User guide
Chapter 16: How to Use Reliable Messaging Function for Web Services (SOAP)
16-2
PUSH Model (Receiving Messages by the Server
System)
In the PUSH model, the sender application of the client system sends a SOAP message and the
receiver application of the server system receives the SOAP message to process it.
Table 16-1 lists the items that must be agreed upon between the applications.
Table 16-1 PUSH Setting Items
PUSH sender (client system) setting item PUSH receiver (server system) setting item
Message type ID Message type ID
Receiver server ID Receiver server ID
Sender client ID Sender client ID
Key pair of the sender client Public key obtained from the sender client
Public key obtained from the receiver server Key pair of the receiver server
URL with which the receiver server of the
PUSH model is registered
URL with which the receiver server of the PUSH
model is registered
Each ID must be agreed upon in advance before specifying it for registration of Web service information.
To use the non-repudiation (signature option) function, it is necessary to prepare a key pair to be used
for SOAP digital signature for each side and to exchange the public keys of the sender client and
receiver server in advance using a file.
It is also necessary to place a sender application and a receiver application separately in the receiver
server environment and sender client environment respectively and to register Web service information
for each application.
Preparing a Key Pair and Public Key Used by the Receiver Server
This section shows the procedure for using the non-repudiation (signature option) function.
The examples shown in this section specify commands used in an Interstage certificate environment.
Refer to "Certificate Management" for more information.
For using an old version of certificate environment, refer to "Configuring an Old Certificate Environment
or Client System Certificate Environment."
Prepare a key pair for the receiver server. The key pair is the same as that for the SOAP digital
signature.
An example of command execution for generating a key pair for the receiving server is shown below:
scsmakeenv -n serverkey -f filename