Bookshelf v7.5: Example of Global Deployment with Siebel Anywhere

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

Example of Global Deployment with Siebel Anywhere

This section 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 (reports for example) 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 Siebel Repository Files (SRF)

Five components for the CFG files

Five components for Client Customer Revisions

Five configurations to distribute the upgrade kits

Six components for Client Executables—one for Client Executables (base), and five for Client Executables_$Language (language pack)

The language pack component has same locate method, locate information, and version method as the base Client Executables component, but with different Version Information: bin\sslcver.dll,VersionString,$Language

Global Deployment Example Records

For the records available, use the values in Table 29, Table 30, Table 31, and Table 32.

NOTE: Other language codes can be substituted for ENU in these example records.

Table 29. Example CFG Record in the Upgrade Components View Files
Field	Comment
Name	CFG ENU
Component Type	Siebel CFG File
Min Version	100
Max Version	Should be blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,bin\$Language\uagent.cfg
Version Method	CFG
Version Information	Siebel,Version

Table 30. Example SRF Record in the Upgrade Components View
Field	Comment
Name	Siebel Client SRF ENU
Component Type	Siebel Repository File
Min Version	Should be blank
Max Version	Should be blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,objects\$Language
Version Method	SRF
Version Information	Siebel,RepositoryFile

Table 31. Example Client Customer Revision Record in the Upgrade Components View
Field	Entry
Name	Customer Revision ENU
Component Type	Customer Revision
Min Version	Should be blank
Max Version	Should be blank
Locate Method	CFG
Locate Information	Siebel,ClientRootDir,bin\clntrev.cfg
Locate Information - language dependent component	Siebel,ClientRootDir,bin\$Language\clntrev.cfg
Version Method	CFG
Version Information	Siebel,Version

Table 32. Example Client Configuration Record in the Siebel Anywhere Configurations View
Field	Comment
Name	Siebel Call Center ENU
Configuration Type	Siebel Client Configuration
In the related components applet, make sure that the following components are included:
Siebel Call Center CFG_ENU	Required
Siebel Client Customer Revisions	Required
Siebel Client Customer Revisions_ENU	Required
Siebel Client Executables	Required
Siebel Client Executables_ENU	Required
Siebel Client Repository File_ENU	Required
Siebel Database Schema	Required
Siebel Upgrade Wizard	Required
Third Party - File Attachment	Not Required

NOTE: You must create a configuration for each language combination. For example, if a user installed both English (ENU) and French (FRA) on a system, create a configuration with the components related to these two languages. For more information regarding multilingual deployments, see Global Deployment Guide.