Example of Global Deployment with Siebel Anywhere

This topic provides an example of a global deployment using Siebel Anywhere. The objective is to allow users to access and use the same application in different languages.

You have upgrade components for the languages you installed with your database server. You will map these to the applicable configurations. These configurations will be based upon the languages that different sets of users require to access the same application.

Assumptions for Global Deployment Example

This example makes the following assumptions:

• You have five sets of users for five different languages.

• You will base your application on Siebel Call Center.

• You will have five SRF files compiled, one for one each language.

• You will have customer revisions, depending on the language.

• You will use the same database.

• Each user only uses the application in one language.

Requirements for Global Deployment Example

You will need:

• Five components for the CFG files

• Five components for the Siebel Repository Files (SRF)

• Five components for Siebel Client Customer Revisions

• Five configurations to distribute the upgrade kits

• One component for Siebel Client Executables (base), including all applicable languages

Global Deployment Example Records

For the records available, use values similar to those in the tables that follow.

Note: Substitute applicable language codes for ENU in these example records.

Table 7-1 shows example values for defining a Siebel CFG File component.

Table 7-1 Example CFG Record in the Upgrade Component List View

Field Name	Value
Name	Siebel Call Center CFG__ENU
Component Type	Siebel CFG File
Min Version	100
Max Version	Leave this field blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,bin\enu\uagent.cfg
Version Method	CFG
Version Information	Siebel,Version

Table 7-2 shows example values for defining a Siebel Repository File component.

Table 7-2 Example SRF Record in the Upgrade Component List View

Field Name	Value
Name	Siebel Client Repository File__ENU
Component Type	Siebel Repository File
Min Version	Leave this field blank
Max Version	Leave this field blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,objects\enu
Version Method	SRF
Version Information	Siebel,RepositoryFile

Table 7-3 shows example values for defining a Siebel Client Customer Revisions component.

Table 7-3 Example Siebel Client Customer Revisions Records in the Upgrade Component List View

Field Name	Value
Name	Siebel Client Customer Revisions Siebel Client Customer Revisions__ENU
Component Type	Customer Revision
Min Version	Leave this field blank
Max Version	Leave this field blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,bin\clntrev.cfg Siebel,ClientRootDir,bin\enu\clntenu.cfg
Version Method	CFG
Version Information	Siebel,Version

Table 7-4 shows example values for defining a Siebel Client Configuration component.

Table 7-4 Example Client Configuration Record in the Upgrade Configurations View

Field Name	Value / Comments
Name	Siebel Call Center ENU
Configuration Type	Siebel Client Configuration
In the related components applet, make sure that the following components are included (assuming that you want to distribute all of these components):	In the related components applet, make sure that the following components are included (assuming that you want to distribute all of these components):
Siebel Call Center CFG__ENU	Required
Siebel Client Customer Revisions	Required
Siebel Client Customer Revisions__ENU	Required
Siebel Client Executables	Required
Siebel Quick Fix	Required
Siebel Client Executables__ENU	Required for language-specific files using delta patch upgrade kits
Siebel Client Repository File__ENU	Required
Siebel Database Schema	Required
Siebel Upgrade Wizard	Required
Third Party - File Attachment	Not required

Note: If you will be creating and distributing language-specific files using delta patch upgrade kits, then you must create a configuration for each language combination. For example, if a user installed both U.S. English (ENU) and French (FRA) on a system, then create a configuration with the components related to these two languages. For more information about multilingual deployments, see Siebel Global Deployment Guide.