======================================================================
Halcyon PrimeAlert (R) Reporter
Version 2.2.0
Release Notes
======================================================================
Copyright (c) 1996-2007 Halcyon Monitoring Solutions, Inc.
Note: For the latest information on this product, visit:
http://www.HalcyonInc.com
Refer to the README file(s) for all other information.
Versions Documented Below: 2.2.0 2.1.0c, 2.1.0b, 2.1.0a, 2.1.0, 2.0.0b,
2.0.0a, 2.0, 1.2.1, 1.1,
2.2.0 1.2 (PrimeAlert WebPortal)
======================================================================
VERSION/DATE: 2.2.0/2008-01-16
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun Management Center (Sun MC) 4.0.
- Upgraded Apache Tomcat to version 6.0.14.
- Upgraded Java Runtime Environment to version 1.5.0 Update 14.
- Upgraded X.org Virtual Frame Buffer to version 7.3.
BUG FIXES
----------------------------------------------------------------------
- The details page of PrimeAlert EventAction version 2.3.0, which has
the new EventAction Status property will be displayed properly.
Previous versions of Reporter will fail and render a blank page.
- The japach sub-process on the agent would, under certain conditions,
spin. This problem has been fixed.
- A process handle leak has been fixed in the japach sub-process
for Windows.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Objects in Reporter may fail to update if created within one hour of
reverting from DST (Daylight Savings Time) to Standard Time in
the current time zone. This issue is self correcting, and Reporter
should begin receiving/graphing data approximately one hour after
the time change. It is suggested that any new objects be created more
than one hour before DST changes take effect.
- Agents are shown in a remote context when the appropriate server
host is connected to via an instance of WebPortal run from a remote
server. See Troubleshooting for details.
- Agents are displayed in a remote server context when connecting to
a secondary port on the Sun MC server host with NAT enabled. See
Troubleshooting for details.
- In certain circumstance, alarms may not be properly acknowledged
if they are acknowledged from any other section other than the Alarm
Search section. See TroubleShooting file for workaround.
- As on Solaris, the Reporter gateway process on Windows, named japach,
does not shutdown when the module is disabled or unloaded.
This issue is functionally benign, the product will continue
to function as expected.
- The Reporter gateway process, named japach, does not shut
down when the module is disabled or unloaded. It is only
shut down when the agent is stopped. Furthermore if the
module is disabled or unloaded, then enabled or re-loaded,
a superfluous error message will appear in the agent.log
logfile noting that the process could not be started.
This issue is functionally benign, the product will continue
to function as expected.
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after Sun MC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- When using the PrimeAlert WebPortal, the Sun MC console package
(SUNWescon) must be installed on the Sun MC server host. If it is not,
long, unintelligible strings such as "base.console.ConsoleTopology:
domain.defaultDomain" will appear in the display.
- Some alarms with a Down or Off severity cannot be acknowledged due to
some problems with Sun MC.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
VERSION/DATE: 2.1.0c/2007-03-05
ENHANCEMENTS
----------------------------------------------------------------------
- None.
BUG FIXES
----------------------------------------------------------------------
- The details page of PrimeAlert EventAction version 2.3.0, which has
the new EventAction Status property will be displayed properly.
Previous versions of Reporter will fail and render a blank page.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Objects in Reporter may fail to update if created within one hour of
reverting from DST (Daylight Savings Time) to Standard Time in
the current time zone. This issue is self correcting, and Reporter
should begin receiving/graphing data approximately one hour after
the time change. It is suggested that any new objects be created more
than one hour before DST changes take effect.
- Agents are shown in a remote context when the appropriate server
host is connected to via an instance of WebPortal run from a remote
server. See Troubleshooting for details.
- Agents are displayed in a remote server context when connecting to
a secondary port on the Sun MC server host with NAT enabled. See
Troubleshooting for details.
- In certain circumstance, alarms may not be properly acknowledged
if they are acknowledged from any other section other than the Alarm
Search section. See TroubleShooting file for workaround.
- As on Solaris, the Reporter gateway process on Windows, named japach,
does not shutdown when the module is disabled or unloaded.
This issue is functionally benign, the product will continue
to function as expected.
- The Reporter gateway process, named japach, does not shut
down when the module is disabled or unloaded. It is only
shut down when the agent is stopped. Furthermore if the
module is disabled or unloaded, then enabled or re-loaded,
a superfluous error message will appear in the agent.log
logfile noting that the process could not be started.
This issue is functionally benign, the product will continue
to function as expected.
- During installation when the install script asks the user
if they would like to install the server layer packages for
PrimeAlert Reporter, it mistakenly claims that:
"The server layer of Sun Management Center
is bundled with this distribution."
This should read:
"The server layer of PrimeAlert Reporter
is bundled with this distribution."
This text output bug is benign, the server layer of Sun MC
is not bundled with PrimeAlert Reporter.
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after Sun MC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- When using the PrimeAlert WebPortal, the Sun MC console package
(SUNWescon) must be installed on the Sun MC server host. If it is not,
long, unintelligible strings such as "base.console.ConsoleTopology:
domain.defaultDomain" will appear in the display.
- Some alarms with a Down or Off severity cannot be acknowledged due to
some problems with Sun MC.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 2.1.0.b/2007-01-30
ENHANCEMENTS
----------------------------------------------------------------------
BUG FIXES
----------------------------------------------------------------------
- Added support for upcoming DST (Daylight Savings Time) changes
beginning in 2007.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Objects in Reporter may fail to update if created within one hour of
reverting from DST (Daylight Savings Time) to Standard Time in
the current time zone. This issue is self correcting, and Reporter
should begin receiving/graphing data approximately one hour after
the time change. It is suggested that any new objects be created more
than one hour before DST changes take effect.
- Agents are shown in a remote context when the appropriate server
host is connected to via an instance of WebPortal run from a remote
server. See Troubleshooting for details.
- Agents are displayed in a remote server context when connecting to
a secondary port on the Sun MC server host with NAT enabled. See
Troubleshooting for details.
- In certain circumstance, alarms may not be properly acknowledged
if they are acknowledged from any other section other than the Alarm
Search section. See TroubleShooting file for workaround.
- As on Solaris, the Reporter gateway process on Windows, named japach,
does not shutdown when the module is disabled or unloaded.
This issue is functionally benign, the product will continue
to function as expected.
- The Reporter gateway process, named japach, does not shut
down when the module is disabled or unloaded. It is only
shut down when the agent is stopped. Furthermore if the
module is disabled or unloaded, then enabled or re-loaded,
a superfluous error message will appear in the agent.log
logfile noting that the process could not be started.
This issue is functionally benign, the product will continue
to function as expected.
- During installation when the install script asks the user
if they would like to install the server layer packages for
PrimeAlert Reporter, it mistakenly claims that:
"The server layer of Sun Management Center
is bundled with this distribution."
This should read:
"The server layer of PrimeAlert Reporter
is bundled with this distribution."
This text output bug is benign, the server layer of Sun MC
is not bundled with PrimeAlert Reporter.
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after Sun MC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- When using the PrimeAlert WebPortal, the Sun MC console package
(SUNWescon) must be installed on the Sun MC server host. If it is not,
long, unintelligible strings such as "base.console.ConsoleTopology:
domain.defaultDomain" will appear in the display.
- Some alarms with a Down or Off severity cannot be acknowledged due to
some problems with Sun MC.
======================================================================
VERSION/DATE: 2.1.0a/2006-12-01
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Windows x64.
BUG FIXES
----------------------------------------------------------------------
- Fixed startup script to guarantee WebPortal runs in the appropriate
locale.
- Fixed WebPortal to correctly show agents in a local context when
NAT (Network Address Translation) is enabled on the server host.
- Navigation bar in WebPortal now correctly resolves the navigation
path when drilling down into an agent when NAT is enabled on the
Sun MC server host.
- Attribute Editor no longer displays an error when loaded from
within an agent when NAT is enabled on the Sun MC server host.
- WebPortal will now correctly show an agent in a local context when
the agent points to a secondary network interface on the Sun MC
server.
- Status messages of all agents within WebPortal no longer become
misaligned with the addition and removal of agents.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Agents are shown in a remote context when the appropriate Sun MC
server host is connected to via an instance of WebPortal run from
a remote system. See Troubleshooting for details.
- Agents are displayed in a remote server context when connecting to
a secondary interface on the Sun MC server host with NAT enabled.
See Troubleshooting for details.
- In certain circumstance, alarms may not be properly acknowledged
if they are acknowledged from any other section other than the Alarm
Search section. See TroubleShooting file for workaround.
- As on Solaris, the Reporter gateway process on Windows, named japach,
does not shutdown when the module is disabled or unloaded.
This issue is functionally benign, the product will continue
to function as expected.
- The Reporter gateway process, named japach, does not shut
down when the module is disabled or unloaded. It is only
shut down when the agent is stopped. Furthermore if the
module is disabled or unloaded, then enabled or re-loaded,
a superfluous error message will appear in the agent.log
logfile noting that the process could not be started.
This issue is functionally benign, the product will continue
to function as expected.
- During installation when the install script asks the user
if they would like to install the server layer packages for
PrimeAlert Reporter, it mistakenly claims that:
"The server layer of Sun Management Center
is bundled with this distribution."
This should read:
"The server layer of PrimeAlert Reporter
is bundled with this distribution."
This text output bug is benign, the server layer of Sun MC
is not bundled with PrimeAlert Reporter.
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after Sun MC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- When using the PrimeAlert WebPortal, the Sun MC console package
(SUNWescon) must be installed on the Sun MC server host. If it is not,
long, unintelligible strings such as "base.console.ConsoleTopology:
domain.defaultDomain" will appear in the display.
- Some alarms with a Down or Off severity cannot be acknowledged due to
some problems with Sun MC.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If ReporterCLU was previously installed in
/var/opt/SUNWsymon/HALReporter, the directory should be moved before
installation because this is where ReporterCLU will be installed.
Upon completion of the install, compare the old version of
HALReporterCLU.properties with the new and fill out the parameters
as appropriate.
======================================================================
VERSION/DATE: 2.1.0/2006-07-25
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun Management Center's Agent Update feature.
- Added support for Solaris 10.
- Added support for Solaris 10 zones.
- Added support for Sun MC 3.6.1.
- Added support for x86/x64 Solaris. See README file for details.
- The Reporter Command Line Utility (ReporterCLU) which is used to
extract reporter data from the command line interface has been
incorporated into the product and is no longer a separate download.
- The Reporter command line utility has been enhanced so that it
can export data in CSV and TSV formats in addition to XML.
- Added Windows support for the Reporter module. This module can
now be loaded into the PrimeAlert Agent for Microsoft Windows.
Windows support does not include process lists.
BUG FIXES
----------------------------------------------------------------------
- Alarms will be properly acknowledged from the Alarm Search section.
- Status messages will be properly reported after the addition or
removal of objects.
- The navigation bar no longer displays the error message 'Unable to
Determine Location' when run with Network Address Translation (NAT)
enabled.
- The attribute editor will no longer fail to load, inaccurately
suggesting that the parent module has been unloaded when NAT is
enabled.
- Agent server context will be properly reported when viewing agent
details on a NAT enabled host.
KNOWN PROBLEMS
----------------------------------------------------------------------
- In certain circumstance, alarms may not be properly acknowledged
if they are acknowledged from any other section other than the Alarm
Search section. See TroubleShooting file for workaround.
- As on Solaris, the Reporter gateway process on Windows, named japach,
does not shutdown when the module is disabled or unloaded.
This issue is functionally benign, the product will continue
to function as expected.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 2.0.0b/2005-04-12
ENHANCEMENTS
----------------------------------------------------------------------
- Added Solaris 10 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 2.0.0a/2003-07-25
BUG FIXES
----------------------------------------------------------------------
- Reporter is now compatible with Sun Management Center 3.5
- The PrimeAlert WebPortal (the "console" for PrimeAlert Reporter)
is now only supported when installed on the Sun MC server layer
There are no components that need to be installed on the Sun MC
console layer only hosts.
UPGRADE STRATEGY
----------------------------------------------------------------------
- For an upgrade from Reporter 1.x to 2.x, refer to the UPGRADE STRATEGY
below for the 2.0 version released 2003-04-10, plus the 2.0.0a note here:
- For an upgrade from Reporter 2.0.0 to 2.0.0a, only the two following
non-standard customizations will require attention if you have them:
Note: All files mentioned are in ESDIR/cfg,
typically /var/opt/SUNWsymon/cfg/
- A non-standard gateway port range.
(all noted files are in ESDIR/cfg, typically /var/opt/SUNWsymon/cfg)
If before the upgrade you had an "http:port" entry in
HALReport-user-config.x that was other than the standard
"26680-26684" port range, you will need to chose a single port
to use in this version, and ensure that both the http:port
entry in HALReport-user-config.x and the "port" entry in
the HALReport-gateway.conf files are set appropriately after
the upgrade. A port range is no longer required or supported.
- A non-standard temporary gateway file directory.
If before the upgrade you had an "http:path" entry in
HALReport-user-config.x that was other than the standard
"/tmp/HALReport", then after the upgrade you should
ensure that both that entry and the "documentroot" and
"cage" entries in HALReport-gateway.conf are configured
properly.
KNOWN PROBLEMS
----------------------------------------------------------------------
- The Reporter gateway process, named japach, does not shut
down when the module is disabled or unloaded. It is only
shut down when the agent is stopped. Furthermore if the
module is disabled or unloaded, then enabled or re-loaded,
a superfluous error message will appear in the agent.log
logfile noting that the process could not be started.
This issue is functionally benign, the product will continue
to function as expected.
- During installation when the install script asks the user
if they would like to install the server layer packages for
PrimeAlert Reporter, it mistakenly claims that:
"The server layer of Sun Management Center
is bundled with this distribution."
This should read:
"The server layer of PrimeAlert Reporter
is bundled with this distribution."
This text output bug is benign, the server layer of Sun MC
is not bundled with PrimeAlert Reporter.
----------------------------------------------------------------------
VERSION/DATE: 2.0/2003-04-10
ENHANCEMENTS
----------------------------------------------------------------------
- Solaris 2.9 support.
- Web GUI for PrimeAlert EventAction
- Web GUI for PrimeAlert FileBrowser
- Probe commands
- Domain management
- Faster alarm queries
- Faster report generation
- Graphing of numeric properties with non-numeric datatypes
- Add support for Netscape 6.x
- Add support for Internet Explorer 6.0
BUG FIXES
----------------------------------------------------------------------
- Fixed a problem where a report category would fail to display when
the category name contained a space, and the category had many rows
in the objects table.
NOTES
----------------------------------------------------------------------
- Removed support for Solaris 2.5.1.
- Removed support for Sun Management Center 2.x.
- Removed support for Internet Explorer 4.x.
KNOWN PROBLEMS
----------------------------------------------------------------------
- PrimeAlert Reporter gathers, and makes accessible to WebPortal users,
historical process data for all Reporter agent hosts. Since the
process data includes the command line arguments for each listed
process, there are security issues involved if users run applications
that will take a login password on the command line. See the
PrimeAlert Reporter README file for details on how to disable process
list monitoring for Reporter agent hosts.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after Sun MC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory.
- By default, PrimeAlert Reporter does not ship with any software for
encrypting traffic between the WebPortal server and WebPortal HTTP
clients. Halcyon can provide customers with a Secure Socket Layer
package for Apache, subject to the export restrictions that apply to
encryption software. If the SSL security package is not employed,
WebPortal users should be aware of the security risks that entail.
- When using the PrimeAlert WebPortal, the Sun MC console package
(SUNWescon) must be installed on the Sun MC server host. If it is not,
long, unintelligible strings such as "base.console.ConsoleTopology:
domain.defaultDomain" will appear in the display.
- Sometimes alarms appear acknowledged when viewing a host, but in the
Alarm Search View or Host Alarm Summary they appear open and are not
acknowledged. This is due to a bug in Sun MC. When an agent is
re-started with acknowledged alarms, these acknowledgements are
cleared from the server's alarm database, but the alarms remain
acknowledged in the agent. The alarms must be re-acknowledged to make
the database consistent with the agent.
- Some alarms with a Down or Off severity cannot be acknowledged due to
some problems with Sun MC.
UPGRADE STRATEGY
----------------------------------------------------------------------
- In order to obtain the full benefit of the new features included in
this version of PrimeAlert Reporter, PrimeAlert Reporter packages
should be upgraded for all Sun MC layers (server, agent and WebPortal
console).
Agent and Server Layers
-----------------------
- After all agent hosts running Reporter 1.2.x have been prepared
for upgrade to version 2.0.0 of PrimeAlert Reporter, perform the
following upgrade steps:
1. Upgrade PrimeAlert WebPortal to the current version, 2.0.0.
This version of WebPortal is bundled with PrimeAlert Reporter
2.0.0.
2. Upgrade PrimeAlert Reporter on the Sun Management Center server
host.
3. Finally, upgrade the Sun MC agent hosts to version 2.0.0 of
PrimeAlert Reporter.
- Caveat: When the agent layer of PrimeAlert Reporter is upgraded, your
existing installation is not checked to obtain a number of required
configuration parameters. If you wish the upgraded Reporter to be
configured similarly to the old installation, the following
parameters should be obtained from the old installation before it is
upgraded:
1. The Gateway http server port range
To obtain the value of the port range, examine the http:port
entry within the file /var/opt/SUNWsymon/cfg/HALReport-user-config.x.
Record the port range.
2. The RRD database directory
To obtain the value of the RRD database directory where historical
data are archived, examine the rrdConfig:rrdDatabaseDirectory
entry within the file /var/opt/SUNWsymon/cfg/HALReport-user-config.x.
Record the directory (the default value is
/var/opt/SUNWsymon/db/rrd).
3. The process list directory
To obtain the value of the process list directory where historical
process lists are archived, examine the
psConfig:psDataDirectory entry within the file
/var/opt/SUNWsymon/cfg/HALReport-user-config.x.
Record the directory (the default value is
/var/opt/SUNWsymon/db/ps).
4. Other non-standard customized parameters in HALReport-user-config.x
If any customized non-standard changes or support fix changes
have been made to this file, the entire file should be backed up
and re-applied after the install if necessary.
Console Layer - PrimeAlert WebPortal
------------------------------------
- If WebPortal is currently installed and running on the console
installation host, then the WebPortal Apache web server should be
shutdown prior to performing the upgrade:
# /var/opt/SUNWsymon/bin/apachectl stop
- Caveat: When WebPortal is upgraded, it does not check your existing
installation to obtain the required configuration parameters. If
you wish the upgraded WebPortal to be configured similarly to the
old installation, the following parameters should be obtained from
the old installation before it is upgraded:
1. The base installation directory (BASEDIR).
To obtain the value of BASEDIR, login to the WebPortal server
host, and run the following command:
# pkgparam HALsmsptl BASEDIR
Note that if you have an older version of the product, it
may read "/opt/SUNWsymon", in this case for in the rest of
this guide presume it is simply "/opt".
If you are using version 2.0.0a or newer, this will be default
be "/opt".
Record the obtained value.
2. The web server port number.
To obtain the web server port number, login to the WebPortal
server host, and run the following commands:
First to determine <LOCALDIR>:
# pkgparam -v HALsmsptl | grep LOCALDIR
Then:
# grep "^Port " <LOCALDIR>/HALWebPortal/conf/httpd.conf
Record the port number.
3. The default Sun MC server host name.
To obtain the default Sun MC server host name, login to the
WebPortal server host, and run the following command:
# grep "^DefaultServerHost=" <BASEDIR>/SUNWsymon/HALsmsptl/ca/halcyon/primealert/modules/WebPortal/WebPortalConfig.properties
Record the host name.
4. The default Sun MC server port.
To obtain the default Sun MC server port, login to the WebPortal
server host, and run the following command:
# grep "^DefaultServerPort=" <BASEDIR>/SUNWsymon/HALsmsptl/ca/halcyon/primealert/modules/WebPortal/WebPortalConfig.properties
Record the port number.
5. Other non-standard customized parameters in httpd.conf,
and other files in <BASEDIR>/SUNWsymon/HALsmsapj/apache/conf/
directory.
If any customized non-standard changes or support fix changes
have been made to this file, the entire file should be backed up
and individual custom modifications re-applied as instructed by
Halcyon Support.
Note: After upgrading to version 2.0.0, the following directories are
no longer used: $LOCALDIR/HALWebPortal/bin, $LOCALDIR/HALWebPortal/logs.
Also, WebPortal port configuration is now contained within
$LOCALDIR/HALWebPortal/conf/server.xml, and other configuration files have
moved to $LOCALDIR/HALWebPortal/webapps/WebPortal/cfg.
(LOCALDIR=`pkgparam HALsmsptl LOCALDIR`).
VERSION/DATE: 1.2.1/2001-04-24
BUG FIXES
----------------------------------------------------------------------
- Fixed a problem that could cause too-large SNMP packets to be
generated. Also, added a new item to the TroubleShooting file that
explains how to configure Reporter to handle the situation where
a network's maximum UDP packet size is less than 64K.
- When a row is added to the Reporter Objects table, the Reporter
module attempts to create a number of database files of fixed size.
Previously, if the database filesystem had less free space than was
required to properly create the database files, a row was added to
the Objects table, but any Reporter data collected for the object was
corrupted; also, it was not possible to delete the improperly created
row in the Objects table. This no longer happens; instead, if the
database files cannot be created properly due to a lack of filesystem
space, the new row in the Objects table will have the Value field set
to "Data Store Error". Then, the Reporter module will attempt to
create the necessary database files every 10 minutes, or until the
user deletes the associated row from the Objects table.
- While using PrimeAlert WebPortal, HTML help for PrimeAlert Reporter
can now be accessed when there are no data rows in the Reporter
Objects table: Each field in the heading row of the Objects table
now has a Help item in its pop-down menu.
- If two Reports are created that have names that differ only with
respect to the number of spaces between the words that comprise each
report name (e.g. "Network Report" and "Network Report"), the two
reports will now be properly created, although they will appear to
have the same name when listed within the Reporter module.
ENHANCEMENTS
----------------------------------------------------------------------
- PrimeAlert WebPortal was previously packaged separately from
PrimeAlert Reporter. For this release, PrimeAlert WebPortal has been
included as the console layer of PrimeAlert Reporter.
- The ability to add and delete PrimeAlert Agents from topology views
(domains and folders) has been added to PrimeAlert WebPortal.
- PrimeAlert Reporter now includes a preconfigured list for the
"Kernel Reader (Simple)" module that is included with Sun Management
Center 3.0.
-----------------------------------------------------------------------
VERSION/DATE: 1.1/2000-11-21
BUG FIXES
-----------------------------------------------------------------------
- None. This is the FCS release.
ENHANCEMENTS
-----------------------------------------------------------------------
- None. This is the FCS release.
-----------------------------------------------------------------------
VERSION/DATE: 1.2/2000-11-21 (PrimeAlert WebPortal)
BUG FIXES
-----------------------------------------------------------------------
- The PrimeAlert WebPortal login screen can now be accessed using the
URL "http://<host>:<port>/portal/main/", in addition to
"http://<host>:<port>/portal/main".
- When loading module instances that have a password as a module
loading parameter, the password is now displayed as a string of
asterisks in the WebPortal results window.
- The PrimeAlert WebPortal can now handle tables that have empty
columns.
ENHANCEMENTS
-----------------------------------------------------------------------
- Graphing infrastructure has been added to PrimeAlert WebPortal in
order to support the new PrimeAlert Reporter module.
- In a detailed host view, the Host Bar now shows the operating system
of the host in question.
- Each time PrimeAlert WebPortal is installed/upgraded on a Solaris
host, a selection of README files is copied from the base directory
of the distribution tarball to the directory
<LOCALDIR>/install/HALWebPortal, where the value of <LOCALDIR> can
be obtained by running the following command on the WebPortal server
host:
# pkgparam HALsmsptl LOCALDIR
- The Alarm Summary window now allows the user to specify a time range
filter for viewing alarms. The time range is specified via a
graphical Time Range Editor.
---//---