How to Define a Partner Product Installation Procedure

The installation procedure

• The CD-ROM must contain at least the file tree created using

  mkCreateRuntimeView -s -t DestDir -d

• The installation procedure must retrieve the V5 installation directory using either a dialog with UNIX, or by reading the value data assigned to the value DESTFOLDER in the registry key HKLM\SOFTWARE\Dassault Systemes\Bxx\yy with Windows, where:
  • HKLM stands for HKEY_LOCAL_MACHINE
  • Bxx is the V5 installed release level, such as B18 for V5R18
  • yy is an integer, starting from 0, that increments with the count of GA installations of the same build level, and that is limited to 19.

  If a 32-bit installation and a 64-bit installation coexist on a Windows machine, to determine to which installation this directory applies, use the value OSNAME of the same registry key, whose value data is INTEL with 32-bit Windows and WIN64 with 64-bit Windows.

• The installation procedure must check that the installed V5 release level matches its own prerequisites by using the CAA global functions CATGetGALevel and CATGetSPKLevel
• The installation directory to be proposed by default should be similar to:
  /usr/partner/B18 or C:\ProgramFiles\partner\B18
  where partner is the partner name
• The installation procedure must check that the installation directory chosen by the customer is empty and is not the V5 installation directory. This will avoid future naming space and uninstallation problems
• At the end of the installation, the installation procedure must create an environment that concatenates the V5 and the partner installed products. Use the setcatenv command to do this:

  setcatenv -e PartnerProduct -p V5_InstallPath:Partner_InstallPath

[Top]

How to Set up Environments

Sample scenario: Two partner add-ons are installed, Prod1 and Prod2. The customer may want to use CATIA alone, CATIA with Prod1, CATIA with Prod2, and CATIA with both products. An environment dedicated to each of these cases must be defined.

• Using CATIA alone:

  setcatenv -e CATIA_Alone

• Using CATIA and Prod1:

  setcatenv -e CATIA_And_Prod1 -p CATIA_InstallPath;Prod1_InstallPath

• Using CATIA and Prod2:

  setcatenv -e CATIA_And_Prod2 -p CATIA_InstallPath;Prod2_InstallPath

• Using CATIA, Prod1 and Prod2:

  setcatenv -e CATIA_And_Prods -p CATIA_InstallPath;Prod1_InstallPath;Prod2_InstallPath

Notes:

• With UNIX, replace ; with :
• Using setcatenv/catiaenv
  • UNIX: catstart_fullpath -run "setcatenv catenv_options"
  • Windows: setcatenv_fullpath catenv_options

Desktop access: Double clicking the CATIA icon starts CATIA and gives access to the resources defined by the concatenation referred to.

Access from the command line (either located in the appropriate directory or by typing the full path name):

• UNIX:

  catstart -env used_product_env -d env_path -run my_appli

• Windows:

  my_appli -env used_product-env [-dir env_path]

This works with Windows and UNIX, with CATIA or any application. With Windows, using an application other than CATIA requires to set the Path environment variable using the file tree/code/bin directory.

[Top]

History

Copyright © 2001, Dassault Systèmes. All rights reserved.