Verifying and Troubleshooting Your Installation

This chapter provides information about verifying and troubleshooting your installation of Siebel CRM. It includes the following topics:

Verifying Installation for Siebel CRM

After installing the Siebel CRM software as a new installation or as a migration installation, review the installation log files, verify the version number of your installed software, and review the directories and files that now exist under the $SIEBEL_ROOT directory that you specified during the installation.

Note: Additional top-level directories are created, which are parallel to the directories for the Siebel Gateway, Siebel Server, and so on. Among others, these directories include applicationcontainer for files related to the application container (which, for example, includes the server.xml file), cfgtoollogs for installation log files, opatch for files related to the opatch utility, and oui for files related to Oracle Universal Installer.

In addition to the steps described in this topic and elsewhere, perform any other tasks that might be necessary for verifying that your Siebel CRM software is functioning correctly. At the minimum, first install and configure all of the key components, including the Siebel CRM software and the Siebel database, and perform the basic verification steps for each component.

For full verification that your installed Siebel CRM server environment is working correctly, you must start one of the Siebel CRM applications in a Web browser. Start a suitable browser, specify a valid URL for one of the Siebel applications that your deployment supports, and log in using valid user credentials. Then access various screens and views in the application and make sure that the application functions properly and that the necessary seed data is present. Try this for all of the Siebel applications and languages that your deployment must support. Additional testing considerations are outside the scope of this document.

The available applications include those for which server component groups were enabled on the Siebel Server and for which Siebel Application Interface configuration was done, using Siebel Management Console. For example, the URL for Siebel Call Center might resemble the following:

http://SiebelApplicationInterfaceHost.FQDN:Port/siebel/app/callcenter/lang

In this URL:

SiebelApplicationInterfaceHost is the host name for the installed Siebel Application Interface.
FQDN is the fully qualified domain name for your deployment. An example is example.com.

Note: It is strongly recommended to use the fully qualified domain name (FQDN) when you enter a URL, because security certificates are generally obtained based on fully qualified domain name.
Port is the HTTPS redirect port number for the installed Siebel Application Interface. You specified this HTTPS redirect port during Siebel Application Interface installation.
lang is the deployed language for the application you are running.

This topic contains the following information:

Reviewing the Installation Log Files

After installing the Siebel CRM modules, review the installation log files to verify that all of the modules installed successfully, particularly if you experienced any difficulties with the installation. The log files are created in the following directory:

$SIEBEL_ROOT/cfgtoollogs/oui

The relevant log files for an installation session are named installActionsdate_time.log file. In the file name, date_time represents the date and time when the file was created; for example, installActions2017-07-02_10-28-04PM.log. For each set of files created, the oldest and largest log file generally represents the Siebel CRM module being installed.

Reviewing the Log Files for the Siebel Application Interface

Siebel Application Interface generates one or more log files as a result of connection attempts with the Siebel Server. These log files reside in SIEBEL_AI_ROOT/log.

Depending on the logging level that you choose, these files record errors, warnings, and general information. Events such as invalid configuration of the Siebel Application Interface are captured in these log files. Analyzing the log files can provide clues for troubleshooting Siebel Application Interface problems.

Verifying That the Application Container Is Running

After installing one or more Siebel CRM modules using the Siebel Enterprise Server installer, verify that the application container is running. You can also check relevant log files, such as catalina.log, that are created in the following directory:

$SIEBEL_ROOT/applicationcontainer/logs

Also verify information about the application container stored in subdirectories. For example, the server.xml file, located in the conf subdirectory, can be checked to validate the HTTPS port number and other information for the installed application container.

