User guide

PUSH Model (Receiving Messages by the Server System)
16-7
Figure 16-2 Reliable Messaging PUSH Screen - Deploying the Sender Application dialog
• Web service identifier
Specify the ID that represents the sender client agreed upon with the receiver server.
• Sender client ID
Specify the ID that represents the sender client agreed upon with the receiver server.
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. Any name that is
unrelated to the machine name and user name is also allowed.
Specify a Sender client ID that is the same to all SOAP messages and transmission destinations in
one client system. Also specify the same Sender client ID if multiple JavaVM operate on one client,
for example, when multiple Java applications are started.
• Message type ID
Specify the ID that represents the type of message agreed upon with the receiver server.
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 client system must be given.