Package Management

AspenTech Inmation OT DataFabric is designed to be a distributed system with a central Node that is connected to remote Nodes which provide connections to a multitude of servers from other vendors. The Package Manager enables the user to deploy specific additional 3rd party services from the central Node to any of the remote Nodes to extend its functionality.

For example, a package can wrap a .NET SDK or API in order to integrate with an external system which supports those, or even expose data managed by the system in a custom fashion.

Packages are stored as a .zip file in the central system package store (packages folder in the AspenTech\inmation.root directory).

Package .zip files

Package Names

The package .zip file has a distinctive name made up of the following parts:

  • Version independent name - for example "PI Bridge"

  • version - must contain only digits. For example "2.0.0.6277"

  • .zip suffix

The parts should then be separated by dots to give the full name. For example: "PI Bridge.2.0.0.6277.zip"

The exact name and version number is required to install the package using WebStudio. If the package name contains elements other than those stated above then package installation will fail.

Package Content

Each package must contain a manifest.xml file and a script.lua file to work with the package installer. Any other files in the package zip directory will be extracted into the appropriate package directory in the service store.

Package Installation

For instructions on how to install packages on remote inmation components using WebStudio, see the Package Installation guide.