Cisco Cisco Workload Automation 6.3 Guía Del Usuario
81
Using the Transporter Export/Import Utility
Using the Export/Import Command Line Interface
UNIX: /root/.transporter/report/
Note:
The options -CO, -VT, and -CD are mutually exclusive. The options “-c”, “-i” are ignored if either of “-CO”, “-VT”,
“-CD” is used. If the options “-c”, “-i” are not used, the entire repository is considered for import.
Example:
Importing the calendar objects in the Cal1 directory:
transcmdline[.sh] -T importcal -s "C:\Output\Mar19\Cal1" -d MyDest -m "C:\Import.map"
Validating Jobs, Job Groups, or Calendars
You use the following command and parameters with the Transporter to validate a job, job group, calendar import prior
to performing the actual import. The validation checks for any errors such as mapping and dependency errors. Before
doing any import validation, you must export the data from the source system. The validate operation generates a report
file named validateReport.txt in one of these directories:
to performing the actual import. The validation checks for any errors such as mapping and dependency errors. Before
doing any import validation, you must export the data from the source system. The validate operation generates a report
file named validateReport.txt in one of these directories:
Windows: C:\Users\Administrator\.transporter\report\
UNIX: /root/.transporter/report/
An empty report indicates that there no errors with this import. If there are errors, you can use Transporter to correct the
mapping file to resolve any mapping errors.
mapping file to resolve any mapping errors.
Syntax:
$ transcmdline[.sh] -T [importjob|importcal] -s <source-directory-name> -d
<destination-connection-name> -m <map-file> -VT
Options:
-T importjob|importcal - Indicate that the transcmdline tool is going to import job or calendar data from a file
rather than work as a transporter.‘-T’ stands for Task. (Required)
rather than work as a transporter.‘-T’ stands for Task. (Required)
-s <source-directory-name> - Specify the name of the directory in which the files containing exported data
reside. (Required)
reside. (Required)
-d <destination-connection-name> - Specify the file name containing the destination system connection
details. (Required)
details. (Required)
-m <map-file> - Specify the name of the map file used to resolve static data differences. (Required except when
using a selection file.) A map file must have been created and saved using the Transporter utility. See the “Mapping
Data Objects” chapter in the CWA Transporter User Guide.
using a selection file.) A map file must have been created and saved using the Transporter utility. See the “Mapping
Data Objects” chapter in the CWA Transporter User Guide.
-VT - Use this option if only an import “validation” is to be done instead of an actual import.
Example:
Validating the data that was exported to a directory named \Job1:
transcmdline[.sh] -T importjob -s "C:\Output\Mar19\Job1" -d MyDest -m "C:\Import.map" -VT
Comparing Jobs, Job Groups, or Calendars
You use the following command and parameters with the Transporter to compare an exported data set with the data in
a destination CWA system. Before doing any comparison, you must export the data from the source system. The
compare operation generates a report file named compareReport.txt in one of these directories:
a destination CWA system. Before doing any comparison, you must export the data from the source system. The
compare operation generates a report file named compareReport.txt in one of these directories: