Installation

Publications Useful For Installation

The reader should also have some knowledge of the basic UNIX file environment and at least one editor.

ENOVIAVPM Maintenance Levels - PTFs

A new VPM PTF is cumulative. In other words, it contains many different corrections. Potentially, it includes corrections to the:

A PTF migration therefore needs to be exhaustive to ensure optimum VPM behavior.

Installing a New PTF

Whenever you install a new PTF it is strongly recommended to:

  • check the new VPM profile in $CATIA/vpm/reffiles/DBMS
  • compare this new profile with your current profile (which is older than the one just unloaded)
  • add the new profile variables to your current profile
  • re-import into VPM your updated current profile.

Installing a PTF n+1 on top of a PTF n (or on top of GA code)

A few steps are necessary to manage correctly the transition between PTF n and PTF n+1:

A - Installing the PTF using catinst (CATIA V4-like procedure)
B - Updating the administrator environment with new PTF content
C - Checking potential data structure migration

A - Installing the PTF Using catinst

For more information on this step you can follow the scenario described in the CATIA Installation Reference Guide (CATIA V4). ENOVIAVPM inherits CATIA installation tools which is why there are still some references to CATIA in this tool. The PTF installation procedure is more or less the same for ENOVIAVPM as for CATIA V4.

For information:

  1. Launch with root id:

    $CAT_UNLOAD/code/bin/catinst

    where CAT_UNLOAD is set with the appropriate VPM unload directory.

  2. Unload the software
    -> Unload all the PTF's UBs:

  3. Configure the installation
    -> Configure Step by Step:

  4. Update YOUR.env to activate the DB2/ORACLE parameters in the new YOUR.env.

    Launch:

    $CATIA/vpm/code/command/VPMInstall.sh -db2 for DB2
    or
    $CATIA/vpm/code/command/VPMInstall.sh -oracle for ORACLE

    This shell option will allow you to update YOUR.env (already upgraded in step 3 c "Create/update administrator environment" above) by adding DB2 or ORACLE parameters in YOUR.env file.

B - Updating the Administrator Environment with New PTF Content

The first VPM installation (using VPMInstall.sh -nocheck) creates certain data (shells, etc.). Some of this data, created by the original VPM installation (from scratch) should have changed between the original VPM complete installation date and the PTF date. This step exists to refresh certain VPM data (shells, etc.).

Example:
When launching the first VPM installation (using VPMInstall.sh -nocheck), all the shells existing in $CATIA/vpm/code/command are copied to $CAT_CUST/code/bin.
Of course, you must not execute VPMInstall.sh -nocheck for each PTF ( this operation should be done one time for data structure creation). It means that all the shells in $CAT_CUST/code/bin should not be up to date toward the ptfn+1
It is the reason why you have to check that all the shells created in $CAT_CUST/code/bin are still correct toward with PTFn+1.

How to proceed

  1. Save your previous ptfx settings
    cd $CAT_CUST/code/bin
    mkdir save_ptfn
    cp * save_ptfn/.

    Example:
    CustoVpmToCatia.sh 
    VPMDBEnv.sh
     
    should be saved because they have been already customized.

  2. Run the shell CpInstFiles.sh:
    cd $CATIA/vpm/code/command
    CpInstFiles.sh $CATIA $CAT_CUST UPDATE

    WARNING!

    This shell will upgrade all the VPM administrator environments by copying all contents needed for the VPM installation PTF upgrade. This is why you were asked to backup some of your data before (in step 1).

    Note that this shell takes into account the following files:

  3. Retrieve your previous settings:
    cd $CAT_CUST/code/bin
    cp save_ptfn/ VPMDBEnv.sh
    .

    cp save_ptfn/ CustoVpmToCatia.sh .
    or
    launch (recommended procedure)
    VPMPostInstall.sh
    (option 1: CATIA V4 interoperability Customization)
    This shell will create a new shell CustoVpmToCatia.sh in $CAT_CUST/code/bin

    cp save_ptfn/CustoVpmToV5.sh .
    or
    launch (recommended procedure):
    VPMPostInstall.sh
    (option 2: CATIA V5 Interoperability Customization)
    This shell will create a new shell called CustoVpmToV5.sh in $CAT_CUST/code/bin

C - Checking Potential Data Structure Migration

(Refer also to VPM Migration.)

Some PTFs may require minor data structure migrations. This is why you are asked to launch this shell in such a case.
This shell has several options. Just follow the help.

cd $CAT_CUST/code/bin
./VPMPostInstall.sh

Option 1 or 2 for getting information about scripts which will be launched depending on each VPM level and PTF
Option 4 or 5 for preparing scripts/command streams depending on the customization
These options will create the correct scripts for migration to a shell.
For these options, the following declaration parameter is needed:

catcdm.c_stream ='$CAT_CUST/MIGRATION';
in $CATMSTR

You will be asked to answer certain questions in order to customize your files. Two shells will be created in $CAT_CUST/MIGRATION

Depending on the migration you need to apply, remove or comment the lines you do not need.

VPM Migration

All relevant information regarding migration is provided in the ENOVIAVPM Installation and Administration Guide Version 1 Release 6.

VPM STEPLIB Directory

WARNING! Do not, under any circumstances, put any customized library fixes or development modules into your VPM STEPLIB directory (usually $CAT_CUST/code/steplib/$OS) unless expressly requested to do so in the official documentation or by the VPM maintenance or development team. This is because the directory is shared with CATIA V4 and interaction between VPM and CATIA V4 may therefore be unpredictable.