Verifying That the Siebel Gateway Has Started

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

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
Operate any of the Siebel applications
Remove the configuration of a Siebel Application Interface, Siebel Server or the Siebel Enterprise (task 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.

To start the Siebel Gateway manually on Windows

Navigate to Control Panel, Administrative Tools, and then Services.
If the Siebel Gateway is not started, then click Action, and then Start.

Verifying the Installation Version Number for Siebel CRM

After installing the Siebel CRM modules, verify the version number of the installed software.

To verify the installation version number for Siebel CRM

Open a shell window.
Set the value of the ORACLE_HOME environment variable to correspond to your top-level installation location, such as /Siebel. For example, you might enter a command like this:
```
set ORACLE_HOME=/Siebel
```
Navigate to the opatch directory within your installation. For example, you might enter a command like this:
```
cd /Siebel/opatch 
```
Enter the following command:
```
opatch lsinventory -invPtrLoc inventory_location
```
In this command, inventory_location is the full path of the oraInst.loc file (for example, /export/home/oraInst.loc), which points to the OUI inventory location. Use the -invPtrLoc option if you want to specify an inventory pointer file other than the default.
The installed components within the specified Oracle home are displayed, with the version number as managed by Oracle Universal Installer. For example, the version number shown for your installed software might be 17.0.

Reviewing the Installation Directories for Siebel Gateway

After installing the Siebel Gateway, review the directory structure created by the installer.

The Siebel Gateway is installed in the $SIEBEL_GATEWAY_ROOT directory within the Siebel root directory that you specified during the installation. The installation location is /Siebel/gtwysrvr or a similar location. Verify that the following Siebel Gateway directories and files now exist in the installation directory. In the list, lang represents each language that you have installed, such as ENU for U.S. English.

gtwysrvr. Top-level directory for Siebel Gateway.
	admin. The template files used for scripts that control the running and configuration of the Siebel Gateway.
	bin. Siebel Gateway start script, stop script, and executable programs.
	cfgenv.csh. C shell variant of the Siebel script for setting environment variables on the server.
	cfgenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server.
	classes. Contains files used in the configuration process.
	EXTCACHE. Contains files used by the Siebel Enterprise Cache. (This directory is not used as of Siebel CRM 17.0, and is included for backward compatibility.)
	input. Contains files related to Siebel Remote.
	install_script. Contains files related to installation and configuration.
	lib. Siebel Gateway program library files.
	locale. Language-specific files and scripts. These are not configurable.
	log. Siebel Gateway log files.
	output. Contains files related to Siebel Remote.
	siebenv.csh. C shell variant of the Siebel script for setting environment variables on the server after you configure the Siebel Enterprise Server modules.
	siebenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server after you configure the Siebel Enterprise Server modules.
	sqltempl. An empty directory, initially. When you install the Siebel Server into the same root directory, that installation procedure populates this directory with SQL files, containing SQL templates that can be used to create SQL statements that the Siebel Server uses to perform specific database operations.
	sys. The backing files and service entry files used by the Siebel Gateway and server control utilities. Do not edit or modify these files, unless you are instructed to do so by Oracle Global Customer Support.
	temp. Stores temporary files generated by the Siebel Gateway.
	upgrade. Files and scripts related to version upgrades of Siebel CRM. Also holds temporary, backup, and state log files used during an upgrade.
	upgrade.log. File that contains information logged during an upgrade.
	zookeeper. Contains files used by Apache ZooKeeper, which maintains the Siebel Gateway registry.

Reviewing the Installation Directories for Siebel Server

After installing the Siebel Server, review the directory structure created by the installer.

The Siebel Server is installed in the$SIEBSRVR_ROOT directory within the Siebel root directory that you specified during the installation. The installation location is /Siebel/siebsrvr or a similar location. Verify that the following Siebel Server directories and files now exist in the installation directory. In the list, lang represents each language that you have installed, such as ENU for U.S. English.

siebsrvr. Top-level directory for Siebel Server.
	admin. The template files used for scripts that control the running and configuration of Siebel Server.
	bin. Binary file directory, containing executable programs, scripts, and language subdirectories related to language-specific server components. Also contains files used by Oracle Global Customer Support for installation workarounds.
	cfgenv.csh. C shell variant of the Siebel script for setting environment variables on the server.
	cfgenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server.
	classes. Contains files used in the configuration process.
	dbenv.csh. C shell variant of the Siebel script for setting environment variables on the server before you run the Siebel Database Configuration Wizard. You create this file by using the script CreateDbSrvrEnvScript before you first run the wizard. For more information, see Installing the Siebel Database.
	dbenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server before you run the Siebel Database Configuration Wizard. You create this file by using the script CreateDbSrvrEnvScript before you first run the wizard. For more information, see Installing the Siebel Database.
	dbtempl. Contains dictionary and local database files required by Siebel Remote for regional users and Mobile Web Client users.
	docking. Contains transaction files, visibility, and other databases required by Siebel Remote.
	enterprises. Files specific to a particular enterprise; contains a server subdirectory that contains files specific to a particular server (for example, log files).
	help. Contains help files.
	input. Contains files related to Siebel Remote.
	install. Contains files used by the installer.
	install_script. Contains files related to installation and configuration.
	IVSE.LIC. Merant ODBC Driver license file.
	ISSTEMPL.
	jre. Contains files for Java Runtime Environment.
	JSON. Contains JSON (JavaScript Object Notation) files.
	lex. Language-related files.
	lib. Library subdirectory. Contains the *.so files used in LDAP or other applications.
	locale. Contains language-specific files. These files are not configurable.
	log. Contains client and utility log files.
	msgtempl. Stores language-specific files for mail merge.
	mw. Contains MainWin binaries, libraries, and scripts that function as a Windows interface. For more information, see article 473791.1 (Article ID) on My Oracle Support. This document was previously published as Siebel FAQ 2240. See also Siebel System Administration Guide.
	output. Contains files related to Siebel Remote.
	plugins.
	reports. Contains the report executable programs used by Siebel Proposals to include reports in proposals.
	SDQConnector. Contains the DLLs, configuration files, and other files necessary to connect the Siebel Data Quality Universal Connector to one or more external data quality products. An external data quality product is validated though Oracle’s partner initiative.
	search. Contains the indexes and scripts used to administer and execute searches.
	siebenv.csh. C shell variant of the Siebel script for setting environment variables on the server after you run the Siebel Management Console.
	siebenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server after you run the Siebel Management Console.
	SMARTANSWER. Contains files related to Siebel Smart Answer.
	sqltempl. Contains SQL statements used by Siebel Server components. Do not modify these files.
	sys. The service entry files and .odbc.ini files used by the Siebel Server and server control utilities. Do not edit or modify these files, unless you are instructed to do so by Oracle Global Customer Support.
	tclient. Contains Web server-related files.
	temp. Stores temporary files for use by the Siebel Server.
	upgrade. Contains files and scripts related to version upgrades of Siebel CRM. Also holds temporary, backup, and state log files used during an upgrade.
	upgrade.log. File that contains information logged during an upgrade.
	xml.
	XMLP.
	xsd.
	XSLT.

Reviewing the Installation Directories for Siebel Database Configuration Utilities

After installing the Siebel Database Configuration Utilities, review the directory structure created by the installer.

The Siebel Database Configuration Utilities software is installed in the DBSRVR_ROOT directory within the Siebel root directory that you specified during the installation. The installation location is /Siebel/dbsrvr or a similar location. Verify that the following Siebel Database Configuration Utilities directories and files now exist in the installation directory. In the list, lang represents each language that you have installed, such as ENU for U.S. English.

dbsrvr. Top-level directory for Siebel Database Configuration Utilities.
	bin. Contains files for internal use.
	common. Contains database platform-independent files.
	DBSRVR_ROOT (oracle, db2udb, or db2390). Contains scripts specific to your database, including upgrade scripts for previous versions of Siebel CRM.
		dboutput (IBM DB2 for z/OS only). Contains subdirectories in which DDL is deposited by the installer for later transfer to the DB2 host when the Siebel Schema installation option Generate DDL Into Files is chosen.
		siebproc (IBM DB2 only). Contains User Defined Functions (UDFs) and stored procedures for IBM DB2, by operating system. See also Installing the Stored Procedures and User-Defined Functions on IBM DB2.
			aix. UDFs and stored procedures for IBM DB2 on AIX.
			hpux. UDFs and stored procedures for IBM DB2 on HP-UX.
			linux. UDFs and stored procedures for IBM DB2 on Linux.
			solaris. UDFs and stored procedures for IBM DB2 on Oracle Solaris.
			win32. UDFs and stored procedures for IBM DB2 on Windows.
		sqlproc (IBM DB2 only). Contains subdirectories that contain the SAR (stored procedure archive) files for each of the supported operating systems that are installed on the server. Contains subdirectories that contain the binary files that are required to install stored procedures. These stored procedures perform data migration as part of an upgrade.
			aix. Stored procedures for IBM DB2 on AIX.
			hpux. Stored procedures for IBM DB2 on HP-UX.
			linux. Stored procedures for IBM DB2 on Linux.
			solaris. Stored procedures for IBM DB2 on Oracle Solaris.
			win32. Stored procedures for IBM DB2 on Windows.
		storproc (IBM DB2 for z/OS only). Contains stored procedures for DB2 for z/OS.
		upgrade. Directories containing files to enable upgrading from specific versions of Siebel CRM that are supported for upgrade to the current release.
	LANG. Contains language-specific and database-specific files for the ancestor Siebel Repository and supporting files. For example, ENU contains language-specific files for U.S. English, and DEU contains language-specific files for German.
	files. This directory contains sample file attachments. You must copy these files to the appropriate subdirectory of the Siebel File System. See Populating the Siebel File System.
	locale. Contains translation files (for Oracle use only).

Reviewing the Installation Directories for the Siebel Application Interface

Review the physical directories created during the installation of the Siebel Application Interface to familiarize yourself with the locations of files relevant to its operation.

The following list shows some of the physical directories and files created after you install the Siebel Application Interface.

Siebel_AI. Top-level directory for Siebel Application Interface (example).
	applicationcontainer. Contains the file setenv.sh and other files and directories related to the application container for the installed Siebel software. Several of these files are updated by the installer at the end of the installation process and can be examined to help make sure that installation was successful.
		conf. Contains the file server.xml, which can be examined for information such as the HTTPS port number of the installed application container.
		webapps. Contains files for the Web applications supported by the application container, including properties files. The subdirectory `webapps/siebel` contains the default HTML file (default.htm) and also subdirectories such as `files`, `fonts`, `htmltemplates`, `images`, `scripts`, and `WEB-INF`. The `files` directory contains CSS files. `WEB-INF` contains files such as web.xml and log4j2-siebel.xml.
	applicationinterface.
	cfgtoollogs. Contains installation log files.
	config. Contains files related to configuration.
	diagnostics.
	inventory.
	jre. Contains files for Java Runtime Environment.
	manifest.
	OPatch. Contains files related to the `opatch` utility.
	oui. Contains files related to Oracle Universal Installer.
	cfgenv.csh. C shell variant of the Siebel script for setting environment variables on the server.
	cfgenv.sh. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server.
	install_script. Contains files related to installation and configuration.

Troubleshooting Installation and Configuration for Siebel CRM

This topic presents troubleshooting information related to installation and configuration of Siebel CRM server modules. Some of the information also applies to additional modules that use the same installer and are also configured using Siebel Management Console, such as Siebel Enterprise Cache and Siebel Constraint Engine.

This topic includes the following information:

Troubleshooting Installation and Configuration for the Siebel Gateway

This topic describes potential errors that can result from a faulty installation or configuration of Siebel Gateway. Such problems can have any of several causes, some of the most common of which are listed in Troubleshooting Installation and Configuration for the Siebel Gateway.

Note: If you cannot start the Siebel Gateway, then you will not be able to configure a Siebel Enterprise or configure and start a Siebel Server.

Table Troubleshooting Siebel Gateway Installation and Configuration

Problem Cause Solution

Problem	Cause	Solution
(AIX, HP-UX, and Oracle Solaris only) In a migration installation of Siebel Gateway, the postinstallation profile creation step fails. The cloudgateway.log file contains an exception error. In some cases, an error might have occurred in updating the CGHostURI entry in the cloudgateway.properties file. See also Troubleshooting Installation and Configuration for the Siebel Server.	The Siebel Application Interface might not have been available when it was required for the configuration process.	Try the following: Clear the CGHostURI entry in the applicationinterface.properties file for Siebel Application Interface, in `SIEBEL_AI_ROOT/applicationcontainer/webapps`. Restart the application container for Siebel Application Interface, as described in Stopping and Starting the Siebel Application Container. Restart Siebel Gateway migration installation.
The Siebel Gateway does not start.	You might not have privileges as the Siebel service owner.	Review the instructions in Creating the Siebel Service Owner Account.
The Siebel Gateway does not start.	Failure to start the Siebel Gateway can be caused by a number of problems including, but not limited to: Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable Incorrect permissions set on shared libraries Missing shared libraries	Use the `ldd` command to show missing libraries. Make sure that `$SIEBEL_HOME/lib` is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set `$SIEBEL_HOME/lib` as the first element of the shared library path environment variable. Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), and siebenv.csh or siebenv.sh. Make sure that all files were correctly generated.

