Defined Asset Configuration

Note: This feature is part of the separately licensed Axeda ConnectedConfiguration feature. If the Axeda Platform is not licensed for ConnectedConfiguration, you will not have access to Defined Asset Configurations.

An Actual Asset Configuration is a tree of key/value pairs (Configuration Items) which contain metadata about a specific Asset. The key corresponds to the Path expression which leads to the value. An Actual Asset Configuration represents the current state of the related asset.

An Asset Configuration that is NOT bound to any specific asset is a Defined Configuration. Defined Configurations can be used for comparisons against Actual Asset Configurations. A Defined Configuration may specify the ideal configuration for an asset. Expression rules can be defined to evaluate Actual Configurations against a Defined Configuration and perform actions based on the results of the comparison.

Creating Defined Configurations

Defined configurations are specified using expression rules. Asset Configuration functions (such as CfgBoolValue, CfgHas, CfgStrValue, and so forth) enable you to compare the values of specific configuration elements of an asset. The Platform saves the results of the comparison, which can be used in later processing.

 

Defined Configuration Dependency

Packages

When creating a software package with the Axeda Software application, you can assign a Defined Configuration as a dependency.

For example, you could create a defined configuration named Windows XP with the following expression:

CfgHas("/Computer/Software/OS/Name", "Windows XP Professional", "any")

Assigning this defined configuration dependency to a software package would restrict the package to assets matching this expression, with the OS Name of “Windows XP Professional”.

NOTE: You cannot edit defined configurations that are currently being used as dependencies on packages.

Deployments

When creating a deployment with the Axeda Software application, you can select a defined configuration to specify routing criteria. These requirements must be met before the deployment can be deployed to a given asset.