Cisco Cisco Workload Automation 6.3 User Guide
38
Mapping Data Objects
How to Map Data Objects
Agent Lists
– This tab displays a list of defined agent lists that exist in the source and provides for a mapping of a
corresponding destination agent list.
Calendars
– This tab displays a list of defined calendars that exist in the source and provides for a mapping of a
corresponding destination calendar.
Note:
If a selected calendar depends upon a fiscal calendar, the fiscal calendar is also transported with the selected
calendar.
Classes
– This tab displays a list of defined job classes that exist in the source and provides for a mapping of a
corresponding destination job class.
Events
– This tab displays a list of defined events that exist in the source and provides for a mapping of a
corresponding destination event.
Groups
– This tab displays a list of defined job groups that exist in the source and provides for a mapping of a
corresponding destination group.
Owners
– This tab displays a list of defined users and workgroup owners that exist in the source and provides for a
mapping of a corresponding destination owner.
Users
– This tab displays a list of defined users that exist in the source and provides for a mapping of a
corresponding destination user.
Variables
– This tab displays a list of defined variables that exist in the source and provides for a mapping of a
corresponding destination variable.
Virtual Resources
– This tab displays a list of defined virtual resources that exist in the source and provides for a
mapping of a corresponding destination virtual resource.
Custom Resources
– This tab displays a list of defined custom resources that exist in the source and provides for a
mapping of a corresponding destination custom resource.
Timezones
– This tab displays a list of defined timezones that exist in the source and provides for a mapping of a
corresponding destination timezone.
How to Map Data Objects
Each list that is displayed by clicking one of the buttons listed above is divided into two columns that display the selected
data object type from the source and destination. If an object type that exists in the source also exists in the destination
Master, it is displayed in the destination column (unless previously mapped to a different destination object). If there is
no matching object type on the destination side (and that object has not been mapped), that space is blank.
data object type from the source and destination. If an object type that exists in the source also exists in the destination
Master, it is displayed in the destination column (unless previously mapped to a different destination object). If there is
no matching object type on the destination side (and that object has not been mapped), that space is blank.
On the right side of each Destination text field is a combo box that displays a list of available values. Select an object
from the list to associate with the source data object. Ideally, you would match up each value displayed on the source
side with a value on the destination side.
from the list to associate with the source data object. Ideally, you would match up each value displayed on the source
side with a value on the destination side.
However, the jobs or other data that are being transported may not use all of the values that exist in the source. You may
wish to map only the data object values that you think are needed and leave the rest unmapped.
wish to map only the data object values that you think are needed and leave the rest unmapped.
Note:
Mappings apply an object’s referenced objects and not the actual object itself.
The idea behind mapping the data objects is to provide a means to automate transporting of data between the source
and destination.
and destination.
With a map file, it is easy to schedule a batch job in CWA to transport a job or job group between the source and
destination. Refer to
destination. Refer to
for information on using Transporter in batch mode.