(AIX, HP-UX, and Oracle Solaris only)

In a migration installation of Siebel Gateway, the postinstallation profile creation step fails.

The cloudgateway.log file contains an exception error.

In some cases, an error might have occurred in updating the CGHostURI entry in the cloudgateway.properties file.

The Siebel Application Interface might not have been available when it was required for the configuration process.

Try the following:

Clear the CGHostURI entry in the applicationinterface.properties file for Siebel Application Interface, in SIEBEL_AI_ROOT/applicationcontainer/webapps.
Restart the application container for Siebel Application Interface, as described in Stopping and Starting the Siebel Application Container.
Restart Siebel Gateway migration installation.

The Siebel Gateway does not start.

You might not have privileges as the Siebel service owner.

Review the instructions in Creating the Siebel Service Owner Account.

The Siebel Gateway does not start.

Failure to start the Siebel Gateway can be caused by a number of problems including, but not limited to:

Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable
Incorrect permissions set on shared libraries
Missing shared libraries

Use the ldd command to show missing libraries.

Make sure that $SIEBEL_HOME/lib is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set $SIEBEL_HOME/lib as the first element of the shared library path environment variable.

Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), and siebenv.csh or siebenv.sh.

Make sure that all files were correctly generated.

Troubleshooting Installation and Configuration for the Siebel Server

This topic describes potential errors that can result from a faulty installation or configuration of Siebel Server. Such problems can have any of several causes, some of the most common of which are listed in the following table.

Table Troubleshooting Siebel Server Installation and Configuration

Problem	Cause	Solution
The Siebel Server cannot be installed.	Insufficient user privileges	For information about setting up appropriate administrative user privileges to install, see Setting Permissions and Ownership and Creating the Siebel Service Owner Account.
	Trying to install or configure the Siebel Server out of sequence	For the required installation and configuration sequence, see Overview of Installing Siebel CRM.
	Failure to install required hardware or software	Installation errors related to software requirements are logged in the Siebel Enterprise Server installer log file. For requirements, see the Certifications tab on My Oracle Support.
	Environment variables not set properly	For more information about environment variables, see Managing Environment Variables.
	Faulty network connection	Sometimes a faulty network connection can result in the system administrator being unable to install to the `$SIEBEL_HOME` directory in which he or she has write privileges. Verify that your network connection is stable.
The Siebel Server does not start.	Failure to start the Siebel Server can be caused by a number of problems including, but not limited to: Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable Incorrect permissions set on shared libraries Missing shared libraries	Use the `ldd` command to show missing libraries. Make sure that `$SIEBEL_HOME/lib` is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set `$SIEBEL_HOME/lib` as the first element of the shared library path environment variable. Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell), siebenv.csh or siebenv.sh, and dbenv.csh or dbenv.sh. Make sure that all files were correctly generated.
Application Object Manager component does not start.	Heavily used servers running more than 50 instances of Object Manager components can experience a condition where some of the Object Managers do not start correctly and log the following error message: Got error 1801210 when dequeuing a connection request (62)	Change TCP stack parameters. For more information about sizing Application Object Manager components, see Siebel Deployment Planning Guide, Siebel Performance Tuning Guide, and other relevant documents on Oracle Technology Network or My Oracle Support.
The Siebel Server does not start after configuration.	Siebel Gateway not started	Verify that the Siebel Gateway was started. Start it if it was stopped.
	Invalid input values for Siebel Server profile creation and deployment	Verify that the input values were valid.
	Insufficient system privileges	Verify that you have sufficient system privileges to start the service. For more information, see Creating the Siebel Service Owner Account.
