Post-Installation Tasks

This section is intended to provide sample configurations and script examples common to long-term operation of a Jive installation. As opposed to the Run Book (Linux), these operations are common to a new installation, but generally not for day-to-day operation of this platform.

Using Commands to Work with Your Managed Instance

Jive includes several command-line tools you can use to perform maintenance tasks with your managed instance. With these tools, you can start and stop the application, upgrade the application, collect information needed by Jive support, and more.

You'll find these documented in the Application Management Command Reference.

Enabling SSL Encryption

The Jive platform is capable of encrypting HTTP requests via SSL or TLS. Enabling encryption of HTTP traffic requires several steps on a platform-managed host. For more about this, see Enabling SSL Encryption.

Setting Up a Document Conversion Node

If you have purchased the Document Conversion module, see Setting Up a Document Conversion Node Some documents -- including PDFs and those from Microsoft Office -- are supported in a preview view in Jive. If you want to convert content from its native format into a form that can be previewed without altering the original document, you'll need the Document Conversion module, which you'll need to deploy on a server that is separate from your core Jive production instances.

Configuring the Text Extraction Location

For content search, all binary content uploaded to Jive, such as .doc, .ppt, .pdf, .txt, or .xls, goes through a process where Jive extracts the plain text from the documents so it can be used in the search index. By default, the output for this process is stored on the web app node in /usr/local/jive/applications/<instance-name>/home/search/search-text-extraction (these are encrypted files). However, we strongly recommend you change this to an NFS-mounted directory on a different node. In clustered environments, the NFS directory must be shared by all web app nodes in the cluster.

To specify the text extraction location, you need to set the CUSTOM_OPTS variable in /usr/local/jive/applications/<instance-name>/bin/instance. If you don't already have this variable, add it. For example:
export CUSTOM_OPTS="-Djive.text.extract.dir=/path/to/chosen/directory"

Configuring Services Directory for On-Premise Search

When you install On-Premise search onto a multi-homed machine and you use the default host value of, On-Premise search may not choose the desired network interface. Therefore, if you are running On-Premise search on a multi-homed machine, you need to explicitly configure which network interface you want to bind to by changing the host values in the serviceDirectory.json file. For more on this, see Configuring Services Directory for On-Premise Search.