About Flattening the Repository
After importing the seed and repository data for each additional language, the language data will exist in the database, but only seed data will be associated with the Workspace – the repository data will not be associated with the Workspace. This is illustrated by comparing ENU records to non-ENU records, as shown in the following tables.
The following table shows the Workspace-specified LOVs for newly imported languages.
|
NAME |
VAL |
LANG_ID |
WS_ID |
|---|---|---|---|
|
Active |
Active |
ENU |
1@1 |
|
Active |
Actif |
FRA |
1@1 |
The following table shows the symbolic string Repository data not specified for newly imported languages.
|
SYM_STR_KEY |
LANG_CD |
STRING_VALUE |
REPOSITORY_ID |
WS_ID |
|---|---|---|---|---|
|
SBL_ACCOUNT- 1004224420-0HD |
ENU |
Account |
1–1–1 |
1@1 |
|
SBL_ACCOUNT- 1004224420-0HD |
FRA |
Compte |
1–1–1 |
In order to set the Workspace Ids on the imported repository objects, you must flatten the repository. You can flatten the repository by running Siebel Tools with an appropriate set of command line parameters. For more information about flattening repositories, see Using Siebel Tools.
To flatten the repository, do the following:
-
In the tools.cfg file, set the following key to the ODBC source of your Siebel database:
[Siebel] ..... ServerDbODBCDataSource = Siebel_DSN ... -
From the command line, change to the Siebel Tools bin folder, and then execute the flatten database process by running Tools with the FlattenWorkspace command line argument:
siebdev.exe /c tools.cfg /u UserID /p Password /d ServerDataSrc /FlattenWorkspace
After completing this process, all repository records for all languages are associated with the base Workspace, as shown by the sample record in the following table:
|
SYM_STR_KEY |
LANG_CD |
STRING_VALUE |
REPOSITORY_ID |
WS_ID |
|---|---|---|---|---|
|
SBL_ACCOUNT- 1004224420-0HD |
ENU |
Account |
1–1–1 |
1@1 |
|
SBL_ACCOUNT- 1004224420-0HD |
FRA |
Comte |
1–1–1 |
1@1 |