Cannot save a new profile in Siebel Management Console.	The specified profile name might already exist.	Provide a unique name for the new profile and retry saving the profile.
URL does not bring up Siebel Management Console.	Installations might not have been correctly performed. Security certificates might not be valid, as configured. You might have specified an incorrect port number in the URL. Other causes might apply.	Verify the following: The installations were correctly performed, Valid security certificates were used, and the security authentication system is available The Siebel Application Interface application container is running The URL is correct and includes the correct HTTP or HTTPS port See also Troubleshooting Installation and Configuration for Siebel Application Interface. For security issues, see also Siebel Security Guide.
URL does not bring up login page for a Siebel application. Cannot log in to a Siebel application.	Configuration of Siebel Server or Siebel Application Interface might not have been correctly performed or completed. Siebel database information might have been specified incorrectly. The Application Object Manager might not have been enabled on the Siebel Server. You might have specified an incorrect port number in the URL. You might have added components on a new Siebel Server, but neglected to update the Siebel Application Interface profile. Siebel system services might not be running. You might be experiencing problems with the security authentication system you are using. Other causes might apply.	Verify the following: The installations and configurations were correctly performed, and database information was specified correctly Security authentication was correctly configured and the security authentication system is available The Siebel Application Interface application container is running The Siebel Gateway and Siebel Server services are running The URL is correct and includes the correct HTTP or HTTPS port See also Troubleshooting Installation and Configuration for Siebel Application Interface. For security issues, see also Siebel Security Guide.

Troubleshooting Installation and Configuration for Siebel Application Interface

This topic provides suggestions for troubleshooting problems that you might encounter when installing and configuring the Siebel Application Interface.

Typical problems are shown in the following table.

Table Troubleshooting Siebel Application Interface Installation and Configuration

Problem	Cause	Solution
Siebel Application Interface profile deployment fails despite no obviously incorrect profile values.	The application container might not have been available to support the configuration process.	Try the following: Clear the CGHostURI entry in the applicationinterface.properties file, in `SIEBEL_AI_ROOT/applicationcontainer/ webapps`. Restart the application container, as described in Stopping and Starting the Siebel Application Container. Deploy Siebel Application Interface again.
The Siebel Application Interface does not start.	Failure to start the Siebel Application Interface can be caused by a number of problems including, but not limited to: Incorrectly set LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable Incorrect permissions set on shared libraries Missing shared libraries	Use the `ldd` command to show missing libraries. Make sure that `$SIEBEL_HOME/lib` is included and set before LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris). If there are library conflicts, then set `$SIEBEL_HOME/lib` as the first element of the shared library path environment variable. Check the LIBPATH, SHLIB_PATH, or LD_LIBRARY_PATH settings in all applicable files, including cfgenv.csh (for C shell) or cfgenv.sh (for Bourne or Korn shell).
After installation, when the Siebel Web Client is started, a message appears, stating: Page Cannot be displayed	The application container is not running.	Make sure that the application container is running. Refresh the connection between your browser and the Siebel Application Interface.
	The Siebel Application Interface port is incorrectly specified.	Verify that the Siebel Application Interface port information is correct.
	Applications were not configured properly.	Make sure that the Local Path for the configured applications is correct and resembles the following: SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel
	Anonymous users have incorrect responsibilities.	Make sure that the specified anonymous users are also defined in the Siebel database with the correct responsibilities. Otherwise, end users cannot access the home page.
	The connect string for the Siebel application is incorrect.	Make sure that the connect string for the Siebel application is correct. The value resembles the following example: ConnectString = siebel.TCPIP.none.none://SiebelServerHost:2321/ EnterpriseServerName/ProductNameObjMgr_language
	Siebel Server components or component groups might not be enabled.	Make sure that the necessary Siebel Server components and component groups are enabled.
Your Siebel application stops responding, displays a blank page or page not found, or times out.	Appropriate settings are not available within the application configuration defined in the profile for the Siebel Application Interface.	Make sure that the configuration contains valid anonymous user and port number values. Also make sure that appropriate values were specified for session time-out and guest session timeout. For information about configuring these and other settings, see Creating a Siebel Application Interface Profile.
Inability to access the Siebel Web Client. The browser status bar might display errors such as: SWESubmitOnEnter is undefined Also, the login page might stop responding. Or, the Siebel Web Client login page does not display properly; for example, images might be missing.	The user account running the Siebel Application Interface does not have proper permissions to the `SIEBEL_AI_ROOT/applicationcontainer/webapps/siebel` directory.	Stop the Siebel Application Interface. Make sure that the permissions meet the requirements described in Requirements for Installing and Configuring the Siebel Application Interface. Restart the Siebel Application Interface, as described in Stopping and Starting the Siebel Application Container.

Verifying the ODBC Data Source

This topic provides information about verifying the ODBC data source for your enterprise database platform. It includes the following information:

Verifying the ODBC Data Source for Oracle Database

Configuring the Siebel Enterprise automatically creates an ODBC system data source name (DSN) that the Siebel Server uses to connect to the Siebel database on the RDBMS.

Make sure that a supported version of the Oracle Database Client has been installed and that the Siebel Server service is started prior to verifying the ODBC data source. This topic applies also to virtual ODBC data sources in a clustered environment.

Caution: In general, do not change the default settings that are created automatically with the ODBC data source. However, if you have upgraded from an Oracle Database that does not use CBO, or if you manually created your ODBC, then you must check your ODBC settings, as shown in the following procedure.

To verify the ODBC data source for Oracle Database (on UNIX)

Navigate to the file $SIEBEL_HOME/sys/.odbc.ini, and open this file for editing.
Locate the section of the file containing a reference to ServerName and Driver.
This section defines the ODBC data source for Siebel Server. A sample section is represented in the following example:
```
[SiebelEnterpriseName_DSN]
ServerName=oraDB4
Driver=$SIEBEL_HOME/lib/SEor827.so
ColumnsAsChar=1
ColumnSizeAsCharacter=1
```
Caution: The ColumnsAsChar and ColumnSizeAsCharacter parameter settings are required in order for the ODBC driver to behave correctly.
ServerName is the Oracle connect string that you entered while configuring the Siebel Enterprise. (To verify this connect string, run sqlplus.) The driver must point to $SIEBEL_HOME/lib/SEor827.so, allowing you to verify the existence of this file.
Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to ORACLE.

