The New Package wizard prompts you for the information required to create a software package that can be deployed to assets.
Important! Not all agents support all types of dependencies or instructions. For complete information about the features of packages supported by agents, refer to Package Features Supported by Axeda Agents.
The wizard information for a package is presented as follows:
o Package Definition - configure the basic information required for a package: a name, a model number, a version number for the package, and, optionally, a description and expiration date of the package.
o Dependencies - select the conditions that must be met for this package to be deployed and for the package to perform its instructions. Depending on the condition you select, appropriate configuration options are presented in this page. Not all agents support all dependencies.
o Instructions - define what actions the agent will perform while running the package on the asset. Also from this page you can select to create custom components to use within the instructions. Not all Agents support all instructions. To see which instructions are supported by the Agents, refer to Package Features Supported by Axeda Agents
o Rollback Instructions - define what actions, if any, an agent will perform if it encounters an error while running the package on the asset. Axeda Agent Embedded, the Axeda IDM Agents, and the AWP agents do NOT support rollback instructions.
o Privileges - select which user groups can view and deploy packages and which can modify and delete packages.
o Package Confirmation - for the configuration properties specified for the package, save the package to the database; otherwise, change the properties before saving or cancel the package configuration altogether.
Warning! When moving backward and forward through the wizard, use the wizard's Back and Next buttons. Do NOT use your browser's back and forward tools.
1. Type a name for the package that will uniquely identify the package in the application displays and in the Axeda Platform.
2. Select an asset Model from the list of models configured in the database. This list shows only those models to which your user group has been given privileges.
3. If you are creating the package, type 1 for the version number in the first box (only the first box is required; the other boxes can remain empty).
4. Optionally, type a brief description of the package and the actions it will perform.
5. This step depends on the Agent:
§ Axeda Gateway and Axeda Connector agents -- select whether the package is for Primary Agents only or for Backup Agents only. Note that when you select Primary Agents, the asset must be running in the Primary Agent mode to be available for deployment; similarly the asset must be running in Backup Agent mode for it to be available for deployment when you select Backup Agent for the package. See Backup Agent for more information
§ Axeda Agent Embedded -- select Primary Agents.
§ Axeda IDM Agent -- select Primary Agents.
§ AWP Agent -- select Primary Agents.
6. If the Enable Package Retries check box is not dimmed, retries are enabled for package deployments. Select this check box if you want the Platform to retry a package deployment if the first deployment fails. Note that package retries work only with assets running Axeda Gateway, Axeda Connector, Axeda Agent Embedded, or AWP agents.
7. If the package should have an expiration date and time, then under Expiration Date, click the radio button next to Date and enter a date for the package to expire. Optionally, enter a Time in the as well. A package never expires by default.
Note: If no expiration date is set for a package, then the package will remain available until it is deleted.
8. Click Next.
Notes about this procedure:
In the Description field, be sure to type line breaks as you type. Otherwise,
the description in the Confirmation step will show it as a long single
line and you will need to scroll to see it all.
You must type a number in the first box of the version number; the other
boxes can be left empty.