|The installation has the following impact on your computer:|
The software is installed (if you used the default location) in the folder directory:
where "OS" is:
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.
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:
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 installation procedure allows you to declare on your computer:
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
in the file:
Note that the line:
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.
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:
To run the command using the default values:
When used with the default values, it adds the following lines:
to the file:
and the following line:
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.
|All end users can now log onto the same workstation and run a Version 5 session, because the environment created at installation is global.|