Cisco Cisco Workload Automation 6.3 User Guide
78
Using the Transporter Export/Import Utility
Using the Export/Import Command Line Interface
Creating a Delta Data Set
You use the following command and parameters with the Transporter to create a delta directory that contains the
differences between newer and older export files. The delta data set in the delta directory can then be imported as
described in
differences between newer and older export files. The delta data set in the delta directory can then be imported as
described in
.
Syntax:
$ transcmdline[.sh] -T delta -s <export-directory-V1> -d <export-directory-V2> -o
<output-directory-name>
Options:
-T delta - Indicate that the transcmdline tool is going to create a delta file rather than work as a transporter. ‘-T’
stands for Task. (Required)
stands for Task. (Required)
-s <export-directory-V2> - Specify the name of the directory that contains files from a newer export operation.
(Required)
(Required)
-d <export-directory-V1> - Specify the name of the directory that contains files from an older export operation.
(Required)
(Required)
-o <output-directory-name> - Specify the name of the output directory in which the result of the delta process
is to be output. (Required)
is to be output. (Required)
Example:
Create and export the delta between newer and older export files:
transcmdline[.sh] -T delta -s "C:\Output\Mar20\Job2" -d "C:\Output\Mar15\Job1" -o
"C:\Output\Mar19\Job3"
Importing Jobs, Job Groups, or Delta Data Sets
You use the following command and parameters with the Transporter to import jobs or job groups that were previously
exported. You also use this command to import delta data that was previously created. You can import full data sets or
specify individual jobs, job groups, or calendars. Before doing any import, you must export the data from the source
system.
exported. You also use this command to import delta data that was previously created. You can import full data sets or
specify individual jobs, job groups, or calendars. Before doing any import, you must export the data from the source
system.
Note:
A delta data set might show that an object has to be deleted. However importing such a delta data set does not
result in deletion of an object in the destination machine. The import process only creates new objects or updates
existing ones.
existing ones.
Syntax:
$ transcmdline[.sh] -T importjob -s <source-directory-name> -d <destination-connection-name> [-a
<job-alias> | -g <job-group-name> | -i <selection-file>] -m <map-file>
Options:
-T importjob - Indicate that the transcmdline tool is going to import job data from a file rather than work as a
transporter.‘-T’ stands for Task. (Required)
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 except if using a selection file. See Note below.)
reside. (Required except if using a selection file. See Note below.)
-d <destination-connection-name> - Specify the file name containing the destination system connection
details. (Required except if using a selection file. See Note below.)
details. (Required except if using a selection file. See Note below.)
Note:
If you are using a selection file, you do not need to use the "-s" and "-d" options as the options are already
specified in the selection file (unless you wish to override the parameter values).
-a <job-alias> - Specify the job to be imported.