Bookshelf Home | Contents | Index | Search | PDF

Siebel Anywhere Administration Guide > Supplementary Information for Specific Upgrade Types >

Example of Updating Specific Lines in the CFG File

---

This topic gives one example of updating specific lines in a CFG file. It is recommended that you have uniform client installations across a Siebel deployment. But if for some reason, some of your Siebel clients use different installation directories than others, the traditional CFG Upgrade Kit will not work for every client in the deployment. The reason for this failure is that certain parameters (for example, ClientRootDir) in a CFG file are directly tied to the installation directory.

To address this issue in Siebel 7, Siebel Systems has provided a stand-alone executable (cfgedit.exe) that is capable of modifying specific lines in a CFG file.

The cfgedit.exe executable compares a new CFG file that you supply (called the source CFG file) with a subscriber's CFG file (called the destination CFG file). If there are differences, cfgedit.exe updates the destination CFG file as needed to match the contents of the source CFG file. In the following example, the source CFG file is source.cfg, and the destination CFG file is uagent.cfg. Table 34 shows the arguments for cfgedit.exe.

Table 34.  Arguments for Cfgedit.exe

Argument	Comment
/S source_CFG_file	Required. The CFG file containing the setting changes that you want to distribute to clients.
/D destination_CFG_file	Required. The subscriber CFG file that you want to update.
/C	Create destination file if it does not already exists. (By default, cfgedit.exe does not create the destination file.)

CAUTION:  Make sure that your source CFG file assigns a value for every listed setting (key). If the source CFG file contains "empty keys," such as "Vertical = [blank]," the formatting of the destination CFG file may be altered in such a way that the file becomes unusable.

It is recommended that you use a kit of the type Customer Revisions to deliver and execute cfgedit.exe. You may create a separate Upgrade Component of the type Customer Revisions to keep track of the CFG version history as well.

The following procedure provides an example of how to update a specific line in a CFG file. In this example you use cfgedit.exe to modify a specific line in the client's ENU uagent.cfg.

To update specific lines in the CFG file

From the application-level menu, select View > Site Map > Siebel Anywhere Administration.
From the Show drop-down list, select Upgrade Kits.

The Upgrade Kits view appears.

Click Auto Create to invoke the Upgrade Kit Wizard.

The Upgrade Kit Wizard - Upgrade Component page appears.

Follow the prompts to specify all necessary information to define your upgrade kit. Use the following on the appropriate pages:
For Siebel Component Type, pick Customer Revisions.

NOTE:  To keep track of the changes to specific configuration files, it is recommended that you create a new upgrade component, such as Client Customer Revision-CallCenterCFG_ENU.

Add cfgedit.exe and source.cfg files to the kit.

Sample file for source.cfg:

[Siebel]
ComponentName= New Component Name
[New Section]
NewKey = New Value

Change the Destination Directory from the default to $SiebelRoot\bin\
Select to execute, cfgedit.exe
For command line arguments, enter the following:

/s source.cfg /d "$SiebelRoot\bin\enu\uagent.cfg"

For more information about version information, see How Siebel Anywhere Versions Work and Determining Version Setting Values.
Activate, apply, and distribute the upgrade kit you built in the previous step.

Bookshelf Home | Contents | Index | Search | PDF