A package is a combination of header information, conditions to be met, and instructions that you define and that Axeda® Agents execute. Each package is assigned a name and asset model. In addition, each package can have a set of conditions, called dependencies, which must be met for the instructions to be carried out. Instructions are the operations that the Agent performs once the conditions are met. Operations can include running applications, transferring files to or from assets, and restarting the Agent or the asset itself.
A package can be logically considered in the following parts:
o The package Header contains information used in communicating the package status between the Axeda® Platform and the Agent.
o Preprocess conditions (called dependencies) determine if a package is downloaded to the selected assets. These conditions include checks for package version as well as information sent to the Platform by an Agent. The Agent in turn checks values of data items and can perform custom-defined checks to determine if the package should be executed.
o Instructions perform actions, including uploading and downloading files, setting values for data items, executing applications, and restarting the Agent or asset. Rollback instructions perform the same types of actions in the event that the Agent encounters an error that causes it to stop processing the package.
o In-process dependencies (a Wait For Condition instruction) check the state of defined data items as well as custom conditions and waits for them to become true before executing the succeeding instructions.
Notes: Not all agents support
all dependenices or instructions. For complete information about the features
of packages supported by agents, refer to Package
Features Supported by Axeda Agents.
For complete instructions for IDM Agents, refer to the document, Axeda
Platform Software Management: A Guide for Axeda IDM Users.
For information about security for packages, refer to Security
for Objects in Axeda® Connected Product Management Applications
and for information about security for these objects when Delegated Administration
is enabled, refer to Security
for Objects in Delegated Administration Units.
In a Platform where Delegated Administration is enabled, the names of packages
may contain prefixes. For details, refer to Names
of Objects in DA Units.