Note: If you use Siebel Marketing, which requires simultaneous heterogeneous database connectivity, then set this variable to ORACLE, regardless of your database platform.
Source the siebenv.csh (for C shell) or siebenv.sh (for Bourne or Korn shell) file.
Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:
```
odbcsql /u database_account_name /p password /s ODBC_DSN
```
where:
- database_account_name is a valid database account name.
- password is the corresponding database account password.
- ODBC_DSN is the ODBC data source name, in the form SiebelEnterpriseName_DSN. In the data source name, SiebelEnterpriseName is the name of your Siebel Enterprise.
If you do not receive an error message, then the ODBC connection is working. If your ODBC DSN is not working, then the program exits with an error message. For more information, see Verifying Network Connectivity for the Siebel Server Computer and Troubleshooting the ODBC Data Source Connection.

Verifying the ODBC Data Source for IBM DB2

Configuring the Siebel Enterprise automatically creates an ODBC system data source name (DSN) that the Siebel Server uses to connect to the Siebel database on the RDBMS.

Make sure that the appropriate database client has been installed and that the Siebel Server service is started prior to verifying the ODBC data source. This topic applies also to virtual ODBC data sources in a clustered environment.

Do not change the default settings that are created automatically with the ODBC data source.

Caution: Do not change the default settings that are created automatically with the ODBC data source.

Note: For information about verifying the ODBC data source for IBM DB2 for z/OS, see Implementing Siebel Business Applications on DB2 for z/OS.

To verify the ODBC data source for IBM DB2 (on UNIX)

Open a DB2 Command Window.
Run the following command:
```
db2 get cli cfg for section SiebelEnterpriseName_DSN
```
In the data source name, SiebelEnterpriseName is the name given the Siebel Enterprise during initial configuration, for example sieb17.
Entering this command generates the following results:
```
Section: SiebelEnterpriseName_DSN
------------------------------------------------- 
dbalias=SBL 
clipkg=6 
txnisolation=1 
```
The value for dbalias is the database alias catalogued for your DB2 database server.
If the SiebelEnterpriseName_DSN section is missing, then run the configdb2 script in $SIEBEL_HOME/bin to set it, and then verify again that the section is present.
See also Guidelines for Preventing IBM DB2 from Running Out of ODBC Statement Handles.
Verify that the SIEBEL_UNIXUNICODE_DB environment variable is set to DB2.
Note: If you use Siebel Marketing, which requires simultaneous heterogeneous database connectivity, then set this variable to ORACLE, regardless of your database platform.
Source the siebenv.csh (for C shell) or siebenv.sh (for Bourne or Korn shell) file.
Test the connection by navigating to $SIEBEL_HOME/bin and entering the command:
```
odbcsql /u database_account_name /p password /s ODBC_DSN
```
where:
- database_account_name is a valid database account name.
- password is the corresponding database account password.
- ODBC_DSN is the ODBC data source name, in the form SiebelEnterpriseName_DSN. In the data source name, SiebelEnterpriseName is the name of your Siebel Enterprise.
If you do not receive an error message, then the ODBC connection is working.
If your ODBC DSN is not working, then the program exits with an error message. For more information, see Verifying Network Connectivity for the Siebel Server Computer and Troubleshooting the ODBC Data Source Connection.

Troubleshooting the ODBC Data Source Connection

This topic describes troubleshooting steps for your ODBC data source connection.

Note: If your database is IBM DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS.

This topic has the following information:

Troubleshooting Connection Problems on Oracle Database

Complete the following instructions to troubleshoot Oracle Database connection problems on AIX, HP-UX, Linux, or Oracle Solaris. See also Configuring Siebel Server Connectivity to the Siebel Database.

If you are unable to verify if your ODBC connection to your Oracle Database is working, then verify that the value of the environment variable TNS_ADMIN is the exact path of tnsnames.ora.

To troubleshoot a failed ODBC connection for Oracle Database (on AIX, HP-UX, Linux, or Oracle Solaris)

Verify that the Oracle connect string entered as part of Siebel Enterprise configuration is valid.
If the connect string entered is correct, then check the ODBCINI environment variable to verify that it was set by entering the following command:
```
echo ${ODBCINI}
```
The following response appears:
```
$SIEBEL_ROOT/sys/.odbc.ini
```
If the ODBCINI environment variable was correctly set, then verify that the .odbc.ini file is valid by reviewing it for the presence of the following parameters:
```
[SiebelEnterpriseName_DSN]
ServerName=oraDB4
Driver=$SIEBEL_ROOT/lib/SEor827.so
ColumnsAsChar=1
ColumnSizeAsCharacter=1
```
Note: The ColumnsAsChar and ColumnSizeAsCharacter parameter settings are required in order for the ODBC driver to behave correctly.
If the .odbc.ini file is valid, then verify that the library path includes the path for the ODBC driver on your operating system by entering the following command:
AIX. Use echo ${LIBPATH}.
HP-UX. Use echo ${SHLIB_PATH}.
Linux and Oracle Solaris. Use echo ${LD_LIBRARY_PATH}.
The following response appears:
```
$SIEBEL_HOME/lib
```
Note: Siebel CRM supports the Oracle 32-bit client. Therefore, if you have installed the Oracle 64-bit client on your Siebel Server, then you must include $ORACLE_HOME/lib32 in your definition for the LIBPATH (AIX), SHLIB_PATH (HP-UX), or LD_LIBRARY_PATH (Linux or Oracle Solaris) environment variable. (If you require $ORACLE_HOME/lib for non-Siebel applications, then make sure that $ORACLE_HOME/lib32 is placed in front of $ORACLE_HOME/lib.)
If the response illustrated for your operating system in Troubleshooting Connection Problems on Oracle Database was correct and you are verifying a Unicode installation, then make sure that the following environment variable is set according to the recommendations from your database platform vendor.
```
SIEBEL_UNIXUNICODE_DB=ORACLE
```
This variable is also set in the siebenv.csh (for C shell) and siebenv.sh (for Bourne or Korn shell) scripts.

Troubleshooting Connection Problems on IBM DB2

Complete the following instructions to troubleshoot IBM DB2 connection problems. See also Configuring Siebel Server Connectivity to the Siebel Database.

To troubleshoot a failed ODBC connection for IBM DB2

Verify that the data source name (SiebelEnterpriseName_DSN) that you entered during the Siebel Server configuration was valid. Also verify that the required IBM DB2 client version is available on the computer and verify that the IBM DB2 catalog step has been completed correctly.

Verifying Installation for the Siebel Database

After installing the Siebel database on the RDBMS using the Siebel Database Configuration Wizard, review the installation log files and the system preferences for the database code page. This topic has the following information:

Reviewing the Installation Log Files for the Siebel Database

Installing Siebel database components on the RDBMS creates several log files within the $SIEBEL_ROOT/log subdirectory. You must review the files in this subdirectory for any errors.

