Executing the Full Publish Process

Before running the Full Publish process, as described in the following procedure, note the following about the Full Publish process:

The Full Publish process must be performed only in Siebel Tools; it cannot be performed in Web Tools.
Not all repository objects are runtime-enabled; only the repository objects that can be compiled are runtime-enabled.
The only time that you need to manually run Full Publish is after a flattening Workspace operation - running Full Publish is not required at any other time. For more information on how to flatten a Workspace, see Flattening Workspace Versions.
After running Full Publish, it will not be possible to run incremental migration to any downstream Runtime Repository environment until a Full Migration has been executed to that environment.

To run the Full Publish process

Open the Command Prompt window on your machine by clicking Start and selecting the Run option.
In the Run window, enter the value CMD in the Open field.
At the Command Prompt, run the Full Publish process as follows:
```
siebdev /c tools.cfg /TL <lang_code> /d <dataSource_name> /u <username> 
/p <password> /FullPublish 
```
- The following example command runs FullPublish in the database with one language, English (ENU):
```
siebdev /c tools.cfg /TL ENU /d ServerDataSrc /u sadmin /p ******** /FullPublish
```
  Notice that the /d parameter in this example refers to the datasource defined in the tools.cfg file.
  
  Note also that the <lang_code> parameter can either be a single language or multiple languages. You must specify the language that needs to be published in the /TL parameter. For more information about Runtime Repository business components that are language independent, review the information in the following table.
- The following example command runs FullPublish in the database with one language, German (DEU):
```
siebdev /c tools.cfg /TL DEU /d ServerDataSrc /u sadmin /p ******** /FullPublish
```
- The following example command runs FullPublish in the database with three languages: English (ENU), German (DEU), and Japanese (JPN):
```
siebdev /c tools.cfg /TL ENU,DEU,JPN /d ServerDataSrc /u SADMIN /p ******** /FullPublish
```

After the Full Publish process completes successfully, you can launch the Siebel application only in those languages that have the application strings and languages that are specified in the Full Publish process. In case you need to launch the Siebel application in any additional language, run Full Publish again by specifying those languages.

In the last example, Siebel application is already published in ENU, DEU, and JPN. However, if their is a requirement for FRA (French), then you need to run Full Publish again specifying all the required languages:

siebdev.exe /c tools.cfg /TL ENU,DEU,JPN,FRA /d ServerDataSrc /u sadmin /p ******** /FullPublish

If you need to drop a language, then repeat the Full Publish process. For example, you can remove JPN as follows:

siebdev.exe /c tools.cfg /TL ENU,DEU,FRA /d ServerDataSrc /u sadmin /p ******** /FullPublish

Full Publish will recompile all the objects again and you can start Siebel later in the three remaining languages.

Note: You cannot add or drop a new language through Incremental Publish; you can do so only through Full Publish. During Full Publish, Siebel will be down.

About Using FullPublishInternal

When you run the FullPublish process for multi-language deployments, it will open a session for each language and run parallel processes for each language. This can result in performance, memory, and CPU issues. As an alternative, the Workspace Administrator can use the FullPublishInternal flag to force sequential (rather than parallel) processing.

This is done by first running FullPublish as normal with your primary and any secondary language, then running FullPublishInternal for each additional language.

For example, if you have 10 languages deployed:

Run FullPublish as normal for two of your required languages as follows:
```
siebdev /c tools.cfg /TL ENU,DEU /d ServerDataSrc /u <username> /p <password> /FullPublish
```
This takes care of the groundwork that is needed (for example, ensures that you have already run FlattenWorkspace) and creates some appropriate system records that are needed behind the scenes.

Then, for each additional language needed, run FullPublishInternal sequentially as follows:


siebdev /c tools.cfg /TL FRA /d ServerDataSrc /u <username> /p <password> /FullPublishInternal
siebdev /c tools.cfg /TL JPN /d ServerDataSrc /u <username> /p <password> /FullPublishInternal
siebdev /c tools.cfg /TL HEB /d ServerDataSrc /u <username> /p <password> /FullPublishInternal
. . .   
. . .