
Figure 21.1: Cluster with mulitple database servers
The main working memory consists of several memory databases on each node.
• The
ManagementDatabase
which holds the working configuration and run-time state of the logging system, services,
resource adaptor entities.
• The
ProfileDatabase
which holds the profile tables, profiles and profile indexes.
Generally both of these memory databases must be configured for fail-over using multiple PostgreSQL database servers.
Before connecting Rhino SLEE to the remote database server, the database must be prepared by executing
$RHINO_NODE_HOME/init-management-db.sh
on that database server:
init-management-db.sh --help
Initialise the Rhino SLEE main working memory database schema.
-h hostname : The host running postgres.
Default is MANAGEMENT_DATABASE_HOST
-p port : The port running postgres.
Default is MANAGEMENT_DATABASE_PORT
-u username : The user to connect to template1.
Default is MANAGEMENT_DATABASE_USER
-d database : The name of the database to create.
Default is MANAGEMENT_DATABASE_NAME
Optional switches override local configuration options
found in $RHINO_NODE_HOME/config/config_variables
You will be prompted for a password on the command line
Once the databases are initialized on each database server, configure rhino for use with multiple PostgreSQL servers by editing
the configuration file
$RHINO_NODE_HOME/config/rhino-config.xml
. This configuration must be applied to each node in the cluster.
Multiple
<persistence-instance>
elements will need to be added to the
<persistence>
element for the
memdb
element
with the
jndi-name
of
ManagementDatabase
and
ProfileDatabase
as shown below.
Each <persistence-instance> element needs to be completed with the attributes of the PostgreSQL server (hostname, database
Open Cloud Rhino 1.4.3 Administration Manual v1.1 124
Comentarios a estos manuales