Optional: Configure Pulse Collector with an embedded DB Server
When Genesys Pulse Collector runs an embedded DB Server, Genesys Pulse Collector does not require a separate DB Server instance to connect to the Genesys Pulse DB.
You can enable an embedded DB Server in Genesys Pulse Collector by setting the dbthread option in the [collector] section to yes.
The Database Access Point application object used by Genesys Pulse Collector should have None value specified in DB Server field on General tab.
Genesys Pulse Collector uses Genesys DB Clients, which require DBMS clients to be installed. Refer to Environment Settings for more information.
You should have the necessary clients installed if the following are true:
- You had the Genesys DB Server installed on the host with Genesys Pulse Collector.
- The Genesys DB Server and Genesys Pulse Collector are of the same architecture (32- or 64-bit).
Embedded DB Server 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 a [log-db] section to collector application options and add all of the options that usually go to the [log] section of Genesys DB Server application.
If there is no [log-db] section specified in collector application options, the embedded DB Server log uses the options found in [log] section, except for the following:
- The value for the verbose option is set to standard.
- The log is written to the file specified in [log] section, with -db suffix added.
- The Linux version of Genesys Pulse Collector running with embedded DB Server is unable to connect to MS SQL Server database.
- Starting with release 9.0.001, Genesys Pulse Collector running with embedded DB Server can connect to Oracle 12c database without any additional installation of Oracle 11.2 clients on the host. For release 9.0.000, make sure that you install Oracle 11.2 client on the host that runs Genesys Pulse Collector.