Page tree
Skip to end of metadata
Go to start of metadata

This page handle the case when extension consider files for analysis even if the files are not part of this technology. For example Tibco Extension is considering wsdl files for analysis, even though WSDL are not Tibco technology files.

Observed in CAST AIP
8.2.x (tick)
8.0.x (tick)
7.3.x (tick)
Observed on RDBMS
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
Step by Step Scenario

Run analysis

Action plan
  1. Check if the file extension is part of the language pack. The language pack is displayed in the Universal technology editor in the CAST Management Studio:
    Figure 1

  2. If not then contact CAST Technical Support and provide the relevant input, else it's expected to analyze the file, for example the above screenshot shows that the analyzer will analyze the WSDL files. However you can manually customize the extension Metamodel file located at <CAST_instal_directory>\Configuration\Languages\"Technology"\"Technology.xml" then do component update of the local and measure base from servman:

    Figure 2

  3.  For example Tibco Metamodel file will be located at <CAST_instal_directory>\Configuration\Languages\Tibco\TibcoMetaModel.xml, and the file extensions are listed as follows:

    <category name="Tibco" rid="2">
        <attribute name="extensions" stringValue="*.aeschema;*.sharedjdbc;*.javaschema;*.sharedhttp;*.sharedjmscon;*.process;*.wsdl;*.sharedjmsapp"/>
        <inheritedCategory name="UniversalLanguage" />
        <inheritedCategory name="CsvLanguage" />

If the above steps do not resolve your issue then contact CAST Technical Support and provide the relevant input

 Ticket # 6962
Related Pages

  • No labels