Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Unified MeetingPlace

MeetingPlace Web MPWEB Database Configuration with a Remote SQL Server

Downloads

Document ID: 50990


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      For Cisco MeetingPlace Server, All Versions
      Additional Steps for Cisco MeetingPlace Server 4.3.0.63 and 4.3.0.100
      Modify Registry Information for Cisco MeetingPlace Server 4.3.0.63 and 4.3.0.100
Related Information

Introduction

This document provides steps to configure the Cisco MeetingPlace Web MPWEB database to use a remote SQL Server.

In this document, "SQL Server" refers to any version of Microsoft SQL Server or Microsoft Desktop Engine (MSDE) mentioned in the Components Used section below.

This document is applicable only when you want to reconfigure your existing MPWeb to use a remote SQL (or different SQL server than one that is currently in use). In this case, you will allow MPWeb to create a new database on the remote SQL server. If you want to migrate the SQL database that your MPWeb currently uses to the remote SQL server, you will need to backup your current MPWEB database, and restore it onto the remote SQL server. For more information on how to back up, see MeetingPlace Web MPWEB SQL Database Backup.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco MeetingPlace Web 4.2.7, 4.3.0.63, 4.3.0.100, 4.3.0.246, and later.

  • Microsoft SQL Server 7.0 and 2000.

  • MSDE 1.0 and 2000.

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.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Configure

At this point, it is assumed that the Cisco MeetingPlace Web server is not in operation. For Cisco MeetingPlace Web versions 4.2.5 and 4.2.7, this means that all MeetingPlace Web services and the World Wide Web Publishing service have been stopped.

For Cisco MeetingPlace Web 4.3.0.x, this means that the MeetingPlace Web Conferencing service has been stopped (and as a consequence, all the MeetingPlace Web services and World Wide Web Publishing service have also stopped).

For Cisco MeetingPlace Server, All Versions

Complete these steps:

  1. On the Cisco MeetingPlace Web server, configure the ODBC settings. To do so:

    1. Select Start > Programs > Administrative Tools > Data Sources (ODBC).

    2. Click on the System DSN tab.

    3. Highlight MPWEB, and click Configure.

      config-mpweb-rem-sqlsvr-1.gif

    4. Change the server to the remote SQL Server hostname.

    5. Click Next.

    6. Select With SQL Server authentication using a login ID and password entered by the user, and enter the SQL Login ID and Password.

      config-mpweb-rem-sqlsvr-2.gif

    7. Verify whether the correct database is selected.

      config-mpweb-rem-sqlsvr-3.gif

    8. Click Next to accept the default selections.

    9. In the next dialog box, click Finish.

    10. Click Test Data Source. A "Tests completed successfully" message is displayed.

    11. Click OK to close the SQL Server ODBC Data Source Test box.

    12. Click OK to close the ODBC Microsoft SQL Server Setup box.

  2. Verify whether the registry has the correct values:

    • DataSource

    • DBPassword

    • DBUserID

    1. Select Start > Run, and type regedit.

    2. Browse to HKLM\Software\Latitude\MeetingPlace Webpublisher\ODBC.

      config-mpweb-rem-sqlsvr-4.gif

    3. Double-click on DatabaseServerName, and enter the name of your remote SQL Server.

    4. Ensure that DataSource contains the correct SQL userid and password values.

    5. If DBName, DBPassword, and DBUserID exist, make sure they have the correct values.

    6. If DBPassword, and DBUserID exist, ensure that they also have the correct values.

  3. Restart the Cisco MeetingPlace Web server. After the restart, perform full functionality testing. If you are working with 4.3.0.x version, do not restart at this stage, because you need to perform additional steps. For the additional steps, see Additional Steps for Cisco MeetingPlace Server 4.3.0.63 and 4.3.0.100.

Additional Steps for Cisco MeetingPlace Server 4.3.0.63 and 4.3.0.100

For Cisco MeetingPlace Web server 4.3.0.63 or 4.3.0.100, in addition to the MPWEB database, there is an additional slave database named MPWEB-Slave-######## (######## is a series of digits that varies from one installation to another). You need to perform the same procedure as in the For Cisco MeetingPlace Server, All Versions section, but apply the procedure to both the MPWEB database and the slave database.

  1. To configure ODBC for the slave database, select Start > Program Files > Administrative Tools > ODBC > System DSN > DCMS, and click configure.

  2. Enter the new SQL server name in the first configuration window, and enter the appropriate information though the rest of the screens.

  3. To modify the registry of the slave database, enter regedit, and navigate to \Data Connection\DCMS\admin\.

  4. Double-click on the key DBServerLocation, and enter the hostname of your remote SQL server.

  5. Double-click on these keys, and enter the appropriate values:

    • DBPASSWORD

    • DBUSERID

  6. Restart the Cisco MeetingPlace Web server. After the restart, perform full functionality testing.

Modify Registry Information for Cisco MeetingPlace Server 4.3.0.63 and 4.3.0.100

For Cisco MeetingPlace Web server 4.3.0.246, the SQL server login information in the registry for the slave database has been encrypted. To change the registry information, complete these steps:

  1. To modify the registry of the slave database, enter regedit, and navigate to \Data Connection\DCMS\admin\.

    DCMS-reg.gif

  2. In the right pane, select the key DBReset, and delete it. Select and delete the MasterDBReset key also.

  3. Double-click on the key DBServerLocation, and enter the hostname of your remote SQL server.

  4. Enter the correct SQL user login ID for these two keys (both must be set to the same user ID):

    • DBUserID

    • MasterDBUserID

  5. Enter the correct SQL user login password for these two keys (both must be set to the same password):

    • DBPassword

    • MasterDBPassword

  6. Restart the Cisco MeetingPlace Web server. After the restart, perform full functionality testing.

Related Information

Updated: Jan 31, 2006 Document ID: 50990