This document describes the procedure to configure compliance in Cisco Unified Presence Server (CUPS) with the use of PostgreSQL for Windows.
Cisco recommends that you have knowledge of these topics:
Windows Server 2008
CUPS Version 8.6.x
PostgreSQL for Windows
The information in this document is based on these software and hardware versions:
Windows 2008 Standard Edition (32-bit)
CUPS Version 188.8.131.5200-2
PostgreSQL for Windows Version 9.1.13
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
This server is part of the workgroup and uses local admin privileges on the Windows server.
Choose the appropriate Installation Directory. Click Next.
Choose the appropriate Data Directory. Click Next.
Enter the password for the default created superuser in the Password and Retype password fields.
Enter the default port number, which is 5432, in the Port field.
From the Locale drop-down list, choose the correct location (in this scenario it is set to English, United States). Click Next.
Click Finish in order to complete the installation.
Note: You do not need to check the Launch Stack Builder at exit? check box.
Log in to the PGadmin interface and enter the password of the PostgreSQL user. Click OK.
Choose Server Groups > Servers > PostgreSQL 9.1 > Login Roles in order to create a new login role. Enter the new Role name in the Role name field.
Click the Definition tab. Enter the password in the Password and Password (again) fields.
Click the Role privileges tab. Choose the privileges as shown in this example. Click OK.
Choose Server Groups > Servers > PostgreSQL 9.1 > Database > New Database in order to create a new database.
Enter tcmadb in the Name field. Enter tcuser in the Owner field.
Click the Definition tab. Ensure that Encoding is UTF8 for this database. Click OK.
Browse to this location (this is dependent upon what you selected as the installation drive).
Edit the postgressql.conf file with these three options:
listen_addresses = '*'
escape_string_warning = off
standard_conforming_strings = off. If you see '#' you will need to remove this for the commands to be active.
Edit the pg_hba.conf file with the this entry. The IP address used here (x.x.x.x) is the IP address of CUPS pub. Also note that subnet mask is important to be formatted in the slash ('/') format else the postgres service will not start.
Restart the postgressql-9.3 service.
Dependent upon the setup and network policy, there might be a need to disable the Windows firewall as well. Otherwise it might block ping reachability from the Cisco Unified Presence node.
Add the external database information to the CUPS Administration page as shown in this example. Replace y.y.y.y with the IP address of the PostgreSQL server.
Once the CUPS external database is created, make sure to associate this node to the compliance node database. Go to the CUPS Administration page and choose Messaging > Compliance.
In Compliance Settings, click the Message Archiver radio button.
For the node hostname, ensure you choose the created External Database in the drop-down list.
If the connectivity is good, the test below is successful.
Restart the Extensible Communications Platform (XCP) router service from the serviceability/network services and attempt to start the message archiver service. The XCP router service will call for a network downtime.
These tables are created in the 'tcmadb' database in PostgreSQL.
All compliance related information will be stored in the 'jm' table.
Use this section to confirm that your configuration works properly.
Try to log in to a Jabber for Windows session and then try to text messages. This leads to a copy of the messages making it to the 'jm' table in PostgreSQL. Here is a sample from the 'jm' table where the messages typed are going to be archived.
This section provides information you can use to troubleshoot your configuration.
These logs are helpful in order to troubleshoot this issue from the CUPS perspective:
XCP Message Archiver
Here is an example of the connectivity test, which can only can be completed from root access.