Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
System administrationThese topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL OneDB™ database servers.
Administrator's GuideThe HCL OneDB™ Administrator's Guide provides the information required to administer HCL OneDB™.
High availability and scalabilityA successful production environment requires database systems that are always available, with minimal if any planned outages, and that can be scaled quickly and easily as business requirements change.
Connection management through the Connection ManagerConnection Managers can control automatic failover for high-availability clusters, monitor client connections and direct requests to appropriate database servers, act as proxy servers and handle client/server communication, and prioritize connections between application servers and the primary server of a high-availability cluster. Connection Managers support high-availability clusters, replicate sets, server sets, and grids.
Configuring connection managementTo configure connection management, you must install software, set environments and connectivity information, create Connection Manager configuration files, and run the oncmsm utility.
Creating Connection Manager configuration files
Parameters and format of the Connection Manager configuration fileThe following example shows the format of the Connection Manager configuration file, and shows which parameters and attributes can be set for each connection-unit type.
NAME Connection Manager configuration parameterThe NAME parameter specifies the name of the Connection Manager instance.

NAME Connection Manager configuration parameter

The NAME parameter specifies the name of the Connection Manager instance.

Syntax

Usage

The NAME parameter is required, and applies to the Connection Manager instance.

The name of the Connection Manager instance is necessary for monitoring, shutting down, or reloading the Connection Manager.

Connection Manager names must be unique in the domain of the connection units that are managed.

Example

In the following example, a Connection Manager instance is named my_connection_manager.

NAME my_connection_manager