-
Title
Why am I seeing UNKNOWN_SOAP_SERVICE for my SOAP Web Service name? -
Description
Why am I seeing UNKNOWN_SOAP_SERVICE for my SOAP Web Service name (i.e. 'Service Name')?
-
Cause
You have not passed a wsdl file files (to describe your SOAP service) into Foglight Experience Monitor (FxM) _and_ there is no "SoapAction" HTTP header in your xml file.
-
Resolution
RESOLUTION 1
Upload your wsdl file to FxM. You do this on the 'Configure' | 'Monitoring' | 'SOAP' page of the FxM web console UI.
(Notes: the wsdl file does not need to be re-added every time the wsdl file changes--only when new SOAP Operations are added or the Web service name changes. FxM is only looking at the WSDL for the relationship between the two. The system will use the WSDL files to correlate SOAP Operations with a specific Web Service--this is strongly recommended for SOAP 1.2 applications. The 'Service Name' column will contain the name of the service that has been extracted from the WSDL file. The 'Servers' column displays the servers where the WSDL file is in use. The 'Ports' column displays the ports that the SOAP services are utilizing. So, all those fields on the screen get populated by what is in the wsdl file.
RESOLUTION 2
Have the people responsible for the SOAP applications add the SoapAction header and set its value to be the Web Service name.
(Notes: This allows you avoid needing to add the wsdl file. If FxM doesn't have that file entered in, it will look for the "SoapAction" HTTP header to try to use that for the Web Service name. Keep in mind that starting with SOAP version 1.2, the SoapAction HTTP header stopped becoming mandatory and became optional. And if its not present (and no wsdl file has been entered), then FxM will just use the UNKNOWN_SOAP_SERVICE as the name for the Web Service ('Service Name').