Each time the WSA starts up, each WSA instance receives a unique, alphanumeric identifier (WSA ID), which the WSA always places in a log file entry that indicates the WSA is starting up. This WSA ID appears in the log file similar to this example, always appearing after the "ID":

ID 2bbafbc35852308b:7a8a02:f18e8ee918:-8000

When a WSA instance first receives a request for one of its deployed Web services, the WSA instance assigns the request an alphanumeric identifier (request ID) that is unique for the current session of the WSA instance. When the WSA logs information about a Web service request, whether the information concerns processing steps or errors, the WSA always includes its unique request ID in the log entry text using the following format, where reqid-value is the request ID for the Web service request to which the log entry applies:

(reqid:reqid-value)

When the WSA returns a SOAP fault to a client, it includes the request ID of the Web service request that triggered the SOAP fault, as well as the WSA ID of the WSA instance where the Web service is deployed. The WSA places these two IDs within the <requestID> element of the SOAP fault message according to the following format, where wsaid-value is the WSA ID and reqid-value is the request ID:

wsaid-value#reqid-value

The client can then obtain these two IDs from the <requestID> element of the SOAP fault and provide it to the WSA host operator to look up more detailed information in the corresponding entries of the WSA log file. The WSA operator then uses the WSA ID to locate the WSA log file for the corresponding WSA instance. They can now open the log file and search for log file entries that contain the "(reqid:reqid-value)" string to find all information related to the specific request and WSA instance.