Page History

...

Neutralization routines can be configured at different scopes (system

• Single-

...

• analysis,

...

•  
• Application-specific

...

• and 
• System-wide,).

Depending on the location of the xml file, precedence and scope will change.

Precedence and scope of configurations is as follows:

• Single-Analysis
  • Neutralizations can apply only to a unique analysis.
  • In this case, the xml file should be located at:

    • [analysis_base_dir]/libraries/[technology]

• Application-specific
  • Neutralizations can apply to all analyses of a specific application.
  • In this case, the xml file should be located at:

    • [agent_home_dir]/conf/apps/[app_name]/libraries/[technology] 

• System

...

• -wide 
  • Neutralizations can apply to all analyses of all applications.
  • In this case, the xml file should be located at:

    • [agent_home_dir]/libraries/[technology] 

  • Exceptions to this rule are: 
    • cpp engine reads from  …/libraries/
    c
    • c 
    • objective engine reads from …/libraries/objetivec and …/libraries/c

Legend:

•  

  [agent_home_dir] : local installation directory of Kiuwan Local Analyzer (KLA)

• [analysis_base_dir] : root directory of application source code to be analyzed, as specified by “-s” option of KLA CLI (Command Line Interface), or in “Folder to analyze” input box when using KLA GUI (Graphical User Interface)
• [app_name] : name of the app to be analyzed, as specified by “-n” option of KLA CLI (Command Line Interface), or in “Application name” input box when using KLA GUI (Graphical User Interface)
• [technology] : name of the Kiuwan technology, as specified in  [agent_home_dir]/conf/LanguageInfo.properties

...

Therefore, next sections will use java_custom_neutralizations.xml as the name for our custom file.

Structure of Custom Neutralization File (CNF)

Next sections describe this structure.