Running the Configuration Assistant

1. To display the Configuration Assistant, after the Oracle GoldenGate Veridata installation is complete, navigate to the bin directory, and run the following command:

   • If the Java location is set:

     vdtca.sh

   • If the Java location is not set:

     vdtca.sh -jreloc <java location>

   .

2. If you choose to install a new MySQL instance, then ensure that the system does not have any other MySQL database installed on the same node.

   Note: The Schema Prefix field supports only the following specific set of characters, as described in

   Permitted characters in unquoted identifiers

   of the MySQL Reference Manual:

   • ASCII: [0-9,a-z,A-Z$_] (basic Latin letters, digits 0-9, dollar, underscore)
   • Extended: U+0080 .. U+FFFF

   Certain special characters, such as hyphens or dashes (-) , are not allowed in the schema prefix.

   Note: If the Configuration Assistant detects a pre-existing MySQL instance in the system, then it displays the information with red text shown as follows:

   For releases 23c to 23.4.0.0:

   Figure 7: Repository Creation Page for a New MySQL Install

   

   For releases 23.5.0.0 and later:

   Figure 8: Repository Creation Page for a New MySQL Install

   

   • In version 23.5, you can choose to install MySQL either with sudo privileges or without sudo privileges, depending on your system permissions and installation requirements.

   • If you select the non-sudo option and click Next, a message is displayed to confirm a non-sudo installation.

   • If you select the sudo option, a message is displayed indicating that you must manually execute the MySQL startup script using sudo privileges to start the MySQL service.

   For Releases 23.26.4.0.0. and later

   For a new MySQL installation, the supported security protocols are:

   • PLAIN – Retains the existing behavior.
   • TLS – Supports the REQUIRED SSL mode.

   Figure 9: Repository Creation Page for a New MYSQL

   

   Note: If the Configuration Assistant shows a warning message saying it has detected a pre-existing MySQL for the new MySQL installation option, then run the following command: yum list installed | grep mysql and verify if any MySQL database or package is installed in the system. If you are sure that the MySQL database does not exist in the system, then you can safely ignore the warning and proceed with the configuration. For example, pcp-pmda-mysql.x86_64 package can cause a false warning.

   If MySQL is an existing database, then in the Repository Creation page, enter the database details for all the text fields.

   • The New Veridata Username and the Username cannot be same. The new veridata user which gets created as part of this process will be allowed to access only the Veridata repository being created.

   • Ensure that the user given in Username has full privilege on the Mysql instance as this user would create a veridata repository in database. If the user does not have the sufficient privileges then the same can be provided by running below queries in MySQL:

     CREATE USER 'superuser'@'%' IDENTIFIED BY 'superpassword';
     GRANT ALL PRIVILEGES ON *.* TO 'superuser'@'%' WITH GRANT OPTION;
     FLUSH PRIVILEGES;
     SHOW GRANTS FOR 'superuser'@'%';

     Figure 10: Repository Creation Page for an Existing MySQL

     

     For releases 23.26.4.0.0 and later

     For an existing MySQL repository, the Repository Creation UI includes a new Security Protocol option with the following values:

     • PLAIN – Retains the existing non-TLS behavior.
     • TLS – Supports PREFERRED, REQUIRED, VERIFY_CA, and VERIFY_IDENTITY.
     • mTLS – Supports REQUIRED, VERIFY_CA, and VERIFY_IDENTITY.

     Figure 11: Repository Creation Page for an Existing MYSQL

     

3. In the Memory Options page, for the Java Heap Sizes, select Use recommended settings (or modify according to your requirements) and click Next.

   Figure 12: Memory Options

   

4. In the Administrator Account Credentials page, enter the Veridata Administrator Username, Password, and Confirm Password and click Next.

   Figure 13: Administrator Account Credentials

   

