STATE_DISABLED STATE_ENABLED VERIFICATION_STATUS_UNKNOWN VERIFICATION_STATUS_NONE VERIFICATION_STATUS_SIGNATURE_NOT_VERIFIED VERIFICATION_STATUS_SIGNATURE_VERIFIED VERIFICATION_STATUS_CHECKSUM_NOT_VERIFIED VERIFICATION_STATUS_CHECKSUM_VERIFIED TMOS_MODULE_ASM TMOS_MODULE_SAM TMOS_MODULE_WAM TMOS_MODULE_PSM TMOS_MODULE_WOM TMOS_MODULE_LC TMOS_MODULE_LTM TMOS_MODULE_GTM TMOS_MODULE_UNKNOWN TMOS_MODULE_WOML TMOS_MODULE_APML TMOS_MODULE_EM TMOS_MODULE_VCMP TMOS_MODULE_TMOS TMOS_MODULE_HOST TMOS_MODULE_UI TMOS_MODULE_MONITORS TMOS_MODULE_AVR TMOS_MODULE_PEM TMOS_MODULE_CGNAT TMOS_MODULE_AFM TMOS_MODULE_AM TMOS_MODULE_SWG TMOS_MODULE_FPS TMOS_MODULE_ILX Gets the names of all application templates.

Gets the names of the actions in the application templates.

Creates a set of application templates. Each template automatically is created with a default empty "definition" action.

Deletes a set of application templates.

Deletes all application templates.

Sets the descriptions for the specified appliation templates.

Gets the descriptions for the specified application templates.

Sets the minimum version of BIG-IP for which this template is valid. Attempting to create an application from this template on an incompatible version of BIG-IP will produce an error. The version is of the form #.#.#, #.#, or #. For example, "11", "11.1", and "11.1.2" would all be valid version strings.

Computes and adds a checksum to each specified template. To each template, either checksum or signature can be added but not both. The system will throw if both algorithms are attempted on one template.

Computes and adds a signature to each specified template. The signature is used during template validation to assure that the template's fields - presentation, implementation, help and macro have not been modified. To each template, either checksum or signature can be added but not both. The system will throw if both algorithms are attempted on one template.

Clear both signature and checksum fields for the specified templates. The difference between enabling "ignore_verification" and "clear_verification" is: "ignore" suspends the verification temporarily while leaving the signature and checksum fields intact. Verification can be resumed. "clear" resets for good the signing information as if the templates had never been signed.

Sets the ignore verification state for the specified templates. If enabled, the system will ignore the signature or checksum. Otherwise the signature or checksum is used during template validation to assure that the template's field - presentation, implementation, help and macro have not been modified.

Gets the state of ignoring the signature or checksum.

Gets the minimum version of BIG-IP for which this template is valid.

Sets the maximum version of BIG-IP for which this template is valid. Attempting to create an application from this template on an incompatible version of BIG-IP will produce an error. The version is of the form #.#.#, #.#, or #. For example, "11", "11.1", and "11.1.2" would all be valid version strings.

Gets the maximum version of BIG-IP for which this template is valid.

Sets the list of modules required by each template. Attempting to create an application from this template when one or more of these modules are not provisioned will produce an error. Note: Beginning with BIG-IP_v11.4.0 if TMOS_MODULE_WAM, TMOS_MODULE_WOM, TMOS_MODULE_WOML, and/or TMOS_MODULE_AM is specified then TMOS_MODULE_AM will be set as the prerequisite module.

Gets the list of modules required by the specified templates.

Gets the error string indicating the prerequisite errors for a template. A blank string indicates no errors. A non-blank error string means that there are prerequisites for the template that are not met on that machine, and creating a system application object from that template on that machine will result in an exception. Note that the contents of the error string are meant to be human readable. While the presence of a non-blank error string can be used programmatically, the contents should only be used for non-programmatic purposes.

Gets the verification status for the specified templates.

