Supported Operating Systems and Databases

Installing and running Jive requires a Linux server operating system and a dedicated database.

Supported OS - Including the latest 3 service packs and a bash shell
RedHat Enterprise Linux (RHEL) version 5 or 6 for x86_64 CentOS version 5 or 6 for x86_64 SuSE Enterprise Linux Server (SLES) 10 for x86_64. SLES 11 for x86_64 is supported in Jive versions 5.0.1 and higher.

Supported OS - Including the latest 3 service packs and a bash shell

RedHat Enterprise Linux (RHEL) version 5 or 6 for x86_64

CentOS version 5 or 6 for x86_64

SuSE Enterprise Linux Server (SLES) 10 for x86_64. SLES 11 for x86_64 is supported in Jive versions 5.0.1 and higher.

Supported Databases
Oracle 10 and 11 Postgres 8.3 and 9 MySQL 5 and 5.5 MS SQL Server 2005, 2008, and 2008 R2

Supported Databases

Oracle 10 and 11

Postgres 8.3 and 9

MySQL 5 and 5.5

MS SQL Server 2005, 2008, and 2008 R2

Important Notes and Restrictions

A bash shell is required on Linux when installing, upgrading, and interacting with the application.
DO NOT deploy Jive and all of its services (application database, analytics database, Activity Engine, cache server, and if you have it, document conversion) from one server. This is not supported. Your web app nodes, Activity Engine, cache server, and document conversion must all be stored on separate servers. You can store the analytics database and core application database on one server, but you must ensure isolation. Be sure to read Database Issues and Best Practices.
The analytics database is supported only on the PostgreSQL and Oracle DBMSes.
The application includes a PostgreSQL DBMS. This pre-packaged DBMS is for evaluation purposes and should not be used for production instances.
At this time Jive supports virtualization running on RHEL or SLES as guest operating systems in a VMware environment. For information on the recommended configuration, see Deploying to a Virtual Environment.
For performance reasons, if you're using the document conversion feature, you must put the conversion software on a machine that is separate from the application server. For more information, see Setting Up a Document Conversion Machine.