Applies To:

Show Versions Show Versions

Manual Chapter: Deploying Applications to your Devices
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Deploying Applications to your Devices

Deploying applications to the devices in a service scaling group

Using a service template created by your network engineer, you create and deploy the applications used by the auto-scaling BIG-IP VE devices in your cloud. When you create an application, you decide which objects to include and which settings to revise and then identify the service scaling group (SSG) to which you want it to deploy.

Create and deploy an application

Before you can create and deploy an application, you must have a service template.


Creating a new application from a template allows you to start from the set of objects defined in the template, modify or add objects, and then deploy the application to your BIG-IP devices. As you create the application, you define which of the template objects you want to include and revise the settings that need to be customized.
Note: Your service template must have an HTTP profile associated with its virtual server, or you will not be able to deploy it.
  1. At the top of the screen, click Applications then, on the left, click APPLICATIONS.
    The screen displays the list of applications currently defined on this device.
  2. Click Create.
    The Create Application screen opens.
  3. For the Template, select the service template you want to use to create this application from.
  4. Use the Name and Description fields to identify this application.
  5. For Environment, identify where you want the application to deploy.
    If you select then
    Select Service Scaling Group From Service Scaling Group, select the name of the service scaling group to which you want to deploy this application.
    Select BIG-IP
    1. From BIG-IP, select the name of the device to which you want to deploy this application.
      Important: If you deploy an application to one of the members in a sync-failover group, the devices in the group must be set to Auto-sync. Otherwise, when the application deploys, the sync-failover group is out of sync, so the group cannot fail-over if the active device goes offline.
    2. To gather statistical data about the performance of this application on the device you deploy it to, select Collect HTTP Statistics.
  6. Determine the objects that you want to deploy in this application.
    1. To omit any of the objects defined in this template, click the (X) icon that corresponds to that object.
    2. To create additional copies of any of the objects defined in this template, click the (+) icon that corresponds to that object.
    3. For each object you decide to include in the application, revise the settings that you need to change.
      Note: When you specify values for fields that reference other configuration objects, you can select objects that already exist in BIG-IQ configuration. But you can also specify objects that are created when this application is deployed. These objects that don't yet exist in BIG-IQ configuration, but are created when this application is deployed are prefixed with a pound sign (#). For example a template could define a pool MyPool1 and a node 45.54.45.54. To specify the application-created object, you select the value prefixed with a pound sign (#) when you select the value for that node. (That option would appear as #45.54.45.54 in the example cited here.
  7. Specify settings for the ELB that triggers device scaling for this SSG.
    1. For Name of Classic Load Balancer, type the name of the load balancer you created for this application.
    2. For Listeners, select the protocols and ports that the ELB will use to communicate with the devices in this SSG.
    Note: The application you plan to deploy on this SSG determines which ELB listener settings are required. Use the protocol and port appropriate for the template used to create this application. For example, if you intend to deploy an application using either the Default-AWS-f5-HTTPS-WAF-lb-template or the Default-AWS-f5-HTTPS-offload-lb-template, you must add two new listeners.
    Load Balancer Protocol Load Balancer Port Instance Protocol Instance Port Cipher SSL Certificate
    TCP 443 TCP 443 N/A N/A
    TCP 80 TCP 80 N/A N/A
    Note: Each application you deploy requires a unique ELB. Similarly, the security group associated with the ELB must be unique. Neither of these AWS objects can be shared when you deploy multiple applications to an SSG.
    Note: The virtual server port for each application in an SSG must be unique. Applications can share an external port, but not the virtual server port. For example: you could configure two applications on the same SSG using Load Balancer Port 80 for both ELBs. But for the Instance Port, the ELB for one application could use 1000 and the second application could use 2000.
  8. If you are using a custom template, for the Load Balancer settings, type 0.0.0.0 for both the Destination Address and Destination Network Mask.
  9. When you have configured the objects that you want to include in this application, click Create.
    BIG-IQ creates the application and deploys it to the target you specified.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.

Additional Comments (optional)