Post-Installation Tasks

This section is intended to provide sample configurations and script examples common to long-term operation of a Jive SBS 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 SBS 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, upgrae 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 SBS Platform is capable of encrypting HTTP requests via SSL or TLS. Enabling encryption of HTTP traffic requires the following steps on a platform-managed host:

Copy cryptographic materials to the host. By default, the Jive HTTPD server attempts to load an X.509 certificate file from the path “/etc/jive/httpd/ssl/jive.crt” and the corresponding key from “/etc/jive/httpd/ssl/jive.key”. The paths to these files are configured in the default Apache HTTPD virtual host file located at “/etc/jive/httpd/sites/default.conf” and can be changed to any path desired.
Enable SSL in the HTTPD server by specifying the “-D SSL” option in the Apache HTTPD configuration extension file located at “/etc/jive/conf/jive-httpd”. To enable SSL, open (or create) this file and add ‘OPTIONS=”-D”’ to the file.
After making the above changes, restart the Jive HTTPD server using the command “/etc/init.d/jive-httpd restart”.

Note that if a third-party load balancer or external HTTP proxy is performing SSL termination upstream of the Jive HTTPD server, it is not necessary to configure the Jive HTTPD server for HTTP encryption in addition to the load balancer.

Note that if the private key file installed to the server is encrypted, the HTTPD server will interactively prompt the user for the password to decrypt the key.

Disabling the Local Jive System Database

Many deployments will not wish to use the locally managed SBS platform database instead, choosing to use an RDBMS that is controlled by an internal corporate IT group. In this case, the local database should be disabled. For information on disabling the application database, see the Operations Cookbook

Note that disabling the database does not stop the service if it is running. Likewise, re-enabling the database does not start the database service.