======================================================================
Halcyon PrimeAlert (R) for Sun Web Server
Version 3.0.0
Release Notes
======================================================================
Copyright (c) 1998-2008 Halcyon Monitoring Solutions, Inc.
Note: For the latest information on this product, go to the
web site at http://www.HalcyonInc.com
Refer to the README file(s) for all other information.
Versions Documented Below: 3.0.0 2.1.0b 2.1.0a 2.1.0
1.0.2 1.0.1a 1.0.1 1.0.0
======================================================================
VERSION/DATE: 3.0.0/2008-03-31
ENHANCEMENTS
----------------------------------------------------------------------
- This version of the module was configured to support data collection
via JMX as made available by Sun Web Server 7.0 and above.
- Log file names and directory paths are now dynamically detected.
These files no longer need to be located in the default location
using the default naming convention.
- Web Server status is determined in a much more robust way, allowing
the user to more easily identify an error or fault condition, as
well as more easily identify the source of the status condition.
BUG FIXES
----------------------------------------------------------------------
- Specifying long instance names for instances of the PrimeAlert for
Sun Web Server module is much less likely to cause instance name
collisions among sub module instances than previous releases.
- The 'Top Cache Entries' table no longer fails to display data when
a Sun Web Server instance with an exceptionally long instance name
is loaded.
- The 'Top Cache Entries' table no longer displays file cache entries
improperly when entries have white space characters in the URL.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This new version of PrimeAlert for Sun Web Server requires that
your license file be updated. Please contact Halcyon Support.
- This version is not compatible with the previous version. If you
need to monitor Sun Web Server 6.x, you must use
PrimeAlert for Sun Web Server 2.1.0b or prior. Note that both
versions of the module can be loaded on the same Sun MC server layer
without conflict.
- This version of the PrimeAlert for Sun Web Server module includes
a change in the module's base name, allowing version 3.0.0 to be
installed without affecting previous installations as noted above.
As a result, previous configurations and customizations are not
imported into the current version of the module and must be manually
reapplied, the module does not overwrite or modify customizations
from previous installations. As such, you are free to apply all
customizations to the current version at any time.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Problem:
Sun Manager Center 3.6 and up is experiencing problems serving help
files from the server layer.
Workaround:
Help documentation is unavailable from the Sun MC server layer. Visit
http://www.halcyoninc.com/docs/ for online documentation of Halcyon
modules.
- Problem:
Some folders are empty or cannot be opened when selecting data
properties for use with Sun Management Center Performance Reporting
Manager or Group Operations.
Workaround:
These folders are placeholders representing Halcyon modules which
are loaded as sub-modules or children of the current module. The
- Problem:
Providing JVM login credentials with a white space or hyphen character
to connect to a Java Virtual Machine using Java Management Extensions
(JMX) causes the module to go down.
Workaround:
Although they are allowable in JVM user names and passwords,
white space characters and hyphens conflict with the current JMX
ObjectName parsing engine and cause the module to go to a down
state. Login credentials must be revised and these characters must
be removed.
NOTES
----------------------------------------------------------------------
- Server traffic results are only accurate up to the module's last
refresh operation. That is, current web server traffic is not
reported until a module refresh operation occurs.
- Performing a web server access log rotation before a module refresh
operation may cause inaccuracies in server traffic results.
If possible, perform web server access log rotation after a module
refresh operation.
- The module ignores records which have the exact same timestamp as
the last record processed during the last refresh operation. That
is, the module is configured to ignore out of sequence records.
- Partial server traffic results are stored in the agent's log
directory. These files are not deleted by the module when it is
deactivated since historical server traffic would be lost.
- Zero server traffic may be reported initially when the time required
for analyzing the web server log file is greater than the console
refresh time interval. This may occur when the size of the web
server log file is greater than 1 GB.
======================================================================
VERSION/DATE: 2.1.0b/2006-12-18
ENHANCEMENTS
----------------------------------------------------------------------
- Added web server access log rotation support.
BUG FIXES
----------------------------------------------------------------------
- Same as version 2.1.0a (please see below).
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Same as version 1.0.2 (please see below).
NOTES
----------------------------------------------------------------------
- Server traffic results are only accurate up to the module's last
refresh operation. That is, current web server traffic is not
reported until a module refresh operation occurs.
- Performing a web server access log rotation before a module refresh
operation may cause inaccuracies in server traffic results.
If possible, perform web server access log rotation after a module
refresh operation.
- The module ignores records which have the exact same timestamp as
the last record processed during the last refresh operation. That
is, the module is configured to ignore out of sequence records.
- Partial server traffic results are stored in the agent's log
directory. These files are not deleted by the module when it is
deactivated since historical server traffic would be lost.
- Zero server traffic may be reported initially when the time required
for analyzing the web server log file is greater than the console
refresh time interval. This may occur when the size of the web
server log file is greater than 1 GB.
======================================================================
VERSION/DATE: 2.1.0a/2006-11-10
ENHANCEMENTS
----------------------------------------------------------------------
- Server traffic is now monitored by URL Host (virtual domain) name
not by directory name.
BUG FIXES
----------------------------------------------------------------------
- Same as version 2.1.0 (please see below).
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Same as version 2.1.0 (please see below).
======================================================================
VERSION/DATE: 2.1.0/2006-07-26
ENHANCEMENTS
----------------------------------------------------------------------
- Added server traffic monitoring support.
- Added Sun Management Center 3.6.1 support.
- Added x86/x64 Solaris support.
- Added Solaris 10 support.
- Added PrimeAlert Neuron support.
- Help documentation update.
- Help files now served from the Sun Management Center server
layer.
- Added Agent Update support.
BUG FIXES
----------------------------------------------------------------------
- Improved SNMP availability test by eliminating full SNMP walk.
NOTES:
----------------------------------------------------------------------
- Removal of iPlanet Web Server 4.1 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Problem:
The rows in the "Current Month" do not refresh right away.
This is a known issue. Please refer to the TroubleShooting notes for
a workaround to this problem.
- Problem:
There is zero traffic reported in the "Current Month" folder for a
given directory.
This is a known issue. Please refer to the TroubleShooting notes for
a workaround to this problem.
- Problem:
Sun Manager Center 3.6 is experiencing problems serving help files
from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
- Problem:
The rows in the "Processes" and "Space Monitoring" folders contain
incorrect parameters.
This is a known issue. The module was initially loaded with either
an incorrect "Web Server Installation Path" or an incorrect
"Web Server Instance" and then reloaded with the corrected load
parameter. The "Processes" and "Space Monitoring" folders
will not update correctly. The "Log File" folder will update
correctly and is not affected by this issue.
Workaround:
Manually change the rows in the affected folders.
- Problem:
HALiWS module uses The Webalizer for web server log file analysis, but
The Webalizer reports at most 133 characters per line. Thus, a
Monitored Directory name can be at most about 100 characters long.
Workaround:
This is a known limitation of The Webalizer. Halcyon recommends
Monitored Directory names are not longer than 100 characters.
======================================================================
VERSION/DATE: 1.0.2/2004-04-30
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun Java System Web Server version 6.1 support.
- Added Web Server availability test.
BUG FIXES
----------------------------------------------------------------------
- The Overview section will not have negative rates when the Web
Server is restarted.
- Changes to the default rows in the Processes, Logfiles and Space
Monitoring sections are persistent across agent restarts.
NOTES:
----------------------------------------------------------------------
- Module has been renamed to "PrimeAlert for Sun Web Server" from
"PrimeAlert for Sun ONE Web Server".
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Sun Manager Center 3.6 is experiencing problems serving help files
from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
======================================================================
VERSION/DATE: 1.0.1a/2003-07-16
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.1/2002-10-12
ENHANCEMENTS
----------------------------------------------------------------------
- Solaris 9 support.
- Support for Sun Management Center Performance Reporting Manager.
- Support for Sun Management Center Group Operations.
- Support for Sun ONE Web Server 6.0
BUG FIXES
----------------------------------------------------------------------
- Module is available in the Module Specification picklist in the
Filters tab of PrimeAlert EventAction.
- Documentation upgrades.
NOTES:
----------------------------------------------------------------------
- Removal of Solaris 2.5.1 support.
- Removal of Sun Management Center 2.x support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 1.0.0.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Problem:
When monitoring multiple Web Server instances, Sun ONE Web Server
will only provide SNMP data for one of the instances.
Workaround:
None
- Problem:
Some folders are empty or cannot be opened when selecting data
properties for use with Sun Management Center Performance Reporting
Manager or Group Operations
Workaround:
See the FAQ for details on how to work around this issue.
- Deployment of Module Configuration Parcels using Group Operations
fails without any errors
Workaround:
Load module manually on each agent.
- Problem:
If the module has been loaded with an incorrect "Sun ONE Web Server
Installation Path" and/or an incorrect "Web Server Instance", and
the mistake is corrected, the "Logfiles" folder will not properly
update with the correct parameters. The "Processes" and "Space
Monitoring" folders will update correctly and are not affected by
this issue.
Workaround:
Reload the module with correct parameters
- Problem:
When multiple versions of Sun ONE Web Server are being monitored on
the same system, the SNMP Agent Status field may have an incorrect
value.
Workaround:
None
======================================================================
VERSION/DATE: 1.0.0/2002-06-24
ENHANCEMENTS
----------------------------------------------------------------------
- None. This is the First Customer Shipment (FCS) release.
BUG FIXES
----------------------------------------------------------------------
- None. This is the First Customer Shipment (FCS) release.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Problem:
If the module has been loaded with an incorrect "iPlanet Web Server
Installation Path" and/or an incorrect "Web Server Instance", then
the mistake is corrected, the "Logfiles" folder will not properly
update with the correct parameters. The "Processes" and "Space
Monitoring" folders will update correctly and are not affected by
this issue.
Workaround:
Reload the module with correct parameters
---//---