The iApps™ framework consists of two main components, application services and templates.
iApps application services use templates to guide users through configuring new BIG-IP® system configurations. An application service lets an authorized user easily and consistently deploy complex BIG-IP® system configurations just by completing the information required by the associated template. Every application service is attached to a specific configuration and cannot be copied the way that iApps templates can.
iApps templates create configuration-specific forms used by application services to guide authorized users through complex system configurations. The templates provide programmatic, visual layout and help information. Each new application service uses one of the templates to create a screen with fields and help that guide the user through the configuration process and creates the configuration when finished.
iApps templates allow users to customize by either modifying an existing template or creating one from scratch. Users can create scratch-built templates using either the iApps Templates screen or any text-editing software.
iApps™ application services generate configurations based on application-centric user entries dictated by the template being used.
The BIG-IP® system comes with several system-supplied templates that you can use as-is to create your application services. You can also use the system-supplied templates as a starting point for your own templates, or you can write templates from scratch using, variously, tmsh and Tcl for the back-end template implementation section, the iApps application programming language for the presentation section, and HTML for the help section.
Before modifying any template, you must license the BIG-IP® modules used by that template.
Ensure that you have administrator privileges on the BIG-IP system you are using to modify a copied template.
An iApps™ application service lets you create and deploy new configurations by filling out screens with forms generated by the underlying information in the iApps template. Within the BIG-IP® Configuration utility, iApps users can manage, reconfigure, and view statistics about an application service once it is created.
The standard BIG-IP® user roles have built-in permission settings for iApps™. Only certain system user roles can create, edit, or delete templates or application services. All user roles with system access can see the contents of iApps templates and application services.
|BIG-IP role||Manage application services?||Edit templates?|
The user roles displayed in the BIG-IP® Configuration utility are identified by slightly different names in tmsh. The cross-reference table below shows the Configuration utility user role name and the corresponding tmsh name.
|Configuration utility user role name||tmsh value||Associated BIG-IP® module|
|Web Application Security Administrator||web-application-security-administrator||ASM™|
|Web Application Security Editor||web-application-security-editor||ASM™|
When you are working in the Application Services properties screen, and select the Advanced view , the Strict Updates field is shown. Selecting Strict Updates protects against accidental changes to an application service's configuration. The Strict Updates setting is on by default when an application service is created.
When the strict updates setting is enabled, users can control only objects that are exposed through the templates. Template reentrancy, covered in the template authoring, is not recommended if strict updates is turned off.