Additional Postinstallation and Configuration Tasks

This chapter describes some additional tasks that you might have to perform to complete configuring Siebel CRM. It includes the following topics:

Starting the Siebel Gateway

You must make sure that the Siebel Gateway system service is started when you do any of the following:

Start any application container for Siebel CRM modules
Start the Siebel Server system service
Configure the Security profile
Create and deploy the Siebel Enterprise profile
Create and deploy a Siebel Server profile
Create and deploy a Siebel Application Interface profile
Create and deploy a Siebel Enterprise Cache Server profile
Create a Siebel Enterprise Cache Client profile
Create and deploy a Siebel Constraint Engine profile
Create and deploy a Siebel Migration profile
Operate any of the Siebel applications
Remove the configuration for any of the Siebel CRM modules mentioned. (These are tasks that you might perform when you are uninstalling the software.)

Note: It is recommended that you review the Siebel Gateway log files, which are found in the $SIEBEL_GATEWAY_ROOT/log directory.

For compatibility with prior releases, the actual name of the system service is Siebel Gateway Name Server (in contrast to the current usage of the name Siebel Gateway for the module itself).

To verify that the Siebel Gateway has started

Navigate to the $SIEBEL_ROOT/gtwysrvr directory and source the following environment setup file. Use one of the following commands, depending on the type of shell that you use:
C shell
```
source siebenv.csh
```
Bourne or Korn shell
```
./siebenv.sh
```
This step sets the Siebel environment variables and path information required to use Siebel utilities.
To configure the Siebel environment shell script to source automatically whenever a Siebel administrator logs on, specify the shell as the default for administrator accounts. Then, add this command to the startup file for the administrator’s account.

To verify that the Siebel Gateway started successfully and is running

Enter the following command:
```
list_ns
```
If the Siebel Gateway Name Server system service is running, then you receive a response like the following, which shows the pid (process ID) of the running process:
```
started at Mon May 01 20:06:55 2017, pid: 4024, autostart: yes
```
If the Siebel Gateway Name Server system service is stopped, then you receive a response like this:
```
stopped at Mon May 01 20:06:55 2017, autostart: no
```
If the Siebel Gateway Name Server system service is stopped, then do the following:
- Execute the start_ns command to start the Siebel Gateway Name Server system service. For more information, see Siebel System Administration Guide.
- Execute list_ns to verify that it is operating correctly.

Stopping and Starting the Siebel Application Container

If it is deemed necessary, then you can stop (shut down) and restart the Siebel application container using the methods in this topic. The application container for Siebel Gateway, Siebel Server (for Configuration Agent), Siebel Application Interface, and any other application container hosting Siebel CRM functionality are automatically started after installation. If application containers are not running, then you can perform the manual tasks listed in the troubleshooting sequence shown in this topic.

As of Siebel CRM 18.8 Update, application containers (Apache Tomcat) provided in installations of Siebel Gateway, Siebel Server (Configuration Agent), and Siebel Application Interface run as a service on Microsoft Windows, while the corresponding system process is named tomcat8.exe. On UNIX operating systems, the system process for Apache Tomcat is named javaw.

Note the following behavior for Microsoft Windows and for UNIX operating systems:

On Microsoft Windows, when the computer restarts, for each applicable Siebel CRM installation, the Siebel Gateway system service (Siebel Gateway Name Server) starts automatically, followed by the application container for all installed Siebel CRM modules, followed by the Siebel Server system service, if also present.
On UNIX operating systems, you can configure autostart for application containers, as described in Configuring Siebel Application Containers for Automatic Start. You can also configure autostart for Siebel Gateway or Siebel Server system services. These tasks are described in Configuring the Siebel Gateway for Automatic Start and Configuring the Siebel Server for Automatic Start.

Caution: If you think you might need to shut down and then restart an application container, then, before you attempt to restart it, you must first check that the application container has shut down completely, for example, by using the Service Control Manager or the Task Manager in Windows. Otherwise, a port conflict failure might impede proper startup of the application container. Sometimes, examining logs might be the only way to indicate the nature of the problem.

Note: Recommendations about whether to install Siebel CRM modules together or separately using the Siebel Enterprise installer are based in part on the fact that modules installed together share the application container. Install modules separately to eliminate such dependencies and maintain availability for your Siebel CRM modules. If the Siebel Gateway and Siebel Server are collocated, then they share the same application container and do not require separate operations to stop or start the application container.

Troubleshooting Task Sequence When Siebel Application Containers Are Not Running

When any of the application containers are not running, follow all applicable steps as follows:

Stop the application container for the Siebel Application Interface.
Stop the Siebel Server system service.
Stop the application container for the Siebel Server (Configuration Agent), if the Siebel Gateway and the Siebel Server are not collocated.
Stop the application container for the Siebel Gateway.
Stop the Siebel Gateway system service.
Start the Siebel Gateway system service.
Start the application container for the Siebel Gateway.
Start the application container for the Siebel Server (Configuration Agent), if the Siebel Gateway and the Siebel Server are not collocated.
Start the Siebel Server system service.
Start the application container for the Siebel Application Interface.

Stopping the Siebel Application Container

To shut down the application container, do one of the following:

Microsoft Windows. Run the Service Control Manager (services.msc), locate the service named like Apache Tomcat 8.5 SiebelApplicationContainer_OracleHome_BuildNumber, and click the Stop button on the toolbar.
In the preceding service name, OracleHome is the Oracle home for the Siebel CRM installation (such as SES or SIEBEL_AI) and BuildNumber is the software build number. The service name is automatically defined in this format at the time the service is created.
UNIX. Navigate to the directory $SIEBEL_HOME/applicationcontainer/bin, and then execute the command ./shutdown.sh.
On UNIX operating systems, the shutdown.sh and startup.sh commands are provided in the following locations. (If the Siebel Gateway and Siebel Server are collocated, then they share the same application container and do not require separate operations to stop or start the application container.)
- Siebel Gateway. SIEBGTWY_ROOT/applicationcontainer/bin
- Siebel Server. SIEBSRVR_ROOT/applicationcontainer/bin
- Siebel Application Interface. SIEBEL_AI_ROOT/applicationcontainer/bin

Starting the Siebel Application Container

To start the application container, do one of the following:

Microsoft Windows. Run the Service Control Manager (services.msc), locate the service named like Apache Tomcat 8.5 SiebelApplicationContainer_OracleHome_BuildNumber, and click the Start button on the toolbar.
In the preceding service name, OracleHome is the Oracle home for the Siebel CRM installation (such as SES or SIEBEL_AI) and BuildNumber is the software build number. The service name is automatically defined in this format at the time the service is created.

Note: Where you need to manually start any application container in your Siebel CRM deployment, do so only in the manner described here.
UNIX. Navigate to the directory $SIEBEL_HOME/applicationcontainer/bin, and then execute the command ./startup.sh.

Note: It is strongly recommended to configure all application containers in your Siebel CRM deployment to start automatically, or else configure none of them to start automatically. For more information, see Configuring Siebel Application Containers for Automatic Start.

Related Books

Siebel System Administration Guide

Configuring the Siebel Gateway for Automatic Start

Complete the procedure that follows to configure the Siebel Gateway to start automatically (autostart). You run the Siebel Gateway service as the same nonroot user who installed the software.

After making the changes described in this topic for your operating system, the Siebel Gateway starts automatically when you restart your server and stops automatically when you shut down the server.

Note: After you perform this task, perform the tasks in Configuring Siebel Application Containers for Automatic Start. Make sure the Siebel Gateway system service starts before the application container starts.

The Siebel Gateway must be the first service to start, and the last to shut down, among all of the servers in the Siebel Enterprise that are served by that Siebel Gateway.

This topic includes the following information:

Configuring the Siebel Gateway for Automatic Start on AIX

Use the procedure in this topic to configure the Siebel Gateway to start automatically on AIX.

