Siebel Installation Guide for UNIX > Verifying and Troubleshooting Your Installation >

Verifying Installation for the Siebel Web Server Extension

After installing the Siebel Web Server Extension (SWSE) software as a new installation or as a patch installation (migration installation), review the installation log files, verify the version number of your installed software, and review the Siebel Web Server Extension (SWSE) directories and files that now exist under the SWSE_ROOT directory that you specified during the installation.

This topic contains the following information:

Reviewing the Installation Log Files for the SWSE

After installing the SWSE, 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:


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, installActions2013-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.

Verifying the Installation Version Number for the SWSE

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

To verify the installation version number for the SWSE

  1. Open a shell window.
  2. Set the value of the ORACLE_HOME environment variable to correspond to your top-level installation location, such as /siebel/ or /siebel/ for an installation of Siebel Web Server Extension software. For example, enter a command like this for Siebel CRM version

    set ORACLE_HOME=/siebel/

  3. Navigate to the opatch directory within your installation. For example, enter a command like this for Siebel CRM version

    cd /siebel/

  4. Enter the following command:

    opatch lsinventory -jre jre_location -invPtrLoc inventory_location


    • jre_location is the full path of the installed Java Runtime Environment (JRE) software. On AIX, you must use the -jre option. It is not required on other operating systems. For more information about the JRE requirements for AIX, see Requirements Specific to UNIX or Linux Operating Systems.
    • 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 or

Reviewing the Installation Directories for the SWSE

Review the physical directories created during the installation of the Siebel Web Server Extension (SWSE) on the Web server host to familiarize yourself with the locations of files such as the eapps.cfg and eapps_sia.cfg configuration files.

NOTE:  Additional top-level directories are created, which are parallel to the sweapp directory for the Siebel Web Server Extension. These directories include ccr for Oracle Configuration Manager files, config for SWSE Configuration Wizard files, cfgtoollogs for installation log files, opatch for files related to the opatch utility, oui for files related to Oracle Universal Installer, and others.

The following list shows some of the physical directories and files created after you install the SWSE on the Web server. Some of these directories are not created until the first login. In the list, lang represents each language that you have installed, such as ENU for U.S. English.

sweapp. Top-level directory for SWSE.


admin. Contains model files used during configuration of the SWSE.


bin. Contains the SWSE configuration files (eapps.cfg and eapps_sia.cfg) and the library files needed for the SWSE functionality.



lang. Language-specific files and scripts. These are not configurable.


cfgenv.csh. C shell variant of the Siebel script for setting environment variables on the server before you run one of the Siebel Configuration Wizards. Bourne or Korn shell variant of the Siebel script for setting environment variables on the server before you run one of the Siebel Configuration Wizards.


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 SWSE and the Application Object Managers in the Siebel Servers.


public. Each language-specific subdirectory contains the default HTML file (default.htm) used to redirect the browser to the SWSE and subdirectories of the Siebel Server. The files are updated from the webmaster directory on the Siebel Server when the Web server is restarted, or when an administrator uses the SWE command UpdateWebImages to manually update the files on the Web server.


For more information, see About the Siebel Enterprise Security Token and Updating Web Server Static Files Using the Siebel Enterprise Security Token. See also the topic about adding a password for updating Web server static files in Siebel Security Guide.



lang. Language-specific files. If you are using Siebel Open UI (in native mode), then do not store your own custom files in subdirectories such as CSS, files, images, or scripts. For more information, see Configuring Siebel Open UI.

Reviewing the Log Files for the SWSE

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

Depending on the logging level that you choose, these files record errors, warnings, and general information. Events such as Web server failures or invalid configuration of the SWSE are captured in these log files. Analyzing the log files can provide clues for troubleshooting SWSE problems. For more information about reviewing log files and monitoring Web servers and SWSE, see Siebel System Monitoring and Diagnostics Guide.

Siebel Installation Guide for UNIX Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.