Launching the Analyzer from a command line
To run the Analyzer from a command line
- Create a backup copy of the Analyzer.bat file in the ARSystemInstallDir/DeveloperStudio folder.
Add the appropriate options to the command line in Analyzer.bat, for example:
analyzer -x "computer1" -u "Demo" -f "Sample%%"For a list of available options, see Command-line options.
- At the command line, run the batch file.
For examples, see Analyzer command examples.
Command-line options
The following table explains the options for Analyzer from a command line.
Option | Parameter | Description |
|---|---|---|
-u | user | Required login parameter that identifies the user account. |
-p | password | Optional login parameter that identifies the user account. If the user account has no password, omit the -p option. |
-x | serverName | Required login parameter that specifies the server to log on to. |
-w | authenticator | The name of an external authentication string or Windows domain. This is related to the Login window's Authentication field, which is discussed in Setting-up-an-authentication-alias. |
-portnum | TCPPortNumber | Used to log on when the portmapper is turned off. |
-o | CSVFilePath | CSV file path for analyzer results. |
-og | Used to process the input data and generate an output group file with the specified name. | |
-excludeIgnoredResults | Results marked as Ignored should not be included in the report. | |
-a | activeLinkName | Analyze the specified active link. |
-A | Analyze all active links. | |
-f | formName | Analyze the specified form. |
-F | Analyze all forms. | |
-n | applicationName | Analyze the specified application. |
-N | Analyze all applications. | |
-q | escalationName | Analyze the specified escalation. |
-Q | Analyze all escalations. | |
-t | filterName | Analyze the specified filter. |
-T | Analyze all filters. | |
-r | relatedType | Include related object for analysis. Valid options are:
|
-modifiedAfter | date | Analyze objects that are modified after date. Use the M/d/yy h:mm format. Time details are optional. |
-modifiedBefore | date | Analyze objects that are modified before date. When you use -modifiedAfter with -modifiedBefore, you can analyze modified objects between two dates. Use the M/d/yy h:mm format. Time details are optional. |
-c | XML file | XML configuration file path for setting advanced options. See the file. |
-i | def file | Definition file path for specifying objects to be analyzed. Use the following options to create the definition file: -i <deffile> -a <active_link_name> for an active link -A -f <form_name> -F -n -N -q <escalation_name> -Q -t <filter_name> -T -r <related_type> -c <xmlfile> X For information about analyzer rules, see Analyzer-rules. |
-og | Overlay group. Value: 1 Run the analyzer utility on the overlaid objects. | |
You can use the following percent (%) wildcard when specifying names for the -a, -f, -n, -q, and -t options.
- %string analyzes objects with a name ending with string.
- string% analyzes objects with a name beginning with string.
- %string% matches string anywhere in object name.
For example, TMS% analyzes all active links with a name beginning with TMS.
Analyzer command examples
In the following example, the Demo user analyzes all of the filters on the vmw23prem95 server, and the results are entered in the filter.csv file.
C:\Program Files\BMC Software\ARSystem\DeveloperStudio> analyzer -x "vmw23prem95" -portnum 2044 -u "Demo" -p "" -T -o "D:\csv\filter.csv"INFO: Analyzer started: Tue Jul 07 13:13:22 GMT+05:30 2009)
Jul 7, 2009 2:13:27 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication printResultCount
INFO: Analyzed 544 objects
1 Errors, 148 Warnings, 594 Infos
Jul 7, 2009 2:13:27 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication start
INFO: Analyzer completed: Tue Jul 07 18:13:27 GMT+05:30 2009)In the following example, the Demo user analyzes the R_Like form with the directly related option, and the results are entered in the like.csv file.
C:\Program Files\BMC Software\ARSystem\DeveloperStudio> analyzer -x "premq617" -u "Demo" -p "" -f "R_Like" -r "Directly" -o "D:\csv\like.csv"INFO: Analyzer started: Tue Jul 07 14:08:11 GMT+05:30 2009)
Jul 7, 2009 2:08:14 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication printResultCount
INFO: Analyzed 4 objects
0 Errors, 14 Warnings, 6 Infos
Jul 7, 2009 2:08:14 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication start
INFO: Analyzer completed: Tue Jul 07 14:08:14 GMT+05:30 2009)In the following example, the Demo user analyzes the forms that start with R, are modified after June 1, 2009 but before July 1, 2009. The results are entered in the wildcard_date.csv file.
C:\Program Files\BMC Software\ARSystem\DeveloperStudio> analyzer -x "premq617" -u "Demo" -p "" -f "R%" -modifiedAfter "6/1/09" -modifiedBefore "7/1/09" -o "D:\csv\wildcard_date.csv"
INFO: Analyzer started: Tue Jul 07 14:13:22 GMT+05:30 2009)
Jul 7, 2009 2:13:27 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication printResultCount
INFO: Analyzed 20 objects
0 Errors, 14 Warnings, 94 Infos
Jul 7, 2009 2:13:27 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication start
INFO: Analyzer completed: Tue Jul 07 14:13:27 GMT+05:30 2009)In the following example, the Demo user ignores the results that were specified to be ignored in the Analyzer in Developer Studio. For more information, see Working-with-the-Analyzer-View-tab. The results are entered in the a3.csv file.
C:\Program Files\BMC Software\ARSystem\DeveloperStudio> analyzer -x "premq617" -u "Demo" -p "" -f "a%" -o "D:\csv\a3.csv" -excludeIgnoredResults
INFO: Analyzer started: Tue Jul 07 15:50:24 GMT+05:30 2009)
Jul 7, 2009 3:50:26 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication printResultCount
INFO: Analyzed 11 objects
0 Errors, 4 Warnings, 2 Infos
Jul 7, 2009 3:50:26 PM com.bmc.arsys.studio.analyzer.core.AnalyzerApplication start
INFO: Analyzer completed: Tue Jul 07 15:50:26 GMT+05:30 2009)