A response file can be used to supply all or some of the command-line parameters for Report Commander. To use a response file, include the response file on the command line as show in this example:
adcrutil @c:\parameters.xml
where "c:\parameters.xml" is the name of the response file.
The response file may be placed in any position on the command line. For example:
adcrutil -parameter1:value @c:\parameters.xml -parameter2:value2
When a response file is processed, the parameters in the file are inserted into the command line at the point where the response file command was encountered. If a parameter appears on the command line and in the response file, the relative positions determine which value is used. In the example above, if the response file contains values for parameter1 and parameter2, the value from the file would be used for parameter1, but the value on the command line would be used for parameter2. For parameters that accept multiple values, the list of values is taken from both the file and the command line.
If you are using response files extensively, you should consider using a project-based approach instead of the command-line approach, using the Project Editor and Project Runner.
The response file is defined using XML.
You can create a sample parameter file that lists all of the available parameters and shows how to define them in the response file. To generate the sample file, use this command:
adcrutil -!xmlparametertemplate:"c:\sample.xml"
where "c:\sample.xml" is the name of the sample file you want to create. You can edit this file in an XML editor or in a plain text editor like Notepad.
You can also generate a parameter file that contains the values you have specified on the command line. To do this, add the command "-!xmlparameterfile" to the command line, along with the parameters you want to save to the response file:
adcrutil -!xmlparameterfile:"c:\response.xml" -parameter1:value -parameter2:value2
The program will create "c:\response.xml", containing the values for parameter1 and parameter2.