Database Setup for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
External Database Installation and Setup
Downloads: This chapterpdf (PDF - 1.26 MB) The complete bookPDF (PDF - 2.17 MB) | Feedback

External Database Installation and Setup

External Database Installation and Setup

This chapter provides information about how to configure an external database to store information from Cisco Unified Communications Manager IM and Presence Service features. The following IM and Presence Service features require an external database:

  • Persistent Group Chat

  • Message Archiver (IM Compliance)

External Database Setup Requirements

Hardware Requirements

  • A remote server on which you install the PostgreSQL or Oracle database.

Software Requirements

  • IM and Presence Service, current release

  • External database:

    • PostgreSQL database, versions 8.3.x through 9.4.x are supported, and in IM and Presence Service Release, 11.0(1) versions: 9.1.9, 9.2.6, 9.3.6, 9.4.1 have been tested.


      Note


      You can also use Version 8.1.x of the PostgreSQL database, but the configuration of these versions may be different to the PostgreSQL database configuration described in this section. See the PostgreSQL documentation for details on how to configure these PostgreSQL database versions. If you use Version 8.1.x of the PostgreSQL database, the database configuration on IM and Presence Service is the same as described in this section.


    • Oracle database, versions 9g, 10g, 11g, and 12c are supported, and in IM and Presence Service Release, 11.0(1) versions: 11.2.0.1.0 and 12.1.0.1.0 have been tested.

  • You can install the database on either a Linux or a Windows operating system. See the relevant database documentation for details on the supported operating systems and platform requirements.

  • IPv4 and IPv6 are supported.

External Database Requirements for IM and Presence Service Features

  • The external database requirements differ depending on the features you want to deploy on IM and Presence Service.

    • Persistent Group Chat feature — You require one unique external database for each IM and Presence Service node in an IM and Presence Service cluster. Each node requires its own logical database, but nodes can share the same physical database installation.

    • Message Archiver (compliance) feature — We highly recommend that you configure at least one external database for each IM and Presence Service cluster; however you may require more than one external database for a cluster depending on your server capacity.


Note


If you deploy both the persistent group chat and message archiver (compliance) features on an IM and Presence Service node, you can assign the same external database to both features.


Additional Documentation

This procedure only describes how to configure the external database on the IM and Presence Service. It does not describe how to fully configure the features that require an external database. See the documentation specific to the feature you are deploying for the complete configuration:

  • For information on configuring the message archiver (compliance) feature on the IM and Presence Service, see Instant Messaging Compliance for IM and Presence Service on Cisco Unified Communications Manager.

  • For information on configuring the persistent group chat feature on the IM and Presence Service, see Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager.

External Database Setup Prerequisites

Before you install and configure the external database on the IM and Presence Service, perform the following tasks:

  • Install the IM and Presence Service nodes as described in Installing Cisco Unified Communications Manager.

  • Configure the IM and Presence Service nodes as described in Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager.

Hardware and Performance Recommendations

When you configure an external database with the IM and Presence Service, you need to consider the following recommendations:

  • We recommend that you use similar hardware for both the external database and the IM and Presence Service nodes.

  • We recommend that you maintain the external database according to the best practice guidelines described in the product documentation. If you do not properly maintain the external database, and you allow the external database to fill up, this causes performance problems in the IM and Presence Service cluster.

Related Information

About Security Recommendations

External Database Connection Security

The IM and Presence Service does not provide a secure TLS/SSL connection to the external database. We recommend that you consider this security limitation when you plan your IM and Presence Service deployment, and consider the security recommendations we provide in this topic.

Maximum Connection Limit Setup


Note


Use this section as a guideline if you wish to limit the number of connections to the database. This section is optional configuration.


For additional security, you can limit the maximum number of permitted connections to the external database. Use the guideline we provide here to calculate the number of database connections that are appropriate for your deployment.

You must modify this guideline to suit your IM and Presence Service deployment and configuration. The guideline we provide here assumes that:

  • You are running both the message archiver (compliance) and persistent group chat features on the IM and Presence Service.

    and

  • You configure the default number of connections to the database for the persistent group chat feature on the IM and Presence Service administration interface.

To limit the number of database connections, configure the max_connections value in the postgresql.conf file located in the install_dir/data directory. We recommend that you set the value of the max_connections parameter equal to this guideline:

max_connections = (N ×10) + Additional Connections

  • N is the number of nodes in your IM and Presence Service cluster.

  • 10 is the default number of connections to the database on the IM and Presence Service, that is, five connections for the message archiver feature and five connections for the persistent group chat feature. You can configure the number of database connections for the persistent group chat feature on the Cisco Unified CM IM and Presence Administration interface.

  • Additional Connections represents any independent administration or database administrator (DBA) connections to the database server.

    For example, if you have an IM and Presence Service cluster containing six nodes, and you require an additional three DBA connections, using the guideline above, you set the max_connections value to 63.

Related Information

Default Listener Port Setup


Note


This section is an optional configuration.


For additional security, you may choose to change the default listening port on the PostgreSQL server. You can configure the default listening port in the postgresql.conf file located in the <install_dir>/data directory.