This topic is part of Configuring the Siebel Gateway for Automatic Start.

To configure the Siebel Gateway to start automatically on AIX

Log on as root to the computer on which the Siebel Gateway was installed.
Execute the following command on a single line:
```
mkitab "sieb_gtwyns:2:wait:su - SIEBEL_ACCOUNT -c \"$SIEBEL_HOME/bin/
siebel_server start\""
```
where:
- SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM
- $SIEBEL_HOME is the installation directory for the Siebel Gateway
Verify if the file /etc/rc.shutdown exists. If it does not exist, then create it and change the permissions:
```
touch /etc/rc.shutdown
chmod 755 /etc/rc.shutdown
```
Edit the file /etc/rc.shutdown and add the following command:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "$SIEBEL_HOME/bin/siebel_server stop"
```
where:
- SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM
- $SIEBEL_HOME is the installation directory for the Siebel Gateway
Save and close the file.

Configuring the Siebel Gateway for Automatic Start on HP-UX

Use the procedure in this topic to configure the Siebel Gateway to start automatically on HP-UX.

This topic is part of Configuring the Siebel Gateway for Automatic Start.

To configure the Siebel Gateway to start automatically on HP-UX

Log on as root to the computer on which the Siebel Gateway was installed.
Copy the file siebel_server to the /sbin/init.d directory, as follows:
```
cp $SIEBEL_ROOT/bin/siebel_server /sbin/init.d
```
In this command, $SIEBEL_ROOT is the full path to the Siebel root directory.
Using any text editor, edit /sbin/init.d/siebel_server. Do one or more of the following:
- Replace $SIEBEL_GATEWAY_ROOT with the path to the Siebel Gateway installation directory.
- Modify hashplings in the script to reference the appropriate shell for this computer, such as C shell, Bash shell, and so on.
Set the appropriate permissions by executing the following command:
```
chmod 755 /sbin/init.d/siebel_server
```
Create a soft link to /sbin/rc3.d/S720siebel_server from /sbin/init.d/siebel_server by executing the following command:
```
ln -s /sbin/init.d/siebel_server /sbin/rc3.d/S720siebel_server
```
Create a soft link to /sbin/rc2.d/K320siebel_server from /sbin/init.d/siebel_server by executing the following command:
```
ln -s /sbin/init.d/siebel_server /sbin/rc2.d/K320siebel_server
```
Create or edit /sbin/init.d/siebel_server_nonroot to add the following line:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "/sbin/init.d/siebel_server $1"
```
In this command, SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM.
Remove /sbin/rc3.d/S720siebel_server and /sbin/rc2.d/K320siebel_server, if they already exist.

Execute the following commands:

chmod 755 /sbin/init.d/siebel_server_nonroot
ln -s /sbin/init.d/siebel_server_nonroot /sbin/rc3.d/S720siebel_server
ln -s /sbin/init.d/siebel_server_nonroot /sbin/rc2.d/K320siebel_server

Configuring the Siebel Gateway for Automatic Start on Linux or Oracle Solaris

Use the procedure in this topic to configure the Siebel Gateway to start automatically on either Linux or Oracle Solaris.

This topic is part of Configuring the Siebel Gateway for Automatic Start.

To configure the Siebel Gateway to start automatically on Linux or Oracle Solaris

Log on as root to the computer on which the Siebel Gateway was installed.
Copy the file siebel_server to the /etc/init.d directory, as follows:
```
cp $SIEBEL_HOME/bin/siebel_server /etc/init.d
```
In this command, $SIEBEL_HOME is the full path to the Siebel root directory.
Using any text editor, edit /sbin/init.d/siebel_server. Do one or more of the following:
- Replace $SIEBEL_GATEWAY_ROOT with the path to the Siebel Gateway installation directory.
- Modify hashplings in the script to reference the appropriate shell for this computer, such as C shell, Bash shell, and so on.
Set the appropriate permissions by executing the following command:
```
chmod 755 /etc/init.d/siebel_server
```
Create a soft link to /etc/rc3.d/S72siebel_server from /etc/init.d/siebel_server by executing the following command.
```
ln -s /etc/init.d/siebel_server /etc/rc3.d/S72siebel_server
```
Create a soft link to /etc/rc2.d/K32siebel_server from /etc/init.d/siebel_server by executing the following command:
```
ln -s /etc/init.d/siebel_server /etc/rc2.d/K32siebel_server
```
Create or edit /etc/init.d/siebel_server_nonroot to add the following line:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "/etc/init.d/siebel_server $1"
```
In this command, SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM.
Remove /etc/rc3.d/S72siebel_server and /etc/rc2.d/K32siebel_server, if they already exist.

Execute the following commands:

chmod 755 /etc/init.d/siebel_server_nonroot
ln -s /etc/init.d/siebel_server_nonroot /etc/rc3.d/S72siebel_server
ln -s /etc/init.d/siebel_server_nonroot /etc/rc2.d/K32siebel_server

Configuring Siebel Application Containers for Automatic Start

Complete the procedure that follows to configure the application containers to start automatically (autostart) on UNIX operating systems.

Note: It is strongly recommended to configure all application containers in your Siebel CRM deployment to start automatically, or else configure none of them to start automatically.

After making the changes described in this topic, the application container starts automatically when you restart your server and stops automatically when you shut down the server. For more information, see Stopping and Starting the Siebel Application Container.

Note: Before you perform this task, perform the tasks in Configuring the Siebel Gateway for Automatic Start. Make sure the Siebel Gateway service starts before the application container starts. After you perform this task, perform the tasks in Configuring the Siebel Server for Automatic Start.

Use the procedure in this topic to configure the application container to start automatically.

To configure the application container to start automatically

Log on as root to a computer on which Siebel CRM was installed.
Copy the file SiebelApplicationContainer_OracleHome_BuildNumber.sh from $SIEBEL_ROOT/applicationcontainer/bin to the standard library of autostart scripts for this computer, such as the /etc/rc.d/init.d directory or /sbin/init.d directory.
OracleHome is the Oracle home for the Siebel CRM installation (such as SES or SIEBEL_AI) and BuildNumber is the software build number. $SIEBEL_ROOT is the full path to the root directory for the installed Siebel CRM software.
Using any text editor, edit the script SiebelApplicationContainer_OracleHome_BuildNumber.sh in the new location. Do one or more of the following:
- Replace $SIEBEL_ROOT with the path to the Siebel CRM installation directory.
- Modify hashplings in the script to reference the appropriate shell for this computer, such as C shell, Bash shell, and so on.

Set the appropriate permissions by executing commands like the following:

chmod 755 /etc/rc.d/init.d/SiebelApplicationContainer_OracleHome_BuildNumber.sh
chown root /etc/rc.d/init.d/SiebelApplicationContainer_OracleHome_BuildNumber.sh

Determine the default run level of the server by running the following command:
```
who -r
```
Based on the run level determined, add symbolic links for the scripts.
For example, if the default run level is 3, then create symbolic links under the /etc/rc.d/rc3.d directory, as in the following example:
```
cd /etc/rc.d/init.d/rc3.d
ln -s /etc/rc.d/init.d/SiebelApplicationContainer_OracleHome_BuildNumber S71SiebelApplicationContainer_OracleHome_BuildNumber
```

Related Books

Siebel System Administration Guide

Configuring the Siebel Server for Automatic Start

Complete the procedure that follows to configure the Siebel Server to start automatically (autostart). You run the Siebel Server service as the same nonroot user who installed the software.

Note: Before you perform this task, perform the tasks in Configuring the Siebel Gateway for Automatic Start and Configuring Siebel Application Containers for Automatic Start. Make sure the Siebel Gateway service starts before the application container starts.

This topic includes the following information:

Configuring the Siebel Server for Automatic Start on AIX

Use the procedure in this topic to configure the Siebel Server to start automatically on AIX.

This topic is part of Configuring the Siebel Server for Automatic Start.

To configure the Siebel Server to start automatically on AIX

Navigate to $SIEBEL_ROOT/bin.
In this path, $SIEBEL_ROOT is the installation directory for the Siebel Server.
Using any text editor, open the file siebel_server. Edit the database environment variable as follows:
Oracle Database
1. Uncomment the line #ORACLE_HOME=.
2. Enter the location for $ORACLE_HOME.
3. Uncomment the line #export ORACLE_HOME.
4. Add the following two lines:
```
TNS_ADMIN=$tns_admin
export TNS_ADMIN
```
  Ask your database administrator for the value of $tns_admin.
IBM DB2
- Add a line to execute db2profile, for example:
```
. /home/db2v8aix/sqllib/db2profile
```
Ask your database administrator for the location of db2profile.
Save and close the file.
Log on as root and execute the following command on a single line:
```
mkitab "start_server:2:wait:su - SIEBEL_ACCOUNT -c \"$SIEBEL_ROOT/bin/
siebel_server start\""
```
where:
- SIEBEL_ACCOUNT s the nonroot user account installing Siebel CRM
- $SIEBEL_ROOT is the installation directory for the Siebel Server
Verify whether or not the file /etc/rc.shutdown exists. If it does not exist, then create it and change the permissions:
```
touch /etc/rc.shutdown
chmod 755 /etc/rc.shutdown
```
Edit the file /etc/rc.shutdown. Add the following command:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "$SIEBEL_ROOT/bin/siebel_server stop"
```
where:
- SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM
- $SIEBEL_ROOT is the installation directory for the Siebel Server
Save and close the file.

