In this lab we will show how to deploy iRule resources with a deployment.

3.2.1. iRule Deployment via Bundled Resource

1. Click iApps -> Application Services

2. Click the ‘Create…’ button

3. Populate the following values in the form:

   Field Name	Value
   Name	Lab3.2
   Template	appsvcs_integration_v2.0.003_custom
   Virtual Server: Address	10.1.20.32
   `Virtual Server: Port <AppSvcsiAp p_presoref.html# preso-pool-port> `__	80
   Pool: Pool Table	Row 1: Index: 0 Monitor(s): 0
   Pool: Members	Row 1: Pool Idx: 0 IP/Node Name: 10.1.10.100 Port: 80 Row 2: Pool Idx: 0 IP/Node Name: 10.1.10.101 Port: 80
   Monitor: Monitor Table	Row 1: Index: 0 Name: /Common/http
   Virtual Server: Client-side L4 Protocol Profile	/Common/tcp-wan-optimized
   Virtual Server: Server-side L4 Protocol Profile	/Common/tcp-lan-optimized
   Virtual Server: HTTP Profile	/Common/http
   Virtual Server: Bundled Items	Row 1: Resource: irule:bundle2 Row 2: Resource: irule:bundle1 Note Be sure to preserve the order shown above. iRules are ordered resources and the ordering below is specifically designed to show that this ordering is preserved.

   
   

4. Click the ‘Finished’ button to deploy the template

5. Review the deployed configuration using the iApp Components view

   • Notice that iRule resources were automatically created and attached to the virtual server.

6. Click Local Traffic -> Virtual Server List. Click the ‘Edit…’ link next to the ‘Lab3.2_default_vs_80’ object.

7. Notice the order of the deployed iRules was preserved during the deployment.

3.2.2. iRule Deployment via URL

Note

To complete this lab you must have a web server configured as detailed in the Lab Environment

The second method of resource deployment is via a URL that dynamically loads the resource at runtime. This functionality is fully documented in the Dynamic Loading from URL section of the Reference Guide.

Note

If you specify a hostname in a URL please be sure to configure DNS resolution on the BIG-IP system

1. Click iApps -> Application Services -> Lab3.2 -> Reconfigure

2. Modify the following values and click ‘Finished’:

   Field Name	Value
   Virtual Server: Bundled Items	Row 3: Resource: irule:urloptional=http://<web server IP> /appsvcs/remote_1_optional.irule Row 4: Resource: irule:url=http://<web server IP>/appsvcs /remote_1.irule

   
   

3. Review the deployed config and deployment log

   • Notice that there are now three iRules tied to the Virtual Server
   • The ‘urloptional’ resource does not exist on the remote server therefore the template skipped deployment of that iRule resource.