5. The Security Options step of the Oracle GoldenGate Veridata Configuration Assistant allows users to configure the security settings for the Web User Interface (UI) by selecting encryption options, certificates, and communication ports. The primary function of this screen is to secure the connection between the client and the server using SSL/TLS protocols. This point outlines each of the available options and describes how to configure them.

• SSL / TLS Security for Web UI

  1. • Purpose: Purpose: Enabling this option ensures that communication between the Web UI / CLI and server is encrypted using SSL (Secure Sockets Layer) or TLS (Transport Layer Security).

     • Default Setting: This checkbox is enabled by default, meaning SSL/TLS is turned on.

     • Implications: If disabled, the communication will not be encrypted, making it vulnerable to eavesdropping and other security threats. You can opt in to disable SSL/TLS for faster and simpler deployment in a test environment.

  2. Certificate Configuration

     To secure the Web UI, Oracle GoldenGate Veridata uses X.509 certificates. The configuration wizard provides two ways to specify certificates outlined as follows:

     1. Use Veridata Self-Signed Certificate:

        • Purpose: Use this option if you want Veridata to automatically generate a self-signed SSL certificate.

        • Pros:

          • Quick and easy setup with no need for external certificate files

          • Useful in non-production environments or internal use cases where a trusted Certificate Authority (CA) is not necessary.

        • Cons:

          • Self-signed certificates are not trusted by web browsers without manual intervention.

          • Not suitable for production environments where certificates must be validated by a third-party CA.

     2. Upload Custom PEM Files

        • Purpose: This option allows users to specify their own SSL certificate, private key, and CA certificate files (in PEM format).

        • Required Files: This is the public certificate (usually with a .pem or .crt extension) that will be used to identify the server to clients.

          • File Input Field: Certificate

          • Example Path: /scratch/vdtInstall/web/certificate.pem

        • CA Certificate File: This file contains the certificate(s) of the Certificate Authority (CA) that signed the server certificate. The CA file is used to verify that the server certificate is trusted.

          • File Input Field: CA Certificate File

        • Example Path: /scratch/vdtInstall/web/ca.pem

        • When to Use: This option is best suited for production environments where an official SSL certificate issued by a trusted CA (such as Let’s Encrypt, DigiCert, or GoDaddy) is required.

  3. Port Configuration

     Oracle GoldenGate Veridata operates over specific ports, and users can define whether to use the default port or a custom one.

     1. Use Default Port (8831)

        • Purpose: The default port for SSL/TLS connections to the Veridata Web UI is 8831.

        • When to Use

          • Suitable for environments where port 8831 is open and available.

          • Easier to configure, especially in less restrictive network environments.

     2. Use Non-Default Port

        • Purpose: Allows users to specify a custom port for Veridata to use for SSL/TLS traffic instead of the default 8831.

        • When to Use

          • In cases where the default port (8831) is blocked or already in use.

          • When a specific port policy is enforced by your IT or security team (for example, using port 443 for HTTPS traffic).

          • Configuration: Enter the custom port number into the input field provided.

  Figure 14: Security Options

  

  For more information on replacing install generated Veridata Self-Signed certificates for WebUI, see Replacing Veridata Web Certificates.

1. Review the configuration summary on the Summary page. Click Save Response File to save the response file if needed.

   Figure 15: Configuration Assistant Summary

   

2. Open a terminal and run sudo su to change to root. After you see the following screen, run the script as root.

   Figure 16: Configure root

   

   Note: The root script should typically take 10-15 seconds.

   If the install_configure_mysql.sh script was executed successfully, the console will display the following information:

   • The Configuration Assistant will set the root user password as what you entered in the next stage of veridata repository creation.

   • MySQL has been installed and started.

   • Please return to the Configuration Assistant and click OK to continue.

     Then follow the console instruction, return to the Configuration Assistant and click OK to continue.

3. After a successful configuration, the Finish page displays the URL of Oracle Goldengate Veridata web application. Input the URL to a web browser to verify that the Oracle GoldenGate Veridata server is running.

   Figure 17: Configuration Complete