Enabling User Access to the Software Over the Network

This task explains how to allow end users access to Version 5 over the network without installing the software on the client. You have two possibilities. You can:
  • set up just a runtime environment on each client: each time the server software is upgraded, all you have to do is recreate a new environment on each client
  • or, to avoid having to set up a runtime environment on each client, you can simply mount the server software and runtime environment directories from the client and run Version 5 using the environment on the server.

We have chosen the AIX platform for the purposes of this scenario.
  When setting up the server you can:
  • copy all the software into the same folder (as illustrated above)
  • or, given that the software is distributed on several CDs ( 1, 2 ...), copy the contents of each CD into a separate folder for each CD, making sure that the name of each folder corresponds to the CD number ( 1, 2 ...) etc.

Setting Up an Environment on the Client
1. Log on as root onto the server.

The name of the server, in our example above, is "ravel".

You already installed the software in:

UNIXInstallPath/aix_a
2. From the server, export the installation directory (UNIXInstallPath) to the client.

The directory must be accessible from the client.
3. Log on as root onto the client.

The name of the client, in our example above, is "chopin".
4. From the client, mount the exported installation directory (UNIXInstallPath) via NFS.
5. Go to the following mounted directory:

UNIXInstallPath/aix_a/code/bin

6. Set the path of the installation directory on the server using the command:

export PATH=UNIXInstallPath/aix_a/code/bin:UNIXInstallPath/aix_a/code/command:$PATH

The following list contains the variables to modify on each UNIX system:

export LIBPATH=UNIXInstallPath/aix_a/code/bin (AIX)

export SHLIB_PATH=UNIXInstallPath/hpux_b/code/bin (HP-UX)

export LD_LIBRARY_PATH=UNIXInstallPath/solaris_a/code/bin (Solaris)
Exporting library paths is required by the setcatenv command which creates the environment as explained below.
7. Create the following global environment (still as "root") using the following command with exactly the syntax indicated, depending on whether you are running CATIA, ENOVIA DMU Navigator or DELMIA:

./setcatenv -e MyEnvironment -p UNIXInstallPath -d MyEnvDirectory -desktop yes -new yes -a global -cs MyProductLine

where "MyEnvironment" is the name of the environment, "MyEnvDirectory" is the name of the folder containing the environment and "MyProductLine" is the name of the product line.

Running the setcatenv command as a normal end user runs successfully, but does not create a global environment.
8. To register document types on the client desktop, go to the directory:

UNIXInstallPath/aix_a/code/command

and run this command:

./catstart -run "setcatenv -p UNIXInstallPath -e MyEnvironment -d MyEnvDirectory -regserver -cs MyProductLine" -env MyEnvironment -direnv MyEnvDirectory

For a description of the setcatenv and delcatenv command syntax for UNIX, refer to Customizing Your Environment on UNIX.
  9. If you need access to the communications backbone and peripheral device broker, the associated port numbers must be set up on the client.

Used to support process interoperability (for example, between CATIA and DMU), the backbone needs to be set up on each computer running applications which need to communicate.

To set up the ports using the default values:

  1. Go to the following installation directory:

    UNIXInstallPath/OS/code/command
  2. Enter the command:

    ./catstart -env MyEnvironment -direnv MyEnvDirectory -run setV5Ports

    where  "OS" is:

    • aix_a
    • hpux_b
    • solaris_a.

For more information, refer to Communications Backbone Files.
10. Log off the root userid.
11. Log on using a normal userid and run a Version 5 session to check your environment has been correctly set up.

You can run Version 5 as follows:

  • double-click the environment icon using the desktop,
  • or, go to the following mounted directory:

UNIXInstallPath/aix_a/code/command

and enter the command:

./catstart -run CNEXT -env MyEnvironment -direnv MyEnvDirectory

./catstart -run DMU -env MyEnvironment  -direnv MyEnvDirectory

./catstart -run DELMIA -env MyEnvironment -direnv MyEnvDirectory

12. To delete this environment, run the command from the same directory:

./catstart -run "delcatenv -d MyEnvDirectory -unregserver -cs MyProductLine" -env MyEnvironment -direnv MyEnvDirectory

./catstart -run "delcatenv -e MyEnvironment -d MyEnvDirectory -desktop yes -a global -cs MyProductLine" -env MyEnvironment -direnv MyEnvDirectory

For a description of the setcatenv and delcatenv command syntax for UNIX, refer to Customizing Your Environment on UNIX.

Accessing the Software Without an Environment on the Client
1. Log on as root onto the server.

You already installed the software in:

UNIXInstallPath/aix_a

2. From the server, export the following directories to the client:

  • UNIXInstallPath/aix_a (installation directory)
  • /CATEnv (runtime environment directory)

Both the installation and runtime environment directories must be accessible from the client.

3. Log onto the client as root.

4. From the client, mount both exported directories via NFS.

5. Go to the following mounted directory:

UNIXInstallPath/aix_a/code/command

6. Log off the root userid.

7. Log on using a normal userid and run a Version 5 session.

In this case, go to the following mounted directory:

UNIXInstallPath/aix_a/code/command

and enter the command:

./catstart -run CNEXT

./catstart -run DMU

./catstart -run DELMIA
Note that you cannot run Version 5 on the client using the environment icon using the desktop: no environment exists on the client, therefore there is no desktop icon.