Overview

For best results and to optimize the features of the Jive installation, configure and maintain the MySQL database based on the vendor's requirements and apply these Jive best practices.

 

Information

For a list of supported version of Databases with Jive, you can refer to the Oracle, PostgreSQL, MySQL and MSSQL database versions supported by Jive article.

UTF-8 requirement

Jive requires the UTF-8 character set. Use the following steps to ensure it is correctly set up:

1. Use the following command to set the database default character set to UTF-8:

   ALTER DATABASE jivecoredb DEFAULT CHARACTER SET utf8;

2. After installation, add the following to the database section of the jive_startup.xmlfile:

   <mysql><useUnicode>true</useUnicode></mysql>

3. In the Jive Admin Console, under System > Management > Locale, ensure that the character set is UTF-8.

 

Installing the driver

The core application and the Activity Engine run using the MySQL JDBC Connector/J driver. The Analytics database is not supported by MySQL.

You can set your classpath to include the MySQL JDBC Connector/J driver by running the following from a command line as the jive user:

jive set webapp.custom_classpath_additions path/JDBC_Driver.jar

where path is the path to the MySQL JDBC driver and JDBC_Driver.jar is the name of the JAR file.

 

Other best practices with MySQL

The default configuration can vary significantly by version, so it is important to consider the following:

• The default storage engine and all Jive tables should use the InnoDB storage engine. Earlier versions of MySQL used BDB\MyISAM as the default storage engine.
• Ensure that the InnoDB Buffer is adequately sized. For dedicated installations with InnoDB storage engines, the buffer is typically set to 80% of the total server available memory.
• Storing attachments in your Jive database is not recommended. If this cannot be avoided, ensure that the maximum attachment size is allowed in the MySQL configuration. For more information, see this Packet Too Large in the MySQL 5.1 Reference Manual.
• With case sensitivity, to avoid upgrade problems, use lower-case table names in MySQL and set the lower_case_table_namessystem variable to 1 in the MySQL configuration. For more information, see Server System Variables in the MySQL 5.0 Reference Manual.