This page was last edited on January 14, 2021, at 01:03.
Comments or questions about this documentation? Contact us for support!
Section: settings
Default Value: No default value
Valid Values: Any valid service name
Changes Take Effect: After restart
Specifies the network service name of a database; see the service_names parameter in the init.ora (or init<dbName>.ora) file. If the service name is specified, the service name replaces the database name. This option applies only to Oracle databases.
Purpose: To set up the database or databases that UCS will use.
RDBMS, either Oracle or Microsoft SQL. See also the eServices 8.0 Deployment Guide. See the Deployment category page for overall prerequisites for deploying UCS.
Genesys supplies upgrade scripts for all releases starting with 7.0.1.
To connect UCS to an Oracle Real Application Cluster (RAC), configure a DAP for UCS as follows:
Here is an example configuration for three nodes, named rac1, rac2, and rac3. The DB port is 1521 and the ONS port is 6251 for all nodes.
[ServerInfo] host: rac1 ports: default, 1521 [Options > settings] ONSConfiguration: nodes=rac1:6251,rac2:6251,rac3:6251 host1: rac2 port1: 1521 host2: rac3 port2: 1521
Support of Oracle RAC also requires that you deploy the Universal Connection Pool library.
When connected to an Oracle RAC configuration, the UCS database layer uses the ucp.jar file for connection handling. If UCS is started against an Oracle RAC without the jar file, UCS will fail to start.
Starting from version 8.5.300.36, UCS now provides the ucp.jar file as part of the installation package.
The below section applies only for UCS versions prior to 8.5.300.36
To deploy the UCP library: