Skip Headers

Oracle® Communication and Mobility Server Installation Guide 10g Release 3 (10.1.3) Part Number E12657-02 |
Home | Contents | Index | Contact Us

Previous | Next
| View PDF

# 6 Post-Installation

This chapter describes typical installation and configuration problems and their solution. It contains the following sections:

- Perform Post-Installation Administrative Tasks

- Tune Database

## Perform Post-Installation Administrative Tasks

You have installed OCMS and verified the installation by using Oracle Communicator to connect to the OCMS SIP Server Container. The OCMS installation is now complete. However, before applications can be deployed on OCMS, the OCMS administrator can perform the following administrative tasks:

- Configure the SIP Servlet Container and the Application Router. Refer to "Configuring the SIP Servlet Container" in Oracle Communication and Mobility Server Administrator's Guide.

- Perform required configuration for Presence, Proxy-Registrar, Edge Proxy, and Aggregation Proxy if these applications were installed. Refer to "Configuring SIP Applications" in the "Managing SIP Applications" chapter in Oracle Communication and Mobility Server Administrator's Guide.

- Provision OCMS users to the Oracle database using the Sapphire Shell (Sash) command-line utility. Refer to the "Provisioning Users and Applications" chapter in Oracle Communication and Mobility Server Administrator's Guide.

- Configure how authorization and authentication are performed for SIP applications and how security is set for SIP servlets. Refer to the "OCMS Security" chapter in Oracle Communication and Mobility Server Administrator's Guide.

- Configure logging for OCMS. Refer to the "Logging" chapter in Oracle Communication and Mobility Server Administrator's Guide.

- When installing the OCMS in a production environment, consider using at least two network cards so that the SIP load traffic and the synchronization data may be separated and not interfere with one another.

- Please refer to your database documentation for more information on database tuning.

## Tune Database

No special database tuning is required to run Oracle Communication and Mobility Server out-of-the-box. However, before a production deployment of OCMS, Oracle recommends you do the following:

- Increase the number of connections from OCMS to the database. For a typical installation, OCMS creates three schema users: one for subscriberdata services (`<prefix>_oraspdsds`), one for location service (`<prefix>_orasdpls`), and one for XDMS (<prefix>_orasdpxdms). Out-of-the-box, both the minimum and maximum number of database connections are configured to be four to each of these schemas.

- Increase the number of processes on the database server. This is especially important if you increase the number of database connections from OCMS as described above, and when there are other applications connecting to the database as well.

- Increase the SGA and PGA cache sizes. Increasing the PGA and SGA sizes allow for a larger amount of data to be stored in cache.

- Add additional database files to each schema if you run out of table space. Out-of-the-box, there is only one database file created for each schema configured with a maximum size of 250MB.

- Please refer to your database documentation for more information on how to tune your database.