| Installing Jive | |
This section is intended to provide sample configurations and script examples common to long-term operation of a Jive installation.
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 encryption of HTTP traffic requires several steps on a platform-managed host: you'll need to enable this for your required load balancer. For more information, see Configuring SSL on a Load Balancer.
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.
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/sbs/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 new text extraction location, you need to set the webapp.custom_jvm_args by typing the following as root. Use jive list set webapp.custom_jvm_args to see if you have set this value. If you have you can add to the existing value.
jive set webapp.custom_jvm_args " -Djive.text.extract.dir=/path/to/new/location"
When you install On-Premise search onto a multi-homed machine and you use the default host value of 0.0.0.0., 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.