iApps typically come in the form of a .tmpl file, which contains the content
needed for the BIG-IP to utilize it as a Service framework.
Different toolkits will install iApps in different ways. We’ll be using the
REST API in a raw form, so the content of the file is what
we need. As a result, we need to ensure that the content of the iApp is URL
encoded to make sure the BIG-IP reads the payload correctly. This is specific
for the iApp deployment over REST API. When using other tools like Ansible, the
whole .tmpl file can be uploaded, removing the need for encoding.
Note
This lab work will be performed from
Lab2.2-DeployingiAppTemplatesonBIG-IP folder in the Postman
Collection
Perform the following steps to complete this task:
Send the Step2:InstallAppSvcsv2.0.004iAppTemplate
request to install the App Services iApp template:
Review the Request JSON Body, and the Response JSON
Body. In this task we installed the App Services iApp Template
and the BIG-IP sent back a response that the iApp was installed with its
object name.
Note
The JSON body in the Request portion is automatically generated
as part of the build process for the App Services iApp and the request
in the Postman Collection was copied from a pre-built collection that
ships with releases of the App Services iApp template.
