Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Manage application monitor templates and component monitors > Configure the SOAP monitor

Configure the SOAP monitor

The are two ways to configure the SOAP monitor:

  • Loading a WSDL file.
  • Manually entering XML.

Load WSDL Files

The SOAP monitor within SAM currently supports the WSDL schema, which must be exposed on a URL. Once the WSDL file is successfully loaded, the file is parsed automatically and the fields, highlighted below, populates. Once the WSDL file has been successfully loaded, you can specify values for the available arguments. There are two types of arguments, simple, and complex.

A simple argument is one where you can define the value directly. A complex argument (e.g. structures, classes, list, and so on) must be user-defined in the XML format. It is recommended that complex arguments be used only by experienced users.

The Advanced Settings are read-only and displays additional information. Because the SOAP envelope is based on the WSDL schema, the Advanced Settings values should not be changed.

The SOAP XML field contains the SOAP envelope which is generated by the WSDL and dynamically changes as you make changes to the SOAP settings. In this field you can check what is to be sent to the web service.

Important: If changes are made to any of the base SOAP settings, the content of the SOAP XML is re-generated and your changes become lost.

Manually Enter XML

The following is an example of a Complex argument and would be placed in the Parameters field. SAM automatically takes the code and place it where it belongs in the envelope:

<tempPhoneNumber xmlns:ns2="" xsi:type="ns2:Array" ns2:arrayType="ns1:TemporaryPhoneNumber[3]">
  <item xsi:type="ns1:TemporaryPhoneNumber">
    <startDate xsi:type="xsd:int">37060</startDate>
    <endDate xsi:type="xsd:int">37064</endDate>
    <phoneNumber xsi:type="xsd:string">+1-212-5551234</phoneNumber>
  <item xsi:type="ns1:TemporaryPhoneNumber">
    <startDate xsi:type="xsd:int">37074</startDate>
    <endDate xsi:type="xsd:int">37078</endDate>
    <phoneNumber xsi:type="xsd:string">+1-212-5554321</phoneNumber>
  <item xsi:type="ns1:TemporaryPhoneNumber">
    <startDate xsi:type="xsd:int">37088</startDate>
    <endDate xsi:type="xsd:int">37092</endDate>
    <phoneNumber xsi:type="xsd:string">+1-212-5557890</phoneNumber>

XML can also be entered manually by typing or pasting XML.

Last modified
15:36, 10 Nov 2016