Before installing Rhino, you need to install Java and a Rhino database instance.

Install Java JDK

Warning Check the Rhino Compatibility Guide to ensure you’ve got a supported Java version.

Check the Java version

To check the the version of the Java installed in the system path, run java -version.

Install a Rhino database instance

Warning Check the Rhino Compatibility Guide to ensure you’re using a compatible database version.

The Rhino SLEE requires an RDBMS database for persisting the main working memory to non-volatile memory (the main working memory in Rhino contains the runtime state, deployments, profiles, resource adaptor entity configuration state, and so on). While a successful connection to the database is required in order to start the first node in a cluster, the Rhino SLEE remains available whether or not the database remains available after the first node has successfully completed bootup procedures.

The database does not affect or limit how Rhino SLEE applications are written or operate — it provides a backup of the working memory only, so that the cluster can be restored if it has entirely failed and needs to be restarted.

The database can be installed on any network-reachable host. When using Savanna clustering mode only a single database is required for the entire Rhino SLEE cluster (the Rhino SLEE can replicate the main working memory across multiple servers). When using pool clustering mode, each node will require its own database, further information can be found in the Pool clustering management database section.

Installing Oracle DBMS

Detailed instructions for the installation of Oracle are outside the scope of this documentation. Contact your Oracle database administrator for assistance.

Installing Postgres DBMS


Download and install PostgreSQL

To download and install the PostgreSQL platform:


Create a user for the SLEE

Once you have installed PostgreSQL, the next step is to create or assign a database user for the Rhino SLEE. This user will need permissions to create databases, but does not need permissions to create users.

To create a new user for the database, use the createuser script supplied with PostgreSQL, as follows.

For versions of PostgreSQL prior to 9.2
[rhino]$ su - postgres
[postgres]$ createuser rhino
Shall the new user be allowed to create databases? (y/n) y
Shall the new user be allowed to create more new users? (y/n) n
For PostgreSQL version 9.2 and later
[rhino]$ su - postgres
[postgres]$ createuser -P -E -d -R rhino

Enter the password for the database user as prompted. (If you do not wish to configure a password, omit the -P and -E flags from the createuser command.)


Configure access-control rules

Instructions for configuring access-control rules differ depending on whether Rhino SLEE and PostgreSQL are on the same or separate hosts:

  • Rhino SLEE and PostgreSQL on the same host — The default installation of PostgreSQL trusts connections from the local host. If the Rhino SLEE and PostgreSQL are installed on the same host, the access control for the default configuration is sufficient. A sample access control configuration is shown below, from the file $PGDATA/pg_hba.conf:

    local  all       all                                trust
    host   all       all  trust
  • Rhino SLEE and PostgreSQL on separate hosts — When the Rhino SLEE and PostgreSQL need to be installed on separate hosts (for example, in a multi-host Rhino cluster, or when a stricter security policy is needed), the access control rules in $PGDATA/pg_hba.conf will need to be tailored to allow connections from Rhino to the database manager. For example, to allow connections from a Rhino instance on another host:

    local  all       all                                     trust
    host   all       all  trust
    host   rhino     postgres    password

    You will also need to configure postgresql.conf so that PostgreSQL listens for incoming connections on * (the null address) rather than localhost.


Restart the server

Once these changes have been made, you must completely restart the PostgreSQL server.

Warning Telling the server to reload the configuration file does not cause it to enable TCP/IP networking — TCP/IP is only initialised when the database is started.

To restart PostgreSQL, use one of the following:

  • the command supplied by the package (for example, /etc/init.d/postgresql restart)

  • the pg_ctl restart command provided with PostgreSQL.

Install a Cassandra database instance

An Apache Cassandra database is required if any of the following are true:

  • The Rhino SLEE will be using the pool clustering mode rather than the Savanna clustering mode.

  • A key/value store will be enabled for application state replication.

  • A session ownership store will be enabled to store application session ownership data.

Detailed instructions for the installation and configuration of Cassandra are outside the scope of this documentation. Contact your database administrator for assistance.

Previous page Next page