Frequently Asked Questions

This section gives you information about questions you may have when working with ARM or the directories structure.

Directories Structure


Directories Structure

What is the Use of Creating a Buildtime View and a Runtime View?

When working with SCM, you must split both views because SCM only manages files stored in the Buildtime view and CATIA deals with files stored in the Runtime view.
If you do not use SCM or RADE tools, you don't have to split both views, you can choose to create only one directories structure. However, when creating and deploying more than one application, it is recommended to create a Buildtime view (or the equivalent of a Buildtime view) for each application to store the required resources. Those resources will be merged in a single Runtime view (or its equivalent ) when deploying applications.

What is the Use of the CATKnowledgeBuildPath Setting?

When building the application, this setting can indicate the location where Knowledge resources have to be stored and read. Using this setting is like inserting a directory at the very beginning of the CATKnowledgePath environment variable. Resources are first searched for in the selected directories structure and then in those indicated by the CATKnowledgePath variable. Using this setting is of interest if resources are not stored in the Runtime view.

In Which Cases Do I Have to Modify Environment Variables?

When deploying applications, If you copy the directories at a location that is not known by CATIA, modify the content of some environment variables (CATMsgCatalogPath, CATKnowledgePath, CATGraphicPath, CATStartupPath...) using the Environment Editor.

If, After Deploying the Created Applications, the Architect Adds Resources, How Will They Be Taken Into Account?

  • You can store the resources on the network and modify the CATKnowledgePath environment variable on all end-user PCs. CATIA needs to be restarted.
  • If the CATKnowledgeBuildPath setting is not already used, you can use it to point a directory on the network for example and then lock this setting (administration mode).
  • You can copy the required resources in the Runtime view of all end-user PCs. CATIA needs to be restarted.

How Do ARM, the New Directories Structure and the Index File Work Together?

If you want to work with ARM and the index file, you have to create the new directories structure because both systems are based on this structure. But you can work with this new structure without working with ARM or the index file.


How Can I Structure My Data if I Want to Create Several Applications in my Buildtime View and if I Want to Deploy Them?

It is strongly recommended to create a framework (if you work with RADE) or a directories structure for each application and to store the resources dedicated to each application in the corresponding framework. When deploying applications resources are merged in the Runtime view.

Do I Need to Exit CATIA so That My Changes Are Taken Into Account?

It depends. If you work with .CATfct, icons, and .CATnls files, you must run the mkrtv command so that your changes are taken into account.


Do I Have to Store the Resources Referenced in the ARM Catalog in Special Directories?

ARM catalogs have to be stored in the CATIA Runtime view (in the knowledgeResourceCatalogs directory) to be taken into account by the Application Resources Management system. Resources referenced by the ARM catalog must be stored in the knowledgeResource directory or in ENOVIA.  For more information, see Creating, Managing and Deploying Knowledge Applications Resources.


Can I Use ARM Without Using the New Directories Structure?

No you cannot.

Can I Add Other Fields to My ARM Catalogs?

No you cannot. ARM is based on a fixed structure containing the following keywords:

  • Name: Corresponds to the name of the resource i.e. the one created by default by the catalog application (for selected features, this keyword cannot be filled freely).
  • Logical Name: Corresponds to the logical name of the resource. It represents the resource identifier. The value must be unique because it will be used by ARM to find the corresponding resource in the catalog.
  • Type: Corresponds to the type of resource that you are trying to reach. Its value must be one of the following values:
    • AssemblyTemplate
    • Table
    • PowerCopy
    • Drawing
    • UserFeature
    • Product
    • RuleBase
    • PartTemplate
    • Rule
    • Analysis
    • Part
  • Usage: Corresponds to a comment indicating what this resource is used for.