Configuring the Siebel Server for Automatic Start on HP-UX, Linux, or Oracle Solaris

Complete one of the procedures that follow to configure the Siebel Server to start automatically as a nonroot user.

This topic is part of Configuring the Siebel Server for Automatic Start.

Configuring the Siebel Server to Start Automatically on HP-UX

Use the procedure that follows to configure the Siebel Server to start automatically on HP-UX.

To configure the Siebel Server to start automatically on HP-UX

Log on as root.
Create or edit /sbin/init.d/siebel_server_nonroot. Add the following line:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "/sbin/init.d/siebel_server $1"
```
In this command, SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM.
Remove /sbin/rc3.d/S720siebel_server and /sbin/rc2.d/K320siebel_server, if they already exist.

Execute the following commands:

chmod 755 /sbin/init.d/siebel_server_nonroot
ln -s /sbin/init.d/siebel_server_nonroot /sbin/rc3.d/S720siebel_server
ln -s /sbin/init.d/siebel_server_nonroot /sbin/rc2.d/K320siebel_server

Configuring the Siebel Server to Start Automatically on Linux or Oracle Solaris

Use the procedure that follows to configure the Siebel Server to start automatically on Linux or Oracle Solaris.

To configure the Siebel Server to start automatically on Linux or Oracle Solaris

Log on as root.
Create or edit /etc/init.d/siebel_server_nonroot. Add the following line:
```
/usr/bin/su - SIEBEL_ACCOUNT -c "/etc/init.d/siebel_server $1"
```
In this command, SIEBEL_ACCOUNT is the nonroot user account installing Siebel CRM.
Remove /etc/rc3.d/S72siebel_server and /etc/rc2.d/K32siebel_server, if they already exist.

Execute the following commands:

chmod 755 /etc/init.d/siebel_server_nonroot
ln -s /etc/init.d/siebel_server_nonroot /etc/rc3.d/S72siebel_server
ln -s /etc/init.d/siebel_server_nonroot /etc/rc2.d/K32siebel_server

Managing Environment Variables

There are several environment variables that must be properly set for optimal functioning of the Siebel Server, as shown in the following. These include:

Siebel environment variables
UNIX operating system environment variables

Note: For information about tuning the UNIX kernel and other parameters for Siebel Server optimization, see Siebel Performance Tuning Guide.

Table Setting and Managing Environment Variables

Environment Variable Purpose Recommended Siebel Value

Environment Variable	Purpose	Recommended Siebel Value
ODBCINI	Tells the ODBC driver manager which file to open to look for the ODBC data source and driver information. Set within the environment setup files, siebenv.csh (for C shell) and siebenv.sh (for Bourne or Korn shell), which are created during Siebel Enterprise Server and Siebel Server configuration. This variable always points to `$SIEBEL_HOME/sys/.odbc.ini`.	Do not modify.
SIEBEL_UNIXUNICODE_DB	Controls the ODBC driver manager responsible for connection to the RDBMS. Reset, if necessary, within each environment setup file before sourcing it.	Set to ORACLE or DB2. This value is set automatically.
LANG	Language environment variable within the environment setup file. Sets the database server client environment appropriate to the language of installation. For more information about specifying locales, see Specifying the Locale for Siebel CRM and Specifying the Locale for Your UNIX Operating System.	Set this to the language in which your database runs.

ODBCINI

Tells the ODBC driver manager which file to open to look for the ODBC data source and driver information. Set within the environment setup files, siebenv.csh (for C shell) and siebenv.sh (for Bourne or Korn shell), which are created during Siebel Enterprise Server and Siebel Server configuration. This variable always points to $SIEBEL_HOME/sys/.odbc.ini.

Do not modify.

SIEBEL_UNIXUNICODE_DB

Controls the ODBC driver manager responsible for connection to the RDBMS. Reset, if necessary, within each environment setup file before sourcing it.

Set to ORACLE or DB2. This value is set automatically.

LANG

Language environment variable within the environment setup file. Sets the database server client environment appropriate to the language of installation.

For more information about specifying locales, see Specifying the Locale for Siebel CRM and Specifying the Locale for Your UNIX Operating System.

Set this to the language in which your database runs.

Tuning UNIX Operating Systems for Siebel CRM

The Siebel environment variables $SIEBEL_HOME and $SIEBEL_ROOT must be set to enable execution of the Siebel Gateway and Siebel Server management utilities documented in Siebel System Administration Guide.

During Siebel Enterprise Server and Siebel Server configuration, the script files siebenv.csh (for C shell) and siebenv.sh (for Bourne or Korn shell) are automatically created in the $SIEBEL_ROOT directory. When sourced, these shell scripts set the environment variables.

If you have configured your Siebel Server to start manually, then you must source either siebenv.csh or siebenv.sh before starting the server. For this reason, you might want to add a call to the appropriate siebenv.* file to the logon files of all of the Siebel administrator UNIX accounts, so that these variables are set automatically whenever a Siebel administrator logs on.

If you want to change the default settings of these environment variables, then you must do so before you start the Siebel Server.

There are several UNIX system environment variables that you must set for proper functioning of the Siebel Server.

For detailed information about tuning the UNIX kernel and other configurable parameters for Siebel Server optimization, see Siebel Performance Tuning Guide. Many other environment variables are documented in Siebel System Administration Guide or other guides on Siebel Bookshelf.

Related Books

Siebel Performance Tuning Guide

Siebel System Administration Guide

Preparing to Run Siebel Server Components

This topic summarizes some of the tasks that you might have to do after installing and configuring Siebel Server and before you run Siebel Server components. It includes the following information:

You might have to perform some of these tasks on multiple Siebel Servers in order to configure them similarly for use in a load-balanced environment.

Note: For detailed information about enabling and disabling server component groups, synchronizing batch components, creating server component job definitions, using Siebel Server Manager, and related tasks, see Siebel System Administration Guide.

Enabling and Disabling Server Component Groups

When you initially configured your Siebel Server, you specified which server component groups to enable. Before you deploy your Siebel Server, verify that the server component groups that you require are enabled. It is also recommended that you disable any server component groups that you do not require. Because you explicitly enabled server component groups when you configured the Siebel Server, you might or might not have to disable component groups after installation and configuration.

As of Siebel CRM 17.0, some new server components are provided. Also, some components have been removed or are no longer used.

For example, additional customer applications for Siebel Open UI are provided that were previously desupported in Siebel CRM 16.0, but were available for standard interactivity in prior releases. As of Siebel CRM 16.0, the Application Object Managers that in previous release were used for Siebel eSales, Siebel eCustomer, and Siebel eMarketing are now used for new customer applications built for Siebel Open UI.

Customers migrating from earlier releases also must consider which product changes are new to them because they were made in intervening releases. For example, in a prior release, some components moved from existing component groups into a new component group, Disconnected Mobile Synchronization (alias MobileSync). Consequently, if your deployment uses Siebel Mobile disconnected applications or uses Siebel Remote or Siebel Replication Manager, then you must enable the MobileSync component group, if you have not already done so, along with the HandheldSync or HandheldSyncSIS component group.

Product changes of these types introduce changed requirements for enabling server components and for deploying applications. The specific requirements that apply to your deployment depend on the products that you are using. Some requirements apply only for migration installations, and vary based on the Siebel CRM release that you are migrating from or the Siebel CRM version in effect when you first configured the software.

For example, for a new installation, you can enable any component groups using the Siebel Management Console. For a migration installation, if you do not reconfigure the Siebel Server and you have to enable any additional component groups, then you can do so manually after installation. In some cases, however, you might have to run certain scripts on the Siebel Server to make new products available.

Before performing a migration installation, also review parameter settings for server components affected by product changes, in case you need to reapply custom settings to components that moved, for example, or in case you must reconfigure the Siebel Server.

Several requirements apply to all migrations to Siebel CRM 17.0, as Additional Tasks for Migration Installations. For example, you must create the Siebel Application Interface profile and apply it to the installed instance of Siebel Application Interface.

For information about the requirements for particular Siebel CRM products, see product documentation on Siebel Bookshelf or elsewhere.

This topic is part of Preparing to Run Siebel Server Components.

Related Books

Siebel System Administration Guide

Siebel Mobile Guide: Disconnected

Siebel Remote and Replication Manager Administration Guide

Siebel Database Upgrade Guide

Enabling and Disabling Language-Specific Application Object Managers and Adding Languages

When you installed and configured the Siebel CRM software, you would have included one or more languages, as described in Installing and Deploying Siebel CRM with Multiple Languages. That topic also describes optional approaches to installing and deploying languages in a phased approach.

If you install the Siebel Server with multiple languages and specify these languages as deployed languages when you configure the Siebel Server, then language-specific Application Object Manager components are created for each deployed language. If you decide that you do not require Application Object Managers for one or more of these deployed languages, then you can use Siebel Server Manager to disable such components prior to deployment.

If you install multiple languages, then it is recommended that you deploy all of the installed languages when you configure the Siebel Server using the Siebel Management Console. As stated, you can disable any language-specific components that you do not require.

You must coordinate the language deployment tasks between your installations of Siebel Server and Siebel Application Interface.

For more information about performing tasks in the Siebel Management Console, see Running the Siebel Management Console.

This topic is part of Preparing to Run Siebel Server Components.

Related Books

Siebel System Administration Guide

Siebel Global Deployment Guide

Synchronizing Batch Components

After installing and configuring the Siebel Server, you must synchronize any batch components before you can operate them. Do this after upgrading the Siebel database, where applicable. For more information about synchronizing batch components, see Siebel System Administration Guide.

This topic is part of Preparing to Run Siebel Server Components.

Migrating Siebel Enterprise Server and Siebel Server Parameter Settings

Some Siebel Enterprise Server and Siebel Server parameter settings can be migrated from one Siebel application environment to another by using the configuration migration utility (cfgmerge). Other customized application data can be migrated by using Siebel Application Deployment Manager (Siebel ADM).

This topic is part of Preparing to Run Siebel Server Components.

Related Books

Siebel System Administration Guide

Siebel Application Deployment Manager Guide

Performing Additional Tasks to Configure Siebel Servers

After installing and configuring a Siebel Server as described in this guide, you might have to perform some additional configuration tasks, such as setting parameters for the Siebel Enterprise, Siebel Server, or server components, such as Application Object Managers.

You perform these types of configuration tasks with Siebel Server Manager, whether by using views in the Administration - Server Configuration screen or by using commands at the srvrmgr command line. For more information about using Server Manager, see Siebel System Administration Guide.

This topic is part of Preparing to Run Siebel Server Components.

Related Books

Siebel System Administration Guide

Updating the CRC Checksum Setting

If you are using a security adapter, then you might have to update the value of the CRC Checksum setting after installing Siebel CRM 17.0 as a migration installation. The value must reflect the checksum value applicable to the security adapter library file, such as a DLL file on Microsoft Windows.

This task might be necessary if you previously determined to use checksum validation for your security adapter deployment, and set the value of the CRC Checksum setting. If a Siebel CRM release that you installed later as a migration installation included an updated security adapter library file, then checksum validation fails and Siebel Web Clients might not start. To prevent this result, you must update the value of the CRC Checksum setting.

For more information about specifying the CRC Checksum setting as part of configuring a security profile, see Configuring a Security Profile. See also Siebel Security Guide.

This topic is part of Preparing to Run Siebel Server Components.

Related Books

Siebel Security Guide

About Installing Additional Siebel Servers for an Existing Siebel Enterprise

You can install and configure multiple Siebel Servers for a Siebel Enterprise.

Typically, before installing and configuring additional Siebel Servers for an existing Siebel Enterprise, you complete installation and configuration for the Siebel Application Interface.

Run the Siebel Enterprise Server installer to install each additional Siebel Server on another server computer, and run the Siebel Management Console to configure this Siebel Server.

You can also deploy a new Siebel Server based on an existing configured Siebel Server, using an existing Siebel Server profile you defined in Siebel Management Console.

After configuring a new Siebel Server, if this new Siebel Server adds a new component or language that is not available in any of the existing Siebel Servers, then you must perform corresponding Siebel Application Interface configuration tasks to make the applications on this Siebel Server available for Siebel native load balancing. In addition, you might have to modify the Siebel Application Interface profile for the installed instance.

This topic is part of Preparing to Run Siebel Server Components.

Customizing the Application Container for Siebel Application Interface

You can perform various configuration steps to customize the application container (Apache Tomcat) for Siebel Application Interface in your Siebel CRM deployment.

These tasks apply only to the application container for a deployed instance of Siebel Application Interface. They do not apply for the application container for any module that uses URLs for internal purposes only, such as Siebel Gateway or Siebel Server.

Note: For each of the customizations described in this section, you must test your applications and verify that your customizations work as expected before you make these changes in your production systems.

This topic contains the following information:

Configuring the Common Logger for Siebel Application Interface

As of Siebel CRM 18.9 Update, you can configure the log level for the Siebel Application Interface common logger, which is used for certain common logging tasks. This log cannot be configured using Siebel Management Console, unlike other types of logging for Siebel Application Interface described in Configuring the Siebel Application Interface.

To configure the log level for the common logger, you edit the file log4j2-siebel.xml, which is located in the directory SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel/WEB-INF.

Modify only the following line, and no other part of the file. For example, you can change the level from ERROR to INFO. You can use the following values: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL. The default log level configured in the file is ERROR.

<logger name="CommonLogger" level="ERROR" additivity="false">

Note: Settings such as INFO, DEBUG, or TRACE can exponentially increase the size of the log files, consume a large amount of disk space, and reduce performance of the Siebel Application Interface node. Use these settings only when some investigation is needed.

If you plan to configure the log level for the common logger, it is recommended to do so after you finish configuring Siebel Application Interface using Siebel Management Console. After modifying the log4j2-siebel.xml file, you must restart the application container, as described in Stopping and Starting the Siebel Application Container.

Related Books

Siebel System Monitoring and Diagnostics Guide

Customizing URLs for Siebel CRM Applications

As of Siebel CRM 19.6 Update, you can perform various configuration steps to customize the URLs you use for Siebel CRM applications. The steps you perform for this task primarily involve editing files on the application container (Apache Tomcat) for Siebel Application Interface.

The keyword siebel is present in the Siebel CRM application URLs as a result of your deploying the siebel.war file on the application container, though it also exists in other configuration contexts. The particular customization you can make is to replace the keyword siebel in the Siebel URLs with a name suitable for your organization, such as myorg. Perform these steps after configuration and deployment tasks using Siebel Management Console. These steps do not involve renaming the siebel.war file.

The existing URL format is as follows:

https://host:port/siebel/app/application/lang

You can customize the Siebel Application Interface to use a different keyword, so the format would resemble the following:

https://host:port/myorg/app/application/lang

An example of a customized URL would be as follows:

https://server1:9000/myorg/app/callcenter/enu

To customize the URLs for Siebel CRM, use the steps in the procedure that follows.

To customize the URLs for Siebel CRM

Log in to the computer where you installed Siebel Application Interface.
Stop the application container, as described in Stopping and Starting the Siebel Application Container.
Navigate to the directory SIEBEL_AI_ROOT/applicationcontainer/conf.
Back up the server.xml file.
Open server.xml for editing, using a suitable text editing tool. For example, on Microsoft Windows you might use Notepad.
In server.xml, locate the <Host> tag, and modify this line to include the autoDeploy element, as follows:
```
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
```

Under this <Host> tag, insert <Context> tags in lines like the following, substituting your preferred keyword for myorg:

<Context docBase="${catalina.base}/webapps/myorg/" path="/myorg" />
<Context docBase="${catalina.base}/webapps/ROOT/" path="/" />
<Context path="/manager" docBase="${catalina.base}/webapps/manager" privileged="true" />

If the webapps directory on the Application Interface also contains the subdirectories host-manager, docs, or examples, then also add <Context> lines like the following:

<Context docBase="${catalina.base}/webapps/host-manager/" path="/host-manager" />
<Context docBase="${catalina.base}/webapps/docs/" path="/docs" />
<Context docBase="${catalina.base}/webapps/examples/" path="/examples" />

Save your updates to server.xml.
Next, you will update any referring links to the affected URLs.
Run Siebel Management Console. In the Siebel Application Interface profile, under the REST Inbound Defaults section, update the value for the REST Response Base URL to reflect the URL change. For example, change this URL:
```
https://host:port/siebel/v1.0/
```
as follows:
```
https://host:port/myorg/v1.0/
```
For more information, see Configuring the Siebel Application Interface.
Modify the re-write.config file. Do the following:
1. Navigate to the directory SIEBEL_AI_ROOT/applicationcontainer/webapps/ROOT/WEB-INF.
2. Back up the re-write.config file.
3. Open re-write.config for editing using a suitable text editor.
4. Modify the following line, substituting siebel with the new keyword myorg, as you did in server.xml. For example, change this line:
```
RewriteRule ^/eai_enu/start.swe?(.*)$ /siebel/app/eai/enu/$1 [L]
```
  as follows:
```
RewriteRule ^/eai_enu/start.swe?(.*)$ /myorg/app/eai/enu/$1 [L]
```
5. Make the same change in the lines for all other Siebel languages.
6. Save your updates to re-write.config.
Modify the ResourceSequence.txt file, which is used by the Siebel Migration application. Do the following:
1. Navigate to the directory SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel/WEB-INF. Then back up the ResourceSequence.txt file, if it exists.
2. If ResourceSequence.txt does not exist, then navigate to SIEBEL_AI_ROOT/applicationcontainer/webapps, back up the siebel.war file, and extract ResourceSequence.txt into a directory of your choice (for temporary use).
3. Open ResourceSequence.txt for editing using a suitable text editor.
4. Modify the following lines, substituting siebel with the new keyword myorg, as you did in server.xml. For example, change these lines:
```
AuthenticationURISuffix=/siebel/v1.0/service/Authentication%20Service%20For%20Migration/AuthenticateUser
RepoUpgradeURISuffix=/siebel/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Application%20Migration%20Utility%20Service%27
```
  as follows:
```
AuthenticationURISuffix=/myorg/v1.0/service/Authentication%20Service%20For%20Migration/AuthenticateUser
RepoUpgradeURISuffix=/myorg/v1.0/service/describe?searchspec=%5BName%5D%20LIKE%20%27Application%20Migration%20Utility%20Service%27
```
5. Save your updates to ResourceSequence.txt. Then replace this file in siebel.war.
  When the application container is restarted, the updated version of ResourceSequence.txt is extracted into SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel/WEB-INF.
Restart the application container, as described in Stopping and Starting the Siebel Application Container.
Perform the same steps for each instance of Siebel Application Interface in your deployment.

Modifying the HTTPS Redirect Port or HTTP Port for Siebel Application Interface

This topic describes the steps you can take to modify the HTTPS redirect port or HTTP port for a deployed instance of Siebel Application Interface.

To modify the HTTPS redirect port or HTTP port for a deployed instance of Siebel Application Interface

Using Siebel Management Console, delete the Application Interface deployment for which you are changing the HTTPS redirect port or HTTP port.
For more information, see Removing the Siebel Application Interface Configuration.
Perform Steps 1 through 5 inCustomizing URLs for Siebel CRM Applications.
In server.xml, replace all instances (three) of the HTTPS redirect port or HTTP port that you are changing with the new port number, which must be free.
Restart the application container, as described in Stopping and Starting the Siebel Application Container.
Restart Siebel Management Console.
In the Siebel Application Interface profile, under the REST Inbound Defaults section, update the value for the HTTPS redirect port or HTTP port.
Deploy the Application Interface profile with the new HTTPS redirect port or HTTP port.
Start a Siebel application that uses this port.

Installing and Deploying Siebel CRM with Multiple Languages

Multiple Siebel language packs can be installed and deployed as part of Siebel CRM installation and configuration. Review this topic and related topics when planning multilingual deployments. Language installation is part of the installation procedure for each installable Siebel CRM module. The task of adding and deploying new languages is described for Siebel Server, Siebel Application Interface, Siebel Web Client, and Siebel Tools.

Scenarios for deploying Siebel CRM with more than one language pack are described in Scenarios for Installing and Deploying Multiple Languages.

For a list of the languages supported by Siebel CRM, see 1513102.1 (Article ID) on My Oracle Support. See also Siebel Global Deployment Guide, Siebel System Administration Guide, and other applicable documentation.

Note the following recommendations:

It is strongly recommended that you install and deploy, or at least install, all of the languages that you expect to require, on each physical server.
It is strongly recommended that you install the same set of language files on each physical server. Doing so helps ensure maximum compatibility between physical servers, so that the system can be reconfigured to meet ongoing requirements. Oracle only tests configurations in which the same set of language files are installed on each physical server that is used in a single Siebel Enterprise.

You can add languages to an existing installation of the same version of Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, or Siebel Tools by using unattended mode (silent mode) only. After you install new languages, you must run the Siebel Management Console and perform the tasks to redeploy the Siebel Server. To do this, you create a new profile or clone the existing profile, delete the Siebel Server deployment item, and then deploy the Siebel Server with the new profile, specifying all of the languages to deploy. Finally, add the new languages to the Siebel Application Interface configuration. See also Scenarios for Installing and Deploying Multiple Languages and Limitations for Installing Additional Languages.

If you include multiple languages with a Siebel Enterprise Server installation, then you designate one language as the primary language to be used for server messages and logging. Typically, the same primary language is also used for the Siebel database, which cannot be changed after database installation.

If you install and deploy a new language in an existing installation, then you must add the language to the Siebel database and perform additional tasks using the Database Configuration Wizard, as described in About Language Deployment Tasks Using the Database Configuration Wizard.

Note: Additional tasks in Siebel Tools might be required in order to fully deploy a language you have added. For more information, see the workspaces administration topics in Using Siebel Tools.

This topic contains the following information:

About Language Deployment and the Siebel Network Image

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

In order to include any languages in a new installation or to add languages that were not previously installed, the languages must be present in the Siebel network image for the applicable release of Siebel CRM. This requirement applies to Siebel CRM 17.0 and to Siebel CRM 20.x Update.

Where a language was not previously included in the network image, you can add languages to each applicable network image (for all applicable releases) using the Siebel Image Creator utility. For details, see Creating the Siebel Installation Image on the Network.

About Language Deployment and Migration Installations

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

For Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, or Siebel Tools, when you perform a migration installation of Siebel CRM 17.0, files for all of the installed languages are automatically included. First, however, you must include all of these languages when you create the network image. For more information about the types of Siebel releases, see About Siebel CRM Releases.

If you plan to perform a migration installation of Siebel CRM 17.0, and you also want to add languages to your existing deployment, then you have two options for how to do this, subject to limitations:

Add languages after installing Siebel CRM. The installer for Siebel Enterprise Server and Siebel Application Interface supports adding languages to an existing installation of the same version, using an unattended installation method. You would perform this task after performing the migration installation tasks for these modules. Some limitations might apply to adding languages to your existing installed Siebel client software. For more information, see Limitations for Installing Additional Languages and Installing and Deploying Additional Languages.
Add languages before installing Siebel CRM. Subject to limitations for your existing installed Siebel CRM server and client software, it might be possible or desirable for you to install new languages before you install Siebel CRM. To determine if this option is possible for the currently installed software in your Siebel deployment and, if so, to determine what steps are required, see the documentation that applies to your currently installed Siebel software version for information about this version.

For versions of the Siebel Installation Guide for prior releases, see 1461732.1 (Article ID) on My Oracle Support. For the Siebel Patchset Installation Guide for Siebel CRM for prior releases, see 1614310.1 (Article ID) on My Oracle Support. For the Siebel Maintenance Release Guide for prior releases, see 880452.1 (Article ID) on My Oracle Support for Siebel CRM 8.1.1.x or see 1441523.1 (Article ID) for Siebel CRM 8.2.2.x.

For example, if your current installation is Siebel CRM 8.1.1.10 on Microsoft Windows, see Siebel Installation Guide for Microsoft Windows, version 8.1, Rev. D, and see Siebel Maintenance Release Guide, Version 8.1.1.10.

For a list of the languages supported by Siebel CRM, see 1513102.1 (Article ID) on My Oracle Support.

Note: Specific installation tasks and requirements might apply for any language pack that is newly supported and thus requires a minimum Siebel release of Siebel CRM 17.0. For more information, see Importing Locale-Specific Data into the Siebel Repository.

About Language Deployment on Siebel Server and Siebel Application Interface

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

When you configure each installed instance of Siebel Server and Siebel Application Interface, you specify which languages to deploy, from among the installed languages. It is possible to deploy a subset of the installed languages. Which languages you deploy on a given server depends on the uses to which you will put that server.

Note the following points about language deployment on Siebel Server and Siebel Application Interface:

On each Siebel Server, the set of deployed languages determines which language-specific components such as Application Object Managers are created on that server. It is recommended that you deploy all of the languages that are installed in the enterprise and optionally disable Application Object Managers for particular languages where they are not required.
On each instance of Siebel Application Interface, you must deploy the superset of all of the languages that are required by all of the Application Object Managers that connect to it. It is recommended that you deploy all of the languages that are installed in the enterprise.

About Language Deployment Tasks Using the Database Configuration Wizard

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

In addition to software installation and configuration tasks, for installed languages other than the primary language for the Siebel database, you must perform the following operations, using the Database Configuration Wizard. You perform these tasks after installing the Siebel database.

Adding the language (including seed data) to the Siebel database. Perform this task once for each nonprimary language that you install.
Importing the Siebel Repository into the Siebel database. Perform this task once for each nonprimary language that you install.
Running the MLOV (multilingual LOV) conversion utility. Perform this task once after installing multiple languages initially and again after adding one or more languages.

About Language Deployment for Unshipped Languages

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

If you are localizing Siebel CRM to use a language for which a Siebel language pack is not provided, then see also the topics about localizing an unshipped language in Siebel Global Deployment Guide.

Limitations for Installing Additional Languages

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

Although it is strongly recommended to install all of the languages that you might require (whether or not you initially deploy them all), you can also add languages to an existing installation. However, several limitations apply.

Note: If you plan to perform a migration installation of Siebel CRM, and you also want to add languages to your existing deployment, then you might be able to install the languages before you install the software. For more information, see About Language Deployment and Migration Installations.

For Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, and Siebel Tools, the limitations for installing additional languages are as follows:

You can install additional languages for existing installations by using the installers of the same version only. For example, you can install the software as a new installation or as a migration installation, then later use the same installers to add languages.
You can add languages by running the installer in unattended mode (silent mode) only, using response files that you have prepared for this purpose. You cannot add languages by running the installer in GUI mode.
You cannot generate response files for an operation to add languages. You must use an edited copy of one of the response files that are provided for Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, or Siebel Tools. For the location of these response files, see Installing and Deploying Additional Languages.
You cannot add languages as part of performing a migration installation. However, you can add languages after the migration installation.
You cannot add languages to an earlier version of the installed software by using the installers for the current release. Conversely, you cannot use the installers for any earlier release to add languages to an installation of the current release.
Before you install additional languages, you must uninstall Siebel CRM 20.9 Update, if you have installed it onto Siebel CRM 17.x or later. Reinstall Siebel CRM 20.9 Update after completing the steps to add the languages.

Scenarios for Installing and Deploying Multiple Languages

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

Consider the following scenarios for installing and deploying multiple Siebel language packs:

Install and deploy all of the languages that you require once. For customers who are installing and deploying languages shipped with the Siebel CRM base release, and who do not plan to deploy other languages at a later date. This option is easiest but might not be suitable for phased language deployments.
Install all of the languages that you will require, but deploy some of these languages later. For customers who are installing and deploying languages shipped with the Siebel CRM base release, but who plan to deploy some of the installed languages at a later date. This option is recommended for phased language deployments.
Install and deploy additional languages in an existing deployment. For customers who are installing and deploying languages shipped with the Siebel CRM base release, and who plan to install and deploy additional languages at a later date. This option might be suitable for some phased language deployments. You can install languages at any time to meet changing business needs. However, deploying languages is easier if you include them when you first install and configure the Siebel CRM software.

Installing and Deploying All Required Languages Once

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

This scenario is intended for customers who are deploying language packs that were provided with Siebel CRM and who are installing all of the language packs that their enterprise will require during initial installation and configuration.

Include all of the required languages with your initial installation and deploy them when you configure the installed Siebel software.

Note: You perform the tasks in this topic in conjunction with topics such as Installing Siebel CRM. Perform all applicable steps that are documented in more detail in these and other topics. These tasks are also part of the roadmap topics in Overview of Installing Siebel CRM.

To deploy multiple languages shipped with Siebel CRM

Install Siebel Enterprise Server software for Siebel CRM 17.0 on all of the applicable servers, with all of the languages that you will require for the enterprise.
Install Siebel Application Interface for Siebel CRM 17.0 on all of the applicable servers, with all of the languages that you will require for the enterprise.
Install Siebel CRM 20.x Update on all of the modules in your Siebel CRM deployment.
Install the Siebel database. This task installs seed data for the primary language into the Siebel database.
Using the Siebel Management Console, create and deploy the Security profile, the Siebel Gateway profile, and the Siebel Enterprise profile.
Create and deploy the Siebel Server profile. During Siebel Server configuration, specify to deploy all of the installed languages.
Create and deploy the Siebel Application Interface profile. During Siebel Application Interface configuration, specify to deploy all of the installed languages.
For each additional installed (nonprimary) language that you are deploying for the first time: add the language to the Siebel database and import the Siebel Repository. Also run the MLOV conversion utility (once).

Installing All Required Languages but Deploying Some Languages Later

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

This scenario is intended for customers who are deploying language packs that were provided with Siebel CRM but who plan to deploy some of these language packs at a later date on particular instances of Siebel Server or Siebel Application Interface. Include all of the required languages with your initial installation.

There are two variations of this scenario that can achieve the desired result. Review each option and decide which one works best for your situation. See also Installing and Deploying All Required Languages Once for details for some tasks.

Note: You perform the tasks in this topic in conjunction with topics such as Installing Siebel CRM. Perform all applicable steps that are documented in more detail in these and other topics. These tasks are also part of the roadmap topics in Overview of Installing Siebel CRM.

Deploying Multiple Languages Now and Later (Option 1)

Use the following procedure to deploy multiple languages now and at a later date. This procedure represents Option 1. Compare it with Option 2.

To deploy multiple languages now and at a later date (Option 1: preferred)

Perform tasks similar to those described in Installing and Deploying All Required Languages Once.
- Install Siebel CRM 17.0 with all of the languages that you will deploy now and at a later date.
- Install Siebel CRM 20.x Update on all of the modules in your Siebel CRM deployment.
- When you configure each Siebel Server and Siebel Application Interface, specify that you want to deploy all of the installed languages.
For each Siebel Server, disable any language-specific Application Object Manager components that you do not yet require.
When you are ready to deploy additional installed languages, re-enable any language-specific Application Object Managers that you previously disabled.
For each additional installed (nonprimary) language that you are deploying for the first time: add the language to the Siebel database and import the Siebel Repository. Also run the MLOV conversion utility (once).

Deploying Multiple Languages Now and Later (Option 2)

Use the following procedure to deploy multiple languages now and at a later date. This procedure represents Option 2. Compare it with Option 1.

To deploy multiple languages now and at a later date (Option 2)

Perform tasks similar to those described in Installing and Deploying All Required Languages Once. In this case, it is assumed that you did not deploy all of the installed languages.
- Install Siebel CRM 17.0 with all of the languages that you will deploy now and at a later date.
- Install Siebel CRM 20.x Update on all of the modules in your Siebel CRM deployment.
- When you configure each Siebel Server or Siebel Application Interface, optionally specify to deploy only a subset of the installed languages.
When you are ready to deploy additional installed languages, perform the following for each Siebel Server:
1. Run the Siebel Management Console, as described in Starting the Siebel Management Console.
2. Create a new Siebel Server profile or clone the existing profile.
3. Delete the Siebel Server deployment item.
4. Deploy the Siebel Server with the new profile, specifying all of the languages to deploy.
Perform the following for each Siebel Application Interface:
1. Run the Siebel Management Console, as described in Starting the Siebel Management Console.
2. Modify the existing Siebel Application Interface profile to add support for required component-language combinations, as described in Creating a Siebel Application Interface Profile.
3. Specify the additional languages to deploy.
4. Save the profile.
For each additional installed (nonprimary) language that you are deploying for the first time: add the language to the Siebel database and import the Siebel Repository. Also run the MLOV conversion utility (once).

Installing and Deploying Additional Languages

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

This scenario is intended for customers who did not install all of the Siebel language packs and who later determine that they require additional supported Siebel language packs that were not previously installed and deployed.

This topic describes adding new languages to your existing Siebel CRM deployment and existing physical resource allocation. As part of expanding language support, you might also install Siebel CRM modules on new servers that include new language packs.

For an existing installation of Siebel Enterprise Server, Siebel Application Interface, Siebel Web Client, or Siebel Tools, you can run the same installer in unattended mode to add any available and supported language packs that you require that were not previously installed. You must perform this installation task using unattended mode (silent mode) only.

For detailed requirements and other information about running Siebel installers and Siebel Management Console, see Requirements for Installing and Configuring Siebel CRM and other applicable parts of this guide.

Perform the tasks in this topic in conjunction with the installation instructions for each installable module and the unattended installation instructions for these modules. Perform all applicable steps, including those that are documented in more detail in other topics.

For more information about performing unattended installations, see Installing Siebel CRM in Unattended Mode and Installing Siebel Web Clients and Siebel Tools in Unattended Mode.

Note: Where you are adding languages to an existing installation, the primary language for the Siebel database will already have been determined when you installed the Siebel Enterprise Server software and the Siebel database. Any language that is to serve as the primary language for a new Siebel database must be included when you first install the Siebel Enterprise Server software.

Oracle-Provided Installation Response Files

The Oracle-provided response files that you can use for adding languages using unattended mode are as follows, depending on your installed Siebel CRM version. Use the file whose name best reflects the version, product, and operating system for each installation you are performing, and modify the file as necessary for your installation task.

811x_ses_addlang_unix.rsp
seaw_mobile_webclient_addlang.rsp
seaw_dedicated_webclient_addlang.rsp
seatools_addlang.rsp

Response File Parameters

The response files that you use when you install additional languages in unattended mode include parameters that specify information about your existing installation, the network image, the new languages you are installing, and so on. Review the parameters in each response file to determine the parameters for which you must provide values. All values must be enclosed in double-quotes.

For any operation to install new languages, you must do the following:

Specify values for the ORACLE_HOME and ORACLE_HOME_NAME parameters, which correspond to values that you specified when you performed the original installation. These settings identify the installation to which you are adding languages.
Specify a value for the s_shiphomeLocation parameter, representing the location of the Disk1 directory in the network image for the Siebel CRM module that you are installing.
Specify a value for the FROM_LOCATION parameter, representing the location of the products.xml file within the Disk1/stage directory in the network image for the Siebel CRM module that you are installing.
Specify a value for the selectedLangs parameter, representing the new language or languages that you are installing.

For Siebel Enterprise Server only, you must set the following parameters to true for each installed module:

b_isGatewayInstalled (if Siebel Gateway is installed)
b_isSiebsrvrInstalled (if Siebel Server is installed)
b_isDBInstalled (if Siebel Database Configuration Utilities is installed)
b_isEAIInstalled (if EAI Connectors is installed)

To install and deploy additional languages on existing installations

Perform tasks similar to those described in Installing and Deploying All Required Languages Once or Installing All Required Languages but Deploying Some Languages Later. In this case, it is assumed that you did not install and deploy all of the languages.
Review Limitations for Installing Additional Languages.
Uninstall Siebel CRM 20.x Update, if you have installed it on top of Siebel CRM 17.x or later, for each applicable installed Siebel CRM module.
Verify that the additional new languages that you require and plan to install are included in the Siebel network image.
Navigate to the location of an existing response file for the Siebel CRM module for which you are adding languages.
For example, for Siebel Enterprise Server on Oracle Solaris, navigate to Siebel_Image/Solaris/Server/Siebel_Enterprise_Server/Disk1/stage/Response.
In this path, Siebel_Image is the directory for your version-specific Siebel network image, such as /Siebel_Install_Image/17.0.0.0.
Edit the response file, as appropriate for the Siebel CRM module for which you are adding languages.
For example, for Siebel Enterprise Server modules and Siebel Application Interface, edit the response file 811x_ses_addlang_unix.rsp.
See the information about response file parameters, before this procedure.

Note: Always back up any existing response file before editing it or replacing it with a newly generated file or an edited version of the file.
Copy the edited file to a suitable location. For example, you might place a file into a subdirectory of the existing location for the response files, or into a temporary location.
Navigate to the location of the installer for the Siebel CRM module for which you are installing additional languages.
For example, for Siebel Enterprise Server on Oracle Solaris, navigate to Siebel_Image/Solaris/Server/Siebel_Enterprise_Server/Disk1/install.
When you are ready to install additional languages as indicated by the settings in each of your edited response files, run each installer program in unattended mode (silent mode) on each computer where Siebel CRM is already installed.
For example, for Siebel Enterprise Server, run a command like the following:
```
./runInstaller -silent -responseFile /export/home/811x_ses_addlang_unix.rsp -invPtrLoc inventory_location 
```
For example, for Siebel Tools, run a command like the following:
```
setup.bat -silent -responseFile C:\811x_tools_addlang_win.rsp
```
Reinstall Siebel CRM 20.x Update, if you previously uninstalled it in Installing and Deploying Additional Languages. Then validate the installation again.
For each applicable Siebel Server, when you are ready to deploy the newly installed languages, and any other languages that were not previously deployed, do the following:
1. Run the Siebel Management Console, as described in Starting the Siebel Management Console.
2. Create a new Siebel Server profile or clone the existing profile.
3. Delete the Siebel Server deployment item.
4. Deploy the Siebel Server with the new profile, specifying all of the languages to deploy.
For each applicable Siebel Application Interface, do the following:
1. Run the Siebel Management Console, as described in Starting the Siebel Management Console.
2. Modify the existing Siebel Application Interface profile to add support for required component-language combinations, as described in Creating a Siebel Application Interface Profile.
3. Specify the additional languages to deploy.
4. Save the profile.
For each additional installed (nonprimary) language that you are deploying for the first time: add the language to the Siebel database and import the Siebel Repository. Also run the MLOV conversion utility (once).
Validate the installation after it has completed.
Repeat the previous steps, where applicable, to install and deploy the new languages for each applicable installed Siebel CRM module.

Note: Add the languages for all of the applicable server installations before you add the languages for Siebel Web Client and Siebel Tools, where needed.

Importing Locale-Specific Data into the Siebel Repository

This topic is part of Installing and Deploying Siebel CRM with Multiple Languages.

Sometimes it is necessary to update the text strings held in the repository for a particular language or for multiple languages. These text strings are held in the Symbolic String Model (SSM) table, and appear on-screen as labels for tabs, fields, and so on, across all of the Siebel applications.

Updates might be needed either because a string has been incorrectly translated for a particular language or because installing a patch release has caused a new string or message to appear for all of the languages for which Oracle ships language packs for Siebel CRM.

Note: These instructions are provided for use with any releases to which they might apply. They might not apply for any particular Siebel CRM release or language.

The following procedure uses the Locale Management Utility (LMU), which is part of Siebel Tools, to import an LMU file. An LMU file might contain strings in just one language or in multiple languages. When running the Locale Management Utility, you can choose to import only the strings for the languages that you are using in your installation. In the procedure, when you are prompted for the file to import, specify the name of the LMU file provided for the applicable language.

Note: Install Siebel CRM before you run the Locale Management Utility.

For more information about using the Locale Management Utility, see Using Siebel Tools and Siebel Global Deployment Guide.

To import strings and other locale-specific attributes into the repository

In Siebel Tools, choose Tools, then Utilities, and then Locale Management.
The Locale Management Utility appears.
Select a source language and a target language.
The source language is the language of the locale-specific data in the LMU file that you are importing. The target language is the Siebel language into which the strings will be imported.
Click the Import tab.
Enter the name of the LMU file from which you want to import locale-specific attributes.
You can also click Browse to find and select the file.
Specify whether you want to mark records in the repository with the Redo flag that have changed since the export occurred.
When the import occurs, the LMU compares the source language records in the repository with the source language records in the import file. If the records in the repository have changed since the export occurred, then they are marked with the Redo flag. This flag helps you identify records that might have to be retranslated.
Click Import.
After completing the import process, update the repository and deliver the updates, then restart the Application Object Manager component on the Siebel Server to see the results.

Related Books

Using Siebel Tools

Siebel Global Deployment Guide

Configuring Support for CalDAV or CardDAV Publishing

This topic provides information about configuring your Siebel CRM environment to support CalDAV or CardDAV publishing. CalDAV (Calendaring Extensions to WebDAV) is an internet standard designed to allow users to access and share calendar data on a remote server. CardDAV (vCard Extensions to WebDAV) is a client-server protocol designed to allow users to access and share address book or contact data on a server. These standards allow users to view external contact or calendar information in Siebel applications.

To enable CalDAV or CardDAV for your Siebel CRM deployment, the following requirements apply:

On the computer or operating system instance where you installed Siebel Application Interface, Transport Layer Security (TLS) must be configured. For more information, see Siebel Security Guide.
On the Siebel Server, the EAI component group must be enabled. For more information, see Configuring the Siebel Server. See also Siebel System Administration Guide and additional documentation on Siebel Bookshelf for Siebel Enterprise Application Integration.
In the Siebel CRM applications, valid email addresses must be associated with all Employees and Contacts. For each mobile user, the email address defined in Siebel CRM must match the user’s email address on the mobile device. For more information, see Siebel Mobile Guide: Connected or Siebel Mobile Guide: Disconnected. See also Siebel Applications Administration Guide.
Users of mobile devices must set up CalDAV or CardDAV publishing on their devices in order to be able to access calendar or contact data. For more information, see Siebel Mobile Guide: Connected or Siebel Mobile Guide: Disconnected.
Additional steps must be performed to enable dynamic mapping for CardDAV. Siebel CRM supports dynamic mapping for CardDAV on mobile devices running supported versions of iOS. CardDAV dynamic mapping defines the mapping between Siebel objects and the CardDAV properties. The Siebel CardDAV Sync module synchronizes the defined entities (address book and contact data) accordingly between a user’s mobile device and Siebel CRM applications.

Related Books

Siebel Security Guide

Siebel System Administration Guide

Siebel Mobile Guide: Connected

Siebel Mobile Guide: Disconnected

Siebel Applications Administration Guide

Inactivating Workflow Processes

As of Siebel CRM 20.7 Update, you can run the InactivateWFs.exe utility in development (Design Time Repository or DR) environments to inactivate workflow processes that are no longer required. The utility inactivates workflow processes that have not already been deployed or modified and which are not present in S_WFA_DPLOY_DEF (the old workflow deployment table). The InactivateWFs.exe utility inactivates workflow processess by setting the Inactive flag for the workflow processes to True and removes the corresponding compiled runtime object definition records. You might want to do this task after installing the current Siebel CRM 20.x Update release (and after running PostInstallDBSetup and related utilities). For more information about workflow processes, see Siebel Business Process Framework: Workflow Guide.

The following procedure describes how to inactivate workflow processes that are no longer required.

To inactivate workflow processes

Run the InactivateWFs.exe utility from the command line using values appropriate to your database. This utility is located in the siebsrvr\bin or Tools\bin directory. The syntax to use is as follows:

InactivateWFs.exe -s <InstallationPath> -t <SiebelTableOwner> -u <TableOwnerUsername> -p <Password> -o <ODBCDataSource>
-d <RDBMSPlatform> -r <RepositoryName> -k <LogDirectory>

For example, for Oracle Database:

InactivateWFs.exe -s "../ses/siebsrvr" -t SIEBEL -u SIEBEL -p ********** -o SIEBEL -d ORACLE -r "Siebel Repository" -k "../ses/siebsrvr/log"

For example, for Microsoft SQL Server:

 InactivateWFs.exe -s "..\ses\siebsrvr" -t dbo -u SIEBEL -p ********** -o Siebel_DSN -d MSSQL -r "Siebel Repository" -k "..\ses\siebsrvr\log"

For example, for DB2390:

InactivateWFs.exe -s "../ses/siebsrvr" -t SIEBEL -u SIEBEL -p ********** -o SIEBEL -d DB2390 -r "Siebel Repository" -k "../ses/siebsrvr/log"

Output appears that is similar to the following:

Stage 1 of 3 : Setting the Repository Id
Stage 2 of 3 : Find the WF data
Stage 3 of 3 : Delete the run time events
Inactivated Workflows : ../ses/siebsrvr/log/InactiveWFs_20200609_003106\InactivateWFs.out

If there are other errors, then review the log file(s) indicated in the error messages, resolve any issues, and then rerun the process.