Automated Updates

In order for a device to poll for, and receive, automated updates it must use the provided REST APIs.

To create an update, the producer must do at least one of the following:

Configure an existing download package and files (files can be stored in FlexNet Operations or can be loaded from an external delivery source),
Associate a download package to a product (for entitlement driven updates),
Configure a new download package to be used as the delivered content.

The next step is for the producer to define an update in FlexNet Operations.

Download packages and updates can be created through the FlexNet Operations Producer Portal UI, through a data import file, or using REST APIs. (Download packages can also be created using SOAP Web Services.)

Client devices must be registered to be able to call into the notification server (this enables the producer to track the device and any updates that are associated with it). A device can either be registered through the UI or it can use the activation ID of a line item to register itself and request an update through a notification command. For more details see either the FlexNet Embedded Client C XT SDK User Guide or the FlexNet Embedded Client .NET XT SDK User Guide.