Using Siebel Tools > Archiving Objects >

Overview of Archiving Objects

Archiving is a process where you export objects from the repository to an archive file. You can then import objects from the archive file back into the repository. You can use an archive to back up sets of objects or move them to another environment that shares the same physical database schema as the source environment. Note the following:

• An archive does not depend on a database because it only includes repository information. You can use it to exchange repository data between environments with different database platforms, including local and server databases, as long as these databases use the same schema.
• If you import objects from an archive, then you can specify conflict resolution rules for each object. You can configure Siebel Tools to ignore an imported object, replace an existing object with an imported object, or merge two objects according to object properties.
• You can archive individual objects or entire projects to an archive.
• You can use code control software to control an archive. For more information, see Configuring Third-Party Code Control.
• If you must back up or move the entire repository to another environment, then see Exporting and Importing a Repository.

Using Export and Import for Different Versions of Siebel CRM

If you export objects from one version of Siebel CRM to another version, then do not import these objects through .sif files into a different version of Siebel CRM because Siebel CRM might modify object definitions between these versions. If you import an object that is not valid, then an invalid configuration might result. Oracle does not support an invalid configuration.

Where Siebel Tools Stores Archive Files

The Temp parameter in the Siebel section of the tools.cfg file identifies the directory where Siebel Tools stores the following items:

• Archive files
• Projects and objects that you check out or check in

Siebel Tools sets this Temp parameter to the client_root\TEMP directory of your Siebel Tools installation directory, by default. For more information, see About the Configuration Files.

Example of an Archive File

Siebel Tools writes SIF files in XML format. It uses the following hierarchy and it includes property values and scripts:

1. Repository
2. Project
3. Object
4. Child Objects

The following code is part of a SIF file created by adding objects to a hotfix. For more information, see Using a Hotfix to Deploy Fixes to the Production Environment:

<REPOSITORY
NAME="Siebel Repository"
... >
<PROJECT
...
NAME="Account (SSE)"... >
<APPLET
ASSOCIATE_APPLET="Account Assoc Applet"
BUSINESS_COMPONENT="Account"
CLASS="CSSFrameListBase"
...
NAME="Account List Applet"
... >
<APPLET_METHOD_MENU_ITEM... >
</APPLET_METHOD_MENU_ITEM>...
</APPLET>
<BUSINESS_COMPONENT
CACHE_DATA="N"
CLASS="CSSBusComp"
... >
</BUSINESS_COMPONENT>
...
</PROJECT>
</REPOSITORY>

How Siebel Tools Minimizes the Data it Processes during Exports and Imports

You can use Siebel Tools to create a Siebel Delta File (SDF), which is a type of file that is similar to an SIF file except that an SIF file contains the entire definition of an object while the SDF file contains only information about modifications to an object. The SDF file contains enough information about the object hierarchy so that it can get the information that Siebel CRM modified.

For example, assume you modify the contents of a comment field in the Contact business component. Assume you use one of the following file types to move this modification from a source environment to a destination environment:

• SIF file. Siebel CRM exports the entire Contact business component into a SIF file, and then imports this file into the destination environment. It must compare each part of data in the SIF file with the counterpart data in the repository that resides in the destination environment.
• SDF File. Siebel CRM exports only the contents of the comment field. It does not export the entire Contact business component. This export is similar to the export that Siebel Tools does with an SIF file except that Siebel Tools does the export according to the object tag or object tag and time. For more information about object tags, see Managing Modifications That Multiple Developers Make.

For more information about using SDF files, see Exporting Modified Objects and Importing Modified Objects.