Work with DeviceID+

After you have deployed DeviceID+ on your web application using the BIG-IP iApp, you may want to fine tune the iApp configuration to better suit your system needs. These instructions present some advanced configuration options for the DeviceID+ iApp template in the BIG-IP.

To configure the DeviceID+ iApp template in the BIG-IP:

  1. In the Main tab in the BIG-IP, go to iApps>Application Services>Applications and select your iApp from the list.

  2. Click the Reconfigure tab (see below).


    The DeviceID+ iApp template configuration settings appear.

  3. At Configuration Level, select Advanced.

  4. In the JS Injection Configuration section:

    • Location for Shape JS Injection: From the drop-down list, select a location in the HTML code of your webpage for the Shape JS Injection.
    • Script Attribute: Choose an attribute that is added at the end of the injected Shape JavaScript, either Async, Sync or Defer. This attribute determines how the JavaScript is loaded and executed.
    • Inject Shape JS in Specific Webpages Only: Select Yes to inject the Shape JS in specific web pages of your web application. Select No to inject the Shape JS in all web pages of your web application.
    • JS Injection Paths: If Inject Shape JS in specific webpages only = Yes, enter here the paths of the webpages in your application to receive the Shape JS injections.
    • Exclude Shape JS injection from specific webpages: Select Yes to exclude the Shape JS injection from specific web pages in your web application.
    • JS Excluded Paths: If you set Exclude Shape JS injection from specific webpages = Yes, enter here the paths of the web pages in your application that the Shape JS injections should be excluded from.
    • Add Additional JS API Endpoints: If the Shape JavaScript is updated with a new endpoint(s) for Telemetry post requests, select Yes and enter the endpoint(s) provided to you from F5 support here.
  5. In the Pool Configuration section:

    • Cookie Persistence for Shape Protection Pool: Select Enable if, after initial load balancing, you want HTTP requests of the same session always sent to the same pool member in the Shape Protection Pool. Select Disable if you want the BIG-IP to perform standard load balancing.
    • Use a Different Domain as a Pool Member: Set to Yes if want all HTTP requests to be directed to a domain that is not the domain in Shape JR URL path.
    • Domain: If you set Use a Different Domain as a Pool Member=Yes, enter here the domain to receive HTTP requests.
    • Add HTTP Health Check: Choose whether to perform the HTTP Health Check on the entire pool. The HTTP Health Check is performed in intervals of 5 seconds. If you activate the health check, the following related settings are displayed:
      • Liveness Path: The path to the site where the health check will be performed on the entire pool.
      • Port: The port on which the health check is performed.
      • Response Code: Enter the code that will indicate a successful health check result in the response from the site that was checked.
  6. In the Advanced Features section:

    • Rewrite XFF Header with Connecting IP: Select Yes to add an XFF header to requests.


      If an HTTP profile attached to one of the web application’s virtual servers has an XFF header added to it and Rewrite XFF header with connecting IP = Yes, requests will show duplicate client IPs in the XFF headers. To avoid this situation, either remove the XFF header from the HTTP profile or set Rewrite XFF header with connecting IP = No.

    • Choose a Parent Server-Side SSL Profile for Shape Pool: Select an SSL profile (or use the default) that will be attached to a new virtual server for routing traffic to the Shape pool.


      Selecting an SSL profile here is mandatory, and only one SSL profile can be selected.

    • Encrypting Virtual Server IP: A default IP is assigned. If you have a virtual server already configured to this IP, assign a different IP here.

    • Use SNI: Select Yes to use Server Name Indication (SNI) for pool members.

    • Enable Debug: Select Yes to enable debug logs.