Pattern to named objects

It's handy to have the host-name, port/protocol, and object type in the name:

• www.example.com_443_vs (virtual server)
• www.example.com_443_pl (pool)
• www.example.com_http_pr (http profile)
• www.example.com_tcp_pr (tcp profile)

You want to be able to easily and quickly associate objects together by name and identify the object type. I like to configure organizational base profiles to enforce standards - so "company_name-http" for my standard http profile, and if customizations need to be done for an application, the application would get its own custom profile based on "company_name-http".

I'd agree with shaggy that its good practise to have the object type in the name although I prefer to prefix it rather than suffix it.

I prefer to use service/application names rather than domain names.

In large environments you should probably consider Administrative Partitions to make things more manageable and hopefully minimise issues when the inevitable human errors occur.

Lastly, if you use the CLI then you'll appreciate that shorter labels are better than long.

Thank you partners shaggy and W.L.B. I agree with you. I prefer prefix also, perhaps remembering the time when I was a developer and I wore this pattern. So, This weekend, I needed to rename multiple objects because they were non-production applications and the names would be conflicting with the new production apps. I guessed it best to create separate partitions for environments, but the customer chose to add a suffix "_NPROD" for non-production sites and keep everything in the "Common" partition. Some of you have seen or have a habit of separating non-production sites of production sites into partitions? W.L.B, you mentioned something about partition, this is how do you suggest? Maybe this applies in new environments where we can define patterns, right?