3 Pre-Installation Tasks

This chapter describes the system configuration tasks you must complete prior to installing Oracle Communications Converged Application Server.

Database Planning for Converged Application Server

Converged Application Server requires the use of a database to store data for Registrar bindings, and to perform authentication for the User Service and Security Service. Prior to installing and configuring the Converged Application Server software, you must install and configure either an Oracle or MySQL database for use as a JDBC data source. When you configure the Converged Application Server software, the Configuration Wizard lets you create JDBC connections for use with Converged Application Server, and populate the data sources with the necessary database tables and indexes.

The administrator of the database you will use must create a database schema (Oracle) or database user (MySQL) for use with Converged Application Server. Oracle recommends that you create two schemas or database users:

Create a schema or database user for the Converged Application Server Location Service data source.
Create a schema or database user for the User Service and Security Service data sources.

Note:

Oracle recommends that you create two schemas or database users, however, you can choose to create a single schema or database user for all of the Converged Application Server data sources, or you can create three schemas or database users, one for each data source. The choice you make depends on your database management preferences.

Database Information to Record

When you install and configure a database, you define system configuration values that you need to enter when you install and configure the Converged Application Server software. When you create the following values, write them down so you can use them during the installation process:

Vendor: The database vendor's name. For Converged Application Server this is either Oracle or MySQL.
JDBC driver: The JDBC driver to use to connect to the database.
Database username: The username to use when connecting to the database.
Database user password: The password for the specified username.
Database SID or database name: If you are using an Oracle database, this is the Database System Identifier. If you are using a MySQL database, this is the name of the database.
Host name: The name or IP address assigned to the server hosting the database.
Port: The port number to use to connect to the database. The default port numbers are port 1521 for the Oracle database, and port 3306 for the MySQL database.

Creating an Oracle Database

Create two Oracle schemas, one for the Registrar bindings, and another for the User Service and Security Service. For instructions on installing the Oracle database software, creating a schema, and granting user privileges, refer to the Oracle database documentation.

Note:

The following, abbreviated instructions are intended to provide an overview of the procedures to create a database for use with Converged Application Server. Refer to the documentation for your Oracle database deployment for information on creating a schema and granting privileges.

To create an Oracle database user:

Start SQL*Plus (the Oracle SQL command line tool).
Log in to the Oracle database as an administrative user with sufficient privileges to create new, database users.
Create the users that you need in the database by entering the following command in SQL*Plus:
```
SQL> CREATE USER username IDENTIFIED BY password DEFAULT TABLESPACE user_tablespace TEMPORARY TABLESPACE temp_tablespace;
```
Where username is the name identifying the database account to use when connecting to the database, password is the password associated with the username, and temp_tablespace is the temporary tablespace to use when storing temporary tables.

Grant the following privileges to the users you create for use with Converged Application Server:

SQL> GRANT CREATE SESSION, CREATE TABLE, CREATE SEQUENCE TO username;
SQL> ALTER USER username QUOTA UNLIMITED ON user_tablespace;

Exit SQL*Plus.

Creating a MySQL Database

Create two MySQL databases, one for the Registrar bindings, and another for the User Service and Security Service. For instructions on installing the MySQL database software, creating a database, and granting user privileges, refer to the MySQL database documentation.

Note:

The following, abbreviated instructions are intended to provide an overview of the procedures to create a database for use with Converged Application Server. Refer to the documentation for your MySQL database deployment for information on creating databases and granting privileges.

Note:

If the MySQL database is installed on a case sensitive operating system such as Linux or Solaris, you must set the MySQL variable lower_case_table_names to 1 to ensure that MySQL is case insensitive. For example:

set-variable=lower_case_table_names=1

For more information refer to the documentation for your MySQL database deployment.

To create a MySQL database:

Log into the MySQL database as an administrative user.
Create a MySQL database:
```
mysql> CREATE DATABASE database_name;
```
Where database_name is a label (or name) that you specify identifying the database.
Verify that the database was created.
```
mysql> SHOW DATABASES;
```
Grant the following connect and resource privileges to the databases you create:
```
mysql> GRANT ALTER, CREATE, DELETE, INDEX, INSERT, LOCK TABLES, SELECT, UPDATE ON database_name.* TO 'username'@'hostname' IDENTIFIED BY 'password' WITH GRANT OPTION;
```
Where username is the name identifying the database account to use when connecting to the database, password is the password associated with the username, and hostname identifies the network address of the host computer running that database.
Exit MySQL.
```
mysql> EXIT;
```

Choosing an Installation Directory

When you install Converged Application Server, you are prompted to specify a Middleware home directory. This directory serves as a repository for common files that are used by multiple Fusion Middleware products installed on the same machine. For this reason, the Middleware home directory can be considered a central support directory for all the Fusion Middleware products installed on your system.

The files in the Middleware home directory are essential to ensuring that Converged Application Server and WebLogic Server operate correctly on your system. They facilitate checking of cross-product dependencies during installation.

For more information on choosing an installation directory, refer to the Oracle WebLogic Server 11g Release 1 (10.3.3) Installation Guide in the Oracle WebLogic Server documentation.

Obtaining the Converged Application Server Software

Oracle makes the Converged Application Server software available through Web distribution as well as DVD, which is available when you obtain the physical product media. Use the following link to obtain the installation program from the Web:

http://edelivery.oracle.com

Four installers are available on Oracle E-Delivery:

Generic JAR file: Use the generic JAR file installer to install the Converged Application Server software on supported Linux and Solaris 64-bit platforms. The generic installer does not include a Java Runtime Environment. See Starting JAR File Installation Programs for UNIX and Windows in Chapter 4, "Installing the Software" for more information.
Linux 32-bit: Use the Linux installer to install the Converged Application Server software on 32-bit Linux operating systems. This installer includes a Java Runtime Environment for Linux, and well as the Oracle Hotspot and Oracle JRockit JDKs.
Solaris 32-bit: Use the Solaris installer to install the Converged Application Server software on 32-bit Solaris operating systems. This installer includes a Java Runtime Environment for Solaris, and the Oracle Hotspot JDK.
Windows 32-bit: Use the Windows installer to install the Converged Application Server software on 32-bit Windows operating systems. This installer includes a Java Runtime Environment for windows, and well as the Oracle Hotspot and Oracle JRockit JDKs.

See "Running the Installation Program" in Chapter 4, "Installing the Software" for more information.