Managing Knowledge Applications Resources

Knowledge workbenches provide you with different ways to define "pseudo applications" or sets of features. Even if these applications are not  C++ developed, they need to be managed like any classic C++ application. A new directory created to ease the managing of these applications and features will help you in this task. This management can be performed using a new environment variable, and a new setting, and possibly the RADE tools.

• List of Managed Files

• About RADE Tools

• About the Knowledge Environment Variable and Setting

• Creating, Managing and Deploying Knowledge Applications Resources

• Creating, Managing and Deploying Knowledge Applications Resources Using RADE Tools and SCM

• Advanced Example

• Frequently Asked Questions

List of Managed Files

Knowledge products can rely on the following Knowledge resources:

.CATfct  Files

.CATfct  files generated by BKT and reused by BK2 products contain types, functions, methods, and exposed main behaviors.

Index Files (.idx)

The index is used by the Knowledgeware Index and is used in the Knowledge language, in Knowledge Expert or in BKT.

Knowledge Custom Types

.CATGscript files are generated in the User Feature type definition tab, and reused by the Knowledge index to build a complete view of the Knowledge dictionary of types.

Application Resources Management .catalog Files

Application Resource Management .catalog files establish a link between a logical name of a resource and the physical resource referenced through the catalog. The objective of those catalogs is to answer this simple question: "give me the object named XXX". This is possible in BKT using the Instantiate Template, the Load, the Knowledge Certify and the Insert Component behaviors. It is also used in PKT by the Knowledge Pattern feature.

Knowledge Resources files

Knowledge Resources can include many kinds of data used as resources in the Knowledge language or in BKT like CATPart, CATProduct and .catalog documents.
If the user wants to open a .CATPart file and indicates the name of the file, the system will try to find this file in the knowledgeResources directory first. If he indicates an ARMCatalogName|Resource name, and if:

Workbenches Files

The Workbenches file called WBIM.xml  is generated by BKT. It contains the local User categories and the Deployed workbenches definition.

CATNls Files

.CATNls files are used by BKT applications, by the User Features, the BuildMessage functions, and the tool tips translations to:

• Use the BuildMessageNLS function that can be used in any Knowledge language-based feature and that can rely on those CATNls files to operate a translation. For example, BuildMessageNLS("CATKneTestCatalog","Zero")) looks for the CATKneTestCatalog.CATNls file and tries to translate the Zero keyword.
• Translate Knowledge types associated to User Features, create a CATTypeXXX.CATNls file translating the attribute names. To find out more, see Creating a NLS User Feature in the Product Knowledge Template User's Guide.
• Customize the yellow tool tips that appear when pre-selecting some objects in the tree. To find out more, see Assigning a Comment to a Knowledge Feature in the Knowledge Advisor User's Guide 

CATScript, CATvba and CATvbsFiles

CATVBA and .CATScript macros, edited in the CATIA macro editor or any editor, are reused by different Knowledge products:

• The LaunchMacroFromFile function in the Knowledge language takes as first argument the name of the file that contains the macro.
• In the Visual Basic behavior in BKT.

Icons

Icons associated to User Features and BKT Technological objects and behaviors are located in the <CATGraphicPath>icons\normal directory.