Install an application (including ENOVIA Business Process Services) into an empty, play database. The purpose of this step is to become familiar with the functionality and to perform a gap analysis for what needs to be configured.
Save the application staging area, which contains the database scripts that install the application and its schema. This staging area can usually be found below the SERVER_INSTALL directory, in the Apps\APP_NAME\<version>\ subdirectory. This subdirectory contains an installAPP_NAMEAPP_VERSION.tcl file, which can be run from within MQL to install the application schema.
Make the System Test environment a copy of the Production environment.
Install the ENOVIA Business Process Services and/or application to the Test environment, review the changes the installation makes, anc customize the XML files as needed. For more information on how to review the installation changes and what to look for, see "Reviewing Changes that an Installation Makes." For customizing information, refer to "Adding Custom Schema."
After making changes to the installation, restore the Test environment so that it is again an exact copy of the Production environment. Apply the new installation (with your changes) to the Test environment. Test the installation and make additional changes to the install scripts as needed.
Repeat the above process until you are satisfied that the installation has not adversely affected your system and that any errors in the customized schema have been fixed.
Perform the necessary testing in the System Test environment until there is an acceptable level of reliability and performance.
Once the scripts are solid and you know what to expect when they are run against the Production environment, you can can the upgrade to the Production system.
Note:
Always back up a Production system before making any schema changes. The installations for both ENOVIA Business Process Services and ENOVIA products make schema changes.