About the Environment Created on Your Workstation on UNIX

The installation has the following impact on your computer:

Installation Path

The software is installed (if you used the default location) in the folder directory:


where "OS" is:

  • aix_a
  • hpux_b
  • solaris_a


The installation offers you the choice of where to create the /CATEnv directory. The default is the root $HOME directory (typically "/"), but you can create the /CATEnv directory anywhere you like.

Note that, if an environment already exists, the installation procedure offers you the choice between replacing it or creating a new environment with a different name.

If you choose the default location, the installation creates the global environment, required to set the Version 5 runtime environment variables, in the /CATEnv directory.

The environment is created in a text file and the environment file name is:


Note: UNIX system administrators can also setup a /CATEnv environment directly in the home directory of end users.

CDE Desktop on AIX, HP-UX and Solaris

The /CATCDE directory required for CDE desktops is created in the /CATEnv directory.

The installation creates the following filetree required for integrating Version 5 into the CDE desktop:

  • /CATEnv/CATCDE/CATIA/dt/appconfig/appmanager/C/CATIA/CATIA.V5R18.B18 (file required for graphic representation of environment in the CDE desktop)
  • /CATEnv/CATCDE/CATIA/dt/appconfig/types/C/CATIA.V5R18.B18.dt (action description file for environment icon)
  • /CATEnv/CATCDE/CATIA/dt/appconfig/types/C/CATIA.dt (action description file for CATIA directory)
  • /CATEnv/CATCDE/CATIA/dt/appconfig/types/C/CATIAFiles.dt (action description file for CATIA document types)
  • /CATEnv/CATCDE/CATIA/dt/appconfig/icons/C (contains icons for CATIA document types).

Note that:

  • The last four are created using the "-regserver" option of the setcatenv command and deleted using the "-unregserver" option of the delcatenv command.
  • CATIAFiles.dt is common to all product lines.

The application is registered in the CDE application base via the "dtAppIntegrate" command which is executed automatically during the installation. The result of registering the application is that the /etc/dt/appconfig/ environment on your workstation is modified. This environment contains links to the application desktop filetree located under /CATCDE (described above).

You do not see the icon immediately. To display the icon, you must click the Application manager icon on the CDE front panel, go into the Desktop Tools cabinet, then double-click the Reload Applications icon. You can also log off and log on to display the icon.

The visible impact on the CDE desktop is:

  • the creation of the MyProductLine directory in the Application Manager cabinet, accessible via the front panel
  • the creation in this directory of the default global environment icon:


Communications Backbone Files

The installation procedure allows you to declare on your computer:

  • a port reserved for the communications backbone process
  • a port reserved for starting the communications backbone process automatically
  • a port reserved for processing events when using peripheral devices (spaceball, spacemouse, joystick).

To do so, check the option "Set up communications ports (strongly recommended)" when prompted.

The communications backbone is Version 5 implementation of message-oriented middleware (MOM), used to support process interoperability for distributed application networks in heterogeneous environments. Installing Version 5 sets up the communications backbone on your computer. The backbone needs to be set up on each computer running applications which need to communicate.

When one application attempts to communicate with another, the backbone process is started automatically. If the process is already running, it is not restarted. A timeout is triggered once there are no more clients attempting to communicate with other applications.

A typical scenario involving the use of the inter-application communications backbone is implemented to allow the ENOVIA Portal DMU Navigator and ENOVIA Portal WEB to communicate: ENOVIA Portal WEB can load geometry and product structures into a viewer such as ENOVIA Portal DMU Navigator, 4D Navigator or CATIA.

If you are installing from scratch, the installation procedure sets up the communications backbone by creating the following lines:

catiav5bb 55555/tcp

catiav5run 55556/tcp

in the file:


Note that the line:

CATDeviceBroker 55557/tcp

which concerns peripheral device handling is also added to this file.

The following line:

catiav5run stream tcp nowait root /path/CATSysDemon

is added to the file:


where "path" is the path containing the Version 5 executable files.

For example:

catiav5run stream tcp nowait root /usr/DassaultSystemes/B18/OS/code/bin/CATSysDemon

  Note: The services file also contains the line:

mi-ray 7001/tcp # Rendering slave

for the Photo Studio Optimizer product.

Tools for Setting Backbone and Peripheral Device Broker Port Numbers

The preferred method for setting port numbers, however, is to avoid manual edits by using the following tool:


The syntax of the command is as follows:

setV5Ports [-backbonePorts p1 p2] [-VRPort p3]|-h

  • -backbonePorts p1 p2: Specifies communication ports for backbone. Default values are 55555 and 55556
  • -VRPort p3: Specifies communication port for peripheral device broker - default value is 55557
  • -h: displays help.

To run the command using the default values:

  1. Log on as root.
  2. Enter the command:

    /usr/DassaultSystemes/B18/OS/code/command/catstart -run setV5Ports

    where  "OS" is:

    • aix_a
    • hpux_b
    • solaris_a.

When used with the default values, it adds the following lines:

catiav5bb 55555/tcp #Dassault Systemes Communication ports
catiav5run 55556/tcp #Dassault Systemes Communication ports
CATDeviceBroker 55557/tcp #Dassault Systemes Communication ports

to the file:


and the following line:

catiav5run stream tcp nowait root /usr/DassaultSystemes/B18/OS/code/bin/CATSysDemon

to the file:


Administrator Setting Environments

When running a session at the end of the installation procedure (as administrator), administrator settings are created in the /CATSettings and /CATTemp directories.

Nodelock Licensing Directories

The Version 5 installation procedure on UNIX sets up on your workstation a filetree for storing IBM License Use Management Runtime (LUM) nodelock licenses, that is, if LUM is not already installed on your workstation. This is needed to manage nodelock licensing.

The nodelock file is created by default in:

/var/ifor/nodelock (AIX)
/opt/lum/ls/conf/nodelock (HP-UX, Solaris)

All end users can now log onto the same workstation and run a Version 5 session, because the environment created at installation is global.