About Package
- Last UpdatedJun 20, 2024
- 2 minute read
You can use the Package feature of AVEVA Work Tasks to deploy one or more artifacts from one cloud environment or repository to another cloud environment or repository. You can deploy artifacts with its associated and child artifacts and configuration state from one cloud environment or repository to another cloud environment or repository.
Note:You can install the Packages created in the cloud environment only.
Prerequisites
-
Ensure that the AVEVA Work Tasks Client Service is running while installing or uninstalling the package.
-
In an environment that contains multiple servers and clients, ensure AVEVA Work Tasks Client Service is running on the machine which has the Enterprise Console site configured.
Advantages of Package
Currently, packaging and deploying one or many artifacts from one environment or repository to another is done either by exporting and importing the artifacts or by using the recovery the task for packaging and deploying one or many artifacts from one environment or repository to another.
Package Versus Export Import
-
Export and import feature is helpful when you want to deploy a single artifact in a different environment.
-
You can export and import only one artifact at a time.
-
An imported artifact is not valid on the target environment, if the associated artifacts are not present.
Package Versus Recovery
You can use the recovery feature to replicate the entire repository with all the artifacts in the target environment. A choice to add only few artifacts to the target environment is not available. This option is beneficial when you want to deploy the entire repository in another environment.
A proper understanding of the Package interface enables you to use the various features of the interface effectively. The Package interface consists of the following two components:
-
Package Template: Use Package Template to design a package, define artifacts to the template, and complete the entire process of design, build, and export the package file. When you export a packaged file, the file is saved with the extension .awsPKG.
-
Manage Package: Use Manage Package to import packages which you exported from the Package Template and install the package in the target environment. You can also create a new package and export it.
Note:
- Only Administrators have the right to install the package.
- Access to the functionalities of Package Template and Manage Package requires special user rights. The functionality might either be disabled or might
not be visible if the user does not have rights to run them.
- You must reset the IIS before generating a package for the first time after installing
the product.