Select Objects Page

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.

Don't import referenced objects that already exist on this server

When this option is checked, adTempus only shows objects that were specifically selected when the export was performed. Other objects included in the file are not shown, and are not imported if they already exist on the server. If they do not already exist on the server, they will still be imported.

When you export a job from adTempus, you select just the job in the export window. However, adTempus also exports all other objects that the job links to or depends on. This includes

• The Job Group that the job is in (and all parent groups of that group)
• The Job Queue
• The Credential Profile
• Any Notification Recipients, Shared Scripts, or other shared objects the job uses
• Any jobs the job is linked to through Responses, Conditions, or Triggers

All of this data is exported so that the job (and its chain) can be fully recreated on the target server. If these other objects already exist on the target server, the Select Objects page indicates this (see above) and lets you decide which objects should be imported. When you check Don't import referenced objects that already exist on this server, these other objects are not shown in the list, and are not imported unless they don't already exist. This makes it easier to focus on only the data that was selected for export.

For example, suppose you are exporting a job from your Test environment and importing it into your Production environment. You only want to import new settings for the job, not for its Job Group, Queue, etc. When Don't import referenced objects that already exist on this server is checked, these objects don't appear in the object selection list, so you don't have to worry about importing them accidentally and overwriting the production settings for these objects.

This option is only available if the export was created by adTempus 4.3 or later.

When you export data, adTempus marks in the export file which object(s) were selected in the Export window, and this information is used to filter out objects that were not explicitly selected.

Special Considerations for Server Settings and Security Containers

If you chose to export server settings, the object list may contain the following special items:

• Server Settings: Select this item if you want to import general server options, server-level Job Variables, or audit and snapshot settings. You will be able to choose which of these to import on the Import Options page.
• Security Container: If you exported default security settings for object types, they will be listed here as, for example "Security Container: Default Job Group Security." If you import these items, they will replace the security settings for the corresponding security containers. See the Security Inheritance topic for information about what each of these containers affects.

If you choose any Security Containers, you must also check the Import security settings option on the Import Options page.

Use care when importing Server Settings and Security Containers, as these settings can have far-reaching consequences. You should create a database backup or system snapshot before importing these items.

Next Step

When you have finished making your selections, click Next to continue to the Import Options step.

More About Duplicate Objects

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.