SOAP and ipMonitor 9.02

Figured out what I was doing wrong.

I was using SoapUI and by default it would build my request as:

<soapenv:Envelope xmlns:soapenv="">schemas.xmlsoap.org/.../" xmlns:ipm="">schemas.ipmonitor.com/.../">

   <soapenv:Header/>

   <soapenv:Body>

      <ipm:MonitorList/>

   </soapenv:Body>

</soapenv:Envelope>

It's working now that I've changed it to this:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsd="">www.w3.org/.../XMLSchema" xmlns:soap="">schemas.xmlsoap.org/.../">

  <soap:Body>

    <MonitorList xmlns="">schemas.ipmonitor.com/.../" />

  </soap:Body>

</soap:Envelope>

Did you ever experiment with the MontiorAdd or MonitorEdit methods of the config API?  Trying to figure out how to format the 'Settings' parameter these two methods take.

I did, but I never really got very far.

The documentation seemed to be non-existent and nothing seemed to work properly for me, so I had to give it up unfortunately.

Good luck to you!

We have been using the soap api for several years to auto manage events.  I found that the best way to handle it was to capture the raw xml message and then transpose the values as needed.  For example, copy the xml into a variable in your code, then use xpath or something to find and replace the values you needed to.  I think you also need to wrap your xml in an export tag, <export>...</export>.

I just ran into this too.  The definition at http://schemas.ipmonitor.com/ipm70/MonitorEdit.htm should have MonitorEdit instead of GroupEdit.

So to get this to work, use MonitorView to get an example config from the server, then use MonitorEdit to push the update back.

The xml structure should look like this:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope ...>
  <soap:Body>
    <MonitorEdit xmlns="...">
      <Settings>
        <monitors xmlns="...">
          <typeid>...</typeid>
          ...
        </monitors>
      </Settings>
    </MonitorEdit>
  </soap:Body>
</soap:Envelope>