Unpack and Gather Information

The Rhino SLEE install requires access to a PostgreSQL database server for storing persistent configuration and deployment information. The database settings you enter here are required for the Rhino SLEE config files. The install script can optionally configure the database for you — you will be prompted for this later in the install process.

Postgres host

Postgres port

Postgres user

Postgres password

Database name

Will be created in your Postgres server and configured with the default tables for Rhino SLEE support.

The Rhino SLEE can be configured in one of two different clustering modes: SAVANNA or POOL.

The Savanna clustering mode is the traditional mode that has existed in Rhino since its inception. In the Savanna clustering mode, nodes communicate with each other over a multicast or scattercast protocol to provide cluster membership and single-image management and replication.

In the pool clustering mode, nodes do not routinely communicate with each other directly (except for a small number of application-level facilities that use the interconnect subsystem). Instead, an external Cassandra database is used to store metadata and application state to be shared with other cluster nodes for discovery and replication. There is no single-image management when using this mode, however it is expected that each node in the cluster will be configured in exactly the same way. When using the pool clustering mode, an Administrator must manually create the Cassandra keyspaces and tables that the Rhino SLEE requires. See Initialise the Cassandra Database for instructions on how to do this.

Clustering mode

This will configure the clustering mode to be either SAVANNA or POOL.

The pool maintenance subsystem is only present when POOL has been selected for the clustering mode.

Database keyspace name for the node pool maintenance subsystem

The name of the database keyspace that will be used for pool maintenance subsystem tables.

The Rhino SLEE provides an optional session ownership facility backed by a Cassandra database cluster. See Replication Support Services for more information.

Enable Session Ownership Facility?

This will enable (True) or disable (False) this facility for the default namespace.

The additional session ownership configuration options below are only relevant if this facility is enabled.

Database keyspace name prefix for the session ownership store

SAVANNA clustering mode:

POOL clustering mode:

This is the prefix that will be used by the Session Ownership Facility when generating database keyspace names to store session ownership data. The variable %{cluster_id} will be replaced by the Savanna cluster ID at runtime, and is only applicable when SAVANNA has been selected for the clustering mode.

Allow automatic data definition updates for the session ownership store?

This option is only available if SAVANNA is selected for the clustering mode. If True is selected here, then the Session Ownership Facility will automatically create and remove keyspaces and tables in the Cassandra database as needed. When set to False, or when using the POOL clustering mode, an Administrator must manually create the necessary keyspaces and tables in the database instead. See Initialise the Cassandra Database for instructions on how to do this.

The Rhino SLEE can optionally use an external key/value store backed by a Cassandra database cluster for its replicated storage. See Replication Support Services for more information.

Replicated storage resource

This will configure the default namespace to use either the DomainedMemoryDatabase or the Cassandra-backed KeyValueDatabase.

The additional key/value store configuration options below are only relevant if KeyValueDatabase is selected here for the replicated storage resource.

Database keyspace name prefix for the key/value store

SAVANNA clustering mode:

POOL clustering mode:

This is the prefix that will be used by the key/value store when generating database keyspace names to store application state. The variable %{cluster_id} will be replaced by the Savanna cluster ID at runtime, and is only applicable when SAVANNA has been selected for the clustering mode.

Allow automatic data definition updates for the key/value store?

This option is only available if SAVANNA is selected for the clustering mode. If True is selected here, then the key/value store will automatically create and remove keyspaces and tables in the Cassandra database as needed. When set to False, or when using the POOL clustering mode, an Administrator must manually create the necessary keyspaces and tables in the database instead. See Initialise the Cassandra Database for instructions on how to do this.

These questions will only be asked if the POOL clustering mode has been selected, the session ownership facility has been enabled, or KeyValueDatabase has been selected as the replicated storage resource.

Cassandra contact points

Comma-separated list of contact points (as host:port pairs) for your Cassandra database cluster.

Cassandra local datacentre name

The name of the local datacentre present at the specified contact points.

The Rhino interconnect is used for internode communication for some functions in both SAVANNA and POOL clustering modes.

Rhino interconnect listen address

