The Packager is designed as a workbench where you can easily access packages and their components with a single click.

The Packager provides standard templates for prototype files and installation dialogs that you can use as a framework to build your individual PIF package or installation dialogs.

The Packager lets you create self-installing PIF packages, which include the Installer, so that no installation tool is required on the target computer.

The Packager lets you create PIF packages that is installed by a nominated non-root user (non privileged installation).

The Packager lets you create patch packages so that there is a way to fix applications without republishing or distributing the entire package. Changes are reversed if the patch installation is rolled back. Updating or removing a product removes all installed patches for that package.

The Packager contains an installation dialog editor that provides you with a work surface, a toolbox, and drag-and-drop features to design the layout of installation dialogs. A Test dialog function lets you preview the installation dialog being created.

The Installer installs PIF packages on a target computer, unattended, or dialog-driven. The Installer also provides features to install UNIX and Linux products in packaging formats other than PIF. For example, PKG and RPM formats, and to manage any installed UNIX or Linux product on the target computer.

The Installer presents installation dialogs in graphical mode when the target computer has Java Runtime Environment (JRE) 1.4 installed; otherwise installation dialogs are in the character-oriented VT100 mode.

The installer supports to create and use installation dialog in multiple languages.

The Installer can perform parameter based unattended package installations.

The Installer automatically resolves all dependencies that are defined in the PIF package and its components. The Installer ensures that all dependent products are installed on the target computer before the PIF package is installed.

When a PIF package is being removed the Installer automatically tries to remove all unused dependant packages. The Installer examines several layers if needed, but checks and removes only those packages that were delivered with the PIF package.

The Installer manages shared files. Changed package files (for example, configuration files) are left unchanged after a package update installation.

You can maintain multiple versions of the package on the target computer. Using a package property you can enable PIF package to install multiple version of the package. At installation time, the Installer creates individual names for each new instance of the main package. You can update and remove specific instances of the same package version.

Within a PIF package you can specify alias names of other PIF or RPM packages (virtual packages), whose functionality or services are covered by this PIF package. The alias names can include the previous name of this package, During installation the dependency check evaluates the list of alias names and resolves dependencies to these packages.