Using analyzers

Analyzers identify modules that break down the fetched content. They are invoked after a URl is fetched into the package instance. In BMC Release Package and Deployment (RPD), you can use the default analyzers or configure your custom ones to perform specific actions.

Analyzers are associated with references in a package. When an associated reference is fetched, the analyzers are run to further process it. You can assign multiple analyzers to a given reference in a certain order to create a processing chain of events.


A reference can have multiple associated analyzers. When the first analyzer explodes the reference with which it is associated, it creates a brand new artifact. Only analyzers with the Copy on Explode property set to Yes are copied and executed on the newly created artifacts.

Some analyzers invoke actions to perform their processing. Most analyzers do so by using a payloaded action method. This means that when an action is run, the artifact contents are sent to the server (storing the contents in a temporary directory), and the specified action is invoked on the server with the current directory set to the directory where the contents were stored. As a result, the action script can access the contents to perform its processing (for example, to extract a file version number). When the action is complete, the temporary directory disappears.

Each separate configuration for an analyzer is saved with a specific name, and this name is assigned to references. For example, the Explode Reference Selectively analyzer extracts files from an artifact based on a regular expression pattern. To extract different sets of files from an artifact, you create multiple analyzer definitions that use the same analyzer but with different file-matching patterns. You can define the Extract DLLs and Extract EXEs analyzers that use the same Explode Reference Selectively analyzer interface module with a %\.dll% file pattern for one and with a %\.exe% pattern for the other. Each analyzer interface module configuration is stored with the analyzer configuration. Therefore, no parameters are assigned when an analyzer is associated with a reference.

Default analyzers

In RPD, you can use the following default analyzers:

  • Explode Reference Contents: This analyzer uses the Explode Reference module.
  • Generate WAR File Table Of Contents: This analyzer uses the Expose WAR Contents module.
  • Generate Windows DLL Version: This analyzer uses the Set Artifact Meta-Data module.
  • Explode Zip File: This analyzer uses the Extract Zip module.

To use a default analyzer, you must add it to the required package. For more information see To add an analyzer to an existing package.

Custom  analyzers

To create your own custom analyzer, do the following:

  1. Go to System > Analyzers, and then, at the bottom-right corner of the analyzers table, click Add Analyzer.
  2. In the Label box, type a name of the analyzer.
  3. In the Copy On Explode list, select whether to copy an analyzer when it explodes the reference with which it is associated.
  4. In the Module list, select the required module, and then click Create.
    For more information about the module types, see Analyzer modules.
  5. On the Summary tab, edit the analyzer parameters if any.

After you create a custom analyzer, you must add it to the required package. For more information, see To add an analyzer to an existing package.

Related topics

Analyzer modules

Working with packages

Was this page helpful? Yes No Submitting... Thank you