Sets the presentation text for a set of actions in application templates. The presentation contains Application Presentation Language (APL) text that describes what input is needed and how it should be displayed in the UI.

Gets the presentation text for the specified application template actions.

Sets the implementation script text for a set of actions in an application templates. The implementation is a TMSH script that can use the answers to the questions in the presentation, provided as variables, to create the configuration objects that make up the application service. This script is executed whenever the application is created or modified.

Gets the implementation script text for the specified application template actions.

Sets the HTML help text for a set of actions in application templates.

Gets the HTML help text for the specified application template actions.

Gets the version information for this interface.

Gets the names of all application templates.

Gets the names of the actions in the application templates.

Creates a set of application templates. Each template automatically is created with a default empty "definition" action.

Deletes a set of application templates.

Deletes all application templates.

Sets the descriptions for the specified appliation templates.

Gets the descriptions for the specified application templates.

Sets the minimum version of BIG-IP for which this template is valid. Attempting to create an application from this template on an incompatible version of BIG-IP will produce an error. The version is of the form #.#.#, #.#, or #. For example, "11", "11.1", and "11.1.2" would all be valid version strings.

Computes and adds a checksum to each specified template. To each template, either checksum or signature can be added but not both. The system will throw if both algorithms are attempted on one template.

Computes and adds a signature to each specified template. The signature is used during template validation to assure that the template's fields - presentation, implementation, help and macro have not been modified. To each template, either checksum or signature can be added but not both. The system will throw if both algorithms are attempted on one template.

Clear both signature and checksum fields for the specified templates. The difference between enabling "ignore_verification" and "clear_verification" is: "ignore" suspends the verification temporarily while leaving the signature and checksum fields intact. Verification can be resumed. "clear" resets for good the signing information as if the templates had never been signed.

Sets the ignore verification state for the specified templates. If enabled, the system will ignore the signature or checksum. Otherwise the signature or checksum is used during template validation to assure that the template's field - presentation, implementation, help and macro have not been modified.

Gets the state of ignoring the signature or checksum.

Gets the minimum version of BIG-IP for which this template is valid.

Sets the maximum version of BIG-IP for which this template is valid. Attempting to create an application from this template on an incompatible version of BIG-IP will produce an error. The version is of the form #.#.#, #.#, or #. For example, "11", "11.1", and "11.1.2" would all be valid version strings.

Gets the maximum version of BIG-IP for which this template is valid.

Sets the list of modules required by each template. Attempting to create an application from this template when one or more of these modules are not provisioned will produce an error. Note: Beginning with BIG-IP_v11.4.0 if TMOS_MODULE_WAM, TMOS_MODULE_WOM, TMOS_MODULE_WOML, and/or TMOS_MODULE_AM is specified then TMOS_MODULE_AM will be set as the prerequisite module.

Gets the list of modules required by the specified templates.

Gets the error string indicating the prerequisite errors for a template. A blank string indicates no errors. A non-blank error string means that there are prerequisites for the template that are not met on that machine, and creating a system application object from that template on that machine will result in an exception. Note that the contents of the error string are meant to be human readable. While the presence of a non-blank error string can be used programmatically, the contents should only be used for non-programmatic purposes.

Gets the verification status for the specified templates.

Sets the presentation text for a set of actions in application templates. The presentation contains Application Presentation Language (APL) text that describes what input is needed and how it should be displayed in the UI.

Gets the presentation text for the specified application template actions.

Sets the implementation script text for a set of actions in an application templates. The implementation is a TMSH script that can use the answers to the questions in the presentation, provided as variables, to create the configuration objects that make up the application service. This script is executed whenever the application is created or modified.

Gets the implementation script text for the specified application template actions.

Sets the HTML help text for a set of actions in application templates.

Gets the HTML help text for the specified application template actions.

Gets the version information for this interface.

An Application Template is used to create and modify Application Services. The template provides a custom UI (presentation) to present questions to the user that are needed to create the application. The implementation script is executed when the application is created or modified to create the necessary configuration objects from the user supplied answers to the presentation questions.