Changing the Configuration of an Existing Instance

Update environment variables in your /usr/local/jive/applications/app_name/bin/instance file to reflect new configuration settings.

In some circumstances, it may be desirable to change the default configuration of platform-managed application server instances. For example, on a larger server-class machine, an application instance will benefit from allocation of more RAM for the JVM heap.

To change this or other settings, edit the instance file for the desired application (sbs by default) located at /usr/local/jive/applications/app_name/bin/instance.

The contents of this file will vary from release to release. Generally, the entries in this file correspond to either:

Environment variable values in the setenv script located in the same directory
Tokenized configuration attributes for the conf/server.xml file in the application directory

For any managed application, all files except the binaries for the web application (by default, each application is linked to these binaries located at /usr/local/jive/applications/template/application) are not managed by the application platform. As a result, any changes to files such as instance will be durable across application upgrades.

Changing the Port

As an example, to change the port that the managed application listens for AJP connections, edit the instance file to alter the port for AJP_PORT.

Prior to edit, the instance file will look similar to the following.

[0806][jive@melina:~/applications/sbs/bin]$ cat instance 
export JIVE_HOME="/usr/local/jive"
export AJP_PORT="9002"
export APP_CLUSTER_ADDR="224.224.224.224"
export JIVE_APP_CACHE_TTL="10000"
export APP_CLUSTER_PORT="9003"
export HTTPD_ADDR="0.0.0.0"
export AJP_BUFFER_SIZE="4096"
export HTTP_ADDR="127.0.0.1"
export JIVE_APP_CACHE_SIZE="10240"
export SERVER_PORT="9000"
export JIVE_NAME="sbs"
export HTTP_PORT="9001"
export AJP_ADDR="127.0.0.1"
export JIVE_CONTEXT=""
export AJP_THREADS_MAX="50"

To alter the AJP_PORT to listen on port 11000, edit the instance file to appear similar to the following:

[0806][jive@melina:~/applications/sbs/bin]$ cat instance 
export JIVE_HOME="/usr/local/jive"
export AJP_PORT="11000"
export APP_CLUSTER_ADDR="224.224.224.224"
export JIVE_APP_CACHE_TTL="10000"
export APP_CLUSTER_PORT="9003"
export HTTPD_ADDR="0.0.0.0"
export AJP_BUFFER_SIZE="4096"
export HTTP_ADDR="127.0.0.1"
export JIVE_APP_CACHE_SIZE="10240"
export SERVER_PORT="9000"
export JIVE_NAME="sbs"
export HTTP_PORT="9001"
export AJP_ADDR="127.0.0.1"
export JIVE_CONTEXT=""
export AJP_THREADS_MAX="50"

Changing the Heap Min/Max Values

To change the JVM min/max values, see Adjusting Java Virtual Machine (JVM) Settings.

Configuring the JVM Route Name of a Node(s)

To configure the route name of your web application node(s), add a line(s) to the instance file in /usr/local/jive/applications/<app_name>/bin as follows, where "node01" is your desired route name:

export APP_CLUSTER_JVMROUTE="node01"

When configuring multiple nodes with jvmRoute attributes, each node should have a different value.