The Select Objects page of the Import Wizard lists all objects found in the source file you have selected. For each object, the State is one of the following values:
New. This is a new object.
Existing. This object already exists in adTempus. The data from the file will replace the current data in adTempus.
Duplicate. Another object with the same name already exists in adTempus, but it has a different identity (see More About Duplicate Objects, below. The data from the file will replace the current data in adTempus.
Select the objects that you want to import by checking the box next to them.
Note: Some objects may be imported even if you don't select them in the list, if they are referenced by objects that you have selected to import. For example, suppose you have selected to import Job "Job A," and Job A uses Credential Profile "freduser." Because this Credential Profile is needed by Job A, it will be imported even if you don't select it in the list.
When you have finished making your selections, click Next to import the selected objects and continue to the Import Results step.
Each object in adTempus has an internal identifier (or "key") that you do not see. This identifier never changes, even if the object's name or other properties change. This allows adTempus to always uniquely identify each object.
If you export an object and then re-import it into the same adTempus server, the identifier in the import file will match the object's identifier in the database, so adTempus will know that the object is "Existing." This is true even if you have changed the name of the object. For example, suppose that you export job "Job A" to a file, then rename it to "Job B." When you import that file, adTempus will know that "Job A" in the file is the same object as "Job B" in adTempus. If you choose to import the job, the values from the file will replace the values currently in adTempus.
However, support you independently created jobs named "Fred's Job" on Server A and Server B. Since these jobs were created separately, they will have different internal identifiers even though they have the same name. If you now export "Fred's Job" from Server A and import it to Server B, adTempus will detect that there is already a job named "Fred's Job," but the existing job has a different internal identifier. In this case adTempus will list the state of "Fred's Job" as "Duplicate," indicating to you that there is already another job with that name.
When a duplicate object is found, there are two possibilities:
You want the object in the file to replace the object already in adTempus. In this case, simply check the box to import the object.
These are really two separate objects, and you don't want the existing object to be replaced. For example, suppose "Fred's Job" from Server A does something completely different from the "Fred's Job" on Server B, and you want to keep both of them. In this case you need to cancel the import and either
Rename the object on the original server and re-export it, or
Modify the import file to rename the object there. See the import/export overview topic for more information on the file format.
See Also