Cisco Cisco Workload Automation 6.3 User Guide
43
Transporting Data Objects
Resolving Mapping Errors and Conflicts for Jobs
Discrepancies between the values of these data objects in each source and destination should be resolved by mapping
an equivalent value in the destination to the data object in the source. However, if left unmapped, only a subset of these
values are considered errors and failure to map these will prevent the job transport. Depending on the job type, these
required fields are Owner, Agent, Agent List, and occasionally Runtime User.
an equivalent value in the destination to the data object in the source. However, if left unmapped, only a subset of these
values are considered errors and failure to map these will prevent the job transport. Depending on the job type, these
required fields are Owner, Agent, Agent List, and occasionally Runtime User.
Occasionally, when transporting jobs, a mapping error or conflict may occur. On those occasions, the Interactive Job
Definition Mapping dialog is displayed to pinpoint and resolve the problem areas.
Definition Mapping dialog is displayed to pinpoint and resolve the problem areas.
Resolving Mapping Errors and Conflicts for Jobs
The Interactive Job Definition Mapping dialog provides a means to resolve any differences between the source and
destination on-the-fly. See
destination on-the-fly. See
below.
Some data object differences are more critical than others. Mapping differences are divided into two types called Errors
and Conflicts. Transporter provides visual clues to help the user quickly pinpoint any mapping problems between source
and destination. Colored text in the Interactive Job Definition Mapping dialog highlights the tab and field where
mapping differences exist.
and Conflicts. Transporter provides visual clues to help the user quickly pinpoint any mapping problems between source
and destination. Colored text in the Interactive Job Definition Mapping dialog highlights the tab and field where
mapping differences exist.
Errors
Errors denote more crucial differences between data object. An error occurs when a vital component of a job in the
source does not exist or is not mapped to an equivalent object in the destination. Errors result from missing values in the
corresponding data fields that are key to a job. These data fields are the Owner, Agent, Agent List, and Job Alias. You
can locate the field with the error by looking for the tab with red text. On that tab, a red arrow will point to each field
containing an error. A job with a mapping error cannot be transported until the error is resolved.
source does not exist or is not mapped to an equivalent object in the destination. Errors result from missing values in the
corresponding data fields that are key to a job. These data fields are the Owner, Agent, Agent List, and Job Alias. You
can locate the field with the error by looking for the tab with red text. On that tab, a red arrow will point to each field
containing an error. A job with a mapping error cannot be transported until the error is resolved.
From the destination list for the Error field, select a value in the destination that should be mapped to the source value.
The number in the Errors field will decrease each time an error is resolved. The job cannot be successfully transported
to the destination until all errors are resolved.
The number in the Errors field will decrease each time an error is resolved. The job cannot be successfully transported
to the destination until all errors are resolved.
Conflicts
Conflicts are the less critical difference between data objects. A conflict occurs when a job object referenced by the
source does not have a corresponding match in the destination. Unlike errors, these attributes are not critical. You can
locate the field with the conflict by looking for the tab with the blue text. On that tab, one or more blue arrows will point
to the field(s) causing the conflict. Conflicts do not prevent the job from being transported, but the conflicts result in a
loss of data if not resolved (e.g., it may be missing dependencies or associated events, etc.)
source does not have a corresponding match in the destination. Unlike errors, these attributes are not critical. You can
locate the field with the conflict by looking for the tab with the blue text. On that tab, one or more blue arrows will point
to the field(s) causing the conflict. Conflicts do not prevent the job from being transported, but the conflicts result in a
loss of data if not resolved (e.g., it may be missing dependencies or associated events, etc.)
From the destination list corresponding to the Conflict field, select a value in the destination that should be mapped to
the source value. The number in the Conflicts field will decrease each time a conflict is resolved.
the source value. The number in the Conflicts field will decrease each time a conflict is resolved.