For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Brian_Miller_01's avatar
Brian_Miller_01
Icon for Nimbostratus rankNimbostratus
Mar 25, 2014

Documentation for SOAP Message Body structure

I'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? T...
application delivery
devops
iControl
LTM
management
Joe_Pruitt's avatar
Joe_Pruitt
Mar 25, 2014

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