Jump to: navigation, search

8.5.106.02

Genesys Pulse Collector Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
12/21/16 General X X

Helpful Links

What's New

  • 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:

    [collector] Section
    dbthread
    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 Guide to 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:

    1. Stop DB Server.
    2. Clear the DB Server field of Database Access Point application object used by Pulse Collector.
    3. 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 Server field on General tab of Database Access Point application object that is used by Pulse Collector should be set to None.

    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-db section to Collector Application options and fill it with all the options that usually go to the log section of Genesys DB Server application. If there will be no log-db section specified in Collector Application options, the logging of embedded DB Server will be controlled by options found in log section except for the following:

    1. The value for verbose option is set to standard.
    2. The log is written to the file specified in log section, but with -db suffix added.

    Limitations

    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.

    [log] Section
    collector-log-level
    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.


Resolved Issues

This release contains no resolved issues.


Upgrade Notes

Refer to the Deployment Procedure for this release to deploy the installation package within your environment.

Supported Languages

See Release 8.5.1 Translation Support.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on April 26, 2018, at 19:33.