Database Prerequisites

Before you install Volt MX Foundry Console Installer, you must perform the following pre-installation tasks:

• Ensure access to a database server.

• A database user should be granted all required permissions as per this document.

• To use your existing SSL certificate, map the SSL certificate to the domain name you want to use.
• To install in domain (multi-node) mode, the JBoss cluster should be preconfigured.

Prerequisites for Volt MX Foundry with Oracle

For installing Volt MX Foundry Database for Oracle, complete the following steps:

Note: Only a qualified Oracle Database Administrator (DBA) must handle the Oracle Database setup in order to successfully complete the Volt MX Foundry database deployment. Oracle software must be installed and basic database must be created before to continue with Volt MX Foundry database schema setup.

Important:  Ensure that a dedicated database user must not be an application user for installation of database. A dedicated user gets logged into audit logs.
After granting privileges, disconnect existing session, and use new session in order to get the new privileges loaded to the user.

    CREATE TABLESPACE MF_DATA DATAFILE '<DATA_FILE_PATH>/MF_DATA_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;
    CREATE TABLESPACE MF_INDEX DATAFILE '<DATA_FILE_PATH>/MF_INDEX_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;
    CREATE TABLESPACE MF_LOB_DATA DATAFILE '<DATA_FILE_PATH>/MF_LOB_DATA_01.DBF' SIZE 2048M AUTOEXTEND ON NEXT 100M MAXSIZE 5120M;
    
    

        CREATE USER <install-user> IDENTIFIED BY <password> DEFAULT TABLESPACE MF_DATA TEMPORARY TABLESPACE TEM PROFILE DEFAULT;
        GRANT DBA TO <install-user>;
        ALTER USER <install-user> QUOTA UNLIMITED ON MF_DATA;
        ALTER USER <install-user> QUOTA UNLIMITED ON MF_INDEX;
        ALTER USER <install-user> QUOTA UNLIMITED ON MF_LOB_DATA;
        
        

        Alter session set container = PDB<MF_DB> ;
        CREATE USER <dedicated-database-local-user> IDENTIFIED BY <password> DEFAULT TABLESPACE MF_DATA TEMPORARY TABLESPACE TEMP PROFILE DEFAULT  CONTAINER=CURRENT;
        GRANT DBA TO <install-local-user> CONTAINER=CURRENT;
        ALTER USER <install-local-user> QUOTA UNLIMITED ON MF_DATA CONTAINER=CURRENT;
        ALTER USER <install-local-user> QUOTA UNLIMITED ON MF_INDEX CONTAINER=CURRENT;
        ALTER USER <install-local-user> QUOTA UNLIMITED ON MF_LOB_DATA CONTAINER=CURRENT;
        
        

        jdbc:oracle:thin:@<Database_Host_IP>:1521/pdbmfdb 
        

        jdbc:oracle:thin:@<Database_Host_IP>:1521:mfdb
        

    For example: jdbc:oracle:thin:@192.168.1.2:1521:mfdb

Prerequisites for Volt MX Foundry with SQL Server

• Database User security role: Create a database login dbclient using SQL server authentication with server roles as sysadmin and public
• Database and schema access: Installer will make use of the above login to create necessary databases and schemas required for the selected Volt MX Foundry components.
• Database Growth sizing: Refer to VoltMX Foundry Deployment Guide > Database Growth Sizing
• Database Transaction log size: Allocate sufficient space for the Transaction log file based on all the transactions activity of all the Volt MX Foundry components installed and as per your database backup policy. Because transaction log sizing is linked to database backup. If additional application logging/events are enabled in multiple components of Volt MX Foundry, then you may need to consider additional size for the transaction log.
• Temp Database and temp log: This is based on usage of all the databases on the server instance, by all applications connecting to these databases. In case of Volt MX Foundry, for sizing of the temp database, consider auto growth with increment size should be of 100MB and with maximum size to 10GB. But if application logging/events are enabled in multiple components of Volt MX Foundry, then the maximum size should be increased upto 20GB. This size will get reclaimed as and when the DB is restarted.
• Database versions: You can use SQL Server Standard Edition or SQL Server Enterprise Edition database for installing Volt MX Foundry. Volt MX Foundry is compatible with these editions. There are no prerequisites specific to these editions as Volt MX Foundry uses features common to both editions.
• Backup plan: You must use your organization’s defined backup and retention policies for Backup strategies for your database.

