4Configuring Global Deployments
Configuring Global Deployments
This chapter discusses how to configure your Siebel CRM applications for a global deployment. It includes the following topics:
About Parameters for Language and Locale
This topic describes the parameters that can be set on the Application Object Manager in order to specify language, resource language, and locale. On the Siebel Mobile Web Client, equivalent parameters are defined in application configuration files (such as uagent.cfg for Siebel Call Center).
The active language for Siebel CRM is the language in effect for an individual user’s session and the language of user interface elements, including multilingual lists of values (MLOVs) that have been enabled. The active language is determined by the setting of the Language Code parameter for the Application Object Manager component to which a Siebel Web Client is connected. The same language is also used for logging and other system messages, unless the resource language is also defined. See also Language.
This topic contains the following information:
Language Code Parameter
This topic is part of About Parameters for Language and Locale.
The Language Code parameter (alias Lang) determines the language used for multilingual lists of values (MLOVs) and other application seed data. This parameter also determines which language-specific directory from the product installation will be used for accessing the Siebel runtime repository. The language of application user interface labels is determined by the language for the Siebel runtime repository. This language was determined by the Siebel Tools or Siebel Web Tools language mode in effect when the Siebel runtime repository was published.
For each language that you install and deploy, Application Object Manager components are created which are already configured with Language Code set to this language. In general, you do not need to change the value of the Language Code parameter for these components.
Special requirements apply when you localize an unshipped language, as noted in Localizing an Unshipped Language.
Unless the OM - Resource Language Code parameter is set to a different language, the Language Code parameter determines which language-specific directories will be used during runtime operation for resource libraries such as DLL files. These resource libraries determine the language in which system and error messages are displayed and the language in which server log file messages are written.
Each language code used by Siebel CRM uses a three-letter code, such as ENU for U.S. English, FRA for French, THA for Thai, and so on. For more information about the language codes used by Siebel CRM, see Language.
The setting of the Preferred Language field for a user or employee record overrides the value of the Language Code parameter for determining the language for multilingual lists of values (MLOVs). This setting is stored in the PREF_LANG_ID column in the S_CONTACT table in the Siebel database. This field does not affect Siebel Mobile Web Client or Developer Web Client users.
See also Localizing Lists of Values and Multilingual Lists of Values.
See also OM - Resource Language Code Parameter.
For more information about the effect of the language mode in Siebel Tools or Siebel Web Tools and about how to set it, see Using Siebel Tools. See also Language.
OM - Resource Language Code Parameter
This topic is part of About Parameters for Language and Locale.
The OM - Resource Language Code parameter (alias ResourceLanguage) can optionally be set to a different language than the Language Code parameter in order to specify the resource language.
The resource language determines which language-specific directories from the product installation will be used during runtime operation for resource libraries such as DLL files. These resource libraries determine the language in which system and error messages are displayed and the language in which server log file messages are written.
Resource library files are provided for all of the languages shipped with Siebel CRM. These files cannot be localized into any other unshipped languages.
For some multilingual deployments, it might be useful, or necessary, to set the resource language to a different value than the Language Code parameter. For example, you might want all of the global users to view MLOV and other seed data in the language determined by Language Code. However, you might choose to set the resource language to a single language familiar to your administrators.
Where Language Code is set to an unshipped language, you must use the resource libraries for a language provided for Siebel CRM. In this case, you can set OM - Resource Language Code to specify which language’s resource libraries to use. For example, where Language Code is set to the unshipped language NOR (Norwegian), you might set OM - Resource Language to DEU (German). For details, see Localizing an Unshipped Language.
See also Language Code Parameter.
Locale Code Parameter
This topic is part of About Parameters for Language and Locale.
The Locale Code parameter (alias LocaleCode) specifies the locale associated with this Application Object Manager component. This setting is used by the Siebel Web Clients for this Application Object Manager.
The Locale Code setting is a three-letter locale code. A locale is a set of rules guiding how common data is displayed to the user or is received from the user. Siebel CRM supports formatting of data, such as dates, time, numbers, and currency, based on locale settings.
Locales are administered using the Locale Administration view. For each language-specific Application Object Manager component on a Siebel Server, the Locale Code is set to a locale that might be appropriate for users for that language.
If you need to support multiple locales for the same language, then you can use either of the following approaches to deploy your Application Object Managers:
On different servers, configure and run different locale-specific Application Object Managers for this language on different Siebel Servers. For example, an FRA Application Object Manager would be running in France with a French locale, while another FRA Application Object Manager would be running in Canada with a French Canadian locale.
On the same server, create, configure and run different Application Object Managers that are specific to both this language and a particular locale. For example, a FRA Application Object Manager running in France would have a French locale, but you could create another FRA Application Object Manager on the same Siebel Server in France that has a French Canadian locale. For more information about creating and configuring Application Object Managers, see Siebel System Administration Guide.
If the Locale Code parameter is not set, then the Application Object Manager and the Siebel Web Clients use the locale defined in the operating system on the computer or operating system instance where you installed Siebel Server. On Microsoft Windows, this setting is defined in Regional and Language Options in the Control Panel. On UNIX, you set locales as described in Siebel Installation Guide for UNIX.
On the Siebel Mobile Web Client or Developer Web Client on Microsoft Windows, the locale is determined by the settings defined in Regional and Language Options in the Control Panel.
Additional Information About Setting Up and Administering Locales
During installation, you need to set locales for your Siebel Web Clients, Siebel Servers, and database. After installation, you can modify the Siebel Server locale or add additional locales. The following table shows where you can find detailed information about performing these procedures.
| For information about ... | See ... |
|---|---|
Administering Siebel Server locales |
Siebel Applications Administration Guide |
Setting Siebel Server locales |
Siebel Installation Guide for the operating system you are using |
Setting Siebel Mobile Web Client and Developer Web Client locales |
On a Windows PC, locales are administered through settings in Regional and Language Options in the Control Panel |
Language Settings for Siebel Mobile Web Client
This topic is part of About Parameters for Language and Locale.
The active language for a user session in the Siebel Mobile Web Client is determined by the Language parameter setting in the application configuration file. There are different configuration files for each language. They are located in a language-specific directory and have the Language parameter set appropriately.
For example, language-specific directories for the current version might include:
C:\Siebel\Client\bin\deu\uagent.cfg(configuration file for Siebel Call Center with Language parameter set to DEU, for German)C:\Siebel\Client\bin\enu\uagent.cfg(configuration file for Siebel Call Center with Language parameter set to ENU, for U.S. English)
Do not modify the Language parameter to change the active language. Instead, the user specifies the appropriate application configuration file for the language in which to run, by using the /c switch in the command line of the siebel.exe application shortcut.
For example, for running Siebel Call Center in German for the current version, the Siebel application shortcut created during installation with the DEU language has a property similar to this:
/c C:\Siebel\Client\bin\DEU\uagent.cfg
Related Books
Siebel Installation Guide for the operating system you are using
Siebel Remote and Replication Manager Administration Guide
About Configuring Language Support for Browser Platforms
A browser platform can include the following:
The Web browser itself
The operating system where the Web browser runs
For the browser standards supported by Siebel Open UI, for particular browser versions that are certified as supporting those standards, and for support information for Siebel CRM in general, see the Certifications tab on My Oracle Support.
For more information about requirements for the Siebel Open UI client, see Deploying Siebel Open UI. See also Siebel Installation Guide for the operating system you are using and other applicable documentation.
The client computer might not include all of the fonts and other resources necessary to display all of the Unicode characters that are outside the default non-Unicode code page. Some manual setup might be required in order to view all of the characters correctly in Web pages, including Siebel application screens.
If characters from some languages appear as hollow or solid boxes, then it might be due to lack of language setup in the browser. Box characters always indicate a problem at the user interface level. Question marks appear when Unicode characters are mishandled on the server or in third-party applications. They can also be due to the character set having been incorrectly configured in the database.
Vendor documentation and support should be definitive on these issues, but the following list provides a starting point for resolving issues. Web browsers display text in several contexts, including:
HTML body text (most of the text in Siebel client screens)
HTML field input (all of the text input in Siebel client screens)
ToolTips
Message boxes (alerts)
Related Books
Deploying Siebel Open UI
Configuring Siebel Open UI
Siebel Installation Guide for the operating system you are using
Siebel System Administration Guide
About Unicode Fonts
This topic is part of About Configuring Language Support for Browser Platforms.
This guide sometimes mentions Unicode fonts. This term refers to a font that contains glyphs for most, if not all, of the possible characters in Unicode. Such fonts might not be shipped as standard parts of the operating system. Customers must license them or otherwise obtain them for installation on their client computers.
A commonly used font of this type is Arial Unicode MS, which comes with every installation of Microsoft Office. The version of this font provided with Microsoft Office 2003 and later is compatible with Unicode 2.1, though it does not contain glyphs for all of the Unicode characters.
See also Configuring Cascading Style Sheets to Specify Different Fonts.
About Integration Considerations
There are many issues to consider when planning application integration for a global deployment of Siebel CRM. This topic contains the following information:
For detailed information about application integration for global deployments, see Overview: Siebel Enterprise Application Integration, documentation for Siebel Enterprise Application Integration (Siebel EAI), and documentation for specific integration products.
For a list of the languages supported by Siebel CRM, and the supported code pages for each database, see 1513102.1 (Article ID) on My Oracle Support.
About Character Conversion Errors
This topic is part of About Integration Considerations.
When the Siebel application sends data to an external application using a non-Unicode (traditional) character set encoding, the external application might not be able to accept all of the data if the data does not belong to the character set encoding of the application. In this situation, unrepresentable characters will be converted to a substitution character.
The substitution character might be a question mark or an upside-down question mark (indicating character loss in the database), depending on the database. A conversion result like this is referred to as unrepresentable character conversion.
The topic About the Transcode Service Business Service describes how to avoid this situation, using techniques for character conversion error handling.
The transport and adapter business services have two character conversion error handling modes:
Generate an error without sending the message
Ignore the error, substitute replacement characters wherever possible, and send the message
These error handling modes are specified in an argument to the business service call.
A second case occurs when you are using a Unicode communication stream, such as XML, to communicate between Siebel CRM and an external, non-Unicode application. In this situation, the character conversion can be handled by the external application after it receives the message. This situation presents the risk that conversion errors might occur and that the external application might not provide the desired error handling functionality.
To avoid problems associated with relying on third-party applications to convert data, you can use the Validate method of the Transcode Service business service, before sending any data to the external application. This method detects whether character conversion performed by the external application will fail. If it will fail, then you can choose not to send the data. For details, see About the Transcode Service Business Service.
About the Transcode Service Business Service
This topic is part of About Integration Considerations.
To supplement the character conversion performed by Siebel EAI components, Siebel CRM offers the Transcode Service business service. You can use methods of this business service in your workflow processes to validate and convert data from one character set encoding to another.
For information about how business services handle character conversion errors, see About Character Conversion Errors. For the language-independent code values that you can specify in business service method arguments for the source or target encoding, see 1513102.1 (Article ID) on My Oracle Support.
The Transcode Service business service supports two methods:
Validate. This method confirms the input property set hierarchy or the value of the input property set. You can use this method to check that a character is valid within a particular character set before proceeding, without actually performing the conversion. The arguments for the Validate method are described in the following table.
Method Argument Required Description ValidationMode
Yes
If set to value, then only the value is validated. Otherwise, the properties are validated for the entire hierarchy.
TargetEncoding
Yes
Specify the language-independent code for the target encoding.
SourceEncoding
No
Specify the language-independent code for the source encoding.
This argument is required when ValidationMode is set to value and the input value contains binary data. Conversion from binary data in SourceEncoding to binary data in TargetEncoding is implied.
Convert. This method converts the value in the input property set to the target encoding in the output. You use this method when data is entering or leaving Siebel applications, and a conversion is required now, so that the next software component in the processing chain can recognize the data. The arguments for the Convert method are described in the following table.
Note: To ignore character conversion errors (that is, invalid character errors or substitution errors) for the Convert method, specify IgnoreConversionErrors = True as a method argument. Otherwise, do not use this argument. (This argument is hidden in Siebel Tools or Siebel Web Tools.)Method Argument Required Description ConversionMode
Yes
Values can be StringToEncoding, EncodingToString, or EncodingToEncoding.
TargetEncoding
Yes
Specify the language-independent code for the target encoding.
Required for StringToEncoding and EncodingToEncoding modes.
SourceEncoding
No
Specify the language-independent code for the source encoding.
Required for EncodingToString and EncodingToEncoding modes.
Note: The Convert method converts the actual encoding of a file, including XML files. However, this method does not change the encoding attribute in the file’s XML header. For example, if you change an XML file’s encoding from UTF-8 to UTF-16, then the XML header still refers to UTF-8, such as in this example:<?xml version="1.0" encoding="UTF-8"?>. To make the encoding attribute match the XML file’s actual encoding, edit the file in a separate step.
About Application-Wide Data
This topic describes some of the types of application-wide data that need to be considered for global deployments of Siebel CRM. Many of these types of data provide multilingual support in the standard product; additional examples include product catalogs, task-based UI, and time zone translations.
Sales Cycles
Sales cycle stages can be localized into different languages by configuring them according the global data approach described in Setting Up Global Data. For more information, see 477104.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 438.
Currency
Make sure that your Siebel CRM applications use the appropriate currency for your users. For information about currency administration, including exchange rates and currency conversion, see Siebel Applications Administration Guide.
Telephone Numbers
You will need to specify telephone number formats for the countries in which you will be deploying the Siebel CRM applications. For information about how to perform this procedure, see Siebel Applications Administration Guide.
Templates
There are many templates to consider when planning a global deployment. They include:
Proposals
Presentations
Email
Fax
Correspondence
For more information about templates for email or fax, see Siebel Email Administration Guide. Each correspondence template is in a specific language. These templates have been localized. For information about creating new correspondence templates, in any language, see Siebel Correspondence, Proposals, and Presentations Guide. Each user can specify a default correspondence template; users can choose the appropriate template for their locale.
Literature
The items that are included in the Literature tab can be in any language. For information about adding items to the Literature tab, see Siebel Applications Administration Guide.
iHelp
iHelp is a language-independent feature, which means that:
The same iHelp can run in multiple languages.
The same logic can be used, but with a localized message displayed.
The language is determined by the current application language.
For more information about creating or administering iHelp, see Siebel Applications Administration Guide.
Siebel SmartScript
Siebel SmartScript is a language-independent module, which means that:
The same SmartScript can run in multiple languages.
The same logic can be used, but with a localized message displayed.
The language can be manually selected or set automatically when a script is started.
For more information about SmartScript, see Siebel SmartScript Administration Guide.
Setting Up Global Data
Global data is master data that is configured to display in the current application language. For example, a Siebel Call Center user accessing an FRA application would see data in French, while another user accessing a DEU application would see the same data in German.
To set up global data for your global deployment, follow steps similar to those in the example tasks in this topic.
Example for Enabling Global Data
The following sample task describes how to use the Opportunity Product business component to enable the Product Description field as global data.
To enable global data (example)
In Siebel Tools or Siebel Web Tools, check out and lock the Opportunity Product project.
In the Object Explorer, navigate to Business Component.
In the Name field, perform a query for Opportunity Product.
In the Object Explorer, navigate to Join and add the following record:
Field Value Table
S_PROD_INT_LANG
Alias
S_PROD_INT_LANG
Outer Join
Yes
In the Object Explorer, select Join, then Join Specification, and add the following record:
Field Value Name
Translate
Destination Column
PAR_ROW_ID
Source Field
Product Id
In the Object Explorer, select Join, then Join Constraint, and add the following record:
Field Value Name
Language
Destination Column
LANG_ID
Value
One of the following values:
Language() corresponds to the value of the Language Code parameter.
LOVLanguage() is the language currently used for LOVs. It might correspond to the value of the Language Code parameter or to the Preferred Language setting for the current user.
Note: LOVLanguage() is designed to work with the multilingual outbound communication functionality. Language() does not work with this functionality.In the Object Explorer, navigate to Field.
In the Name field, perform a query for Product Description.
Change the Join to S_PROD_INT_LANG and the Column mapping to DESC_TEXT.
Translating Globally Enabled Fields
The following sample task describes how to translate a globally enabled field, using the Product Description field from the preceding sample procedure as an example.
To translate a globally enabled field
Expose the view that contains the field that you want to translate.
Note: In the example provided previously in this topic, the view would already be exposed, because Products is an object that is global-data ready.Navigate to the Administration - Product screen, then the Products view.
In the Products list, select a product that you want to translate.
In the More Info form, on the link bar, click Translations.
Enter the translated names and language codes for the product.
Configuring the Siebel Calendar
Calendar applets can be configured to respect the standard calendar layouts for many locales. This includes specifying the first day of the week shown in the first column of a weekly or monthly view and the workdays shown on a 5-Day calendar view. These settings can be populated by the Siebel administrator for each locale as explained in the section on customizing calendars in Configuring Siebel Open UI. The Calendar screen in your Siebel applications can be configured to support the requirements of users based in different locales in a global deployment.
Related Books
Siebel Applications Administration Guide
Using Siebel Tools
Configuring Siebel Business Applications
Configuring Siebel Open UI
Configuring Cascading Style Sheets to Specify Different Fonts
To successfully run Siebel CRM applications, your cascading style sheet files (CSS files) for Siebel applications must specify fonts that are available on your systems and that support the languages and locales in which you will run the applications.
By default, the style sheets specify fonts for Windows platforms only. The specified fonts are not Unicode fonts, and might not support the character sets that you require for all of the languages that you deploy. (The term Unicode font is used here loosely to refer to any font that contains a wide range of the characters required to support the many languages included in the Unicode standard.)
You can use utilities on your client systems, such as the Character Map utility on Windows, to determine which characters are available in any installed font.
For some example font settings that might be suitable on different operating system platforms for supported languages or locales, see the second table in this topic.
Some scenarios in which you might need to modify font specifications in your cascading style sheets include the following:
If your database uses Unicode, and some users need to be able to view data using multiple languages, then the cascading style sheets applicable to these users might need to be modified to specify Unicode fonts.
For example, if U.S. English (ENU) users need to view data using Japanese (JPN) characters, then Unicode fonts would be required for the ENU users, such as to change from Arial to Arial Unicode MS. If the JPN users do not require viewing data in other languages, then a Shift-JIS font could be specified for these users, because the display characteristics might be more suitable.
Note: Style sheet files can include font names that contain non-ASCII characters only if the file is saved using UTF-8 encoding.If you are deploying your Siebel applications with any language that is not supported by the default fonts specified in the cascading style sheets, then the style sheets applicable to users for this language must be modified to specify a suitable font. See example fonts listed in the second table in this topic.
Your style sheets must specify fonts that are available on the client computers and browsers where users run the Siebel applications. See example fonts listed in the second table in this topic.
You might also need to specify different fonts in order to display special symbols such as mathematical symbols, to change the font to suit your company’s design standards, and so on. (These scenarios are not specifically related to deploying languages.)
You might need to modify multiple cascading style sheet files, depending on which Siebel products and features you are deploying.
Cascading style sheet files and other types of files, such as image files, are stored in the Siebel Application Interface installation. See Siebel Installation Guide for the operating system you are using.
For more information about modifying cascading style sheets, see Configuring Siebel Business Applications, Siebel Developer's Reference, and Configuring Siebel Open UI. See also 477498.1 (Article ID) on My Oracle Support. This document was previously published as Siebel FAQ 2104.
The following table lists some example font settings that might be suitable on different operating system platforms for installations supporting multiple languages or locales. These are Unicode-enabled fonts. Other suitable fonts might be available from font vendors. See also About Unicode Fonts.
| Windows Font Names | UNIX Font Names | |||
|---|---|---|---|---|
| Windows | AIX | HP-UX | Linux | Solaris |
Arial Unicode MS (usually available only to licensed users of Microsoft Office) Oracle Albany |
IBM Thorndale Worldtype (X11.fnt.ucs.ttf) Oracle Albany |
Worldtype (X11.fnt.ucs.ttf) Oracle Albany |
Oracle Albany |
Worldtype (X11.fnt.ucs.ttf) Oracle Albany |
The following table lists some example font settings that might be suitable on different operating system platforms for installations supporting a single language or locale. Where applicable, Unicode-enabled fonts such as those listed in the first table in this topic might be deployed instead. Other suitable fonts might be available from font vendors.
| Language or Locale | Siebel Language Code | Windows Font Names | UNIX Font Names | |||
|---|---|---|---|---|---|---|
| Windows | AIX | HP-UX | Linux | Solaris | ||
Arabic (Saudi Arabia) |
ARA |
Arial |
Times New Roman WT J |
Naskh |
ClearlyU Arabic Extra |
Naskh MT |
Chinese (Simplified) |
CHS |
SimSun |
Times New Roman WT J |
Zycjksun |
ClearlyU |
Zycjksun |
Chinese (Traditional) |
CHT |
MingLiu |
Times New Roman WT J |
ARMingtiL |
ClearlyU |
Zycjksun |
Czech |
CSY |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Danish |
DAN |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Dutch |
NLD |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
English (United States) |
ENU |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Finnish |
FIN |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
French (France) |
FRA |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
German (Germany) |
DEU |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Hebrew |
HEB |
Arial |
Times New Roman WT J |
Arial |
ClearlyU |
Arial |
Italian |
ITA |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Japanese |
JPN |
MS PGothic |
Times New Roman WT J |
(Font name uses Japanese characters) |
ClearlyU |
(Font name uses Japanese characters) |
Korean |
KOR |
MS Gulim |
Times New Roman WT J |
Hybatang |
ClearlyU |
Gothic |
Polish |
PLK |
Arial |
Not available |
Not available |
Not available |
Not available |
Portuguese (Brazil) |
PTB |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Portuguese (Portugal) |
PTG |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Russian |
RUS |
Arial |
Not available |
Not available |
Not available |
Not available |
Spanish (Modern) |
ESN |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Swedish |
SVE |
Arial |
Times New Roman WT J |
Arial |
Luxi Serif |
Arial |
Thai |
THA |
Tahoma |
Times New Roman WT J |
Angsana |
ClearlyU |
AngsanaUPC |
Turkish |
TRK |
Arial |
Arial |
Arial |
XFree86-ISO8859-9-75dpi-fonts |
Arial |
Verifying Bidirectional Capability
Siebel applications display a left-to-right or right-to-left user interface, according to the current language and locale. For example, Siebel CRM applications display from right-to-left for Arabic (ARA) or Hebrew (HEB).
Framesets in Siebel Web templates, as used by the Siebel Web Engine, automatically reflect the UI directionality (either left-to-right or right-to-left) defined for the current locale.
Verifying UI Directionality Settings for Arabic or Hebrew
User interface elements display from right-to-left for Arabic or Hebrew. It is recommended to verify that UI directionality is set to Right To Left for the Arabic and Hebrew locales.
For the Siebel Web Client, the UI directionality setting is already correctly defined by default as Right To Left for the Arabic and Hebrew locales, as shown in the Locales view, which is part of the Administration - Data screen. Do not modify this setting.
For Siebel Mobile Web Clients and Developer Web Clients, verify the following setting in the Arabic or Hebrew application configuration (CFG) file for your Siebel application, such as uagent.cfg for Siebel Call Center:
[InfraObjMgr] UIDirectionality = RTL
Modifying Fonts in Cascading Style Sheets
Depending on which fonts are available on your client computers, you might need to modify cascading style sheets (CSS files) to specify different fonts for use with your language. For more information, see Configuring Cascading Style Sheets to Specify Different Fonts.
Creating Language-Specific Object Manager Components
If you are implementing a language that shipped after the initial product rollout (this scenario might not apply), then see Scenarios for Installing and Deploying Siebel Languages. See also the details for the scenario for installing and deploying additional languages in an existing deployment, which are located in the Siebel Installation Guide for the operating system you are using.
Configuring Case Insensitivity
You can create indexes that directly support case-insensitive queries on eligible text columns. Such queries might be particularly useful for multilingual deployments.
The Case Insensitivity Wizard configures specified columns for case-insensitive queries by defining case-insensitive columns and indexes in the repository. The wizard also sets the Default Insensitivity property for these columns to DB Case & Accent.
The exact steps and requirements for configuring case and accent insensitivity might differ for new install scenarios and upgrade scenarios.
For detailed information about running the Case Insensitivity Wizard to configure case-insensitive queries for specified columns, see applicable background and task topics in the following documents on Siebel Bookshelf:
Configuring Siebel Business Applications
Siebel Database Upgrade Guide
Siebel Performance Tuning Guide