Installing to a Populated Database

This topic describes issues that may arise when installing ENOVIA Business Process Services to an already populated database.

Related Topics
MatrixIniDefaults Program
BPS Version Must be Correct for Applications
Preventing Custom Pages from Being Overwritten

ENOVIA Business Process Services must be installed before other ENOVIA products (but after ENOVIA Live Collaboration Server). ENOVIA Business Process Services adds most of the administrative objects used in the applications, including all types, attributes, policies, relationships, roles, groups, persons, vaults, and stores.

The installation process also manages issues that may occur when installing over a populated database, such as:

  • Identifying previous versions of administrative objects that need to be updated.
  • Identifying previous versions of administrative objects that should not be updated because they have been modified (and updating might override the modifications).
  • Preventing naming conflicts by renaming objects in the framework that have the same name as an existing object (but not the same symbolic name). The installation renames the framework object using the format eServer[version]~[original name].
  • Identifying existing administrative objects with the same symbolic name as an object that is being installed. If the installation is attempting to add the object, it skips the Add command.
  • Backing up program, administrative, and business objects; and UI components.
  • Schema Changes.mql

Note: The checks for identifying whether objects have been modified, mentioned in the first two bullets above, are not available in the current release.

Note: Only RELEASED versions of the framework support the upgrade process described above. Customers who receive PRE-RELEASE software as part of a Beta or Customer Sponsorship program are given the software for evaluation purposes only. The setup program does not automatically upgrade databases from a Beta version to a released version. Installation of pre-release versions of the framework requires the database to be empty.