Prerequisites for Volt MX Foundry with MSSQL - Applicable for Engagement Services

Database collation needs to be set for a database. This is possible while creating a database with your required language as database collation. For example, use Database collation as Arabic_100_CI_AS for Arabic language support. Similarly for other languages use appropriate collation for support. Use SQL Server Management Studio to create a database with the name as vpnsdb and with appropriate collation support.

Prerequisites for Volt MX Foundry with MySQL

Applicable for Engagement Services

1. Create the database needed for Engagement Services with unicode character set as UTF8. Also ensure that you modify the my.cnf or my.ini with the following parameters:

    \[client\]  
    default-character-set = utf8  
    \[mysql\]  
    default-character-set = utf8  
    \[mysqld\]|  
    character-set-client-handshake = FALSE  
    collation\_server='utf8\_unicode\_ci'  
    character\_set\_server='utf8'  
    

1. Next, restart the MySQL service and run the following query to verify the details:

    mysql> show variables like '%coll%';  
    +----------------------+-----------------+  
    | Variable\_name | Value |  
    +----------------------+-----------------+  
    | collation\_connection | utf8\_unicode\_ci |  
    | collation\_database | utf8\_unicode\_ci |  
    | collation\_server | utf8\_unicode\_ci |  
    +----------------------+-----------------+  
    3 rows in set (0.00 sec)  
    mysql> show variables like '%char%';  
    +--------------------------+----------------------------+  
    | Variable\_name | Value |  
    +--------------------------+----------------------------+  
    | character\_set\_client | utf8 |  
    | character\_set\_connection | utf8 |  
    | character\_set\_database | utf8 |  
    | character\_set\_filesystem | binary |  
    | character\_set\_results | utf8 |  
    | character\_set\_server | utf8 |  
    | character\_set\_system | utf8 |  
    | character\_sets\_dir | /usr/share/mysql/charsets/ |  
    +--------------------------+----------------------------+
    

Applicable for Identity Services

If you are using any lower versions of MySQL 5.7 such as v5.7.12 or lower during installation, you may encounter an error due to which the installation rolls back. This error occurs due to a bug in the MySQL database.

For more information, refer MySQL Bugs

Following are the error details:

• Error: Migration V810_27_01__DeleteDuplicateAcsUserIdProviderGuidRowsAddUniqueConstraint.sql failed
• SQL State: HY000
• Error Code: 1093
• Error Message: You can’t specify target table ‘users’ for update in FROM clause
• Location:

To resolve this error, run the following commands in the MySQL Server:

1. Execute the following command before running the installer:

SET GLOBAL optimizer_switch = 'derived_merge=off';

2. Once the installation is done, set derived_merge ON using the following command:

SET GLOBAL optimizer_switch = 'derived_merge=on';

Steps before installing (or) upgrading Volt MX Foundry with the existing database

Perform the following activities before installing (or) upgrading Volt MX Foundry with the existing database:

• Take database backup
• Make sure you have previously installed directory
• Take a backup of applications deployed at the server level. (Post installation, take backup of the changes done to the binaries).
• Post installation (or) upgrade process, replace old authService.key, workspaceService.key, and ACCOUNTS_ENCRYPTION_KEY   (applicable only for identity and workspace components).

Create /tmp Folder

Volt MX Foundry Installer required a /tmp folder in Linux environment to unpack installer. When the /tmp folder is not found, the Installer shows I/O exception at the time of unpack exception, shown below:

This must specify in the pre-req of installation. Installation must required temp folder to unpack MF installer (either default / custom temp folder).