iControl Traning ....

I think you still have it a bit backwards. Webservices have two components: a client and a server.

 

 

The server component of iControl is software that is part of the BIG-IP system. The server component is F5's part of the equation and nothing you should be concerned with. We have a web service endpoint listening on our devices and you just create the client code to communicate with it.

 

 

The client portion is typically a proxy library that is created from our supplied WSDL files (basically describe all the web services/methods/parameters). Proxies can be created by various toolkits out there (Axis/.Net/etc). For Axis you will run WSDL2Java on the WSDL files and it will create a bunch of .java wrapper files that make a java binding ontop of our methods. This is the only piece you need to be concerned with.

 

 

With that being said, if you are using .Net or Java, I'd suggest you take a look at the iControl assembly I've created in the Labs section of DevCentral. I've basically wrapped all the proxy code into a distribution making it very easy to program against.

 

 

If I didn't make it clear, please let me know where I need to explain further.

 

 

-Joe