Skip to main content

Vastbase G100 Database Integration Guide

HAP Server uses MySQL as its default relational database. Since v7.5.4, it also supports Vastbase. For environments with domestic technology requirements, you can use this database instead of MySQL.

Follow these integration steps:

  1. Deploy Vastbase G100 V2.2 in B mode (MySQL compatibility mode), using a standalone or primary-standby configuration.

    For HAP standalone deployments or simplified clusters, choose standalone mode. For standard or professional clusters, choose primary-standby mode.

  2. Download the HAP database initialization scripts.

  3. Initialize the data

    Connect to Vastbase using vsql, which is available after deployment.

    Run the initialization scripts (adjust the vastdata data directory and SQL file paths for your environment). Enter the password when prompted.

    The following example uses /data/vastdata as the data directory.

    vsql -h /data/vastdata -U vastbase -d postgres -f /usr/local/init_vastbase/1_Database.sql
    vsql -h /data/vastdata -U vastbase -d mdproject -f /usr/local/init_vastbase/2_MDProject.sql
    vsql -h /data/vastdata -U vastbase -d mdstructure -f /usr/local/init_vastbase/3_MDStructure.sql
    vsql -h /data/vastdata -U vastbase -d mdapplication -f /usr/local/init_vastbase/4_MDApplication.sql
    vsql -h /data/vastdata -U vastbase -d mdcalendar -f /usr/local/init_vastbase/5_MDCalendar.sql
    vsql -h /data/vastdata -U vastbase -d mdlog -f /usr/local/init_vastbase/6_MDLog.sql
    vsql -h /data/vastdata -U vastbase -d mdproject -f /usr/local/init_vastbase/7_Data_MDProject.sql
    vsql -h /data/vastdata -U vastbase -d mdapplication -f /usr/local/init_vastbase/8_Data_MDApplication.sql
  4. Create an application account

    Connect to the database using the vastbase account:

    vsql -h /data/vastdata -U vastbase -d postgres

    Create an account (for example, hap), replacing the password placeholder with an actual password:

    CREATE USER hap WITH PASSWORD '<HAP_PASSWORD>';

    Run the following in vsql to grant read and write permissions on the five application databases:

    \c mdproject
    GRANT CONNECT ON DATABASE mdproject TO hap;
    GRANT USAGE ON SCHEMA public TO hap;
    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO hap;
    GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO hap;

    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO hap;
    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT USAGE, SELECT ON SEQUENCES TO hap;

    \c mdstructure
    GRANT CONNECT ON DATABASE mdstructure TO hap;
    GRANT USAGE ON SCHEMA public TO hap;
    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO hap;
    GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO hap;

    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO hap;
    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT USAGE, SELECT ON SEQUENCES TO hap;

    \c mdapplication
    GRANT CONNECT ON DATABASE mdapplication TO hap;
    GRANT USAGE ON SCHEMA public TO hap;
    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO hap;
    GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO hap;

    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO hap;
    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT USAGE, SELECT ON SEQUENCES TO hap;

    \c mdcalendar
    GRANT CONNECT ON DATABASE mdcalendar TO hap;
    GRANT USAGE ON SCHEMA public TO hap;
    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO hap;
    GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO hap;

    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO hap;
    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT USAGE, SELECT ON SEQUENCES TO hap;

    \c mdlog
    GRANT CONNECT ON DATABASE mdlog TO hap;
    GRANT USAGE ON SCHEMA public TO hap;
    GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO hap;
    GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO hap;

    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO hap;
    ALTER DEFAULT PRIVILEGES FOR ROLE vastbase IN SCHEMA public
    GRANT USAGE, SELECT ON SEQUENCES TO hap;

    \q

    Allow Remote Connections Edit /data/vastdata/pg_hba.conf on the server and add the following before existing reject rules:

    hostssl mdproject,mdstructure,mdapplication,mdcalendar,mdlog hap <客户端或应用服务器来源IP>/32 sha256

    Replace <客户端或应用服务器来源IP> with the actual source IP address used to connect to the database. /32 permits only that IP address.

    Reload the configuration as the vastbase system user; no restart is required:

    vb_ctl -D /data/vastdata reload
  5. Initialize HAP services

    Before initializing services, add the following environment variables (replace connection parameter values with actual values):

    ENV_RDB_TYPE: "12"
    ENV_RDB_URI_MDPROJECT: "Host=127.0.0.1;Port=5432;Username=hap;Password=******;Database=mdproject"
    ENV_RDB_URI_MDLOG: "Host=127.0.0.1;Port=5432;Username=hap;Password=******;Database=mdlog"
    ENV_RDB_URI_MDSTRUCTURE: "Host=127.0.0.1;Port=5432;Username=hap;Password=******;Database=mdstructure"
    ENV_RDB_URI_MDCALENDAR: "Host=127.0.0.1;Port=5432;Username=hap;Password=******;Database=mdcalendar"
    ENV_RDB_URI_MDAPPLICATION: "Host=127.0.0.1;Port=5432;Username=hap;Password=******;Database=mdapplication"
    ENV_STANDALONE_DISABLE_SERVICES: "mysql"
  6. Complete the remaining system initialization steps.