|
Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >
Verifying Installation for Siebel Business Applications
After installing the Siebel Business Applications 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 Business Applications 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: SiebelApplicationInterfaceHost.FQDN:Port/siebel/app/callcenter/lang In this URL:
This topic contains the following information:
Related Topic
Installing Siebel Business Applications Server Modules
Configuring Siebel Business Applications Server Modules
Troubleshooting Installation and Configuration for Siebel Business Applications
Stopping and Starting the Application Container
Reviewing the Installation Log Files
After installing the Siebel Business Applications components, 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_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 module being installed. See also Troubleshooting Installation and Configuration for Siebel Business Applications. 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. See also Troubleshooting Installation and Configuration for Siebel Business Applications. Verifying That the Application Container Is Running
After installing one or more components 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. See also Troubleshooting Installation and Configuration for Siebel Business Applications and Stopping and Starting the 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.
See also Troubleshooting Installation and Configuration for Siebel Business Applications. Verifying the Installation Version Number
After installing the Siebel Business Applications components, verify the version number of the installed software. To verify the installation version number for Siebel Business Applications
- 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. |
|
dbtempl. Dictionary and local database files required by Siebel Remote for users. |
|
EXTCACHE. Contains files used by the Siebel Enterprise Cache. (This directory is not used in Siebel Innovation Pack 2017, 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. |
|
objects. Empty directory. When you install the Siebel Server into the same root directory, that installation procedure populates this directory with a lang subdirectory (such as enu for U.S. English) with a corresponding Siebel Repository file (siebel_sia.srf). UNIX CELL |
|
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 Business Applications. 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. |
|
apache. Files used by embedded instances of Apache Tomcat, which supports Siebel REST services and other functionality. See also Siebel REST API Guide. |
|
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 serve. |
|
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. |
|
ESCRIPTTEMPL. |
|
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. |
|
input. Contains files related to Siebel Remote. |
|
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. |
|
nlp. Contains natural-language processing files. |
|
objects. Contains language-specific Siebel Repository files. |
|
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 Business Applications. Also holds temporary, backup, and state log files used during an upgrade. |
|
upgrade.log. File that contains information logged during an upgrade. |
|
webtempl. Contains Siebel Web templates and HTML files that support the applets and views required for Siebel Web Clients for Siebel Business Applications. Store your own custom Web template files or HTML files only in the custom subdirectory. For more information, see Configuring Siebel Open UI. |
|
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. |
|
db_server (oracle, db2udb, or db2390). Contains scripts specific to your database, including upgrade scripts for previous versions of Siebel Business Applications. |
|
|
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. |
|
|
|
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. |
|
|
|
src. |
|
|
|
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 Business Applications 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). |
|
pe60. |
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). |
|
admin. Contains model files used during configuration of the Siebel Application Interface. |
|
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 the file web.xml. |
|
applicationinterface |
|
bin. Contains library files needed for the Siebel Application Interface functionality. |
|
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. |
|
locale. Contains resource files with information about any run-time errors. These language-specific files and scripts are not configurable. |
|
log. Reports communication errors between the Siebel Application Interface and the Application Object Managers in the Siebel Servers. |
|
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. |
|
