Last Updated : 2004/09/13
The following sections identify the system requirements for installation and activation.
| CAA RADE Products | run on | ||
|---|---|---|---|
| Unix | Windows 2000 | Windows XP | |
| CAA - C++ Interactive Dashboard (CID) | NO | YES | YES |
| CAA - JAVA Interactive Dashboard (JID) | NO | YES | YES |
| CAA - Multi-Workspace Application Builder (MAB) | YES | YES | YES |
| CAA - C++ Unit Test Manager (CUT) | YES | YES | YES |
| CAA - JAVA Unit Test Manager (JUT) | YES | YES | YES |
| CAA - C++ Source Checker (CSC) | YES | YES | YES |
| CAA - C++ API Documentation Generator (CDG) | YES | YES | YES |
| CAA - Source Code Manager (SCM) | YES | YES | YES |
| CAA - Data Model Customizer (DMC) | NO | YES | YES |
| CAA - Teamwork Release Manager (TRM) | YES | YES | YES |
| CAA - Web Application Composer (WAC) | NO | YES | YES |
| CAA - Interactive Test Capture (ITC) | YES | YES | YES |
Run time software requirements are the same as those described in the applicable CATIA, DELMIA, and ENOVIA Version 5 announcement letters. In addition:
| Applications Build with CAA RADE On | Will Run On | |
|---|---|---|
| Windows 2000 | Windows XP | |
| Windows 2000 | YES | YES |
| Windows XP | NO | YES |
The hardware requirements are the same as the ones for CATIA, DELMIA, and ENOVIA products depending on the API you will work on, except the followings:
The following components at the indicated level are required:
Note : On Windows , the Fortran runtime DLL previously at level 5 are now delivered at level 6.6B (.6.913.106) in the intel_a\code\bin directory.
Please refer to Program Directories for CATIA, DELMIA, and ENOVIA products for patches generally recommended for these product lines and not specific to CAA RADE products or CAA APIs.
The hardware requirements are the same as the ones for CATIA, DELMIA, and ENOVIA products depending on the API you will work on, except the followings:
The following components at the indicated level are required:
Compiler: VisualAge C++ Professional for AIX V5.1 at level 6.0
Compiler: VisualAge C++ Professional for AIX V5.2 at level 6.0
Following build-time patches are required in addition to the run-time patches recommended for CATIA Version 5 Release 14 (listed in the CATIA Program Directory):
The hardware requirements are the same as the ones for CATIA, DELMIA, and ENOVIA products depending on the API you will work on, except the followings:
The following components at the indicated level are required:
Please refer to Program Directories for CATIA, DELMIA, and ENOVIA products for patches generally recommended for these product lines and not specific to CAA RADE products or CAA APIs.
The hardware requirements are the same as the ones for CATIA, DELMIA, and ENOVIA products depending on the API you will work on, except the followings:
The following components at the indicated level are required:
Following build-time patches are required in addition to the run-time patches recommended for CATIA Version 5 Release 14 (listed in the CATIA Program Directory):
The hardware requirements are the same as the ones for CATIA, DELMIA, and ENOVIA products depending on the API you will work on, except the followings:
The following components at the indicated level are required
Following build-time patch is required in addition to the run-time patches recommended for CATIA Version 5 Release 14 (listed in the CATIA Program Directory):
IBM DB2 Universal Database or Oracle Enterprise Edition :
IBM DB2 Version 8.1 Fix Pack 3 minimum, on Windows, IBM AIX, HP-UX 11.11 or Sun Solaris
IBM DB2 Version 7.2 FixPack 10a on HP-UX 11.0 or SGI IRIX
ORACLE 9.2.0.3 minimum on Windows, AIX, HP-UX or Sun Solaris
ORACLE 8.1.7 on SGI IRIX
(*) These functionalities are not supported with Windows XP.
- Although access to the online documentation might work on other HTML browsers, incidents specific to other browsers than above mentioned products are not eligible for support
(*) Note the oldest LUM level supported by IBM is 4.6.5
An approximate size of 300 Mb on Windows and 375 Mb on UNIX is needed to install the software.
This chapter describes the installation method to install the functions.
CATIA V5 Solutions CAA APIs, DELMIA V5 Solutions CAA APIs and ENOVIA Solutions CAA APIs media contain all deliveries necessary to install all available APIs.
If you use a CAA vendor-written application, the CATIA V5 Solutions CAA APIs, DELMIA V5 Solutions CAA APIs or ENOVIA Solutions CAA APIs level must be the same than the one of the CATIA V5 Solutions, DELMIA V5 Solutions or ENOVIA Solutions level installed. In addition, the CAA vendor must supply the application rebuilt on that level.
Installation of CATIA V5 Solutions CAA APIs, DELMIA V5 Solutions CAA APIs, ENOVIA Solutions CAA APIs can be divided into three main steps:
Windows
UNIX
Special CD-ROM mount configuration on HP-UX only:
After mounting the CD-ROM, change directory to the mount point and enter
the command: ./start
Then a full self-explanatory graphic interface appears, where you can easily
navigate.
Remark:
To build AIX 64 bit CAA applications on top of AIX 64 bit ENOVIA DMU runtime, the dedicated CAA 64 bits CD must be used. UNIX instructions then apply.
The CAA online documentation, also named CAA Encyclopedia, is installed with the CAA APIs. You can access it with an HTML browser at the following addresses:
<CATIA, DELMIA, or ENOVIA CAA APIs installation path>/CAAV5HomePage.htm
or
<CATIA, DELMIA, or ENOVIA CAA APIs installation path>/CAADoc/Doc/online/CAACenV5Default.htm
Please refer to the homepage.htm file on the CD-ROM.
CAA RADE V5 medium contains all deliveries necessary to install all available products and options.
CAA RADE V5 installation can be divided into three main steps:
Windows
You must belong to the administrator group, or have the privileges assigned to the Administrator group. Otherwise, you will not be able to start the installation.
The installation procedure starts automatically. A full self-explanatory graphic interface appears, where you can easily navigate.
The installation procedure is described in the CAA Encyclopedia installed with the CAA APIs CD-ROM. To find this procedure documentation, from the CAA Encyclopedia home page, click Getting Started, and click Installing CAA RADE V5 Products. To initialize the TCK which defines the tool configuration you can use, refer to the Tools documentation in the CAA Encyclopedia. From the home page, click Tools at the bottom right corner, then click TCK Tool Config, and click Introducing TCK.
UNIX
After mounting the CD-ROM, change directory to the mount point and enter
the command: ./start
The installation procedure starts automatically. A full self-explanatory
graphic interface appears, where you can easily navigate.
The installation procedure is described in the CAA Encyclopedia installed with the CAA APIs CD-ROM. To find this procedure documentation, from the CAA Encyclopedia home page, click Getting Started, and click Installing CAA RADE V5 Products. To initialize the TCK which defines the tool configuration you can use, refer to the Tools documentation in the CAA Encyclopedia. From the home page, click Tools at the bottom right corner, then click TCK Tool Config, and click Introducing TCK.
The licensing product is delivered on the CD-ROM released with CAA RADE V5. The installation procedure for LUM is included in the CAA RADE V5 installation documentation. Refer to the Memo to Users for instructions on obtaining keys for CAA RADE V5.
Please refer to the homepage.htm file on the CD-ROM.
CAA RADE V5 is NLS-enabled. It is supplied with the english and french localizations.
CAA RADE V5 supports DBCS.
This procedure describes how to get started with the C++ Interactive Dashboard on Windows.
where
The available licenses are displayed. Check those that match the
configurations and products you want to use, click Apply, and close the
dialog box
This is described in the CAA Encyclopedia installed with the CAA APIs CD-ROM.
From the home page, click Getting Started, and click Installing CAA
RADE V5 Products.
The CAA authorized C++ and IDL APIs are located in the PublicInterfaces directories of the exposing frameworks.
CAA authorized APIs:
As a rule, never use other APIs from the PublicInterfaces directories, as well as APIs located in the ProtectedInterfaces directories. APIs from header files located in the PublicInterfaces directories that include the CAA Tag @CAA2Level L0 at the top are beta-authorized APIs. They are not intended to be used in your applications, except for tests. There are neither build time stable, nor run time stable, and can disappear without previous notice.
If you already use non-authorized APIs, your CAA applications may not rebuild onto V5R14. An API authorization request service is available from the CAA Internet site. Dealing with this is explained either in:
This service is dedicated to help you build your current application already using non-authorized APIs on V5R14. It is in no way the channel to ask for new authorized APIs. To this purpose, create a PER (Program Enhancement Request) with your V5 software vendor representative.
You can access the CAA Encyclopedia online documentation with a HTML browser
at the following addresses:
<CATIA, DELMIA, or ENOVIA CAA APIs installation path>/CAAV5HomePage.htm>
or
<CATIA, DELMIA, or ENOVIA CAA APIs installation
path>/CAADoc/Doc/online/CAACenV5Default.htm>
When using two CAA RADE V5 releases on the same workstation:
While installing CAA CATIA LA media, if you choose Complete Installation and you see that the required space is OKb in the Start Copying Files panel, please cancel installation otherwise unpredictable results may occur. A workaround is to perform a complete installation of the base CAA CATIA media, before installing CAA CATIA LA media.
From V5R14 onwards, RADE can be installed in the same folder than other V5 brands, such as CATIA, DELMIA, or ENOVIA LCA. This is proposed by default. If you choose to install in the same folder than another V5 brand, pay attention when launching RADE and/or this brand. The environment taken by default is the last one installed. You should then always declare the appropriate environment using the -env and -direnv options. For example:
catstart -env CATIAEnv -direnv CATIAEnvFolder
CATVBTLicenser.exe -env RADEEnv -direnv RADEEnvFolder
If you modify your RADE environment and change the CATUserSettingPath variable, pay attention that the last folder name must always end with RADE.
If you have already installed a configuration and its license, and if you later on install an add-on and another license for both the same configuration and the add-on, you may have messages when using the products packaged in the configuration when they search for their licenses, but they will run normally.
For example, if you have already installed the CAA C++ Extended Development Configuration (CDC) and its license, and if you install the CAA Source Code Manager (SCM) product and a license for both CDC and SCM, the CAA RADE products you were previously using with CDC will issue a message similar to "No license available to fulfill CDC request" before getting their licenses from the license manager, but they will run normally.
To enroll an ITC license using the RADE Licences Manager (CATVBTLicenser), in the left part of the dialog, select CAA - C++ Unit Manager Product or CAA - All RADE Products, depending on what you have installed, and select ITC in the right part. Selecting CAA - Interactive Capture Product in the left part of the dialog is of no use.
Since V5R7, when using the implementations of the CATIDocEnvironment and CATIDocLocator interfaces of the ObjectModelerBase framework, the CATIA Team PDM license is checked and the methods fail if no license is found.
A new MkCheckSource error (VISI) detects the usage of prohibited implementations of Specs Modeler interfaces. An example is the CATSpecObject class. You are invited to check this error, and modify your code to use the appropriate interface in place of the internal class. For example, do not use CATSpecObject, but instead use the interface that CATSpecObject implements and that supplies the CATSpecObject method. In V5R14, without this migration, your code could fail.
When launching the SCM monitor on HP-UX with a local DB2 server, the SQL1224N error may be raised. To overcome this problem, configure DB2 to use a client/server connection (typically, "db2 catalog tctpip node" + "db2 catalog database at node" statements).
If you check the FEATURE and/or
ENOVIA add-ins using the Rational Rose Modeler Edition Add-ins/Add-in Manager
command, Rational Rose Modeler Edition abends when exiting. Nevertheless, the
FEATURE and/or ENOVIA add-ins are correctly taken into account by
Rational Rose
For ENOVIA
Publish works correctly only if the ENOVIA LCA database log size has been updated with the following order:
db2 update dbcfg for $1 using LOGFILSIZ 6000 LOGPRIMARY 6 LOGSECOND 6.
where $1 is the name of the LCA
database. Failing to do this will lead to mask not being updated during the
publish operation.
On locales other than English (en_US) on the AIX Operating System, you can get following error messages on standard output/error when executing a CAA sample or application:
Can't open library libTheViewLibrary.a --> reason = A file or directory in the path name does not exist
or:
Could not load program MainExe:
Could not load module libShared_1.a.
Dependent module Shared_2.exp could not be loaded.
Whereas the library exists and is accessible from the application.
In the case the command /usr/bin/dump -H on the impacted library shows an invalid dependency on an export file, such as:
dump -H libShared_1.a INDEX PATH BASE MEMBER 0 /lib:/usr/lib 1 libJS0GROUP.a 2 Shared_2.exp
The problem may be caused by unexpected collation order in non English locales. Problem was reported with German locale setting (de_DE), but other locales may be impacted.
To workaround this problem, you should:
export LC_COLLATE=CYou can also add the export of the environment variable at the end /usr/Dassault/Systemes/T14/aix_a/code/command/mkinit.sh
Building CAA samples or applications in debug mode (mkmk -g) on Solaris may fail due to additional links to unauthorized symbols added by the Solaris C++ compiler.
When using CATIProductInSession, this sample was making the
assumption that an active representation exists even in a program that doesn't
perform any visualization. This was not true but was working in the case of the
sample. Modifications in CATIProductInSession implementations in V5R14SP1
enforce that no active representation exist when there is no visualization. The
sample has been changed accordingly. Customer code that has been derived from
this sample must be corrected as well.