Deploying Configurations

Use the Device Manager page to deploy configurations and apply them to deployed applications.

Before you begin

The software and configurations must be uploaded to the Edge Manager Repository.

About this task


  1. In the left navigation pane, select Device Manager > Devices.
  2. To deploy configurations to multiple devices, Create and apply filters, or select devices by clicking the box on the left of the device.
    1. Once the devices are selected, select Device Operations > Deploy Configuration, then go to Step 4.
  3. To deploy configurations to a single device, click the device in the device list, then click the Configurations tab.
    The Deployment Schedule section displays information about software and configuration packages deployed to the device, including:
    • Name – The name of the software or configuration package.
    • Version – The version of the software or configuration package.
    • Revision – This field displays only for configurations.
    • Status – The status of the deployment. Statuses include:
      • In Progress – When one or more tasks begins progress, and some tasks are successful, some are pending, and no failure occurs, a number displays how many are still incomplete, for example, In Progress (4).
      • Pending – All tasks have a pending status before an operation starts.
      • Success – The deployment succeeded.
      • Failed – The deployment failed.
        Note: If the installation script for the package saves messages to a status file, the Failed status is a clickable link, which launches a window with an error message about why the installation failed.
      • Canceled – The deployment was canceled.
      • Unknown – The status is unknown.
    • Retries – The number of times the task has been retried.
    • Scheduled On – The date and timestamp for when the deployment is scheduled.
    • Scheduled By – The name of the user who scheduled the deployment.
    • Start – The date and timestamp for when the deployment starts (the package begins downloading to the device).
    • Execution Start – The date and timestamp for when the installation of the package starts on the device.
    • End – The date and timestamp for when the installation is complete.
    • Description – The description for the package.
    • Execution Logs – Once the installation has a status of "Finished," you can click the details link to view the detailed log for the installation. Until the installation is complete, "Not available" is displayed.
      Note: This feature is not supported on some devices, in which case, "Not available" is displayed.
    1. Click Deploy Configurations, then go to Step 4.
  4. In the drop-down list at the top right of the configurations list, select:
    • Predix Edge – Select if you are deploying configurations to apply to applications that are deployed to devices running Predix Edge OS.

    Click on a configuration name to display the files included in the configuration package. Click Back to go back to the configurations list.

  5. If you selected Predix Edge in the previous step, click Next to specify the application ID to which you are applying the configuration, then click Next.
  6. If you are deploying to Predix Edge, click Next again to schedule the deployment, otherwise, click Schedule.
  7. In the Schedule Deployment dialog, select the date and time for deployment to the device.
    Note: You can set the time zone timestamp formatting (UTC or local) in the Settings page.
    1. In Timeout, set the timeout for each operation in weeks, days, hours, minutes, or seconds, per device.
      Note: When the operation is not scheduled, the timeout starts from the moment you create the task. When the operation is scheduled, the timeout is the scheduled time plus the timeout time you set.
    2. (Optional) In the Retries field, enter a number for how many times to retry the deployment in case of failure (including if the deployment times out).
    3. Click Submit.
    The Deployment Status dialog appears.
  8. In the Deployment Status dialog box, click Close.
    The configuration is deployed and applied to the application.