User guide

Settings for the SOAP Digital Signature
15-11
Web service identifier
Enter the identifier of the Web service.
For information on how to specify the Web service identifier, refer to Chapter 9 Managing Web
Service Information in the SOAP Service User's Guide.
[Server Function]: Response Sending setup: SOAP signature generation
[Client Function]: Request Sending setup: SOAP signature generation
Set whether to generate the SOAP digital signature when sending a request of a SOAP message
or a response.
"No" is set by default.
[Server Function]: Response Sending setup: Details button
[Client Function]: Request Sending setup: Details button
This button is used to switch between "Details" and "Standard" view of the SOAP digital signature
generation setting.
The above figure shows when the Details button has been clicked.
SOAP signature target
Specify the signature targets.
If the object being signed is the XML element with the ID attribute or the attachment file, select
"URI/ID" and then specify the signature target.
If XPath is to be used to specify the signature target, select "XPath" and then describe the
signature target.
For information about how to specify the signature target, refer to Specifying the Signature
Target.
Xpath or URI/ID
Set how to specify the signature target. "XPath" or "URI/ID" can be set. "XPath" is set by
default.
Add Signature Target button
As many signature targets as desired can be specified. To add two or more signature targets,
click the Add Signature Target button to add the next signature target.
[Server Function]: Request Sending setup: Destination role (actor) name
[Client Function]: Response Sending setup: Destination role (actor) name
Specify the URI of the intermediary of the SOAP message if he (she) should perform some
operation. Omitting this item will specify the behavior for the ultimate destination of the SOAP
message.
[Server Function]: Request Sending setup: mustUnderstand
[Client Function]: Response Sending setup: mustUnderstand
Specify whether the receiver of the SOAP message must always process elements in the header or
the processing is selectable.
"No processing required" is set by default.