Genesys Pulse Collector Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
Pulse Collector now has an ability to run an embedded version of Genesys DB Server. When running an embedded DB Server, Pulse Collector does not require a separate Database (DB) Server instance in order to connect to the Pulse DB. You can enable an embedded DB Server in Pulse Collector using the following option:
Change takes effect: After restart
Valid values: yes, no
Default value: no
Enables or disables running of embedded DB Server in Pulse Collector internal thread.
Software Requirements Changes
When running Embedded DB Server, Pulse Collector uses Genesys DB Clients which require the DBMS clients to be installed. Follow the instructions under the "DBMS Environment Settings" chapter of
Genesys DB Server User Guideto install and configure those clients. Note that you probably already have necessary clients installed if all of the following is true:
- You are upgrading Pulse Collector from an earlier release.
- You had the Genesys DB Server installed on the host with Pulse Collector.
- The Genesys DB Server and Pulse Collector are of the same architecture (32 or 64-bit).
Application Configuration Changes
If you are running Pulse Collector with Embedded DB Server after an upgrade from an earlier version, you can either perform all of the following steps to modify the configuration or just the first one and leave the configuration unchanged:
- Stop DB Server.
- Clear the
DB Serverfield of Database Access Point application object used by Pulse Collector.
- Uninstall DB Server and delete its application object.
You are not required to configure a separate DB Server application for new installations of Pulse Collector running an Embedded DB Server. The value of the
DB Serverfield on
Database Access Pointapplication object that is used by Pulse Collector should be set to
New Configuration Options
The embedded DB Server produces its own log messages. To control what goes to the log and where the log should be written add
log-dbsection to Collector Application options and fill it with all the options that usually go to the
logsection of Genesys DB Server application. If there will be no
log-dbsection specified in Collector Application options, the logging of embedded DB Server will be controlled by options found in
logsection except for the following:
- The value for
verboseoption is set to
- The log is written to the file specified in
logsection, but with
The Linux version of Pulse Collector using an embedded DB Server is unable to connect to MS SQL Server database.
Pulse Collector now uses a unified format for the custom log messages:
TIMESTAMP SEVERITY_LEVEL THREAD_ID Message text
New configuration option to control log level for the custom log messages.
Changes take effect: Immediately
Valid values: Debug, Trace, Info, Warning, Error, Fatal (case insensitive)
Default Value: Info
Defines log level for the custom Pulse Collector log messages. Messages with severity below this level will not be logged.
Message severity levels:
- Debug—detailed debug messages.
- Trace—detailed informational and progress messages.
- Info—brief informational and progress messages.
- Warning—indicates minor recoverable errors or situations.
- Error—indicates more severe, but recoverable errors.
- Fatal—indicates severe, unrecoverable errors.
- Message which stand for informational messages that appear regardless to current log level.
Note: Log output of earlier Collector releases corresponds to the current Trace log level.
This release contains no resolved issues.
Refer to the Deployment Procedure for this release to deploy the installation package within your environment.