This section describes the recommended methodology.
|We assume that:
When working with SCM, you have to create a Buildtime view that is managed by SCM and a Runtime view to open CATIA. CATIA cannot be started from the Buildtime view and SCM cannot deal with files stored in the Runtime view. So both views have to be split.
The very first thing to do consists in creating a CAA workspace whose structure is identical to the one shown below.
Create the Buildtime view manually. It must be identical to the view below.
view is a workspace containing frameworks including code modules
and CNext directories.
|The RADE tool to be used at this stage is SCM. SCM
integration consists for the application architect in locating the
resource at the right place in the framework directory, and in checking
in and checking out the files.
Files like CATScript, CATGScript, CATNls can be checked-out concurrently by several users because it is possible to merge the information. Other objects (CATPart, .catalog for example) cannot be automatically merged. As a consequence, they cannot be concurrently checked out. The conflicts will have to be managed outside the tool. To share the application with other users, the architect promotes his work to its father workspace or publishes his work to his children workspaces.
From the Start menu, select Programs>CATIA>Tools>Environment Editor V5R16.
Select Environment>New from....
Check Add a new path to this environment and enter a new path in the NewPath field.
Enter the name of the application you want to create and click OK when done.
CATKnowledgeBuildPath setting with
the path of the "knowledge" directory of your Buildtime view.
Create the Runtime view. To do so, copy the CNext directory located in the Buildtime view into the <OS> directory of the Runtime view. The structure must be identical to the one below.
|Note that you can copy the CNext directory
anywhere if this location is known by the environment, that is to say,
provided you set the
|The RADE tool to be used at this stage is
MAB. Use the mkrtv command
then the mkGetPreq command (mkGetPreq
<CATIA_folder>\BSF) to create the link between your code and CATIA
code. The structure must be identical to the view above.
The administrator installs the CATIA version he used to develop his application on all client computers or on a server.
The administrator copies the <OS> (directories structure and content), and more generally, the whole Runtime view of his directories structure on the client computer or on a server.
The administrator sets the required variables:
The administrator empties and locks the
CATKnowledgeBuildPath setting on the client install. For more
information about the way to lock settings, see CATIA Infrastructure
Installation Guide: Administering Version 5: Locking Settings.
The targeted user will access all knowledge resources i.e. CATIA native ones
and the new deployed application resources.