Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Repositories > Exporting and Importing Repository Objects >

Importing Object Definitions

---

You can import object definitions from an archive file into a local repository.

The Import process consists of the following major steps (described in the following sections):

Preparing the target repository for import
Loading an archive file into the Import Wizard's preview window, and specifying the default resolution of conflicts between imported and pre-existing object definitions
Adjusting the details of conflict resolution
Importing as specified
Testing and checking in the changed projects

Preparing the Target Repository for Import

You need to import into a checked-out project or projects on the local database of a client computer—do not import to the Server database. Make sure the following conditions exist before importing:

The import file is accessible to the local machine by way of the network or local drives.
The target repository is open in Siebel Tools and is the active repository.
The projects that will be affected by import have been checked out to the local database. This includes any project that any object definition in the export file is assigned to.

The only exception consists of projects (or their object definitions) that are in the archive file, but that do not exist yet in the target repository. These are not checked out because they do not exist in the target repository.

NOTE:  In some cases it may be difficult to know in advance which projects need to be checked out. The Import wizard informs you of any projects that were not locked but need to be. This occurs on the second panel of the Import wizard, after it has analyzed the object definitions in the archive file and compared them to the object definitions in your repository.

Loading Object Definitions from an Archive File Into the Preview Window

You need to load the object definitions from an archive file into preview window to resolve any conflicts between objects.

To load object definitions from an archive file into the preview window

Open the target repository in Siebel Tools, if it is not already open.
Select Tools > Import From Archive.

The Select Archive To Import dialog box appears.

Navigate to the archive (.sif) file in the dialog box and click Open.

The Import Wizard - Preview window appears.

This window identifies the projects and the nonproject top-level object definitions in the archive file you have opened so you can preview the contents of the archive file.

Select a radio button in the Conflict Resolution radio button group.

This specifies the default resolution for conflicts between the archive file and the target repository. You will have the opportunity in subsequent windows in the Import Wizard to change this choice for individual object definitions.

There are three choices available in the Conflict Resolution radio button group, as follows:

Overwrite the object definition in the repository. If the same top-level object definition is found in the archive file and target repository, delete the version in the target repository, along with its children, and replace them with the object definition and children from the archive file.
Merge the object definitions from the archive with the definition in the repository. Merging is the default, and generally the safest option. When the same top-level object definition occurs in both the target repository and the archive file:
Replace differing properties in the target top-level and child-level definitions with those in the file being imported.
Add new child object definitions to the target repository if they are not already present.
Do not change child object definitions in the target repository that are not also present in the archive file.

The resulting top-level object definition has the same properties and children as the object definition in the archive, plus any children that were already present in the repository definition.

Do not import the object definition from the archive. Do not change the object definitions in the target repository.
Validate your selections and click Next to proceed.
If there are object definitions you will be replacing or modifying and whose projects are not locked, the following warning message appears:

If this message appears, you need to cancel the import process, lock the projects, and restart the Import Wizard.

Adjusting the Details of Conflict Resolution

You have made general decisions about conflict resolution in the Conflict Resolution radio button group in the previous window of the Import wizard. In the Review Conflicts and Actions window (shown in Figure 240), you can make adjustments for individual object definitions and properties.

Figure 240. Review Conflicts and Actions Window

The three windowpanes are Conflicting Objects, Object Differences, and Attribute Differences.

Conflicting Objects Windowpane

The Conflicting Objects windowpane displays the hierarchy of object definitions for which there are differences. It is used for navigation and behaves like the Object Explorer in Detail mode. The hierarchy in this windowpane mirrors the object type/object definition hierarchy in a Siebel repository, but shows only conflicts to resolve rather than all repository or archive object definitions.

If you select an object definition in the hierarchy, it and others at its level appear in the Object Differences windowpane.

Object Differences Windowpane

The Object Differences windowpane displays object definitions, one to a row. It shows for each object definition whether it exists only in the archive file, only in the target repository, or in both, and what resolution is specified. You can change the resolution here.

The object definitions displayed in the Object Differences windowpane include those at all hierarchical levels, not just top-level object definitions. This provides the means for making adjustments to the resolution for any affected object definitions.

The File and Repository list columns indicate whether each identified object definition is present in the archive file or target repository. An "X" indicating the object definition's presence can appear in the File list column, the Repository list column, or both. These list columns are for information only; you cannot change the check marks.

The Action list column indicates the proposed resolution for each object definition in the list. This setting is initially generated for each object definition from the default behavior selected in the Conflict Resolution radio button group in the Preview window. You can right-click on the value in the Action list column and select a different value from a shortcut menu. The available selections include the following:

File. Equivalent to the "Overwrite the object definition in the repository" selection in the previous window.
Merge. Equivalent to the "Merge the object definitions from the archive with the definition in the repository" option in the previous window.

The resulting top-level object definition has the same properties and children as the object definition in the archive, plus any children that were present in the repository definition.

Repository. Equivalent to the "Do not import the object definition from the archive" option in the previous window.

For more information about these options, see Loading Object Definitions from an Archive File Into the Preview Window.

Attribute Differences Windowpane

The Attribute Differences windowpane displays the property value conflicts for the currently selected object definition in the Object Differences windowpane. Those properties are listed only where there is a conflict.

The Attribute Differences list contains the following list columns:

Attribute List Column. Name of the property.
File List Column. Value of the property in the archive file version of the object definition.
Repository List Column. Value of the property in the target-repository version of the object definition.
Resolution List Column. Value of either File or Repository for each property, depending on whether the archive-file or target-repository version of the object definition is to determine the value of the property in the final definition.

This list column can be updated only if the object definition whose properties are being displayed has an Action setting of Merge in the Object Differences list. Otherwise, the shortcut menu options are read-only and are grayed out, and the value displayed is the same as that in the Action column of the Object Differences list.

To change the Resolution value from Repository to File or the reverse, right-click on the Attribute row to change and select Repository or File from the shortcut menu.

After you click Next in the Review Conflicts and Actions window, you are shown a summary of your changes and prompted to proceed or cancel, as shown in Figure 241.

Figure 241. Summary Prompt

If you choose to proceed, the Summary window appears, as shown in Figure 242.

Figure 242. Summary Window

Importing occurs while the Summary window is displayed. The import actions are logged and displayed as they occur. When the import process is completed, click Finish.

A log file named importlog.txt is created in Siebdev\temp. It contains the same list of messages that appeared in the Summary window. You may find it useful to store this file elsewhere for a record of what changes were made to the repository. It is also a good idea to change the filename so it reflects the date of the import.

Bookshelf Home | Contents | Index | Search | PDF