ENOVIA Live Collaboration ENOVIA Business Process Services (BPS) includes several components. Before installing any of them, you must install the BPS version that supports the application version that you are installing. The BPS installation installs the user interface components, and then lets you launch a separate Schema Installer. It is important to understand that database schema and business object instance data is installed with all ENOVIA products, including ENOVIA Business Process Services. Because of this, it is important to back up the system to which they are being installed. This backup should include the file system, as well as the database itself. It is strongly recommended that a System Test environment be in place that is an exact duplicate of the Production environment where the software will ultimately be operated. This System Test environment is where the software should first be loaded and tested. The purpose of testing is to make sure the application can be installed without errors and that, once installed, it functions as expected. Customers and/or ENOVIA Professional Services often modify an application in order to satisfy specific needs of the user community. To facility this, the schema installer looks at a custom directory for the modification XML files and merges the files accordingly. Refer to "Adding Custom Schema" for more information. If you are doing upgrades or installing a new application, you can expect to take 4 to 12 hours to test and validate the installation scripts for the schema and document any changes you had to make (or what changes the installation scripts made). The amount of time will decrease as you install to each next environment (Development, then Test, then Production). You will need to allow for additional time to perform standard system regression tests. The amount of time required for system regression tests depends on the number of changes made to JSPs and custom triggers. Note: Do not assume that because everything is fine in one environment it will also be fine in the next environment. In some cases, an environment may have gone through one or two upgrades before being promoted to the next environment. This is why it is so important to make an exact copy of the Production environment (and backups!) before upgrading or installing new software. | |||||||||||