Deploying an external configuration 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. Log in to the DB2 Command utility (Windows™) or DB2 host (UNIX™) as the DB2 administrator.
3. 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

Microsoft® SQL server script

Run the following command:

sqlcmd -i <sql file name> -U <username> -P <password> -S <host> -d <database name>

Type

The database type, which is either DB2, PostgreSQL, MSSQL, 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, CONFIG is the string that identifies the default database name:

   CREATE DATABASE CONFIG ALIAS CONFIG using codeset UTF-8 territory us
    PAGESIZE 8192 WITH "CONFIG Tables";

   Note: PAGESIZE 8192 is an example. Adjust according to your requirements.

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.

MSSQL 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 to connect to.

Instance name

The database instance name to connect to. When it isn't specified, a connection is made to the default instance.

Trust the server certificate

Select this check box if the server TLS/SSL certificate should not be validated.

Windows authentication

Select this check box to enable Windows (Kerberos) authentication for connections to the SQL server.

Keytab

If windows authentication is selected, then the keytab file is used instead of a password for authentication. Keytab files are uploaded using the Kerberos configuration.