Packages

The deployment of Dollar Universe administrative packages is described in the section "Administration Packages".

With the Packages feature, the user will be able to stock or archive Dollar Universe V5 or V6 objects on the Univiewer Management Server and deploy them over several Dollar Universe V6 nodes via a package file.

A package is named and can contain several objects of these types:

• Design Mode> Graphical Design
• Design Mode> Job Design
• Design Mode> Environment (except Nodes and Profiles)

The package can then be deployed to one or more Nodes to be executed.

The whole user package cannot exceed 3 MB.

Administration packages (node settings packages and autopatch packages) do not appear in this list. They are managed in Administration mode> Nodes> Nodes> Administration Package.

In the case of DUAS V5 users table: During the insertion in a package, a V5 user is converted to a V6 submission account. The corresponding system user is eventually created on the system and the Windows user service is created to localsystem.

(The security rules for access are managed in Administration mode>Security>Logins).

Actions:

• New, Display, Update, Duplicate

  Opens the package creation window. Refer to section: "Package Details". In display mode no changes can be made. In update mode, you can modify all characteristics except the name.

• Delete

  Deletes the package from the UVMS but doesn't delete the objects deployed.

• Tools > Import

  Imports a package from a backup file. A .unipkg file generated from the Package > Export procedure can be imported.

  Prior to importing the package, it can be renamed. The import procedure is as follows:

  • A dialog box listing the files is displayed. Select a file from the drive and click Open.

  • A dialog box is displayed to rename the package on the Univiewer Management Server. By default, the field contains the package name (which can differ from that of the file). It can be updated. Click Ok.

  • The package is imported into the UVMS package list. If a package already exists with the same name, a confirmation dialog is displayed before overwriting the existing package.

• Tools > Export

  Exports a package to a backup file. The default extension for such files is .unipkg. A backup file may be used to import a package to another UVMS.

  This export file contains node settings or objects, as well as the package name.

  The default name of the export file is the package name and date and time of update of the package: YYYYMMDD_HHMM. e.g.:

  NSP_20180626_1145.unipkg

  The export file can be imported later using Package > Import feature.

• Tools > UVMS Exchange

  Sends an object package to a UVMS if it has a Connected status in the local UVMS (for advanced architecture: UVMS master / UVMS subordinates, external UVMS).

  This action is for selecting UVMS nodes hat are destinations for object or node settings packages.

  • OS

    Select the operating system of targeted UVMS for sending packages, or select All to display all of them.

    In the list, check the boxes for the destination UVMS. The buttons Select all… help if the list contains lots of nodes.

  Click OK to start the exchange. The deployment is synchronous. If the package exists already on the target UVMS, a message warns the user and asks if the existing package on the target UVMS should or should not be overwritten by the new one.

Columns:

• Package

  Name of the package

• Comment

  Package description

• Package Creator

  The name of the login that created / modified the package

• Package Version

  The creation / modification date of the package

• Package Origin

  The source of the last package modification:

  • The file name, if the package was imported from a file.
  • The name of the UVMS, if the package was created or modified directly on the UVMS.