For example, log files created might be named srvrupgwiz1.log (the most recently created), srvrupgwiz1_01.log, srvrupgwiz1_02.log, and so.

Note: For information about reviewing log files using the logparse utility, see Siebel Database Upgrade Guide. This utility is located in $SIEBSRVR_ROOT/bin.

Some other files generated, by supported RDBMS, are listed as follows.

Oracle Database. For Oracle Database, the following log files are also generated when you create tables, indexes, and seed data:

ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
ddlseq.log
ddlora.log
ddlview.log
ddlview_sia.log
seedssa.log
seedver.log
pkgseq.log
pkgldel.log
seedora.log
pkgvis.log
trgreset.log
ifstrg.log
ifindxstrg.log
set_utc_on.log
month_fn.log

IBM DB2. For IBM DB2, the following log files are also generated when you create tables, indexes, and seed data:

ddl_ctl.log
dataimp_prim.log
dataimp_prim_lang.log
db2ddl.log
siebproc.log
seeddb2.log
seedver.log
seedssa.log
ddlview.log
ddlview_sia.log
grantstat.log
updatestats.log
loadstats.log
set_utc_on.log

Verifying System Preferences and Settings for the Database Code Page

After you complete installing Database Configuration Utilities and installing the Siebel database, you must verify system preferences and other settings for the Siebel application that indicate whether you are using Unicode, and indicate the code page that you are using.

For more information about code pages, see Planning RDBMS Installation and Configuration. For Siebel CRM language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

The following procedure assumes that you have already installed Siebel Tools.

For information about installing Siebel Tools, see Installing Siebel Tools.
For information about starting Siebel Tools, see Verifying Successful Installation of Siebel Tools.

To verify system preferences and settings for the database code page

Start Siebel Tools and connect to the Siebel database.
Navigate to Screens, System Administration, and then System Preferences.

Look for System Preference Name = Enterprise DB Server Code Page. Verify that the value has been set correctly, based on the value that you selected during the installation of the Siebel database components (see Installing the Siebel Database).

Note: The value of Enterprise DB Server Code Page must be in lowercase, for example, utf-8 or utf-16. An Oracle Database character set might have a different value, although the system preference value must be utf-8. The utf-16 code page is also known as UCS-2, although the system preference value must be utf-16.

Possible values for the system preference are listed in the following table:

Language	Database	Value
All	Oracle Database	utf-8 (for Unicode)
All	IBM DB2	utf-16 (for Unicode)
Japanese	Oracle Database, IBM DB2	cp932 (or equivalent)
Western European	All	cp1252 (or equivalent)

Verify that the column UNICD_DATATYPS_FLG in the table S_APP_VER is set correctly. The flag value must be in uppercase.

Possible values for UNICD_DATATYPS_FLG are listed in the following table:

Code Page	Database	Value
Non-Unicode code page	All	N
Unicode	Oracle Database	8
Unicode	IBM DB2	Y

To specify that you are using an EBCDIC code page

As of Siebel CRM 20.6 Update, if you are using an EBCDIC code page for DB2 on z/OS, then you must set the EBCDICCodePage enterprise parameter to specify that you are using this type of code page. This advanced parameter replaces the system preference of the same name, which was introduced in Siebel CRM 19.10 Update.

Note: This parameter changes the sort order to ASCII in your EBCDIC database. The parameter prevents intermittent workspace delivery failures related to the sort order of WS_SRC_ID records.

To set this parameter, run Server Manager and enter a command like the following for the enterprise:

change entparam EBCDICCodePage=TRUE

If you are using Siebel Tools, then set this parameter in the [Siebel] section of the tools.cfg file, as follows:

[Siebel]
EBCDICCodePage=TRUE

Troubleshooting Installation for the Siebel Database

These topics provide suggestions for troubleshooting problems that you might encounter when installing and configuring the Siebel database. This topic contains the following information:

Troubleshooting Installation for the Siebel Database

Typically, problems during database installation result from insufficient storage space having been allocated, or from the installer having improper user privileges.

Acceptable Errors for Installation of the Siebel Database

The log files might include errors that are expected and benign. Compare any error messages found in the log files to the sample error messages in the errors.txt file, which is located in the installation subdirectory for your database, for example, oracle. If a log file is not listed in the errors.txt file, then there are no acceptable error messages for that log file. No further action is required if the log files contain errors listed in the errors.txt file.

Note: Only one of each type of error occurring in a particular log file appears in the errors.txt file.

If you find errors that are not listed in the errors.txt file, then correct the condition that caused the errors, and rerun the Upgrade Wizard. The wizard restarts from the point where it left off.

Do not review only the error numbers because these might have changed following installation of a new driver version. Instead, compare the error descriptions to find out which are acceptable errors for this database.

Caution: Although other errors are rarely encountered, this review is critical. Certain errors, such as a failure to create indexes, might result in performance problems or anomalous behavior in Siebel applications.

You can view a log summary generated using the logparse utility. For more information, see Siebel Database Upgrade Guide.

Troubleshooting Siebel Repository Import for the Siebel Database

Typical problems that can occur at this stage are shown in the following table. These errors might appear in the log files produced by the Siebel Repository import process.

Table Troubleshooting Siebel Repository Import for the Siebel Database

Problem	Cause	Solution
Cannot import a Siebel Repository	Importing a Siebel Repository with the same name as an existing Siebel Repository	Choose a unique name for the new Siebel Repository.
Database runs out of tablespace pages and cannot allocate new data pages	Insufficient tablespace size	Increase the tablespace sizes.
(IBM DB2 only) Errors regarding the settings for DB2 configuration parameters, such as APP_CTL_HEAP_SZ	Values too low	Reset the DB2 configuration parameters to higher values. Guidelines for Siebel CRM suggest using only minimum values.

Verifying Installation for Siebel Tools

After installing Siebel Tools, as a new installation or as a migration installation, review the installation log files, verify the version number of your installed software, and review the Siebel Tools directories and files that now exist under the SIEBEL_TOOLS_ROOT directory that you specified during the installation.

This topic contains the following information:

Reviewing the Installation Log Files for Siebel Tools

After installing Siebel Tools, review the installation log files to verify that all of the components installed successfully, particularly if you experienced any difficulties with the installation. The log files are created in the following directory:

SIEBEL_TOOLS_ROOT\cfgtoollogs\oui

The relevant log files for an installation session are named installActionsdate_time.log file. In the file name, date_time represents the date and time when the file was created; for example, installActions2017-07-02_10-28-04PM.log. For each set of files created, the oldest and largest log file generally represents the Siebel CRM module being installed (such as Siebel Tools).

Verifying the Installation Version Number for Siebel Tools

