Perform the following tasks before installing Sentinel. For more information on these prerequisites, including the list of certified platforms, see Section 2.0, System Requirements.
Ensure that each machine in the Sentinel architecture meets the minimum system requirements.
Ensure that the operating systems for all components of the system are certified platforms and that the operating system has been hardened by using current best security practices.
If you are installing on SUSE Linux Enterprise Server (SLES) 10, ensure that SLES is using the ext3 file system.
For a minimal or headless installation, the operating system for the Sentinel Server machine must include at least the Base Server and X Window components of SuSE Linux Enterprise Server.
If you are installing the Collector Manager on a 64-bit machine, ensure that the 32-bit libraries are available. The 32-bit libraries are required when running a Collector that is written in the proprietary Collector language (this includes almost all Collectors written before June 2008) as well as when running certain Connectors such as the LEA Connector. JavaScript based Collectors and the plug-ins of Sentinel are 64-bit enabled. Verifying the availability of these libraries is important on Linux platforms, which might not include them by default.
You must install SUNWxcu4 package on your Solaris machine before installing Sentinel 6.1.
Ensure that a Sentinel-certified database is installed. If you are using Oracle, Enterprise Edition with partitioning is required for the data archive to work. For more information on certified versions, see Section 2.0, System Requirements.
Get the Sentinel, Crystal Reports Server, and Crystal Reports Developer serial numbers and license keys from the Novell Customer Center. If you have purchased the optional Advisor exploit detection data feed, verify in the Customer Center that this data subscription is listed with the rest of your Novell products.
Install and configure an SMTP server if you want to send e-mail notifications from Sentinel.
Create a directory with ASCII-only characters (and no special characters) from which you want to run the Sentinel installer.
Provide Power user privileges to the Domain User. For more information, see Section 3.4.1, Providing Power User Privileges to Domain Users.
Sentinel installations using the full installer should always take place on a clean system. If Sentinel 6.0 was previously installed on any of the machines, Novell recommends that you follow the uninstallation procedures in Section 9.0, Uninstalling Sentinel. For information on uninstalling previous versions of Sentinel, see the relevant Installation guides on the Novell Documentation Web site.
NOTE:Instructions for upgrading from a previous version of Sentinel 6.0 to Sentinel 6.1 are included with the patch installer.
IMPORTANT:If you install Sentinel as a domain user, where the user is not a part of administrator group in the Active Directory machine and the local machine, then the domain user should be a Power User to start the Sentinel Services.
On the Windows desktop, right-click My Computer and select .
In the Computer Management window, select > > .
Double-click and add the domain user in domain/domain user format in the local system where Sentinel is installed by using this domain user.
Before installing the Sentinel Database components, you must ensure the following prerequisites are met:
If you are installing on SLES 10, the file system for the operating system must be ext3.
The Oracle database must be installed and running.
The Oracle client and the Oracle JDBC client (for Oracle 10g, use ojdbc14.jar and for Oracle 11g, use ojdbc6.jar) must be installed on the machine from which you are running the installer. If you run the Sentinel installer on the database machine, ensure that a compatible JDBC client is already installed by the database installer. If you run the Sentinel installer on another machine, the database instance must be manually created and the compatible JDBC client must be manually installed on the machine with the installer. Although newer Oracle drivers are backward compatible, Sentinel testing was performed with the drivers that were shipped with the Oracle database (for example, 10.2.0.3 drivers were tested with the 10.2.0.3 database).
NOTE:Sentinel cannot start the Oracle 10 database because of the errors in the Oracle dbstart and dbshut scripts. You need to modify the dbstart and dbshut scripts after installing Sentinel. For more information on modifying these scripts, see Section 3.8.7, Modifying Oracle dbstart and dbshut scripts.
For performance reasons it is highly recommended that if you are installing in a RAID system and if your RAID environment allows, configure the Sentinel database so that the Transaction Log points are stored on the fastest write disk available. This Transaction log disk is a separate physical disk where the database files are stored.
You should allow the Sentinel installer to create the Oracle database instance for Sentinel.
The database instance creation can be performed manually if required. To ensure the compatibility of this instance with Sentinel, see Section B.5, Manual Oracle Instance Creation (Optional). If you chose this option, you must run the Novell createEsecDBA.sh script and use the Sentinel installer to add the database objects to the manually created Oracle database instance. For more information, see Section 3.6, Custom Installation.
NOTE:If you are using an existing or manually created Oracle database instance, it must be empty except for the Sentinel Database User for successful installation.
Get the login credentials for the Oracle operating system user (default: oracle).
Get the login credentials for Oracle users SYSTEM and SYS.
Ensure that the following environment variables are set for the Oracle operating system user:
ORACLE_HOME (for example, echo $ORACLE_HOME might produce /opt/oracle/product/10gR2/db)
ORACLE_BASE (for example, echo $ORACLE_BASE produces /opt/oracle)
PATH (must include $ORACLE_HOME/bin)
Determine an appropriate Oracle listener port number (the default port number is 1521).
Create directories for the following storage locations:
Data Directory
Index Directory
Summary Data Directory
Summary Index Directory
Temp and Undo Directory
Redo Log Member A Directory
Redo Log Member B Directory
Archive Directory
NOTE:The oracle user must have the write permissions for these directories. To provide write permissions for these directories, execute the following commands for each directory as the root user:
chown –R oracle:dba <directory_path> chmod –R 770 <directory_path>
After the Sentinel Database is installed on Oracle, the database contains the following users:
Table 3-2 Database Users
The SQL Server database must be installed and running.
The Sentinel Database installer requires the SQL Server client tools to be installed on the system where the Sentinel Database installer is run.
The sc command to start the SQL Server Agent Service must be available on your database operating system. If not, the SQL Server Agent Service must be started manually for partitioning and data archiving to work properly. Also, it must be scheduled to restart after a reboot using another utility.
Get the login credentials for the System Administrator database user
If the database uses SQL Authentication mode, the default database administrator user is sa.
If the database uses Windows Authentication only mode, you must run the installer when you are logged into Windows as a System Administrator database user.
Set the MSSQLSERVER service to log in using the Local System Account.
Determine the SQL Server Instance Name, if applicable.
NOTE:If you named your database instance during the SQL Server install, use the same name when prompted for the SQL Server instance name when installing the Sentinel Database and DAS components. If you did not name your database instance during the SQL Server install, leave the instance name blank during installation (if you are typing the hostname, do not add \<instance_name> to the database hostname).
Create directories for the following storage locations:
Data Directory
Index Directory
Summary Data Directory
Summary Index Directory
Log Directory
Archive Directory
Determine the SQL Server Instance port number (the default port number is 1433).
The Sentinel system uses several accounts for installation and system operation.These accounts exist in the Sentinel database and might use SQL Server authentication or Windows authentication. To use Windows authentication for one or more of the Sentinel users during Sentinel installation, the corresponding Windows Domain user must exist before installing the Sentinel Database.
The domain user should have Power User privileges to start the Sentinel services. See Section 3.4.1, Providing Power User Privileges to Domain Users for more information.
The following Sentinel users can be assigned to a Windows Domain User:
Sentinel Database Administrator, used as the schema owner (named esecdba by default, if using SQL authentication; might be any domain account if using Windows Authentication).
Sentinel Application User, used by Sentinel applications to connect to the database (named esecapp by default, if using SQL Authentication; might be any domain account if using Windows authentication).
Sentinel Administrator, used as the administrator for logging to the Sentinel Control Center (named esecadm by default, if using SQL authentication; might be any domain account if using Windows authentication).
Sentinel Report User, used for creating reports (named esecrpt by default, if using SQL authentication; might be any domain account if using Windows authentication).
NOTE:The database contains the Sentinel Database Administrator user, Sentinel Application User, and Sentinel Administrator user by default.
Sentinel does not support Microsoft clustering or High Availability for Windows.
After installing the Sentinel Database on SQL Server using local authentication, the database contains the following users:
esecdba: Database schema owner. The DBA privilege is not granted to the Sentinel Database User because of security concerns, so to use Enterprise Manager (the GUI for the SQL database), you must create a user with DBA privileges.
esecapp: Database application user. This is the application user used to connect to the database.
esecadm: Database user that is the Sentinel Administrator. This is not the same user account as the Sentinel Administrator operating system user.
esecrpt: Database report user.
sa: System administrator database user.
On Windows, you need to install SQL Server with mixed mode authentication to log in to the Sentinel Control Center using either Windows or SQL Server authentication. If you install SQL Server with Windows authentication, you can log in through Windows authentication only.
To modify your authentication mode settings:
In SQL Server Management Studio, right-click the server for which you want to modify the settings.
Select , then click .
From the options or , select your option for authentication.
If you are not installing the Sentinel Database on the same machine as the Sentinel server, you must install the Sentinel Database before installing the other components of Sentinel.