Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >
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:
Related Topic
Installing Siebel Tools
Verifying Oracle Database XE
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, installActions2015-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 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\15.0.0.0.0\Tools . For example, you might enter a command like this:
set ORACLE_HOME=C:\siebel\15.0.0.0.0\Tools
- Navigate to the
opatch directory within your installation. For example, you might enter a command like this:
cd C:\siebel\15.0.0.0.0\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 version 15.0 is shown as 15.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\15.0.0.0.0\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. NOTE: The objects directory contains the SRF file. Monitoring of any SRF file by virus scanning software might significantly degrade Siebel Tools performance. If you have virus scanning software installed on your computers, then configure it to skip SRF files. Because these files are binary data files, the risk of virus infection is low, and so excluding these files from scanning is usually acceptable. Alternatively, you can scan SRF files less frequently than other files.
SIEBEL_TOOLS_ROOT. The directory for the Siebel Tools installation, such as C:\siebel\15.0.0.0.0\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. |
local |
The local, extracted database. |
files |
Local file attachments. |
inbox |
Not used for Siebel Tools. |
outbox |
Not used for Siebel Tools. |
locale |
Text files for installed languages containing version information. |
log |
Log files from Siebel Tools operations. |
msgtempl |
Message files. |
objects |
Location of the compiled Siebel Repository file used by Siebel Tools (siebel_sia.srf). Also the default location for SRF files created using the Siebel Tools object compiler. |
opatch |
Files used by the opatch utility. |
oraclexe |
The installation path for Oracle Database XE. This directory is created if you have installed that module for the local database, as described in Installing Oracle Database XE for the Local Database for Siebel Tools. |
public |
HTML files, graphics files, and cascading style sheet files. |
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 . |
sample |
Location where the Siebel Sample Database (sse_samp.dbf) is installed, if you installed it in the Siebel Tools installation directory. This directory applies to the SAP SQL Anywhere version of the sample database only. |
files |
Where the sample file attachments are installed. |
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. |
webtempl |
Location of Siebel Web Template (.swt) files. |
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.
In the current release, the license keys for Siebel CRM base applications do not need to be entered manually. The license keys are provided in the seed data that is imported into a new Siebel database. The license keys are also part of the seed data that is imported into an existing database as part of Incremental Repository Merge or database upgrade operations. For more information about performing these operations, see Siebel Database Upgrade Guide.
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 Table 15. 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 15. Siebel Tools ODBC Data Sources
|
|
LOCAL_XE |
Connects to the local database using Oracle Database XE. NOTE: For a Siebel Web Client installation, the ODBC data source for a Siebel Sample Database that uses Oracle Database XE is named SAMPLE_XE.
|
SSD Local Db default instance |
Connects to the local SAP SQL Anywhere database. NOTE: For Siebel Innovation Pack 2015, the local database for Siebel Tools can use either SAP SQL Anywhere or Oracle Database XE. SAP SQL Anywhere is not available for new deployments after September 2015. For more detailed information on how this change affects Siebel Tools and Siebel Remote, see Siebel Release Notes on My Oracle Support for Innovation Pack 2015 (Doc ID 1996273.1).
|
SSD default instance |
Connects to the Microsoft SQL Server database or 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. See also Requirements for Installing Siebel Tools.
|