This chapter provides an overview of the process of installing the database for use with Oracle Communications Services Gatekeeper.
Note: | Individual files names are given in the form: filename<version>.type. As an example, the file referred to as jrockit-j2sdk<version>.bin.gz could have the full name jrockit-j2sdk1.4.2_05-linux-ia32.bin.gz |
Although there are substantial differences among the installation procedures for each type of database, all installation types include the following basic steps:
Use these instructions if you are using Oracle 10g with RAC as your database. For more information on using OWLS RAC with multidatasource configuration, see Oracle WebLogic Server Configuring and Managing WebLogic JDBC at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jdbc_admin/.
Note: | This is the only database configuration supported for production environments that require High Availability. |
Oracle 10g RAC must be installed on dedicated servers not running in the cluster building up the Oracle Communications Services Gatekeeper.
Define the number or of processes to be equal to (wlng.datasource MaximumCapacity + wlng.localTX.datasource MaximumCapacity
) times the number of Oracle Communications Services Gatekeeper servers in the cluster. MaximumCapacity is defined as a parameter in the connection pool settings for the JDBC datasources. Normally this value is 150 for both datasources.
Oracle Communications Services Gatekeeper must be configured with an additional set of parameters to make it work correctly with the database. This action is performed during the domain configuration phase. See Configuring the Domain for Oracle Communications Services Gatekeeper for more information.
Follow the instructions in this section if you are using an Oracle 10g single instance as your database.
The Oracle 10g instance must be installed on a dedicated server not running in the cluster building up the Oracle Communications Services Gatekeeper.
Define the number or of processes to be equal to (wlng.datasource MaximumCapacity + wlng.localTX.datasource MaximumCapacity
) times the number of Oracle Communications Services Gatekeeper servers in the cluster. MaximumCapacity is defined as a parameter in the connection pool settings for the JDBC datasources. Normally this value is 150 for both datasources.
Oracle Communications Services Gatekeeper must be configured with an additional set of parameters to make it work correctly with the database. This action is performed during the domain configuration phase. See Configuring the Domain for Oracle Communications Services Gatekeeper for more information.
Follow the instructions in this section if you are using MySQL as your database.
Note: | MySQL is not supported in environments that require High Availability. |
MySQL can be installed either on a server in the cluster building up the Oracle Communications Services Gatekeeper or on a separate server. If it is installed in the cluster, it should be in the same server as the Network Tier.
Before you start, make sure you have the appropriate installation binaries (5.0 or 5.1) for your platform. The binaries can be downloaded from
http://www.mysql.com
.
The following is a summary of the commands needed to install MySQL on some versions of Linux. You should check the specific instructions for your version. It assumes an installation directory of /usr/local:
groupadd mysql
useradd -g mysql mysql
cd /usr/local
ln -s /usr/local/mysql-standard-<version> mysql
cd mysql
scripts/mysql_install_db --user=mysql
chown -R root .
chown -R mysql data
chgrp -R mysql .
bin/mysqld_safe --user=mysql &
max_connections
is equal to (wlng.datasource MaximumCapacity + wlng.localTX.datasource MaximumCapacity
) times the number of Oracle Communications Services Gatekeeper servers in the cluster. MaximumCapacity is defined as a parameter in the connection pool settings for the JDBC datasources. Normally this value is 150 for both datasources. For example:[mysqld]
set-variable=max_connections=400
You should also add settings for default character set and storage engine:
set-variable=default-character-set=<desired character set>
Note: | The recommended character set is latin1. |
set-variable=default-storage-engine=<desired default storage engine>
The Windows version is available with a GUI installer. Detailed instructions on using the installer are available at the MySQL web site. Unless you need to install the database in a non-standard location, you can select Typical Install.
You can also use the Instance Configuration Wizard to do configuration basics. (Use the default choice unless specified below):
Note: | The recommended usage type is Non-transactional Database. |
wlng.datasource MaximumCapacity + wlng.localTX.datasource MaximumCapacity
) times the number of Oracle Communications Services Gatekeeper servers in the cluster. MaximumCapacity is defined as a parameter in the connection pool settings for the JDBC datasources. Normally this value is 150 for both datasources. Use the dropdown menu. You can change this value later if necessary.Note: | The recommended character set is Latin1. |
GRANT ALL ON *.* TO <Gatekeeper database user>@'<ip-address>' IDENTIFIED BY '<password>'
You must do this for every IP address in the cluster.
CREATE DATABASE <database name>
If you choose to use MySQL 5.1, you must replace the existing MySQL 5.0 connector JAR file with the MySQL 5.1 connector JAR file.