Cisco Cisco Workload Automation 6.3 Mode D'Emploi

Page de 86
39
Mapping Data Objects
Saving the Mapping of Data Objects
Default Mapping Option
You can configure a default mapping value for each type of data object. Each list of potential values for a data object type 
in the source starts with a default. This default has no value until it is assigned a destination value.
Specify a value for default by selecting a value from the list on the Destination side. This default value will be used during 
object transporting whenever a corresponding data object is not mapped in the destination.
Not only can using a default value cut down on possible mapping errors, it can also save you considerable time. For 
example, if you are mapping connection objects and a large number of connections exist in the Source, but only one 
connection is used in the Destination, make the one connection the default. This avoids having to map each individual 
object. However, if the default value is incompatible with the type of data object being mapped, an error will still result. 
For example, if a connection object requires a Unix value and the default value is a Windows value, an error will result. 
In another example, an error would also result if a text string variable is required but the default value is a date calculation 
variable.
Remove Mapping Option
One of the options in the list on the destination side is <<Remove>>. If there is no corresponding destination data object 
to match an existing data object in the Source, you can just delete any reference to the data object when transporting 
objects between Source and Destination. There is no <<Remove>>
 option on the source side. It only exists on the 
destination side.
The <<Remove>> option allows a source object to be transported to the destination. For example, jobs must have an 
owner and an agent so you cannot remove the owner or agent data objects.
Note: 
With the <<Remove>> option, data is transported to the destination, while “removing” object references that had 
been mapped to <<Remove>>. Note that an object's required references cannot be removed; mapping an object's 
required reference to <<Remove>> results in an error when trying to transport the object. For example, a job is required 
to have an agent, so if the job's agent is mapped to <<Remove>> you cannot transport the job
.
Saving the Mapping of Data Objects
The mapping process can be time consuming depending upon the number of data objects you are working with. If you 
think you might transport the same data types between the same source and destination, you should preserve the 
mapping you have completed for the selected data objects. Creating a mapping file will save time and effort when 
repeating the transporting process in the future. A 
.map extension is added when the mapping file is saved for easy 
identification.
Creating a Mapping File
To create a mapping file:
1.
Complete the mapping of the data objects between the source and destination.
2.
From the File
 menu, select Save Map to display the Save Map File dialog.
3.
Name and save the file to the desired directory location. Providing a qualified map file name will be helpful when 
searching for the file in the future.
An Information
 dialog confirms that the map file was created successfully.
The information within the map file can be examined by opening the file with a standard text editor program like Notepad.