Cisco Cisco Workload Automation 6.3 Mode D'Emploi

Mapping Data Objects

Saving the Mapping of Data Objects

Mapping Reports

Transporter can display two mapping reports that provide details about how data objects were mapped in the current 
session: 

Scheduler Object Mapping Rules—Lists the mapping object type and its corresponding mapping rules that are 
described in a .

map file. The report also provides the name of the map file and its source and destination.

Invalid Mapped Objects—Lists those data objects that it determines to have invalid mapping because the data object 
was deleted or renamed in the destination Master.

To view the Scheduler Object Mapping Rules Report:


From the Reports menu, select Mapping Report, 

or



From the Scheduler Object Mapping dialog, click the Report button.

The Scheduler Object Mapping Rules report is displayed in the default browser. See 

 for 

an example. 



From the Reports

 menu, select Invalid Mappings.

The Invalid Mapped Objects report lists the mapping object type and its corresponding mapping rules that is 
considered invalid. The report also provides the name of the map file and its source and destination Master. The 
Invalid Mapped Objects report is displayed in the default browser. See 

 for an 

example.

Mapping Timezones

CWA can have an associated Timezone. For the Transporter, this means that Timezones can be mapped from source to 
destination. 

A Job can reference a Timezone which affects transporting of Jobs. Timezones are referenced via the Scheduler Object 
Mapping dialog.

The following example shows a source Job (with no Parent) with a referenced Timezone. There is a matching destination 
Timezone (AAA TIMEZONE).

The example below shows a Job (with a Parent, \JOB GOUP) with a referenced Timezone that is inherited from its Parent 
Group. There is a matching Timezone in the destination (TIMEZONE 01).

The following example shows a Job (with a Parent, \JOB GOUP) with a referenced Timezone that is NOT inherited from 
its Parent Group. There is a matching Timezone in the destination (TIMEZONE 01). Note that Timezone inheritance is 
independent of other inherited values (unlike Agent inheritance which is tied to AgentList and Runtime User inheritance).