Interface to bind the interconnect server to. This may be either a single address or a range in CIDR notation, such as 192.168.0.0/24. If specified as a range, only one network interface on the host must match.

Rhino interconnect listen port range start

The interconnect server will bind to an available port in the range specified here.

Rhino interconnect listen port range end

Directory to install Rhino SLEE

Where to install Rhino (~ = the user’s home directory on Linux/Unix).

Location of license

The Rhino SLEE requires a license file. Please enter the full path to your license file. You may skip this step by entering '-', but you will need to manually copy the license file to the Rhino SLEE installation directory.

Java installation directory

Value of the JAVA_HOME environment variable (if it is set)

Location of your Java J2SE/JDK installation. (see Install Required Software).

Java heap size

An argument passed to the JVM to specify the amount of main memory (in megabytes) which should be allocated for running Rhino. To prevent extensive disk swapping, this should be set to less than the total physical memory installed in the machine.

Rhino is managed using a collection of JMX Management MBeans, exposed to external management clients using Java RMI connections.

Management interface listen addresses

Network interfaces that the management server will listen on. To bind to all local network interfaces, use an asterisk: *. Alternatively, a comma-separated list of local interface hostnames, IP addresses, and/or network prefixes with netmask mask length in CIDR notation can be specified. If a network prefix is used, the management interface will bind to any local IP address falling within the given network address range.

Management interface remote method invocation (RMI) registry port

Used for accessing the Management MBeans from a Java RMI client, such as the Rhino command-line utilities.

Management interface JMX remote service port

Used for accessing the JMX remote server. REM uses this for remote management.

Management interface JMX remote service port (for SSL)

Used for accessing the JMX remote server via SSL. REM uses this for remote management.

Management client IP addresses

Defaults to the IP addresses available on the host where the installer is run.

A comma-separated list of IP addresses that are permitted to connect to the management ports.

Rhino typically provides a profile snapshot server, used by the profile snapshot utility rhino-snapshot as well as rhino-export in snapshot mode. Profile snapshots allow profile table content to be extracted by clients in a more efficient manner than a normal JMX export.

Support for snapshot connections is enabled by default but can be disabled if desired. These questions will only be asked if support is enabled.

Profile snapshot listen addresses

Interface to bind the profile snapshot server to. This may be either a single address or a range in CIDR notation, such as 192.168.0.0/24. If specified as a range, only one network interface on the host must match.

Profile snapshot server port range start

The profile snapshot server will bind to an available port in the range specified here.

Profile snapshot server port range end

Rhino clients can obtain Rhino statistics using either the JMX protocol or by a direct connection utilising a proprietary TCP protocol. Refer to Running rhino-stats for more information about this option.

Support for direct connections is enabled by default but can be disabled if desired. These questions will only be asked if support is enabled.

Direct stats connections listen address

Interface to bind the direct stats connection server to. This may be either a single address or a range in CIDR notation, such as 192.168.0.0/24. If specified as a range, only one network interface on the host must match.

Direct stats connections port range start

The profile snapshot server will bind to an available port in the range specified here.

Direct stats connections port range end

These questions will only be asked if SAVANNA has been selected for the clustering mode.

Cluster communication mode

Networking implementation to send clustering traffic over. One of MULTICAST or SCATTERCAST.

Cluster ID

An integer ID that uniquely identifies this cluster.

These questions will only be asked if MULTICAST has been selected for the Savanna cluster communication mode.

Address Pool Start

A pool of multicast addresses that will be used for group communication by Rhino services.

Address Pool End

These questions will only be asked if SCATTERCAST has been selected for the Savanna cluster communication mode.

Scattercast Base Port

Base port used for automatic endpoint port assignment in scattercast mode

Scattercast Port Offset

Offset used for automatic endpoint port assignment in scattercast mode

Scattercast Initial Endpoints

The scattercast initial endpoints, specified in the format: <node,ip-address[,port]>* As an example: 101,192.168.1.1 102,192.168.1.2 103,192.168.1.3,12500 In this example node 101 will use the defined Base Port and offset for the port (e.g. 12000 - offset + nodeID = 12000) and node 102 is doing the same (e.g. 12000 - offset + nodeID = 12001). Node 103 has explicitly set the port to 12500.