BIG-IP version 10 introduced the concept of application templates. The goal was to provide a wizard for multiple well-deployed applications, abstracting some of the configuration details and reducing human error in the intricacies of following the deployment guides for these applications. A powerful step forward, but there were some limitations, such as the inability to customize the template or the deployment of that template, nor was there a way to centrally (and singly) clean up a template-driven deployment. However, this was only the beginning of the vision. Enter F5 iApp (tm).

What's an iApp?

An iApp is a user-customizable framework for deploying applications. It consists of three components: Templates, Application Services, and Analytics. An iApp Template is where the application is described and the objects (required and optional) are defined through presentation and implementation language. An iApp Application Service is the deployment process of an iApp Template which bundles all of the configuration options for a particular application together. You would have an iApp Application Service for SharePoint, for example. iApp Analytics include performance metrics on a per-application and location basis.

iApp Essentials: Wiki | Samples |  Forums | APL Reference