About Publishing Changes

The language import processes and the MLOV Conversion process makes changes to the Design Repository which are not automatically compiled into the Siebel Runtime Repository. The Siebel Runtime Repository requires a record for each language for each object. For example, an Account Form Applet has a record for each language. However, after importing languages, a Runtime Repository record exists only for the original language, typically English, as shown in the following image.

The Runtime Repository before running Full Publish for English and French languages: This image shows only one record.

Note: When the Runtime Repository is in this state, any attempt to login to Siebel CRM application returns a misleading error indicating Incorrect user ID or password. The actual issue is that the Siebel Runtime Repository and Workspace are in an invalid state. As a byproduct of the flattening process, even the base language users are unable to use the Siebel CRM application.

To address this problem and merge the changes and language-specific repository information into the Siebel Runtime Repository, you must perform a Full Publish. You can use the following command from the Siebel Tools bin folder to perform a Full Publish:

siebdev /c tools.cfg /TL {Comma-Separated Language Codes} /d ServerDataSrc /u SADMIN /p ******** /FullPublish

For example, the following command would regenerate the Runtime Repository for all 22 out-of-the-box languages:

siebdev /c tools.cfg /TL ENU,ARA,CHS,CHT,CSY,DAN,DEU,ESN,FIN,FRA,HEB,ITA,JPN,KOR,NLD,PLK,PTB,PTG,RUS,SVE,THA,TRK /d ServerDataSrc /u SADMIN /p ******* /FullPublish

Note: At this time, Full Publish must be run on all desired languages at the same time. Processing occurs in parallel, which requires a lot of memory and requires a large number of database operations. For this reason, it is recommended that this process be run on a machine with a significant (16GB+) amount of memory and that the Full Publish process is run on a server on the same network subnet as the Siebel Database Server.

After the Full Publish process completes, the Siebel Runtime Repository is populated with the records supporting all languages. In the following image, since Full Publish was run for English and French, you can see that there are now entries in the Applet Runtime Repository table for both languages.

The Runtime Repository after running Full Publish for English and French languages: This image shows two records.