CMS Snapshot Analysis - Run Analyzer - Information - How to reproduce user issues for Extension

Created by user-32741, last modified by John McMahon on Jan 19, 2024
Purpose

This page explains how to reproduce Fatal Error , Non-Fatal Error, Performance issue and warnings that occur during analysis or snapshot of a Universal Analyzer technology.

Applicable in CAST Version
Release
Yes/No
8.3.x(tick)
Applicable RDBMS
RDBMS
Yes/No
CSS(tick)
Action plan

Perform the following steps to reproduce Fatal Error, Non-Fatal Error, Performance issue and Warnings that may occur during analysis or snapshot of a Universal Analyzer technology.

  1. In order to proceed with the below steps, get the Relevant input based on the following categories.
    Non-Fatal Error / Warning / Fatal Error - Relevant Input
    Performance Issue - Relevant Input
  2. Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.
  3. Import the databases
  4. Synchronise the databases - Mngt and KB in case of analysis issues. Mngt , KB and CB in case of snapshot issues.

  5. Configure the analysis

    1. Open CAST-MS

    2. Get the deployment folder path.

    3. Map the source code path in order to respect the deployment defined in configuration.
    4. Go to the current Version tab and check the path of AU whether it is mapped to the same path of the deployment folder.
    5. If customer provides the complete source code then the complete source code in the mapped deploy folder and run the analysis.
    6. If customer provides only couple of files as requested by support, then recreate the user defined UA analysis unit and keep the source files in one folder and add folder in the CAST-MS configuration tabs to analyze those files. Refer the official documentation which explains How to configure different files in the Source Setting Tab.
    7. Configure DLM only if the issue is related to DLM. If not required delete it from CAST-MS because while configuring the analysis you might not have the dlm.xml file. For more info refer this page
    1. Only if the issue is related to missing links and reference pattern, configure reference pattern otherwise remove it from CAST-MS.For more info refer this page
    2. If you don't require the settings in"Tools before analysis" and "Tools after analysis" for your reproduction then remove these configurations from Content enrichment tab in CAST-MS.For more info refer this page
    3. Uncheck the analysis units of other technologies if you have other technologies apart from the technology that is being analyzed but in case of missing links between inter technologies (for ex: missing links between java method and oracle table) you have to be careful while unchecking the analysis units of other technologies. This will shorten down the analysis run time. For more info, refer this page
    4. If Architecture model is configured, the same configuration should be made. For more info, refer this page

    5. If any UA COE technology or any other custom language is used then you will need the contents of the %ALLUSERSPROFILE%/CAST/CAST/<major_version> folder. Follow the below steps:

      1. Open the file CastGlobalSettings.ini
      2. Go to the the path mentioned in the file for field CAST_ALL_USERS_PATH
      3. Copy and paste the contents of <Sherlock_export>\ConfigurationFiles\UA_InstalledLanguages\ into this folder

    6. For UA extensions Copy and paste the contents of <Sherlock_export>\ConfigurationFiles\Extensions into %ALLUSERSPROFILE%/CAST/CAST/<major_version>/Extensions
      Note - If you know the version of the Language package or Extension used then you can download the same using Extension Downloader

    7. If the UA language is Siebel or Peoplesoft and if you want to reproduce any error caused by single file then you need not run the analysis on the entire source code but only on that particular file.

    8. Check all the tabs in the CAST-MS for different configuration done by customer, make sure you have the same configuration otherwise your analysis will fail at some other step and you will end up with different issue.

  6. Run the analysis

  7. Run the Snapshot. If you want to run only snapshot by skipping analysis then refer the page - CMS Snapshot Analysis - Compute Snapshot - Information - How to compute snapshot by skipping analysis
Notes/Comments

Applicable technologies:

Related Pages