In this section:
DTP can be installed with or without an embedded database server (Windows and Linux only). See Installing and Configuring the Database for database requirements, as well as for instructions on installing a MySQL database. Contact your Oracle database administrator if you are using an Oracle database.
DTP Enterprise Pack Database
DTP Enterprise Pack, which includes Extension Designer and Policy Center, ships with it's own embedded MongoDB. If you are installing DTP Enterprise Pack, we recommend using an XFS file system in Linux per the MongoDB documentation.
MongoDB on Linux
Kernel and File Systems
When running MongoDB in production on Linux, you should use Linux kernel version 2.6.36 or later, with either the XFS or EXT4 filesystem. If possible, use XFS as it generally performs better with MongoDB.
With the WiredTiger storage engine, use of XFS is strongly recommended to avoid performance issues that may occur when using EXT4 with WiredTiger.
Asynchronous I/O Library
The libaio package, which is included in some Linux distributions, is required if you are using the DTP distribution for Linux that ships with an embedded database server. If the library is not already on your Linux system, install it using the appropriate package manager for your distribution. The following instructions are provided to help you install libaio on several common Linux distributions:
Red Hat and CentOS
sudo yum install libaio
sudo apt-get install libaio1
Install the RPM for the libaio package from the Fedora website at http://fedoraproject.org/.
Minimum Number of Database Connections
The database server should provide at least 150 concurrent connections for DTP. If the database server does not provide sufficient connections, DTP may not be able to create a new connection to the database prior to reaching the maximum number of connections.
The standard DTP distribution installation does not ship with the MySQL and Oracle JDBC drivers necessary to set up a database connection. You will need to download following drivers:
- MySQL Java Connector, version 5.1.32 or later.
- Oracle Database JDBC Drivers - Minimum version is 11g Release 2 - Java 1.6 (ojdbc6.jar).
When the installation is complete, place the drivers in the
You do not need to download and install the JDBC drivers if you are installing the DTP distribution that includes an embedded database server. The drivers are packaged with the database server so that you can begin using the database immediately.
The MySQL Connector/J 8.0 JDBC driver has a known defect that may impact MySQL servers hosted on CentOS and Red Hat Enterprise Linux systems. See https://bugs.mysql.com/bug.php?id=90813 for details.
MySQL Charset and Collation Settings
The MySQL creation scripts for the DTP and GRS databases use the character set utf8 and collation utf8_general_ci so that UTF-8 characters (e.g., Japanese or Chinese) can be stored in the database. DTP does not support UTF-8 4 byte character encoding ("utf8mb4")
The MySQL server character set and collation must also be set to UTF-8 to save UTF-8 characters in the database. We highly recommend that the MySQL server changes are made prior to creating the DTP and GRS databases:
- Locate the my.ini (Windows) or my.cnf (Linux) and open it in an editor
- In the section under [mysqld], add/edit the following properties:
character-set-server = utf8
collation-server = utf8_general_ci
See the MySQL documentation for more information about server character set configuration: https://dev.mysql.com/doc/refman/5.6/en/charset-server.html.
Oracle Charset and Collation Settings
Oracle recommends setting the target character set to AL32UTF8. See the Oracle Database Migration Assistant for Unicode documentation for instructions: https://docs.oracle.com/database/121/DUMAG/ch2migrasteps.htm#DUMAG136.
DTP may make many simultaneous requests to the server, which may cause the MySQL server to open many files at the same time to process the requests. As a result, the limit on open file descriptors set by MySQL may be exceeded. Please refer to the MySQL documentation for more information on this issue, including possible resolutions: http://dev.mysql.com/doc/refman/5.6/en/table-cache.html.