After installing Siebel Tools, verify the version number of the installed software.

To verify the installation version number for Siebel Tools

Open a DOS window.
Set the value of the ORACLE_HOME environment variable to correspond to your installation location, such as C:\Siebel\Tools. For example, you might enter a command like this:
```
set ORACLE_HOME=C:\Siebel\Tools
```
Navigate to the opatch directory within your installation. For example, you might enter a command like this:
```
cd C:\Siebel\Tools\opatch
```
Enter the following command:
```
opatch lsinventory
```
Installed components within the specified Oracle home are displayed, with the version number as managed by the Oracle Universal Installer software. For example, the version number of an installation of Siebel CRM 17.0 is shown as 17.0.

Reviewing the Installation Directories for Siebel Tools

The following minimum directories are created for a Siebel Tools installation. These directories, the files and subdirectories they contain, and various other files are created in the directory that you specified during the installation, such as C:\Siebel\Tools. Use Windows Explorer to verify the directory structure on your computer. In the list, lang represents each language that you have installed, such as ENU for U.S. English.

SIEBEL_TOOLS_ROOT. The directory for the Siebel Tools installation, such as C:\Siebel\Tools (or a similar location). This installation directory contains the subdirectories identified here. You can change the name during the installation process. For more information, see Requirements for Installing Siebel Tools.

bin	All binary files (.exe, .dll, .cfg, .dsn, .enu, .bat), configuration files, and user preference files.
	lang	Language-specific DLL files.
	dll	Siebel Tools program library files.
	bin	Siebel Tools binary files.
	exe	Siebel Tools executable files.
cfgtoollogs	Contains installation log files.
classes	Java code files.
	examples
	examples\src
	examples\src\com
	examples\src\com\siebel
	examples\src\com\extra
	examples\src\com\integration
	examples\src\com\integration\mq	Examples of Java code files.
	examples\src\com\integration\servlet	Examples of Java code files.
help	Siebel Tools help files.
	lang	Help files for the language that you installed.
locale	Text files for installed languages containing version information.
log	Log files from Siebel Tools operations.
msgtempl	Message files.
opatch	Files used by the `opatch` utility.
public	Contains the default HTML file (default.htm) and also subdirectories such as `files`, `fonts`, `htmltemplates`, `images`, and `scripts`. CSS files are located in the `files` directory, for example.
reppatch	Location of the XML files used by the maintenance update wizard. All log files generated by this wizard are also created under `reppatch\log`.
scripts	Location of Java scripts.
sqltempl	SQL statement fragments used by certain Siebel Tools operations.
temp	Temporary working area.
upgrade	Not used for Siebel Tools.

Verifying Successful Installation of Siebel Tools

After installing Siebel Tools, verify that installation was successful by starting Siebel Tools and connecting to the Siebel database.

To verify that the Siebel Tools installation completed successfully

Start Siebel Tools and log in to the Siebel database.

Verifying Directory Permissions for Siebel Tools

After installing Siebel Tools, verify that the Siebel Tools user has sufficient permissions to read and write data to the Siebel Tools installation directory.

To verify directory permissions for Siebel Tools

Select the Siebel Tools root directory and right-click on it.
Choose Properties and go to the Sharing tab.
Make sure that the Siebel Tools user has read and write access.

In addition, in user account properties, the Siebel Tools user must not be defined as a restricted user in the group membership section.

Verifying the ODBC Data Sources for Siebel Tools

The Siebel Tools installer creates the ODBC data sources described in the following table. By default, these are created as system data sources, which are visible to all of the user accounts on the computer where Siebel Tools is installed.

Table Siebel Tools ODBC Data Sources

Data Source	Use
SSD default instance	Connects to the Oracle Database.
SSD	Connects to the IBM DB2 database.

For Oracle Database, verify that the following registry keys are set as shown. These values are required in order for the ODBC driver to behave correctly.

PacketSize = 0
EnableScrollableCursors = 0
ColumnsAsChar = 1
ColumnSizeAsCharacter = 1

For more information about how to run the Microsoft ODBC Administrator to verify ODBC data sources, see Verifying the ODBC Data Source. Consult this topic as it is presented in Siebel Installation Guide for Microsoft Windows. See also Requirements for Installing Siebel Tools.

Verifying Installation for the Siebel Web Client

After installing the Siebel Web Client software as a new installation or as a migration installation, review the installation log files, verify the version number of your installed software, and review the Siebel Web Client directories and files that now exist under the SIEBEL_CLIENT_ROOT directory that you specified during the installation.

This topic contains the following information:

Reviewing the Installation Log Files for the Siebel Web Client

After installing the Siebel Web Client software, review installation log files to verify that all of the components installed successfully, particularly if you experienced any difficulties with the installation. The log files are created in the following directory:

SIEBEL_CLIENT_ROOT\cfgtoollogs\oui

The relevant log files for an installation session are named installActionsdate_time.log file. In the file name, date_time represents the date and time when the file was created; for example, installActions2017-07-02_10-28-04PM.log. For each set of files created, the oldest and largest log file generally represents the Siebel CRM module being installed, such as Siebel Web Client.

This topic applies to the Siebel Web Client installation, optionally with the local database or sample database.

Verifying the Installation Version Number for the Siebel Web Client

After installing the Siebel Web Client software, verify the version number of the installed Siebel Web Client software.

This topic applies to the Siebel Web Client installation, optionally with the local database or sample database.

To verify the installation version number for the Siebel Web Client

Open a DOS window.
Set the value of the ORACLE_HOME environment variable to correspond to your installation location, such as C:\Siebel\Client. For example, you might enter a command like this:
```
set ORACLE_HOME=C:\Siebel\Client
```
Navigate to the opatch directory within your installation. For example, you might enter a command like this:
```
cd C:\Siebel\Client\opatch
```
Enter the following command:
```
opatch lsinventory
```
Installed components within the specified Oracle home are displayed, with the version number as managed by the Oracle Universal Installer software. For example, the version number of an installation of Siebel CRM 17.0 is shown as 17.0.

Reviewing the Installation Directories for the Siebel Web Client

The following minimum directories are created for a Siebel Web Client installation. These directories, the files and subdirectories they contain, and various other files are created in the directory that you specified during the installation, such as C:\Siebel\Client. Use Windows Explorer to verify the directory structure on your computer.

SIEBEL_CLIENT_ROOT. The directory for the Siebel Web Client installation, such as C:\Siebel\Client (or a similar location). This installation directory contains the subdirectories identified here. You can change the name during the installation process. For more information, see Requirements for Installing Siebel Web Clients.

bin. Contains all of the binary files (*.exe, *.dll, and so on), configuration files (*.cfg), user preference files, and language-specific files.

cfgtoollogs. Contains installation log files.

fonts. Contains font files.

