NimbostratusI'm automating F5 Local Traffic Manager actions using an orchestrator and would like to use SOAP web services directly; is there documentation that applies to the structure of SOAP Message bodies? The WSDLs are not as detailed as I would like.
The WSDL is the standard way to describe the SOAP contract between the client and server implementation. I use the WSDL's to generate the client proxy code for the Java and .Net/PowerShell libraries so they should be good from a tool standpoint. The only issue with our implementation is that it's built around RPC/Encoded encoding and some tools have stopped support on that encoding in favor of Document/Literal. Since we have 1000's of customers using our current implementation, it's not so easy to swap out the protocol format so we are stuck with RPC/Enc for the time being.
If our SOAP implementation isn't for you, you might want to take a look at the new REST interface we've introduced. Look at the iControlREST namespace in the wiki and you should find some documentation and samples using it.
-Joe
