Configuration database

We can view and update the current configuration database settings with the Configuration Database tab on the Cluster Configuration management page. If Oracle is set as the external configuration database and either the local management interface or runtime server trace specification includes Oracle trace points (for example, oracle.*) the underlying Oracle JDBC jar file is changed to a debugging jar file. This might have adverse effects on performance and as such Oracle tracing should only be enabled for debugging purposes and disabled once complete. Warning: Enabling trace for Oracle components “oracle.*” might result in the Oracle database administrator password being logged in clear text.

The configuration database stores configuration data, including policy information. This data is shared with all appliances in the cluster.

Local to the cluster

Use of the internal configuration database.

Database export

Exports the current configuration data from the internal database so that it can be imported into an external database of the chosen type. This option is useful if we want to migrate the appliance's internal configuration database to an external database. Supported external database types are DB2, Oracle, and PostgreSQL. The exported data are compressed into a zip file. A readme file is included in the zip file to provide instructions on how to import the data into the external database. For DB2 and Oracle, the configuration database schema (table and index definitions), which is available from the File Downloads area of the appliance, must be applied to the database that will house the configuration data before the data can be imported. For PostgreSQL, this step is not required as the zip file also contains the database schema.

Remote to the cluster

Use of an external configuration database. Specify the following information for the external configuration database:

Use external database for internal file sharing

Allow the configurations to be modified on non-primary nodes of the cluster. When we enable this option, the appliance will be rebooted when the change is committed. During the reboot, the files will be migrated between the local file system and the external configuration database.

Type

The database type, which is one of DB2, Oracle, or PostgreSQL.

Address

The IP address or hostname of the external database server.

Port

The port on which the external database server is listening.

Username

The name of the database administrator.

Password

The password for the database administrator.

DB2

Secure

Select this check box to create a secure connection with the DB2 server. Before a secure connection can be established, we must first import the certificate for the appliance to use for communication with the DB2 server. The certificate must be imported into the lmi_trust_store and rt_profile_keys key files. Use the SSL Certificates page to import the appropriate certificate.

Database name

The name of the database instance on the external DB2 server.

Enable HADR and ACR

Select this checkbox to enable High Availability Disaster Recovery and Automatic Client Reroute.

Alternate Address

The IP address or hostname of the failover database server in the HADR configuration.

Alternate Port

The port on which the failover database server in the HADR configuration is listening.

Oracle

Secure

Select this check box to create a secure connection with the Oracle server. Before a secure connection can be established, we must first import the certificate for the appliance to use for communication with the Oracle server. The certificate must be imported into the lmi_trust_store and rt_profile_keys key files. Use the SSL Certificates page to import the appropriate certificate.

Service name

The name of the service instance on the external Oracle server.

Driver type

Type of Oracle JDBC driver used to connect to the Oracle server. Available options are Thin and OCI.

PostgreSQL

High availability, with an external PostgreSQL server, is achieved through the use of an external load balancer.

Secure

Select this check box to create a secure connection with the PostgreSQL server. Before a secure connection can be established, we must first import the certificate for the appliance to use for communication with the PostgreSQL server. The certificate must be imported into the lmi_trust_store and rt_profile_keys key files. Use the SSL Certificates page to import the appropriate certificate.

Database name

The name of the database instance on the external PostgreSQL server.

• Deploying an external configuration database
  To optimize performance or increase storage capacity for the appliance, we can deploy an external configuration database. We can configure the appliance to connect to DB2, PostgreSQL, or Oracle database on an external server.

Parent topic: Manage cluster configuration