On this page:


Summary: Once you have created your language package, there are various steps you need to go through to ensure that CAST takes your package into account correctly. This section describes the required actions.

Step 1 - Validation

The first step is to validate your language package. This is done using the UA Assistant (UAAssistant.exe) that can be found at the root of your CAST installation. This tool checks that your language packages are correct and conform to the required standards before they are used, thus avoiding errors during an analysis.

The UA Assistant will only validate the following files, however the presence of other items such as the plugin and prepro folders or the XXXCastMetrics.xml file will not affect the validation process.

The validation process is quite simple - specify your language package parent folder, click Validate, then check the results. Refer to the embedded UA Assistant help for more details about this process.

Step 2 - packaging the language package

You now have a choice about what you would like to do. You can:

At present either option will function, however, CAST recommends that you start to include your Universal Analyzer language packs in custom extensions as the legacy option may be removed at some point in the future.

Include your Universal Analyzer language package in a custom extension (new in CAST AIP 8.0.x)

Configuration\Languages\<Language_Pack>

Install your Universal Analyzer language package directly (legacy option)

This method is identical to the only method that was available in previous releases of CAST AIP (prior to CAST AIP 8.0.x).

  • CAST recommends that you start to include your Universal Analyzer language packs in custom extensions as described above as this legacy option may be removed at some point in the future.
  • In addition the installation method will install ALL language packs located in the %ALLUSERSPROFILE%\CAST\CAST\<version>\Configuration\Languages\<Language_Pack> folder.

A - Save to disk

Once a package has been validated successfully and any errors reported by the UA Assistant have been cleaned up, you can now use the Save to Disk option in the UA Assistant (UAAssistant.exe):

This will transfer the entire language package to the default installation location which is used in the next step. The location is here:

%ALLUSERSPROFILE%\CAST\CAST\<version>\Configuration\Languages\<Language_Pack>

B - Install the language pack

The next step is to use CAST Server Manager (servman.exe located at the root of your CAST installation folder) to install the language pack in your CAST schemas. This can be done:

This section deals with both situations.

  • It is not necessary to install a Language Pack into a CAST Measurement Service schema.
  • Installing an extension in a group (Management/Analysis/Dashboard Services) of CAST schemas will allow you to use that extension with ALL Applications that are managed by these CAST schemas. Therefore, you will need to repeat this step for each "group" of CAST schemas with which you want to use the extension. For example, if you have the environment listed below you will need to install the extension in Schemas A and B for Applications A, B and C to be able to use the language pack:
    • Schemas A used by Application A
    • Schemas B used by Application B and Application C
  • This installation method will install ALL language packs located in the %ALLUSERSPROFILE%\CAST\CAST\<version>\Configuration\Languages\<Language_Pack> folder.

On completion, the language pack will be displayed in the Universal technology editor in the CAST Management Studio:

Note that if you have created the language pack specifically for a language that will be handled by the Universal Importer (see Defining a new language), then the language will NOT appear in the Universal technology editor as shown above.

Installing the language pack with new CAST schemas

Note that:

  • if you do not see this screen, then your language pack is not located in the correct folder
  • the screen may display other items - these are CAST AIP Extensions located in %PROGRAMDATA%\CAST\CAST\Extensions




Installing the language pack with existing CAST schemas



Note that:

  • if you do not see this screen, then your language pack is not located in the correct folder
  • the screen may display other items - these are CAST AIP Extensions located in %PROGRAMDATA%\CAST\CAST\Extensions


Step 3 - Install a custom CAST Delivery Manager Tool plugin (optional)

This step is optional - it is only required if your custom Universal Analyzer language has a corresponding CAST Delivery Manager "plugin" provided by CAST. This "plugin" instructs the CAST Delivery Manager Tool how to recognize your custom language, what files need to be extracted and packaged and how the corresponding Analysis Unit is created.

See Downloading and installing a CAST DMT extension in archive format for more information.

If you do not have a custom plugin, you must still use the CAST Delivery Manager Tool to package your source code - see below.

Step 4 - Use the CAST Delivery Manager Tool / CAST Management Studio

The final step is to use the CAST Delivery Manager Tool to package your source and then use the CAST Management Studio to analyze the source code and generate a snapshot.

Note that when running an analysis when the <all users dir> option has been used will always cause the following WARNING to appear in the extension log (ApplicationExtensions.castlog):

Extension <all users dir> at version <version> cannot be found on disk so it is deactivated. Please download it.

This warning can safely be ignored as it has no impact.