Manual Chapter : Deploying Application Services to Your Devices

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 8.3.0, 8.2.0, 8.1.0, 8.0.0, 7.1.0
Manual Chapter

Deploying Application Services to Your Devices

How do service catalog templates work?

A service catalog template allows you to create and deploy the application services to individual BIG-IP devices or to the auto-scaled BIG-IP VE devices in your cloud. When you create an application service, you decide which objects to include and which settings to revise, and then identify the device, or service scaling group (SSG) to which you want it to deploy.
Both service catalog templates and AS3 templates deploy application services to managed devices. However, the work flow for using each template type is significantly different. For details about how AS3 templates work, refer to Managing BIG-IQ AS3 Templates on

Create and deploy an application service

workflow graphic, create and deploy application service step
Creating a new application service 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 service to your BIG-IP devices. As you create the application service, you define which of the template objects you want to include and revise the settings that need to be customized.
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
    , then, on the left, click
    The screen lists the AS3 and service catalog templates defined on this BIG-IQ.
  2. Under Service Catalog Templates, click
    The Create Service Template screen opens to General Properties.
  3. Use the
    Application Name
    settings under Application Properties to identify this application.
  4. For the
    , select the service catalog template you want to use to create this application from.
    You must use one of these following templates:
    • Default-AWS-f5-HTTPS-WAF-lb-template
    • Default-AWS-f5-HTTPS-offload-lb-template
    • A custom template cloned from either of these two templates.
  5. Use the
    Application Service Name
    settings under General Properties to identify the application service.
  6. For
    Traffic Service Environment
    , select
    Service Scaling Group
    and then select the name of the service scaling group (SSG) to which you want to deploy this application service.
  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
      , select the protocols and ports that the ELB will use to communicate with the devices in this SSG.
    The applications you plan to deploy on this SSG determine 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 applications using either the
    or the
    you must add two new listeners:
    Load Balancer Protocol
    Load Balancer Port
    Instance Protocol
    Instance Port
    SSL Certificate
    Each application you deploy requires its own, dedicated resources. For each application you need:
    • A unique ELB.
    • A security group associated with that ELB.
    • A virtual server port.
    You must use a unique ELB for each SSG to which you deploy application services. AWS does not permit these objects to be shared between SSGs. You can deploy multiple application services to a single SSG, and application services can share an ELB, but only when they deploy to the same SSG.
    For example, you could deploy an application service (
    ) to an SSG (
    ) and use load balancer
    . You could then deploy a second application (
    ) to
    and (again) use
    . The application services can share the load balancer because they are on the same SSG. However, if you want to deploy (
    ) to a different SSG (
    ), you would have to use a new load balancer (
    For an example of how you would configure two applications on the same SSG: You would need two ELBs, each with its own security group. You could use
    Load Balancer Port
    for both ELBs, but the
    Instance Port
    on one ELB could use
    and the second application could use
  8. Determine the objects that you want to deploy in this application service.
    1. To omit any of the objects defined in this template, click the (
      ) 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 that you decide to include in the application service, revise the settings that you need to change.
      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 service is deployed. These objects that don't yet exist in BIG-IQ configuration, but are created when this application service is deployed are prefixed with a pound sign (#). For example, a template could define a pool
      and a node
      . To specify the application service-created object, you select the value prefixed with a pound sign (#) when you select the value for that node. (That option would appear as
      in the example cited here.
  9. If you are using a custom template, for the Load Balancer settings, type
    for both the
    Destination Address
    Destination Network Mask
  10. When you have configured the objects that you want to include in this application service, click
    BIG-IQ creates the application service and deploys it to the SSG you specified.