Publish in Batch Mode

CA TDM lets you publish data in a batch mode. You can publish data without running the user interface. This ability helps you build scripts that are controlled by dynamic run parameters and also combine multiple publishes so that you can quickly prepare a test environment. This feature also allows you to interface the tool with products such as Quality Center from HP. You can pre-populate data for matching test scripts being run under the control of Quality Center.
tdm10
CA TDM lets you publish data in a batch mode. You can publish data without running the user interface. This ability helps you build scripts that are controlled by dynamic run parameters and also combine multiple publishes so that you can quickly prepare a test environment. This feature also allows you to interface the tool with products such as Quality Center from HP. You can pre-populate data for matching test scripts being run under the control of Quality Center.
Prepare and Generate the XML Control File
CA TDM uses a control file in XML format to publish in batch mode. Use the publish dialog to create this XML file. After you click the forward arrow icon on the publish dialog, select the
Batch
option, and click the forward arrow icon to generate the batch files.
Two files are created; a windows command file and .xml control file. You can edit these files and can move them to a server for submission. You can also use them with the batch .csv submission control file.
An example format of the created .xml file is as follows:
<GTDatamaker™>
<rep>GTREP</rep>
<tgt>Travel_e</tgt>
<src>Travel</src>
<ld_id>1260</ld_id>
<publish>true</publish>
<connect_rep>true</connect_rep>
<connect_tgt>true</connect_tgt>
<connect_src>true</connect_src>
<username>Administrator</username>
<password>marmite</password>
<onduplicate>continue</onduplicate>
<publishto>TGT</publishto>
<outfile>\1260</outfile>
<outdir></outdir>
<infile></infile>
</GTDatamaker™>
If you want to force a specific CDATE value, include the following XML:
<cy>2010</cy>
<cm>08</cm>
<cd>09</cd>
The description of various parameters is as follows:
  • Rep
    Specifies the exact name of profile that is used to connect to the repository.
  • Tgt
    Specifies the exact name of profile that is used to connect to the target.
  • Src
    Specifies the exact name of profile that is used to connect to the source.
  • infile
    (Optional) Specifies the name of a .csv control file containing substitution variables.
  • outfile
    Specifies the name of the log file and any output files to be created.
  • ld_id
    Specifies the test case ID. Right-click on the context line of the GUI to obtain this ID
  • publish
    Specifies whether to publish. True publishes the data and false allows you to test whether the script is correct up to the point of publish.
  • connect_rep
    Identifies whether to connect to the repository or not.
  • connect_tgt
    Identifies whether to connect to the target or not.
  • connect_src
    Identifies whether to connect to the source or not.
  • Cy
    (Optional) Specifies the current year.
  • Cm
    (Optional) Specifies the current month.
  • Cd
    (Optional) Specifies the current day.
  • Publishschema
    (Optional) Specifies the schema for publishing.
  • username
    Specifies the Datamaker UI user to log in.
  • password
    Specifies the Datamaker UI user password.
  • onduplicate
    Specifies whether to exit or continue when duplicate is detected. Exit fails immediately at the first duplicate; continue carries on to the end of the publish where duplicates are logged.
  • publishto
    Specifies the destination of your published data. Values are TGT or SRC or FILE. If the option FILE is selected, the parameter OUTFILE must be also set.
  • outdir
    Specifies the directory to which all output files are directed.
  • max_lov_items
    Specifies the maximum number of items that are allowed in each list that the LOV processing creates.
  • iterations
    Specifies the number of times you want to repeat the publish.
Move the Control Files to Another Computer
You can move the .xml, .csv (if used), and .bat file to another computer and can run it from there. Verify and amend the following items:
  • Verify the exact location and driver of any hard-coded paths in the .bat and .xml file.
  • Ensure the <tgt>, <src>, and <gtrep> connection profiles exist, spelt the same way (including case), and connect to the correct schema.