How to use REST to create a Virtual Server with profile

It's perhaps worth mentioning that with protocol profiles, you need to add the 'context' key if you specify more than one.

If you specify only one, it will be used as the Client Side profile and the Server Side profile will be set to "(Same as Client)".

But if you want them to be different, you need to use something like this:

profiles = [
  {
    'name': '/Common/tcp-lan-optimized',
    'context': 'serverside'
  },
  {
    'name': '/Common/tcp-wan-optimized',
    'context': 'clientside'
  }
]

This is from the Ruby code we use to set both of the TCP profiles.

We have been able to use the REST interface to create VIPs with all of their subcomponents without the need for a POST followed by a PUT, so far. That includes most profiles, persistence profiles, enabled VLANs, iRules... I haven't come across something I couldn't set on the first pass.

This running BIGIP 12.1.2 software, though. Other versions may have more limitations.