Installing Schema with the Schema Installer

Change to the <media_name>/1/ directory under the distribution directory you used when you first installed the framework.

cd /<media_name>/1

Start the Schema Installer.

./setup.SchemaInstaller

Change to the SchemaInstaller\ subdirectory under the distribution directory you used when you first installed the framework.

cd SERVER_INSTALL\Apps\Framework\VERSION\SchemaInstaller

Start the Schema Installer.

setup.exe

Choose the desired installation type:

• 1. Standard (Recommended)—Choose this option for the recommended standard installation. If you choose this option, setup will undo all transactions if it encounters problems. You can use the log files to determine which transactions were attempted and to diagnose the errors. The standard installation automatically runs the installation scripts after copying the files to the staging area.
• 2. Advanced—Choose this option if you want to change the default settings for the prompts in step 5, below. If you choose this option, setup will proceed with the installation even if errors are encountered. This option also allows you to copy files to the staging area now and then run the installation scripts later.

Choose the directories for the installation to use.

• Distribution directory—This directory defaults to the directory above the current directory. Type in a new path, or press Enter to accept the default.
• Build script directory—This is the path where the scripts that build the application in the database are placed. The default is SERVER_INSTALL\Framework\. If you specify a directory that does not exist, the setup program will create the directory.
• RMI Installation directory—This is the path that contains the ENOVIA Live Collaboration Server installation.

Tell setup where the Schema Customization directory is located.

Tell setup where MQL is located (including the application scripts), and the user name and password for a user with Business and System Administrator privileges, such as creator. If the user does not have a password, accept the default.

If you selected the Advanced option in step 1, above, you are prompted for the following:

• Install to staging area only & don't update database—The default for this option is no, which means that after you complete the installation, setup copies all files to the staging area and runs the installation scripts to update the database. If you want to copy files to the build script directory only and run the installation scripts later, enter yes. When you are ready to run the installation scripts, use MQL to run the installFrameworkVERSION.tcl file, located in the Apps\Framework\ directory. To create log and error files, use the -stderr and -stdout MQL options.
• Undo the whole Framework transaction in case of failure—The default for this option is yes. Undoing all transactions makes it easier for you to correct problems with the new installation without introducing problems into your existing setup. The log file for the framework lists all transactions even if they are undone.

  You should change this option, allowing transactions to proceed even when there are errors, ONLY if you know how to correct the error or if you are just installing for test purposes.

Note: The Standard option in step 1 accepts the defaults.

Enter the names of the Data and Index table spaces for the eService Production vault. For non-Oracle databases, the values must be the same.

The eService Production vault is the vault that will be used for production data. Consult your Database Adnministrator for information on the table space names used.

If you do not specify a table space name, the tables and indexes for the product vault will be created in the database's default table space, which may not be sized appropriately for production data storage.

For Oracle, if you specify only an Index Table Space, the Data Table Space will default.

Confirm your selections.

• Select 1 to continue.
• Select 2 to cancel.

If you continue with the installation, the system creates installation directories, copies files to the directories, and builds the script files. A file named installSchemaInstallerVERSION.tcl is created in the directory you specified for the build scripts. VERSION is the software version number.

Setup then runs the installation scripts, unless you chose not to update the database in the Advanced setup.

Note: It may take several minutes to run all the scripts. If you have an extensive database in place, it could take much longer.

Specify which schemas you want to install.

• Do you wish to install All Application schema—This option includes schemas for all ENOVIA products. The schema for ENOVIA Business Process Services is automatically installed, whether or not you install the application schema.
• The list may also include applications defined in a custom SchemaManifest.xml file, and may have removed one or more of the default schemas (not recommended).

Note: If you are upgrading a database from a previous release, you must choose to install All Application schema.

If errors are encountered and you chose to undo transactions in case of errors, setup undoes all changes. Check the files named installSchemaInstallerVERSION.log and SchemaChangesMQLVERSION.log in your installation script directory to get details about errors and to see exactly what items may have been added and/or modified.

If there are no errors, you may still want to review the log files to see if any items were renamed as a result of name collisions.

If you have backups of any customized properties files, compare your customized files with the new files from the updated version. Either update the new files with your customizations, or update your customized files with any new settings added by the installation.

Refer to the aplication administrator's guides for any application-specific setup issues. Refer to the ENOVIA Studio Modeling Platform documentation set for File Collaboration Server setup, deployment settings, and server setup and diagnostics.