- Success at-a-glance
- Detailed requirements descriptions
- Common pitfalls during the installation
- Diagrams of Single- and Multi-Node Installations
- Further Information
Jive Professional Services is here to assist you with your on-premises installation and configuration. Depending on the scope defined in your Statement of Work, Jive will either implement the installation or ride shot-gun with your IT team. The engagement will be conducted either on-site or remotely over web share.
It's in everyone's interests that the Installation/Configuration be as productive and efficient as possible. To that end, Jive Professional Services has developed the following pre-requisites and guidelines to ensure that Jive can hit the ground running as soon as we engage with your technical team. Please read and complete the sections below and return to your Jive Engagement or Project Manager prior to start of your Jive Professional Services project.
-Jive Professional Services
Ensure that the following items are available and completed before the date of your Jive installation. Each is described in far more detail later on.
|Application server(s) available||see details below||yes|
|Cache server(s) available||this is required if there are more than one web servers in the cluster||no|
|Doc conversion server(s) available||no|
|EAE server(s) available||yes|
|Search server(s) available||no|
|OS installed on all servers||see details below||yes|
|Root access to all servers||there are several OS-level configurations that require root access to alter. Installing Jive, however, can be done with a less-privileged account||no|
|Application database available|
|EAE database available||yes|
|Analytics database available||no|
|OCI driver installed||only for Oracle DB||yes|
|The dB account used by Jive must have the appropriate grants||CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE PROCEDURE, CREATE SYNONYM, CREATE TYPE||yes|
|Load balancer available||yes|
|Jive license available||yes|
|SMTP Information available||yes|
|Other config information available|
POP3 / IMAP, LDAP
Detailed requirements descriptions
Please read and understand the detailed descriptions below. Not having all the requirements below will slow the installation, and may even postpone it.
|Individual Hardware Node Requirements|
|Jive can be installed either on physical hardware or a virtual machine. Both virtual and physical machines need to fulfill the following requirements:|
|Physical Storage||Jive creates a new directory at /usr/local/jive. The associated mount point needs most of the 10 GB of space. The space needs will grow with time.|
|The following operating systems are supported. No other OSs are supported. Jive cannot be installed on Solaris, Windows or any other operating system not listed below.|
|Red Hat Enterprise Linux (RHEL)||An equivalent version of 64 bit CentOS is also supported|
|SUSE Linux Enterprise Server (SLES)|
|Note: The operating systems must be configured for UTF-8 encoding.|
|Hardware Node Descriptions|
|A Jive installation is comprised of several physical or virtual servers. Each server performs a distinct and important task, each requiring significant processing power and memory usage. Guaranteeing acceptable community performance is done by separating the tasks to their own server.Following is a list of all the nodes needed for a Jive installation. Each node needs to fulfill the hardware and operating system requirements.Note: All nodes should be in the same data center and should not have firewalls or filtering between them. The nodes pass large amounts of data with each other over several ports, some of them dynamically allocated. Filtering data between the servers can severely impact performance and functionality.|
|Application Node||Required||This contains the actual web application. At least one is required, but at least two are recommended for performance and redundancy. High-load systems will need multiple application servers.|
|Enterprise Activity Engine (EAE)||Required||This node processes and analyses user activity in the community, in order to present each user with information about new content most relevant to him.|
|Document Conversion server||Optional--only if document previews are desired||It is possible to present the user with a Flash-based preview of binary documents, for instance of PowerPoints, PDF or Word documents. Converting binary documents to flash is a CPU-intensive process, so requires its own server.|
|Cache Server||Required for multi-application server systems; not needed for single-application server systems||This is a far cache for multi-node system, used for improving performance in a high-load system. One cache server is sufficient for several application servers.|
|Both the Jive application server and the EAE server need to read and write to their own database. It is thus necessary to provide databases for two separate schemas. In addition, the analytics warehouse gathers usage information for later analysis. If this feature is to be activated, then a third schema (accessed from the Application server) is also necessary.The following databases are supported by Jive:|
|PostgreSQL||Jive is most heavily tuned and tested on PostgreSQL. It is the database Jive uses internally for both its production instances of Jive and for primary development.|
|Oracle||Both the web server and the EAE server support the latest Oracle drivers. See the section Oracle Drivers below for further details.|
|Microsoft SQL Server|
|Other Software / Services|
|The Jive installer provides most of the software needed, including the Apache web server, Tomcat web application server and other necessary third-party tools. It is possible, even likely, that necessary dependencies need to be installed for the Jive installation to succeed. For this reason, it is highly recommended that the various nodes all have access to the Internet, in order to install dependencies using yum, zypper or other dependency management system.Moreover, various services and systems should be made available for your Jive installation. It is necessary to have access information for them during the installation.|
|SMTP Server||Required||The Jive server needs the ability to send emails. It does so to inform users of new activity, to invite users to the community, to allow users to reset their password, and much more.|
|POP3 / IMAP Server||Optional||Jive allows users to create and respond to content via email. For instance, if a user receives an email notification about a new discussion, responding to that email automatically posts the response in the community. To achieve this, Jive needs a mailbox that it can periodically check for incoming mail. It needs read and write access to this mailbox.|
|AD / LDAP||Optional||It is possible to connect Jive to an internal AD instance for authentication. To do so, it needs global, read-only access to the AD installation, at least from the base DN and below. During installation, the following information is needed:|
|Jive Purchases access||Need to download the appropriate key||You must have at least one person with access to the Jive purchases page. This is found at https://myaccount.jivesoftware.com/purchases.jspa. If you do not access to this page, please file a case in your support group requesting it or contact your Jive representative.|
Here is a matrix indicating the Oracle drivers needed for the specific Jive version:
|JDBC Driver Notes|
IMPORTANT ORACLE INSTANT CLIENT NOTES
Support for the latest Oracle drivers was added in Jive 8.
For Oracle 11gR2 use 11.2, for Oracle 12c use 12.1.
Use the ojdbc7.jar during application configuration.
Jive versions < 8:
SBS Driver MUST use OCI, version 11.1.x or 10.2.x ONLY.
The 11.2 driver produces random segfaults and currently is not supported.
EAE Driver MUST use THIN, latest version recommended
188.8.131.52 is latest version as of 10/2012
|11gR2||Active||Yes||Y||Y||Y||Y||Y||Y||Latest Production Release|
It is important to note that, while OCI drivers are required on the web application nodes, only thin drivers may be used on the EAE nodes.
Common pitfalls during the installation
Missing root access to all of the servers
Running the Jive installer will fail unless done as root. A user with "admin" rights is not enough, but access to the root login shell via sudo is.
Missing admin access to the database
The installation needs to create a schema on the database. It is important for the database user to have full access (excluding GRANT rights) to the necessary databases.
OCI binaries not installed on the servers
Only a factor when using Oracle. Jive cannot be installed without 64 bit OCI instant client binaries installed on both the application and EAE servers.
No dependency manager on the servers
Jive is an extremely complex system and requires many packages that aren't always present in new OS installations. Resolving such dependencies is trivial if the servers have a package resolution software installed (yum, zypper or apt-get) and have access to the Internet. Without this, dependencies need to be downloaded and installed manually, which is at best extremely time-consuming.
Too little space on the servers, or improper disk allocation
It is important that the installer have enough disk space to complete its installation. Jive will also need enough disk space to run properly. Several gigabytes of space are needed in the /usr/local mount point, and at least one gigabyte in the root.
Jive License not available
Although an evaluation license is available for all Jive installations, a production license is necessary to property install and configure your Jive instance. At the very least, not having access to a production license means that optional systems such as analytics, Outlook Connector or Mobile Module cannot be installed and configured.
Improper encoding at the OS level or in the database
It is vitally important that UTF-8 be used at all levels of the installation. Jive cannot properly display international characters without UTF-8 encoding.
Diagrams of Single- and Multi-Node Installations
The following diagrams describe the various nodes and communication paths within a complete Jive installation.
Jive with a single application node
Jive with multiple application nodes
The Application Server contains the web application, HTTPD client and other services for properly servicing requests.The Enterprise Activity Server (EAE) performs CPU-intensive computation of the relevance of new and edited content in order to display it to the end-user. For instance, the activity server will determine if a piece of content should be brought to a person's attention given keywords found within the document, what the user is watching and what the user has indicated as important to him.The Document Conversion Server provides support for displaying web-based (flash) previews of Office documents, including Word, Excel, PDF and other documents. A document conversion server is strictly optional, but if it does not exist, it is not possible to provide a web preview and the user will first need to download the documents to view them. A Cache Server is also required to handle far-cache requests from all the application server. It is primarily a memory-intensive process.
|Topic||Jive 7.0||Jive 8.0||Jive 9.0|
|Supported Operating Systems||link||link||link|
|Deployment Sizing and Capacity Planning||link||link||link|
|Deploying to a Virtual Environment||link, link||link, link||link, link|
|Database Issues and Best Practices||link||link||link|