Add Database Connections

You must have working database connections for your Extract and Replicat processes. Follow these steps to create database connections to connect your source and target hosts for replication.

Launch the Administration Service interface and log in.
Click **DB Connections** from the left navigation pane.
Click the plus sign (**+**) sign next to **DB Connections**. The Credentials dialog box is displayed.
Enter the following details in the displayed fields:

Note: All the fields listed below may not be applicable to all the databases. Review the details of each field to know if it is applicable to a database.

Credential Domain

Specify a domain name to which the database credential is associated. For example, “OracleGoldenGate” is the default domain name, in case you don’t specify a domain name.
Credential Alias

This is the alias for your database credential, such as ggeast.
Connection Type

Type of connection to be used to connect to the database. The following two connection types are available:
- Data Source Name: The DSN entry for the database connection.
- Database Server and Port: On selecting this option, the Database Hostname or IP Address and Port Number fields are displayed. Specify the database hostname or IP address and port number, respectively.
- Data Source Name
  
  The DSN entry for the database connection.
- Database Server / Database Hostname or IP Address
  
  Name or IP address of the server where the database is running.
- Port / Port Number
  
  Port number for connecting to the database server.
- Database Name
  
  Name of the database to which you want to connect.
- User ID
  
  User ID or username of the database user.
  Note: If the user name in the database has a dash in it, for example OGG-ADMIN, then the following error occurs:
```
OGG-08221 Cannot register or unregister EXTRACT *extract_name* because of the following SQL
error: OCI Error ORA (status = 44004-ORA-44004: invalid qualified SQL name.
```
- Password and Verify Password
  
  Password used by database user to log in to the database.
- Security Protocol
  
  Security protocol that is used to connect to the database. You can use the any of the following three security protocols:
  1. Plaintext
    
    It is the default security protocol when Connection Type is Database Server and Port.
  2. TLS
    
    On selecting this option for SQL Server, the Trust Server Certificate option is selected by default. If you deselect the Trust Server Certificate option, you would need to specify the values for SSL Path and SSL Certificate options.
  3. mTLS
  When TLS option is selected, the following two sub-options are displayed:
- SSL Mode: The available options are:
  - PREFERRED, REQUIRED, VERIFY_CA, and VERIFY_IDENTITY for MySQL.
  - PREFER, REQUIRE, VERIFY-CA, VERIFY FULL for PostgreSQL.
  Select the applicable SSL mode.
  
  On selecting PREFERRED or REQUIRED for MySQL or PREFER or REQUIRE for PostgreSQL, specify any additional applicable attributes in the Additional Attributes text box.
  
  On selecting VERIFY_CA or VERIFY_IDENTITY SSL mode for MySQL or VERIFY_CA or VERIFY_IDENTITY SSL mode for PostgreSQL, the following fields are displayed:
  - SSL Path: The path name of the directory that contains trusted SSL Certificate Authority (CA) certificate files.
  - SSL CA: The path of the CA certificate file in PEM format.
  - SSL CRL: The path of the file containing certificate revocation lists in PEM format.
- Additional Attributes: Specify any additional information in this field.
  
  When mTLS mode is selected, the following sub-options are displayed:
- SSL Mode: The available options are:
  - PREFERRED, REQUIRED, VERIFY_CA, and VERIFY_IDENTITY for MySQL.
  - PREFER, REQUIRE, VERIFY-CA, VERIFY FULL for PostgreSQL.
  On selecting PREFERRED or REQUIRED for MySQL or PREFER or REQUIRE for PostgreSQL, the following fields are displayed:
  - SSL Path: The path of the directory that contains trusted SSL Certificate Authority (CA) certificate files in PEM format.
  Note: For PostgreSQL, if the sslpath is specified then certificate names should not have full path however, if sslpath is not specified then the certificates must have complete path.
  - SSL Certificate: The path of the SSL public key certificate file in PEM format. On the client side, this is the client public key certificate and on the server side, this is the server public key certificate.
  - SSL Key: The path of the SSL private key file in PEM format. On the client side, this is the client private key, and on the server side, this is the server private key.
    
    On selecting VERIFY_CA or VERIFY_IDENTITY SSL mode for MySQL or VERIFY_CA or VERIFY_IDENTITY SSL mode for PostgreSQL, the following fields are displayed, in addition to the fields listed above:
  - SSL CA: The path of the CA certificate file in PEM format.
  - SSL CRL: The path of the file containing certificate revocation lists in PEM format.
  - Additional Attributes: Specify any additional information in this field.

Click Submit.
Click the **Connect database** icon to verify that the connection is working correctly. If the connection is successful, the Connect to database icon turns blue. You'll also see sections to set up checkpoint and heartbeat tables after the connection is successful.
From the DB Connections page, you can also perform the following tasks from the Action column:
- Connect to database
- Copy DB Connection
- Alter the DB Connection
- Delete the DB Connection

After successfully connecting to the database, you can add TRANDATA, SCHEMATRANDATA, checkpoint, and heartbeat tables required by Extract and Replicat.