Installing the Schema Manually

If you did not include the schema when you installed Collaboration and Approvals, you can add the schema manually.

  1. Open MQL and run the following scripts in the order listed. 
    <server>/Apps/BusinessProcessServices/<VERSION>/Modules/ENOFramework/installFramework<VERSION>.tcl
<server>/Apps/BusinessProcessServices/<VERSION>/Modules/ENOSchemaInstaller/installSchemaInstaller<VERSION>.tcl
<server>/Apps/BusinessProcessServices/<VERSION>/Modules/ENOAppsCommon/installCommonComponents<VERSION>.tcl
<server>/Apps/BusinessProcessServices/<VERSION>/Modules/ENOTeamCentral/installTeamCentral<VERSION>.tcl
<server>/Apps/BusinessProcessServices/<VERSION>/Modules/ENOWhereUsed/installWhereUsed<VERSION>.tcl

    Where <VERSION> is the version level being installed, for example: V6R2022x.

  2. For each web app, locate the modules.ini file in <INSTALLATION_PATH>\server\Apps\PROCESSNAME\<VERSION>\modules\APPNAME\modules\Modules.ini. For example: 
    <INSTALLATION_PATH>\server\Apps\VariantConfigpassuration\<VERSION>\Modules\ENOVariantConfiguration\Modules.ini
    which contains the following: 
    [Modules]
Names=ProductLine,EffectivityFramework,VariantConfigurationBase,DMCPlanning

[ProductLine]
ModuleDirectory=ENOProductLine
DisplayName=Product Line
InstallType=Required
Schema=None

[EffectivityFramework]
ModuleDirectory=ENOEffectivityFramework
DisplayName=Configuration Effectivity Services
InstallType=Required
Schema=Configuration Effectivity Services

[VariantConfigurationBase]
ModuleDirectory=ENOVariantConfigurationBase
DisplayName=Variant Configuration Base
InstallType=Required
Schema=None

[DMCPlanning]
ModuleDirectory=ENODesignManufacturingPlanning
DisplayName=Design Manufacturing Configuration Planning
InstallType=Optional
Schema=Design Manufacturing Planning
  3. The modules section of the modules.ini file indicates the order in which the tcl scripts need to be run for that web app. In addition, if the Schema tag for each module has a value other than None the related tcl files must also be run, including the app's own installSchemaInstaller<VERSION>.tcl .

    In our example, this means to run the following scripts in this order: 

    ENOProductLine\installProductLine<VERSION>.tcl
ENOEffectivityFramework\installSchemaInstaller<VERSION>.tcl
ENOEffectivityFramework\installEffectivityFramework<VERSION>.tcl
ENOVariantConfigurationBase\installVariantConfigurationBase<VERSION>.tcl
ENODesignManufacturingPlanning\installSchemaInstaller<VERSION>.tcl
ENODesignManufacturingPlanning\installDMCPlanning<VERSION>.tcl

The database is updated with the schema required to run the 3DEXPERIENCE platform Web apps.