Deploying an external configuration database

To optimize performance or increase storage capacity for the appliance, you can deploy an external configuration database. You can configure the appliance to connect to DB2®, PostgreSQL, or Oracle database on an external server.

1. Use the File Downloads management page in the local management interface to access the configuration database deployment files for your environment.

   Table 1. Configuration database deployment scripts

   Database type	Deployment scripts
   DB2	/access_control/database/db2/config/cluster_config_db2.sql
   PostgreSQL	/access_control/database/postgresql/config/cluster_config_postgresql.sql
   Oracle	/access_control/database/oracle/config/cluster_config_oracle.sql

2. Save the deployment script on the database server.
3. Run the DB2, PostgreSQL, or Oracle script to create the external database.

   PostgreSQL script

   Run the following command:

   psql --echo-all --variable ON_ERROR_STOP=1 --file <sql file name> 
   --username <username> --host <host> --port <port> <database name>

   Oracle script

   1. Copy the downloaded cluster_config_oracle.sql file into the Oracle home directory. For example, ORACLE_HOME=/opt/oracle/app/oracle/product/11.2.0/dbhome_1 
   2. Log in to SQL*Plus.
   3. At the SQL prompt, run START cluster_config_oracle.sql.

   DB2 script

   1. Create a DB2 instance to contain the configuration database. For information about creating the DB2 instance, see the DB2 documentation.
   2. Open the cluster_config_db2.sql file in an editor on the DB2 server.
   3. Replace the following macros with the values specific to your environment:

      &DBINSTANCE

      The name of the DB2 instance.

      &DBUSER

      The name of the DB2 administrator.

      &DBPASSWORD

      The password for the DB2 administrator.

   4. Save the changes.
   5. Log in to the DB2 Command utility (Windows) or DB2 host (UNIX) as the DB2 administrator.
   6. Run the following command:

      db2 -tsvf <fully_qualified_path_to_script>

      The following example shows the fully qualified path to the script:

      db2 -tsvf /tmp/cluster_config_db2.sql

4. Validate that the tables were successfully created.
5. Ensure that no errors were returned during the creation and log in to the database to manually check that the tables exist.
6. From the top menu of the local management interface, select Manage System Settings > Cluster Configuration to open the Cluster Configuration management page.
7. Select the Database tab.
8. You must enter the following JDBC connection information:

   Type

   The database type, which is either DB2, PostgreSQL, or Oracle.

   Address

   The IP address 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 also requires the following information:

   Secure

   Select this check box to create a secure connection with the server.

   Note: Before a secure connection can be established, you must first import the certificate that the appliance uses to communicate with the server 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.

   Complete the following steps to identify and specify the DB2 database name when your DB2 database is remote to the cluster that you are configuring.

   1. Open the cluster_config_db2.sql file that was used to create the database and tables.
   2. In the CREATE DATABASE entry, get the name that is specified. In the following entry, HVDB is the string that identifies the default database name:

       CREATE DATABASE HVDB ALIAS HVDB using codeset UTF-8 territory us 
           COLLATE USING UCA400_NO PAGESIZE 8192 WITH "HVDB Tables";

   PostgreSQL also requires the following information:

   Secure

   Select this check box to create a secure connection with the server.

   Note: Before a secure connection can be established, you must first import the certificate that the appliance uses to communicate with the server 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.

   Oracle also requires the following information:

   Secure

   Select this check box to create a secure connection with the server.

   Note: Before a secure connection can be established, you must first import the certificate that the appliance uses to communicate with the server into the lmi_trust_store and also a keystore which only contains public keys that needs to be created. Use the SSL Certificates page to create this keystore and to import the appropriate certificate

   Certificate Store

   Choose the keystore which contains the certificate that will be used to communicate with the server.

   Service name

   Specify the name of the Oracle instance on the external server. Contact your Oracle database administrator for this information. SID will work but might show a warning in the LMI on saving configuration. This can be ignored.

9. Click Save.
10. Deploy the changes.