Forum Discussion
Jun 08, 2007
The notification mechanism is via a HTTP-POST call formatted as a SOAP message. If you don't want to implement a webservice listener, then you can still build a listener that works. The only requirements is that you make it "look" like a web service. You'll need to be able to parse the SOAP content in the HTTP POST body. And after that you'll need to return a response with a valid SOAP response indicating success. Here's a response returned from the BIG-IP default listener
HTTP/1.1 200 OK
Date: Fri, 08 Jun 2007 14:56:13 GMT
Server: Apache
Secure;
Connection: close
Transfer-Encoding: chunked
Content-Type: text/xml; charset="UTF-8"
1cexmlns:E="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:A="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:s="http://www.w3.org/2001/XMLSchema-instance"
xmlns:y="http://www.w3.org/2001/XMLSchema"
xmlns:iControl="urn:iControl"
E:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">xmlns:m="urn:iControl:Management/EventNotification">
0
If you go that route, good luck. We'll do our best, but if you are rolling your own implementation, then it might be harder for us to help you out if you get stuck.
-Joe