Implement the OTA Updates module

You can implement the OTA Updates module by creating an OTA Updates property configuration for your application or site in Control Center, changes to your existing server configuration if necessary, and testing before production activation.

How to

  1. Perform the initial integration tasks.
    1. Create your origin server DNS record.
      For more information, see Create DNS server records.
    2. Establish an SSL certificate.
  2. Configure an OTA Updates property.
    1. Create an OTA Updates property.
      For more information, see Create an OTA Updates property.
    2. Associate a property hostname to an EIB edge hostname.
    3. For EIB configurations only: Associate a test hostname to an edge hostname.
    4. Configure the mandatory and recommended behaviors in the default rule.
    5. Configure the OTA Updates recommended behaviors.
    6. Configure the authentication method for OTA Updates clients.
      For more information, see Configure authentication.
    7. Configure optional behaviors.
      For more information, see Optional behaviors.
  3. Test the OTA Updates configuration.
    1. Activate the OTA Updates property in the staging environment.
    2. Point your browser to edge servers.
      For more information, see Point your browser to an edge server.
  4. Activate the OTA Updates configuration.
    1. For EIB configurations only: Point your browser to the EIB edge server.
    2. Activate the OTA Updates property in the production environment.
    3. Optional: Verify the Edge IP Binding feature of the OTA Updates property.
      For more information, see Verify the Edge IP Binding configuration.
    4. Change the DNS record to point to your configuration.