Overview

Universal Data Mover Gateway can use a database space of an existing database or you can install a database specifically for the Controller.

We recommend an initial size of 100MB.

Database Permissions

In order to install Universal Data Mover Gateway, the database user configured for the UDMG Server requires DDL (Data Definition Language) permission in the database during the install and during the migration steps for release upgrade.

Once the install has been completed successfully, the configured database user requires only DML (Data Manipulation Language) permissions for running the UDMG Server.

Database Management Systems

The following database management systems are supported:

Below are the generic steps for the preparation of a database instance for UDMG and how this can be done for the different database types. 

• database server
• database instance
• database user

Depending on the exact flavor, database type, environment topology, and other performance or security requirements, more advanced configuration parameters or procedures may be needed that are not in scope for this guide. 

Once the database user is ready, the database parameters can be setup in UDMG Server configuration. The database content is initialized on the first execution and further maintained during release upgrades (see the "Upgrading UDMG Server" in the Linux and Windows installation guides)

MySQL

[mysqld]
# Fix 'ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled'
log_bin_trust_function_creators = 1

mysql> CREATE DATABASE udmg;

MariaDB [(none)]> CREATE DATABASE udmg DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

mysql> CREATE USER 'udmg_user'@ IDENTIFIED BY 'udmg_password';
mysql> GRANT ALL PRIVILEGES ON udmg.* TO 'udmg_user'@ WITH GRANT OPTION;
mysql> FLUSH PRIVILEGES;

[mysqld]
# Fix 'ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled'
log_bin_trust_function_creators = 1

mysql> CREATE DATABASE udmg;

mysql> CREATE USER 'udmg_user'@ IDENTIFIED BY 'udmg_password';
mysql> GRANT ALL PRIVILEGES ON udmg.* TO 'udmg_user'@ WITH GRANT OPTION;
mysql> FLUSH PRIVILEGES;

PostgreSQL

PostgreSQL for Linux

1. Create a blank database on the server. An already existing database can be used, but this is not recommended.

2. Add a user that will be used as the owner of the related tables but also to authenticate with the server.
   In order to install or perform upgrades, this database user requires DDL (Data Definition Language) permission in the database during the installation or upgrade.
   Once the installation or upgrade has been completed successfully, the configured database user requires only DML (Data Manipulation Language) permissions.

Here is how to configure the database for a local installation where the database server is on the same host. For multi-node installation, please refer to your database administrator.

• Install a PostgreSQL database server.

• Once the installation is complete, initialize the PostgreSQL database.

• Enable and start the PostgreSQL Server:

• Create a user for UDMG Server.

Login as a PostgreSQL administrative user, start the PostgreSQL Console (psql), and create the database user for UDMG:

ALTER DATABASE udmg OWNER TO udmg_user;

• Finally, change the pg_hba.conf, to allow database connection with a password. For example, for a system where the database server is on the same host as the UDMG Server, by changing this line from:

to:

The exact configuration depends on the OS and database version, on the preferred security settings, and on the system architecture.

PostgreSQL for Windows

1. Create a blank database on the server. An already existing database can be used, but this is not recommended.

2. Add a user that will be used as the owner of the related tables but also to authenticate with the server.
   To install or perform upgrades, this database user requires DDL (Data Definition Language) permission in the database during the installation or upgrade.
   Once the installation or upgrade has been completed successfully, the configured database user requires only DML (Data Manipulation Language) permissions.

Here is how to configure the database for a local installation where the database server is on the same host. For multi-node installation please refer to your database administrator.

• Install a PostgreSQL database server.

• Once the installation is complete, initialize the PostgreSQL database.

• Start the PostgreSQL Server:

For example, from the Service Management Console management:

• Create a user for UDMG Server.

Login as a PostgreSQL user, start the PostgreSQL Console (psql), and create the database user:

Finally, change the pg_hba.conf, to allow database connection with a password.

For example, for a system where the database server is on the same host as the UDMG Server, by changing this line from:

to:

For a system where the database server is on the same subnet as the UDMG server, change it to:

The exact configuration depends on the OS and database version, preferred security settings, and system architecture.

The location of the pg_hba.conf can be returned by PostgreSQL Console (psql):

The current password encryption method can be returned by PostgreSQL Console (psql):

Oracle

Universal Data Mover Gateway requires the Oracle client libraries for connectivity to the Oracle database.

Microsoft SQL Server

USE [master]
GO
CREATE DATABASE udmg;
GO
CREATE LOGIN [udmg_user] WITH PASSWORD='pa55W0rd', DEFAULT_DATABASE=udmg;
GO
ALTER AUTHORIZATION ON DATABASE::[udmg] TO [udmg_user];
GO