User guide

PUSH Model (Receiving Messages by the Server System)
16-5
• Message type ID
Specify the ID that represents the type of message agreed upon with the sender client.
The format used to specify the message type ID must follow "NMTOKEN" of XML and the
characters of the ID must be usable for the file name and directory name. A unique name within
one server system must be given.
• Sender ID (Sender client ID)
Specify the ID for the sender client of the PUSH model agreed upon with the sender client.
The format used to specify the Sender client ID must follow "NMTOKEN" of XML and the
characters of the ID must be usable for the file name and directory name. A unique ID must be
given to each message type ID.
• SOAP signature verification ID
"No Signature" is set by default.
To use the non-repudiation (signature verification) function, specify an alias of the public key for the
sender client. Select the alias specified when the public key obtained from the sender client that
was stored in Preparing a Key Pair and Public Key Used by the Receiver Server.
• Add Sender button
Adds settings of the sender client that sends SOAP messages of the PUSH model of the same
message type ID.
To restrict access to the receiver server, register only one sender client for one message type. For
information on access restriction, refer to the SOAP Service User's Guide.
Clicking the Confirm button at the end enables the Reliable Messaging function, and so the
receiver server can now receive reliable messages.
Note
The Receiver server ID, Sender client ID, and Message type ID are used as the directory name and file
name for storing reliable messages. Therefore, it is necessary to specify characters that can be used
for the directory name and file name in the operating system used. If a character that cannot be used
for the directory name or file name is specified, an error occurs when executing the Reliable Messaging
function.