I'am creating some objects on my lab environment and just discover iApps.
It's a best practice mix some iApps with "traditional" deployment?
It's iApps recommended on a real production environment with hundreds or thousands of VServers?
In a real case, I don't know which way choose, cause maybe for http, microsoft related Apps and similar there are some templates, but maybe you can have some Apps "uniAPPable" and mix those process could be confusing..
I'm wrong? It's a better use iApps as possible and mix with manual definitions?
Roughly 1/3 of F5 customers use iApps, so it's safe to say that they are interesting. There is nothing to prevent you from mixing iApp-controlled config with manual config, and it is common practice to do so. In fact, iApps inherently provide protection for the config that they generate in order to prevent inadvertent manual tampering--a property called "strict-updates." iApps are especially popular for more complex configurations, like Microsoft Exchange, for example, which requires up to 1200 mouse clicks to configure manually and 50 mouse clicks to configure with the iApp. iApps are also often used to roll out a cookie-cutter config to multiple BIG-IP's. Some customers run hundreds of iApps, some run none--the choice is yours.
Thank you Fred! I will follow your advice and work with it!