InterOp:Connect/CATIA V5 Installation

From DocR21

Contents 1 Important Installation Instructions 1.1 Windows 1.1.1 Example 1.2 AIX 1.2.1 Example 2 Setting the CATIA V5 Component Environment – Required for 64-bit Platforms 2.1 Step 1 2.1.1 Windows 2.1.1.1 Example 2.1.2 AIX 2.1.2.1 Example 2.2 Step 2 2.2.1 Windows 2.2.1.1 Example 2.2.2 AIX 2.2.2.1 Example

Important Installation Instructions

For your run-time environment, set the following environment variables:

Note: The X3DT environment variable is assumed to be set to the path of InterOp installation directory.

X3DT=<Path to the InterOp installation>

Windows

1. Start a command prompt.
2. Run the following command:

   set PATH=%X3DT%\lib3dx\intel_a\code\bin;%PATH% (for 32-bit platform)

   set PATH=%X3DT%\lib3dx\win_b64\code\bin;%PATH% (for 64-bit platform)

Example

SET PATH=c:\interop\lib3dx\intel_a\code\bin;%PATH%

AIX

1. Run the following command:

   export LIBPATH=$X3DT/lib3dx/aix_a/code/bin:$LIBPATH

Note: CATIA V5 requires FORTRAN Runtime on AIX OS. This run time can be installed from the IBM Web site. For example, FORTRAN Runtime generally includes ibxlf90.a, libxlf90_r.a, and libxlsmp.a.

Example

export LIBPATH=/interop/lib3dx/aix_a/code/bin:$LIBPATH

Note: For UNIX-based platforms such as AIX, you need to set the DISPLAY environment variable to a viewing device for CATIA V5 libraries. The process may fail if the DISPLAY environment variable is not set correctly. For example, to set the DISPLAY environment variable, you would enter:

export DISPLAY = myWorkStation:0.0

Setting the CATIA V5 Component Environment – Required for 64-bit Platforms

While the InterOp CATIA V5 component can be used without any specific settings, running the translator on a machine on which some CATIA V5 products were used may trigger undesirable effects as the CATIA V5 environment settings are going to be shared.

A good example is the CATIA V5 license configuration which is part of those settings. When InterOp initializes CATIA V5, the CATIA V5 settings are automatically read and CATIA V5 requests the last active licenses. In case the settings are shared, and because InterOp does not unlock the same licenses, CATIA V5 will open a pop-up window to warn you that your current licenses were not found.

In order to avoid this, Spatial highly recommends the use of the setcatenv executable and the CATDefaultEnvironment variable to set the CATIA V5 environment appropriately.

Important: This is required for the 64-bit version of the product.

Step 1

The executable setcatenv creates a named environment to be used by CATIA V5 libraries.

The -a user|global options determine whether the environment created will be specific to a user or common to all users on the machine.

If the -a global is used, setcatenv must be run with administrator/root rights.

While installing, perform the following activities for your particular platform.

Windows

1. Start a command prompt.
2. Run the following command:

   %X3DT%\lib3dx\intel_a\code\bin\setcatenv -e <Environment Name> -desktop no -a user -p %X3DT%\lib3dx

Example

c:\interop\lib3dx\intel_a\code\bin\setcatenv -e InterOpB18 -desktop no -a user -p c:\interop\lib3dx

AIX

1. Run the following command:

   $X3DT/lib3dx/aix_a/code/bin/setcatenv -e <Environment Name> -desktop no -a user -p $X3DT/lib3dx

Example

/interop/lib3dx/aix_a/code/bin/setcatenv -e InterOpB18 -desktop no -a user -p /interop/lib3dx

Step 2

While launching the application, set the following environment variables for your particular platform.

Windows

1. Start a command prompt.
2. Run the following command:

set PATH=%X3DT%\lib3dx\intel_a\code\bin;%PATH%

set CATDefaultEnvironment=<Environment Name>

Example

SET PATH=c:\interop\lib3dx\intel_a\code\bin;%PATH%
SET CATDefaultEnvironment=InterOpB18

AIX

1. Run the following commands:

export OSDS=aix_a

export LIBPATH=$X3DT/lib3dx/aix_a/code/bin

export CATDefaultEnvironment = <Environment Name>

Example

export OSDS=aix_a 
export LIBPATH=/interop/lib3dx/aix_a/code/bin 
export CATDefaultEnvironment=InterOpB18

Note: <Environment Name> refers to a user-defined name. We recommend using a release-specific name. This allows two or more installations to reside on the same machine. For details, refer to Installation.