Changes that an Installation Makes

When performing an installation, you need some way of determining the changes that the installation is making to the schema, busines object data, and JSPs. One way of tracking the schema changes is to create an XML export file prior to running the installation. After installing, you can use the XML compare utility from MQL to review the changes that were made to the schema. You can also use the log file created for each installation in the SERVER_INSTALL\Apps\APP_NAME\<version>\ directory to track changes to schema and business objects. For more information on the log file, see "Installation Log File."

Related Topics
Important Installation Considerations
Installation Changes You May Need to Review
Preparing to Install to a Production Environment

When reviewing the changes that an installation has made, look for any changes that may conflict or are not needed because of customizations that you have made. Some changes to watch out for are listed below. Keep in mind, however, that the install scripts make changes to support the business processes within each application. You need to decide whether these changes are consistent with your business process and are needed based on the existing customizations you have made.

For example, suppose that the installation for ENOVIA Engineering Central adds an extra notification or signature to the ECR Standard policy. This change is made because the Product Engineer needs to approve the ECR before it goes to a full Change Board review. Your business process, however, requires approval from a Project Engineer instead of the Product Engineer. You have triggers that already handle this, thus making the newly-added Engineering Central notification unnecessary (or unwanted). Alternatively, if you are using out-of-the-box Engineering Central, this notification is crucial and if removed, ECRs will get hung up at a particular state because no one was notified to do anything with it.