lex. Contains dictionary files used by the spelling checker.

local. Where the local database is stored.

locale. Stores language-specific files.

log. Stores the log files from Siebel Web Client operations, such as synchronization.

msgtempl. Stores message files used by the Siebel Web Client.

opatch. Contains files used by the opatch utility.

oraclese. The installation path for Oracle Database SE2. This directory is created if you have installed that module for the local database, as described in Installing and Using Oracle Database SE2 for the Local Database.

public. Contains the default HTML file (default.htm) and also subdirectories such as files, fonts, htmltemplates, images, and scripts. CSS files are located in the files directory, for example.

sqltempl. Contains SQL scripts. Do not modify these files.

temp. Contains working report files.

upgrade. Contains Siebel Anywhere upgrade files that have been retrieved by the user.

Verifying ODBC Data Sources for the Siebel Developer Web Client

Verification of ODBC data sources for the Siebel Developer Web Client is similar to that for Siebel Tools. For information, see Verifying the ODBC Data Sources for Siebel Tools.

Verifying Installation for Oracle Database SE2

Oracle Database SE2 is installed with Siebel Mobile Web Client. You can verify the existence of or the successful installation of Oracle Database SE2 in multiple ways. This topic includes the following information:

Verifying Installation of Oracle Database SE2

Use the following methods to verify the installation of Oracle Database SE2 for Siebel Mobile Web Client. Also perform the other verification steps in this topic. See also the documentation for Oracle Database Standard Edition 2 (Oracle Database SE2) on Oracle Help Center.

To verify installation of Oracle Database SE2

Do any or all of the following:
- Open SERVICES.MSC and check for OracleServiceSE.
- Open Programs and Features and check for Oracle Database SE2 under installed programs.
- Check for the presence of the oraclese directory in the Siebel Mobile Web Client installation.
- Open the install.log file, which is available under the %temp% folder. Make sure that [ResultCode] is set to zero.
- Run the command below to find the entry for Oracle Database SE2 in the registry:
```
reg query HKLM\SOFTWARE\ORACLE\KEY_SE /v ORACLE_BASE
```
- Start Siebel Mobile Web Client and connect to the LOCAL_SE data source.
Note: Connecting to LOCAL_SE for the first time initializes the local database. Users must attempt this only after a local database has been extracted for them by the system administrator.

Verifying the ODBC Data Source for Oracle Database XE

Installing Oracle Database SE2 with Siebel Mobile Web Client automatically creates an ODBC system data source name (DSN) that Siebel Mobile Web Client uses to connect to an Oracle Database SE2 installation. The ODBC data source is LOCAL_SE for a Siebel Mobile Web Client installation, with the local database using Oracle Database SE2.

To verify the ODBC data source for Oracle Database SE2

Open ODBCAD32.exe, which is available in the C:\Windows\SysWOW64 directory.
Check that one of the following ODBC data sources has been added under the System DSN tab, corresponding to your installation: LOCAL_SE.
Make sure that the DSN connects.

Verifying the TNSNAMES.ORA Entry for Oracle Database SE2

Use the following procedure to verify the TNSNAMES.ORA entry for Oracle Database SE2.

To verify the TNSNAMES.ORA entry for Oracle Database SE2

Open TNSNAMES.ORA, which is available under Oracle_DB_Client\network\admin.
Verify that a new entry of LOCAL_SE has been added.

Verifying Network Connectivity for the Siebel Server Computer

The Siebel Server must have network access to other Siebel CRM modules, such as the Siebel Gateway, the Siebel Application Interface, the Siebel database on the RDBMS, and the Siebel File System. Use the following procedure to verify that the Siebel Server computer can access other Siebel CRM modules.

Note: For information about verifying network connectivity for IBM DB2 for z/OS, see Implementing Siebel Business Applications on DB2 for z/OS.

To verify network connectivity for the Siebel Server computer

Verify network connectivity to the Siebel Gateway, the Siebel Application Interface, and the Siebel database from the Siebel Server computer, using the test utility for your network type.
For TCP/IP networks, use the ping utility to verify network connectivity. Or test the connection through Control Panel, Administrative Tools, Data Sources (ODBC), and then System DSN.
For Oracle Database, verify connectivity to the Siebel database, then go to Step 4.
Use the tnsping utility and Oracle Database connectivity alias, as appropriate to your database, from a command prompt window to make sure that you can connect to the database using the network connect string that you defined.
For IBM DB2, verify connectivity to the Siebel database, as follows:
1. Open a DB2 Command Window to make sure that you can connect to your database.
2. Enter:
```
db2 connect to database_alias user user_ID using password
```
  where:
  - database_alias is your database alias
  - user_ID is a valid user name on DB2
  - password is the password for that user_ID
  If your connection is valid, then you see a message that looks like the following:
```
The connection test is successful

Database Server = DB2/AIX/Solaris x.x.x
SQL authorization ID = SADMIN
Database alias = DB_Alias
```
3. If your connection is not valid, then verify your configuration.
4. To close the connection, type db2 terminate.
Provide network connections from the Siebel Server to all of the applicable Siebel File System directories.

For more information, see Creating the Siebel File System.
Verify that the Siebel File System directories are visible and that the Siebel service owner account has the necessary permissions on these directories.
If you are clustering the Siebel File System, then use the Network IP resource or Network Hostname Resource assigned to that cluster file share.

Verifying Network Connectivity for Mobile Users

Siebel Mobile Web Client users must be able to connect to the Siebel Remote Server, using TCP/IP, to synchronize with the master Siebel database. Make sure that you have the correct network software and hardware installed to support this connectivity and that your remote users are able to establish a TCP/IP connection to the server. To check connectivity, use the ping utility.

Related Books

Siebel Remote and Replication Manager Administration Guide

Configuring the Siebel Mobile Web Client When Neither Siebel VB nor Siebel eScript Is Licensed

By default, the Siebel Mobile Web Client has Siebel VB or Siebel eScript enabled. The parameter EnableScripting is set to True in the application configuration files. If this parameter is True, but neither Siebel VB nor Siebel eScript is licensed, then the Siebel Mobile Web Client does not start. An error message is returned, indicating that you must turn off Siebel VB or Siebel eScript before running the Siebel Mobile Web Client.

To configure the Siebel Mobile Web Client when neither Siebel VB nor Siebel eScript is licensed

Set EnableScripting to FALSE in the configuration file used by your Siebel Mobile Web Client, such as uagent.cfg for Siebel Call Center. This configuration file is located in the directory SIEBEL_CLIENT_ROOT\bin\LANGUAGE.
where:
- SIEBEL_CLIENT_ROOT is the directory where you installed the Siebel Mobile Web Client.
- LANGUAGE is the three-letter code for the language in which you are running the Siebel Mobile Web Client.