Changing the Root Context (optional)

By default, Jive installs and configures using the root context, for example This is the recommended configuration and default installation behavior, but non-root contexts such as are also supported. To use a non-root context, you need to set an environmental variable that changes default installation behavior.

Important: Never use "community" as your non-root context because the application already uses this string.
The RPM has several flags you can set before installation to dictate default behavior. By default, on fresh installs the RPM runs:
appadd --verbose sbs
This command gives you the basic application setup with Apache files responding on port 80 of the root context and pointing to your Tomcat installation on the default ports. It also copies /usr/local/jive/application/template to /usr/local/jive/application/sbs. However, you can set the following environmental variable to change this behavior before installing:
Or, if you forgot to set the environmental variable and want to change the default settings you can issue:
apprm sbs
appadd --context-path=engage engage

apprm removes the existing installation of Jive while retaining the database. appadd creates the new application instance. In this case, the context path would be the text to appear after the root URL ( and the argument engage would be the name of the directory created in /usr/local/jive/applications/.

Note that appadd has several flags that control the configuration files. For example:
appadd --auto-port --context-path=sbs1 sbs1
appadd --auto-port --context-path=sbs2 sbs2

auto-port is aware of existing installations and will stagger the ports to allow multiple instances on a single server. This is useful for testing Jive, but note that single-server deployments are not recommended or supported for production.

For more about appadd see the appadd command reference.