background image

2

Novell Sentinel 6.1 SP1 Hotfix 2

n

ov

do

cx (e

n)

  16
 Ap
ril 20

10

For more information on global filters, see 

Global Filters (http://www.novell.com/documentation/

sentinel61/s61_user/?page=/documentation/sentinel61/s61_user/data/bhjlkyb.html#bhjlkye)

.

2.2  JRE Upgrade

The Java* Runtime Environment* (JRE*) has been upgraded from 1.5 to 1.6 as Java 2 Platform, 
Standard Edition (J2SE)* 5.0 will be unsupported by Sun* as of October 30, 2009.

2.3  LDAP Authentication

A Sentinel 6.1 server can now be configured for LDAP authentication to enable users to login to 
Sentinel using a Novell eDirectory™ or Microsoft* Active Directory* username and password.

NOTE: 

LDAP authentication is currently supported only on Linux* servers.

For more information on configuring a Sentinel server for LDAP authentication, see 

Configuring 

Sentinel 6.1 Server for LDAP Authentication (http://www.novell.com/documentation/sentinel61/
s61_install/?page=/documentation/sentinel61/s61_install/data/blutcr3.html)

.

2.4  Collector Manager

By default, the EventRouter, which is one of the components of the Collector Manager, runs in the 
standalone mode. In this mode, the EventRouter handles internal functions such as maps and 
applying global filters on events parsed by the Collector Manager.

Sentinel 6.1 SP1 Hotfix 2 enables the EventRouter to operate in server and client modes on both 
DAS machines and Collector Manager machines. The Collector Manager installation on which the  
EventRouter is configured to run in client mode is referred to as Light Weight Collector Manager. 

NOTE: 

You should configure a Light Weight Collector Manager on machines that have limited 

CPU and RAM for the Collector Manager process.

For more information on configuring a Light Weight Collector Manager, see 

Configuring the Light 

Weight Collector Manager (http://www.novell.com/documentation/sentinel61/s61_install/?page=/
documentation/sentinel61/s61_install/data/bgms016.html#bl53pzx)

.

3  Prerequisites

The prerequisites for the hotfix depend on the Sentinel version and platform. Read each section 
carefully to determine whether the steps apply to your environment.

If Sentinel 4.x or 5.x is installed, it must be upgraded to Sentinel 6.1 by using the upgrade 
installer. See the 

Patch Installation Guide

 for instructions.

If Sentinel is not yet installed, install Sentinel by using the Sentinel 6.1 installer. See the 

Sentinel Installation Guide

 for instructions.

If Sentinel 6.1 is installed, ensure that you have upgraded to Sentinel 6.1 SP1. 

The complete product documentation is available at the 

Novell Sentinel 6.1 Documentation Web site 

(http://www.novell.com/documentation/sentinel61)

.

Summary of Contents for SENTINEL 6.1 SP1 HOTFIX 2 - READ ME 9-2009

Page 1: ...the latest software fixes and enhancements to an existing installation of Sentinel 6 1 SP1 and 6 1 SP1 Hotfix 1 This hotfix must be installed on all existing Sentinel 6 1 SP1 clients and servers This...

Page 2: ...arsed by the Collector Manager Sentinel 6 1 SP1 Hotfix 2 enables the EventRouter to operate in server and client modes on both DAS machines and Collector Manager machines The Collector Manager install...

Page 3: ...partitioned or archived the PatchDb script might fail if the AUDIT_RECORD table is too large relative to the amount of temporary tablespace available There are two approaches to ensure that the PatchD...

Page 4: ...d to authenticate as an administrative user 7 On the command line return to the extracted hotfix top level directory and run the script to start the hotfix installer On Windows service_pack bat On Uni...

Page 5: ...he Oracle dba group The user has the Java 1 6 executable as the PATH variable TIP You can run the PatchDb script directly on the database server machine if the prerequisites are met However in some en...

Page 6: ...lation 10 After the installation is complete check for any errors If there are no errors the Sentinel database patch installation is complete If there are errors resolve the errors by referring to the...

Page 7: ...dress of the SQL Server Sentinel database machine SQL Server database instance name if any Port number of the SQL Server database Name of the SQL Server database to patch ESEC by default 1 for the Win...

Page 8: ...the date and time format to your local time zone see the Java Web site http java sun com j2se 1 6 0 docs api java text SimpleDateFormat html 1 Edit the SentinelPreferences properties file On Windows...

Page 9: ...efect Number Description 530554 Sentinel Control Center SCC and Sentinel Solution Designers SSD launchers shortcuts do not launch the respective Sentinel applications on WIndows Workaround For SCC rig...

Page 10: ...ctive stream for a prolonged time period 498871 ESM pays attention to the default attribute for Connection methods 459625 SDM no longer lets you create impossible configurations with at least MS SQL 4...

Page 11: ...comply with all export control regulations and to obtain any required licenses or classification to export re export or import deliverables You agree not to export or re export to entities on the cur...

Reviews: