Cisco Cisco Workload Automation 6.3 User Guide
80
Using the Transporter Export/Import Utility
Using the Export/Import Command Line Interface
-O - Use this option to force update of the relationships with referenced artifacts in the destination during import.
Without this option, the relationships with referenced artifacts are not updated during a import and only the job is
updated in the destination.
Without this option, the relationships with referenced artifacts are not updated during a import and only the job is
updated in the destination.
Note:
The options -CO, -VT, and -CD are mutually exclusive. The options “-a”, “-g”, “-i” are ignored if either of “-CO”,
“-VT”, “-CD” is used. If the options “-a”, “-g”, “-i” are not used, the entire repository is considered for import.
Examples:
Import all data that was exported to a directory named \Job1:
transcmdline[.sh] -T importjob -s "C:\Output\Mar19\Job1" -d MyDest -m "C:\Import.map"
Import a specific job group named MyJobGroup that was exported to the \Job1 directory:
transcmdline[.sh] -T importjob -s "C:\Output\Mar19\Job1" -g MyJobGroup -d MyDest -m "C:\Import.map"
Importing Calendars
You use the following command and parameters with the Transporter to import calendars that were previously exported.
Before doing any import, you must export the data from the source system.
Before doing any import, you must export the data from the source system.
Syntax:
$ transcmdline[.sh] -T importcal -s <source-directory-name> -d <destination-connection-name> [-c
<calendar-name> | -i <selection-file>]
Options:
-T importcal - Indicate that the transcmdline tool is going to import calendar data to 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 calendar
data reside. (Required except if using a selection file. See Note below.)
data 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).
-c <calendar-name> -Specify the calendar name to be imported.
-i <selection-file> - Specify the file that contains names of multiple Calendars to be imported.
-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
using a selection file.) A map file must have been created and saved using the Transporter utility. See the
.
-CD - Use this option to indicate that a delta is being imported.
-CO - Use this option to see a “comparison” of the export files with the destination CWA system instead of perform
an actual import. A report file named compareReport.txt is created one of these directories:
an actual import. A report file named compareReport.txt is created one of these directories:
Windows: C:\Users\Administrator\.transporter\report\.
UNIX: /root/.transporter/report/
-VT - Use this option if only an import “validation” is to be done instead of an actual import. A report file named
validateReport.txt is created one of these directories:
validateReport.txt is created one of these directories:
Windows: C:\Users\Administrator\.transporter\report\