Configuration and Maintenance Guide for MeetingPlace 7.1
Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server
Downloads: This chapterpdf (PDF - 326.0KB) The complete bookPDF (PDF - 5.46MB) | Feedback

Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server

Table Of Contents

Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server

Accessing Information on the SQL Server Database

How to Create and Use a Least-Privileged SQL Account for Web Conferencing

Creating a Least-Privileged SQL Account for Web Conferencing

Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

How to Change and Apply a New SQL Password to Cisco Unified MeetingPlace Web Conferencing

Changing the SQL Password If You Know the Old Password

Changing the SQL Password if You Do Not Know the Old Password

Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing

How to Manage the SQL Database Size

Modifying the SQL Database Properties to Manage Database Size

Examples: Modifying the SQL Database Properties to Manage Database Size

How to Back Up and Restore MPWEB SQL Database

Creating a Backup File by Exporting the MPWEB Database

Examples: Exporting the MPWEB Database to Create a Backup File

Restoring the Database

Examples: Restoring the Database

Restoring Cisco Unified MeetingPlace Web Conferencing to a Different Server

How to Detach and Attach the MPWEB SQL Database

Detaching the Database

Examples: Detaching the Database

Attaching the Database

Examples: Attaching the Database

Relocating the Database

How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

Preparing the Current Cisco Unified MeetingPlace Web Server

Installing the Replacement Cisco Unified MeetingPlace Web Server

Building the Replacement Cisco Unified MeetingPlace Web Server

Updating the Indices on the SQL Database

How to Use a Custom TCP Port for the SQL Server Connection

Customizing the Port for an SQL Database

Customizing the SQL Port for the "Remote" SQL Database

Switching to the "Remote" SQL Database on the Custom Port


Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server


Release: 7.1
Revised: March 1, 2013 1:25 pm

All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be "remote" in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.


Note The SQL commands and operations described in this section are provided only for your convenience and should not be treated as definitive reference. For additional details about these commands and operations, search the Microsoft Knowledgebase for your version of Microsoft SQL Server.


Accessing Information on the SQL Server Database

How to Create and Use a Least-Privileged SQL Account for Web Conferencing

Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

How to Change and Apply a New SQL Password to Cisco Unified MeetingPlace Web Conferencing

How to Manage the SQL Database Size

How to Back Up and Restore MPWEB SQL Database

Restoring Cisco Unified MeetingPlace Web Conferencing to a Different Server

Relocating the Database

Updating the Indices on the SQL Database

How to Use a Custom TCP Port for the SQL Server Connection

Accessing Information on the SQL Server Database

Use the Database administration page to access information on the SQL Server database.

Restriction

All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be "remote" in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.

Before You Begin

If you have SQL Server installed on a separate machine, make sure that the time on SQL Server is synchronized with the Cisco Unified MeetingPlace Application Server and Web Server.

Procedure


Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Database.

Step 4 Select a database command.

Step 5 Select Submit.


How to Create and Use a Least-Privileged SQL Account for Web Conferencing

By default, the Cisco Unified MeetingPlace Web Conferencing installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, and configure the Web Server to use this account.

Complete the following procedures in the order shown to create and use a least-privileged SQL account:

Creating a Least-Privileged SQL Account for Web Conferencing

Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

Creating a Least-Privileged SQL Account for Web Conferencing


Caution If you choose to create a SQL account that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, ensure that it meets all the specified database role requirements in this procedure. Failure to do so can cause a database connection failure between the web conferencing application and the SQL Server and result in a total outage or broken features.


Note If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.


Procedure


Step 1 Open the SQL Server Enterprise Manager and create a new login:

a. On the Start menu, select Programs > SQL Server 2000 > Enterprise Manager.

b. Select a server group to expand it, then select the name of a server.

c. Select Security > New Login.

The SQL Server Login Properties window displays.

Step 2 Enter a name for the login on the General tab.

Step 3 Select SQL Server Authentication.

Step 4 Enter a password for the account.

Step 5 Select MPWEB from the Database drop-down menu to set the MPWEB database as the default database.

Step 6 Select the Database Access tab.

Step 7 Specify the database roles for the MPWEB database:

a. Check the MPWEB database in the Databases table.

b. Check the boxes for the following roles in the Database Roles table:

db_datareader

db_datawriter

db_ddladmin

db_owner

Step 8 Repeat Step 7 for each additional MPWEB slave database.

The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.

Step 9 Select OK to complete the account configuration.


Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

The MeetingPlace Gateway Configurations utility allows you to update the Web Server with the least-privileged SQL login account that you have already created. It does not create a SQL Server login or update the SQL Server for you.

Before You Begin

Change the username and password on SQL Server. See the "Creating a Least-Privileged SQL Account for Web Conferencing" section for instructions.

Procedure


Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing Service.

Step 2 Open the MeetingPlace Gateway Configurations utility.

Step 3 Select the Web Conferencing tab.

Step 4 Enter the hostname or IP address of the SQL Server that you want to update in the Server field.

Enter local for a local server.

Step 5 Enter the username and password that you applied to the SQL Server.

Step 6 Select OK.

Step 7 Restart the Cisco Unified MeetingPlace Web Conferencing Service.


Note When you restart the Web Server, all manual changes made to the registry are lost.



Related Topics

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Restarting All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Opening the MeetingPlace Gateways Configuration Utility in the Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager module

Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure

Information in the Cisco Unified MeetingPlace Web Conferencing SQL database is replicated from the Cisco Unified MeetingPlace Application Server. As changes occur in the Application Server database, the SQL database is updated in real-time.

Each time the Web Server boots up, it compares the Application Server hostname that it has stored in the SQL database with that configured in the Gateway SIM. If the hostnames match, any changes that occur in the Application Server database are replicated to the SQL database in real-time.

If the hostnames do not match, Cisco Unified MeetingPlace Web Conferencing will consider the Application Server to have changed and fail to boot up.


Note The hostname in the Cisco Unified MeetingPlace Web Conferencing SQL database is the value you entered when you installed the web conferencing application.


Before You Begin

Complete this procedure if you cannot start the Cisco Unified MeetingPlace Web Server because you changed the value of the hostname in the Gateway SIM.

Restrictions

This procedure is strictly limited to the situation where the database on the Cisco Unified MeetingPlace Application Server is the same as the database on the Cisco Unified MeetingPlace Web Server.


Caution Misuse of this procedure in any other situations will cause database corruption and subsequent Cisco Unified MeetingPlace Web Conferencing functional failures.

Procedure


Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing service.

Step 2 Verify that all web conferencing services are shutdown, including the IIS Admin Service and WWW Publishing Service.

Step 3 Open Enterprise Manager and navigate to the \Databases folder.

Step 4 Select and expand the MPWEB database.

Step 5 Select Tables from the left pane.

Step 6 Right-click System in the right pane.

Step 7 Select Open Table > Return All Rows.

Step 8 Change the value in the HostName column to the desired value.

Step 9 Start the Cisco Unified MeetingPlace Web Conferencing service or reboot the server.


Related Topics

If the hostnames on the SQL Server and the Gateway SIM do not match because the Application Server has changed, see Changing the Cisco Unified MeetingPlace Application Server Connection Configured in the Gateway SIM in the Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager module.

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

How to Change and Apply a New SQL Password to Cisco Unified MeetingPlace Web Conferencing

Complete the following tasks in the order shown to change the SQL password and apply the new password to Cisco Unified MeetingPlace Web Conferencing:

Changing the SQL Password If You Know the Old Password or

Changing the SQL Password if You Do Not Know the Old Password

Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing.

Changing the SQL Password If You Know the Old Password

Before You Begin

If you do not know the old password, proceed to the "Changing the SQL Password if You Do Not Know the Old Password" section.

Procedure


Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing service.


Caution Changing the SQL Server account password while the Cisco Unified MeetingPlace Web Conferencing service is running will result in an immediate outage. Stop the service before continuing with the password change procedure.

Step 2 Open Enterprise Manager.

Step 3 Expand the Security folder.

Step 4 Select Logins.

A list of accounts displays on the right.

Step 5 Double-click the SQL account that you want to change.

Step 6 Change the password in the configuration window.


What to Do Next

Proceed to the "Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing" section.

Related Topics

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Changing the SQL Password if You Do Not Know the Old Password

Before You Begin

If you do know the old password, complete the "Changing the SQL Password If You Know the Old Password" section instead.

Procedure


Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing service.


Caution Changing the SQL Server account password while the Cisco Unified MeetingPlace Web Conferencing service is running will result in an immediate outage. Stop the service before continuing with the password change procedure.

Step 2 Open a DOS command window.

Step 3 Log in to SQL Server by entering C:\osql -E nt_acct, where nt_acct is NT account that has access right to the server.

Step 4 Change the password by entering sp_password null, new_pwd, sa, where null represents the password that you do not know and new_pwd is the new SQL password.

Step 5 Enter go.


Example: Changing the SQL Password by Using osql

This example shows the osql commands executed to log in to osql by using the NT account mpadmin and to change the SQL account SA password from some unknown value to new_pwd.

C:\>osql -E mpadmin
1>	sp_password null, new_pwd, sa
2>  go
Password changed
1> exit

What to Do Next

Proceed to the "Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing" section.

Related Topics

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Applying the New SQL Password to Cisco Unified MeetingPlace Web Conferencing

Before You Begin

Ensure that the username and password information that you will provide exists on the SQL Server and that the proper database access rights are assigned.

See the "Creating a Least-Privileged SQL Account for Web Conferencing" section for more information.

Verify that all web conferencing services are stopped, including IIS Admin and WWW Publishing services.


Caution You cannot create or change the username or password on the SQL Server in the Web Conferencing tab. This tab supplies Cisco Unified MeetingPlace Web Conferencing with only the proper SQL database login information.

Complete either the "Changing the SQL Password If You Know the Old Password" section or the "Changing the SQL Password if You Do Not Know the Old Password" section. You will need this information for Step 3 of this procedure.

Procedure


Step 1 Open the Cisco Unified MeetingPlace Gateway Configurations utility.

Step 2 Select the Web Conferencing tab.

Step 3 Change the old SQL password to the new SQL password.

Step 4 Select Apply.

Step 5 Select OK.

Step 6 Restart the Cisco Unified MeetingPlace Web Conferencing service.


Note When you restart the Web Server, all manual changes made to the registry are lost.



Related Topics

Opening the MeetingPlace Gateways Configuration Utility in the Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager module

How to Manage the SQL Database Size

Modifying the SQL Database Properties to Manage Database Size

Examples: Modifying the SQL Database Properties to Manage Database Size

Modifying the SQL Database Properties to Manage Database Size

The MPWEB database that Cisco Unified MeetingPlace Web Conferencing creates is comprised of two files: MPWEB.mdf and MPWEB.ldf. The MDF file contains the actual data, while the LDF contains changes (both the content and timing) made to that data.

On a SQL server that has been actively and properly managed through regular database backup, this LDF file (also called Transaction Log) remains a reasonable size. However, if the SQL database has not been backed up in a while, this transaction log may become very large.

To help prevent the file from growing too large, configure the following three properties for the MPWEB database:

Recovery = Simple

Torn Page Detection = On

Auto Shrink = On


Caution This procedure applies only to the MPWEB database. Do not apply this procedure to any MPWEB slave database (these databases have names that begin with "MPWEB_").

Procedure


Step 1 Open a DOS command window.

Step 2 Log in to SQL Server by entering C:\osql -U userid -P password, replacing userid and password with the applicable value.

Step 3 See the current properties of the database.

a. Enter sp_helpdb MPWEB.

b. Enter go.

Step 4 Modify properties.

a. Enter alter database mpweb set auto_shrink on, recovery simple, torn_page_detection on.

b. Enter go.

Step 5 If you are low on disk space because the database file is already large, force an immediate database shrink and remove empty space in the database files by entering dbcc shrinkdatabase ('mpweb', percent). where percent is the amount of free space that you want to allow.


Examples: Modifying the SQL Database Properties to Manage Database Size

In the following examples, the output is displayed for each command that is used in the "How to Manage the SQL Database Size" section.

Sample Output for Viewing Current Database Properties

In this example, Recovery Mode is set to FULL and Torn Page Detection and Auto Shrink are not configured on this database.

1> sp_helpdb MPWEB
2> go
name         db_size       owner        dbid    created         status  
compatibility_level
MPWEB    1254.00 MB    sa           5       Oct 16 2003
Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=FULL,
Version=539, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52,
IsAutoCreateStatistics, IsAutoUpdateStatistics

Sample Output for Modifying Database Properties

1> alter database mpweb set auto_shrink on, recovery simple, torn_page_detection on
2> go
1> sp_helpdb MPWEB
2> go
name         db_size       owner        dbid    created         status   
compatibility_level
MPWEB   1254.00 MB    sa            5       Oct 16 2003
Status=ONLINE, Updateability=READ_WRITE, UserAccess=MULTI_USER, Recovery=SIMPLE,
Version=539, Collation=SQL_Latin1_General_CP1_CI_AS, SQLSortOrder=52, IsAutoShrink,
IsTornPageDetectionEnabled, IsAutoCreateStatistics, IsAutoUpdateStatistics

Sample Output for Decreasing File Size

In this example, the size of the files are decreased in the MPWEB database to allow 10 percent free space in the files of MPWEB.

1> dbcc shrinkdatabase ('mpweb', 10)
2> go
DbId   FileId CurrentSize MinimumSize UsedPages   EstimatedPages
 ------ ------ ----------- ----------- ----------- --------------
      5      2        2912        1280        2912           1280
(1 row affected)
DBCC execution completed. If DBCC printed error messages, contact your system
administrator.

How to Back Up and Restore MPWEB SQL Database

Complete the following procedures in the order shown to back up and restore the MPWEB database:

Creating a Backup File by Exporting the MPWEB Database

Examples: Exporting the MPWEB Database to Create a Backup File

Restoring the Database

Examples: Restoring the Database

Restoring Cisco Unified MeetingPlace Web Conferencing to a Different Server

Creating a Backup File by Exporting the MPWEB Database

This backup file can be restored only on a SQL Server 2000 with equivalent or later service pack installed.

Procedure


Step 1 Export the MPWEB database.

To export the MPWEB database to create a backup copy while Cisco Unified MeetingPlace Web Conferencing is running (as part of a daily backup procedure, for example), proceed to Step 2.

or

To export the MPWEB database so that it can be imported on another SQL Server that can continue operations for this Cisco Unified MeetingPlace Web Server, stop the Cisco Unified MeetingPlace Web Conferencing service and wait for all of the web conferencing services, IIS Admin service, and World Wide Web publishing service to cease.

Step 2 Access the SQL Server.

If the SQL Server that is hosting the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.

a. Select Start > Run.

b. Enter cmd.

or

If the SQL Server hosting the MPWEB database runs on a separate Windows server, locate that Windows server and log on.


Note If you cannot log on to the applicable Windows server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can connect remotely to the SQL Server.


Step 3 Connect to SQL Server by using osql with the SA account and the appropriate password.

Enter osql -U sa -S servername, where servername is the Windows server name.

If the SQL Server runs locally, you can omit the option -S servername.

If you are not allowed to connect to this SQL Server as sa, connect by using an account with enough privileges to back up a database.

Step 4 Select a fully qualified path and filename for your database export.


Note If you are connected to the SQL Server by running osql on a remote workstation or server, this path must be valid on the Windows server that hosts SQL Server, not on your local workstation.


Step 5 Export the database.

a. Enter backup database MPWEB to disk = 'fullyqualifiedpath', where fullyqualifiedpath is the location that you chose in Step 4.

b. Enter go.

Step 6 Review the informational messages to confirm that the operation is successful.

Step 7 Determine the slave database name(s) on your SQL Server.

a. Enter select name from sysdatabases where name like 'MPWEB%'.

b. Enter go.

The results should include either one or two slave databases.

Step 8 Back up the slave database(s).

a. Enter backup database [MPWEB_XX] to disk = 'C:\temp\mpweb_XX.dat', where XX are the digits of the first slave database and brackets enclose the database name.

b. Enter go.

Step 9 Repeat Step 8 for the second slave database, if applicable.

Step 10 Enter exit to exit osql.

Step 11 Save the mpweb.dat and each mpweb_XX.dat file in a safe location, on a tape or network drive on another server, for example.


Related Topics

Examples: Exporting the MPWEB Database to Create a Backup File

What to Do Next

Proceed to the "Restoring the Database" section

Examples: Exporting the MPWEB Database to Create a Backup File

In the following examples, the output is displayed for each command that is used in the "Creating a Backup File by Exporting the MPWEB Database" section.

Sample Output for Connecting to the SQL Server

C:> osql -U sa -S SERVERNAME
Password: password
1>

Sample Output for Exporting to the Database

1> backup database MPWEB to disk = 'C:\temp\mpweb.dat'
2> go

Sample Output for Viewing Informational Messages

Processed 616 pages for database 'MPWEB', file 'MPWEBData' on file 1.
Processed 3 pages for database 'MPWEB', file 'MPWEBLog' on file 1.
BACKUP DATABASE successfully processed 619 pages in 1.709 seconds (2.962 MB/sec)

Sample Output for Determining the Slave Database Name

In this example, the name of the slave database is MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.

1> select name from sysdatabases where name like 'MPWEB%'
2> go
---------------------------------------------------
name                
[char              ]
--------------------------------------------
MPWEB               
MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1

Sample Output for Backing Up the Slave Database

1> backup database [MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1] to disk =
'C:\temp\mpweb_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.dat'
2> go

Sample Output for Exiting osql

1> exit
C:>

Restoring the Database

Before You Begin

You must have a file called mpweb.dat or mpweb_XX.dat.

This file must have been exported with the backup database command from a SQL Server release that is earlier or equal to the release of the SQL Server to which you want to import the database. See the "Creating a Backup File by Exporting the MPWEB Database" section for instructions.

If you are restoring the database as part of a failed upgrade and had SSL configured on the original Web Server system, note that you will have to install the SSL certificates again after the restore.

Procedure


Step 1 Access the SQL Server.

If the SQL Server that hosts the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.

a. Select Start > Run.

b. Enter cmd.

or

If the SQL Server hosting the MPWEB database runs on a separate Windows server, locate that Windows server and log on.


Note If you cannot log on to the separate Windows server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools including the osql command, so you can connect remotely to the SQL Server.


Step 2 Connect to SQL Server by using osql with the SA account and the appropriate password.

Enter osql -U sa -S servername, where servername is the Windows server name.

If the SQL Server runs locally, you can omit the option -S servername.

If you are not allowed to connect to this SQL Server as SA, connect by using an account with enough privileges to back up a database.

Step 3 Check if a database called MPWEB exists on this server.

a. Enter select name from sysdatabases where name like 'MPWEB%'.

b. Enter go.

Step 4 If a MPWEB database exists, verify that no Cisco Unified MeetingPlace Web Server is currently using this database.

Step 5 (Optional) If one or multiple Cisco Unified MeetingPlace Web Servers are using the database, complete the following:

a. Log on as an administrator on each server.

b. Stop the Cisco Unified MeetingPlace Web Conferencing service.

c. Wait for all the Cisco Unified MeetingPlace Web Conferencing services, the IIS Admin service, and the World Wide Web publishing service to stop.

d. Enter drop database MPWEB to drop the database.

e. Enter go.

Step 6 Before you import your MPWEB database to SQL Server, find out which database physical files are associated with this MPWEB database.

a. Enter restore filelistonly from disk = 'C:\temp\mpweb.dat'.

b. Enter go.

Step 7 Verify the installation folder of the SQL Server where you want to restore this database and check the physical location of the SQL Server master database.

a. Enter sp_helpfile master.

b. Enter go.


Note Unless you have a specific reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery, we recommend that you restore the MPWEB database to the default Data folder of this SQL Server installation.


Step 8 Restore your database and relocate the database physical files to the correct location.

a. Enter restore database MPWEB from disk = 'C:\temp\mpweb.dat' with move 'MPWEBData' to 'D:\MSSQLServer\Data\MPWEB.MDF', move 'MPWEBLog' to 'D:\MSSQLServer\Data\MPWEB.LDF'.

b. Enter go.


Note You must use the with move clause to successfully restore the database because the database backup file contains physical file locations that are not valid for this SQL Server installation.


Step 9 Ensure that the operation was successful by reviewing the informational messages.

Step 10 Repeat Step 8 and Step 9 for each slave database to restore the MPWEB_XX slave database files.

Step 11 Enter exit to exit osql.


Related Topics

Examples: Restoring the Database

Examples: Restoring the Database

In the following examples, the output is displayed for each command that is used in the "Restoring the Database" section.

Sample Output for Connecting to SQL Server

C:> osql -U sa -S SERVERNAME
Password: password
1>

Sample Output for Checking if the MPWEB Database Exists

1> select name from sysdatabases where name = 'MPWEB'
2> go
name
-----------------------------------------------------
MPWEB
1>

Sample Output for Dropping the Database

1> drop database MPWEB
2> go
Deleting database file 'D:\MSSQLServer\Data\MPWEB.LDF'.
Deleting database file 'D:\MSSQLServer\Data\MPWEB.MDF'.
1>

Sample Output for Checking Associated Files

In this example, the MPWEB database was exported from a MSDE 2000 server. The default `Data' folder for this server is D:\MSSQLServer\Data, and the MPWEB database was created with one data file (logical name = `MPWEBData', physical name = D:\MSSQLServer\Data\MPWEB.mdf) and one log file (logical name = `MPWEBLog', physical name = D:\MSSQLServer\Data\MPWEB.ldf).

1> restore filelistonly from disk = 'C:\temp\mpweb.dat'
2> go
---------------------------------------------------
LogicalName PhysicalName            Type  FileGroupName Size          MaxSize              
----------- ------------------------ ------ ------------- --------------
---------------------
MPWEBData  D:\MSSQLServer\Data\MPWEB.mdf D     PRIMARY
    2490368.000000 35184372080640.000000
MPWEBLog   D:\MSSQLServer\Data\MPWEB.ldf L     NULL
    1310720.000000 35184372080640.000000

Sample Output for Verifying Folder Installation and Location of SQL Database

In this example, SQL Server (version 2000) was installed in D:\MSSQLServer, and the default 'Data' folder is D:\MSSQLServer\data.

1> sp_helpfile master
2> go
name        filename        filegroup        size              maxsize            growth    
usage
----------------------------------------------------------------------
master
       D:\MSSQLServer\data\master.mdf
       PRIMARY
      15744 KB           Unlimited          10%                data only
1>

Sample Output for Restoring the MPWEB Database by Using the Move Clause

In this example, additional running upgrade step messages are displayed because the database backup file was created by an earlier version of SQL Server.

1> restore database MPWEB from disk = 'C:\temp\mpweb.dat' with move 'MPWEBData' to
'D:\MSSQLServer\Data\MPWEB.MDF', move 'MPWEBLog' to 'D:\MSSQLServer\Data\MPWEB.LDF'
2> go
Processed 216 pages for database 'MPWEB', file 'MPWEBData' on file 1.
Processed 1 pages for database 'MPWEB', file 'MPWEBLog' on file 1.
Converting database 'MPWEB' from version 515 to the current version 539.
Database 'MPWEB' running the upgrade step from version 515 to version 524.
Database 'MPWEB' running the upgrade step from version 524 to version 525.
Database 'MPWEB' running the upgrade step from version 525 to version 526.
Database 'MPWEB' running the upgrade step from version 526 to version 527.
Database 'MPWEB' running the upgrade step from version 527 to version 528.
Database 'MPWEB' running the upgrade step from version 528 to version 529.
Database 'MPWEB' running the upgrade step from version 529 to version 530.
Database 'MPWEB' running the upgrade step from version 530 to version 531.
Database 'MPWEB' running the upgrade step from version 531 to version 532.
Database 'MPWEB' running the upgrade step from version 532 to version 533.
Database 'MPWEB' running the upgrade step from version 533 to version 534.
Database 'MPWEB' running the upgrade step from version 534 to version 535.
Database 'MPWEB' running the upgrade step from version 535 to version 536.
Database 'MPWEB' running the upgrade step from version 536 to version 537.
Database 'MPWEB' running the upgrade step from version 537 to version 538.
Database 'MPWEB' running the upgrade step from version 538 to version 539.
To achieve optimal performance, update all statistics on the 'MPWEB' database by running
sp_updatestats.
RESTORE DATABASE successfully processed 217 pages in 0.428 seconds (4.136 MB/sec).
1>

Sample Output for Restoring the MPWEB Slave Database

1> restore database [MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1] from disk =
'C:\temp\mpweb_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.dat' with move
'MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1Data' to
'D:\MSSQLServer\Data\MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.MDF', move
'MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1Log' to
'D:\MSSQLServer\Data\MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.LDF'
2> go

Sample Output for Exiting osql

1> exit
C:>

Restoring Cisco Unified MeetingPlace Web Conferencing to a Different Server

Before You Begin

If you are restoring the database as part of a failed upgrade and had SSL configured on the original Web Server system, note that you will have to install the SSL certificates again after the restore.

This procedure assumes that you have a backup file that was saved before the upgrade.

Procedure


Step 1 Sign into another Web Server that is running just the operating system.

Step 2 Restore the backup file that was saved before the upgrade.

Step 3 Install Cisco Unified MeetingPlace Web Conferencing on top of it.


How to Detach and Attach the MPWEB SQL Database

This section describes part of the process for relocating the Cisco Unified MeetingPlace Web Server (MPWEB) database to a dedicated Microsoft SQL Server instance.

For performance and management reasons, you can choose to relocate the Cisco Unified MeetingPlace Web Conferencing SQL database (MPWEB) to your own standalone instance of Microsoft SQL Server 2000 or 2005 (in backward compatibility mode).


Note All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be "remote" in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.


Complete the following procedures in the order shown to detach and attach the MPWEB SQL database:

Detaching the Database

Examples: Detaching the Database

Attaching the Database

Examples: Attaching the Database

Relocating the Database

Detaching the Database

You must detach the MPWEB database with the sp_detach_db command from a SQL Server release that is earlier or equal to the release of the SQL Server to which you want to import the database.

Procedure


Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Stop the Cisco Unified MeetingPlace Web Conferencing service.

Step 4 Wait for the Cisco Unified MeetingPlace Web Conferencing services, IIS Admin service, and World Wide Web Publishing service to stop.

Step 5 Access the SQL Server.

If the SQL Server hosting the MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt:

a. Select Start < Run.

b. Enter cmd.

or

If the SQL Server hosting the MPWEB database runs on a separate Windows server, locate that Windows server and log on.


Note If you cannot log on to the separate Windows server, log on to any Windows based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.


Step 6 Connect to SQL Server by using osql with the SA account and the appropriate password.

If the SQL Server runs locally, you can omit the -S servername option.

If you are not allowed to connect to this SQL Server as SA, connect by using an account that has enough privileges to backup a database.

Step 7 Access the MPWEB database.

a. Enter use mpweb.

b. Enter go.

Step 8 Display a list of the database files.

a. Enter sp_helpfile.

b. Enter go.

Step 9 Access the SQL Server master database.

a. Enter use master.

b. Enter go.

Step 10 Detach the MPWEB database.

a. Enter sp_detach_db 'MPWEB.

b. Enter go.

Step 11 Decide what you should do with the physical files that you identified in Step 8.

These files constitute your detached database. For example, you can archive these files or use them to attach the associated MPWEB database to another SQL Server.

Step 12 Determine the slave database name(s) on your SQL Server.

a. Enter select name from sysdatabases where name like 'MPWEB%.

b. Enter go.

Step 13 (Optional) For each additional database named MPWEB_XX, repeat Step 7 through Step 11 to detach that database, replacing the database name MPWEB with MPWEB_XX.


Note The databases are logically linked; therefore, if you want to archive the detached MPWEB database, you must do the same for each MPWEB_XX database. If you want to reattach the MPWEB database to another SQL Server, you must also reattach the MPWEB_XX database(s).


Step 14 Enter exit to exit osql.


Related Topics

Examples: Detaching the Database

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Examples: Detaching the Database

In the following examples, the output is displayed for each osql command that is used in the "Detaching the Database" section.

Sample Output for Connecting to SQL Server

C:> osql -U sa -S SERVERNAME
Password: password
1>

Sample Output for Accessing the MPWEB Database

1> use mpweb
2> go

Sample Output for Displaying a List of Database Files

In this example, the database MPWEB relies on two physical files: C:\MSSQL2K\Data\MPWEB.mdf and C:\MSSQL2K\Data\MPWEB.ldf.

1> sp_helpfile
2> go
name         fileid    filename                   filegroup size   maxsize  growth usage    
------------- ---------- --------------------------- --------- ------- --------- -------
---------
MPWEBData             1 C:\MSSQL2K\Data\MPWEB.mdf   PRIMARY  
2432 KB Unlimited 1024 KB data only
MPWEBLog              2 C:\MSSQL2K\Data\MPWEB.ldf   NULL     
1280 KB Unlimited 10%    log only

Sample Output for Accessing the SQL Server Master Database

1> use master
2> go

Sample Output for Detaching the MPWEB Database

1> sp_detach_db 'MPWEB'
2> go

Sample Output for Determining the Slave Database Name

In this example, the name of the slave database is MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1.

1> select name from sysdatabases where name like 'MPWEB%'
2> go
---------------------------------------------------
name                
[char              ]
-------------------------------------------- 
MPWEB_E22AF0EC-805F-45D4-8F76-FB0C6378A5EC-1

Sample Output for Exiting osql

1> exit
C:>

Attaching the Database

Ensure that you have a valid detached MPWEB database, usually two files named MPWEB.mdf (data file) and MPWEB.ldf (log file) though file names may vary.

Procedure


Step 1 Access the SQL Server.

If the SQL Server to which you want to attach your MPWEB database runs on the Cisco Unified MeetingPlace Web Server, access the command prompt.

a. Select Start > Run.

b. Enter cmd.

or

If the SQL Server runs on a separate Windows server, locate that Windows server and log on.


Note If you cannot log on to that Windows server, log on to any Windows-based workstation or server on the network that has a valid installation of SQL Server Client tools, including the osql command, so that you can remotely connect to the SQL Server.


Step 2 Connect to SQL Server by using osql.

Enter osql -U sa -S server-name, where server-name is the Windows SQL Server to which you want to attach the MPWEB database.

If the SQL Server runs locally, you can omit the -S server-name option.

Step 3 Enter your password for the appropriate SA account.


Note If you are not allowed to connect to this SQL Server as SA, connect by using an account that has enough privileges to attach a database.


Step 4 Determine if a database named MPWEB already exists on this server.

a. Enter select name from sysdatabases where name = 'MPWEB'.

b. Enter go.

Step 5 If no MPWEB database exists, proceed to Step 6.

or

If a MPWEB database exists, ensure that it is not being used by an existing Cisco Unified MeetingPlace Web Server.


Note You cannot attach a MPWEB database to this SQL Server if an active MPWEB database exists already. Before you proceed, you must detach the existing MPWEB database by completing the "Detaching the Database" section.


Step 6 To verify the installation folder of the SQL Server to which you want to restore this database, check the physical location of the SQL Server master database.

a. Enter sp_helpfile master.

b. Enter go.


Note Unless you have a reason to restore your MPWEB database to another disk location, such as for performance and tuning or data recovery reasons, we recommend that you restore the database to the default data folder of this SQL Server installation.


Step 7 Copy the MPWEB.mdf and MPWEB.ldf files under the data folder that you identified in Step 6.

Step 8 Attach the MPWEB database.

a. Enter sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf'.

b. Enter go.

Step 9 (Optional) If you have a valid set of files for the MPWEB_XX slave database(s), repeat Step 4 through Step 9 for each slave database, replacing MPWEB with MPWEB_XX to attach that database.

Step 10 Enter exit to exit osql.


Examples: Attaching the Database

In the following examples, the output is displayed for each osql command that is used in the "Attaching the Database" section.

The following examples use the files MPWEB.mdf and MPWEB.ldf:

Sample Output for Connecting to SQL Server

C:> osql -U sa -S SERVERNAME
Password: password
1>

Sample Output for Checking if the MPWEB Database Exists

1> select name from sysdatabases where name = 'MPWEB'
2> go
name
-----------------------------------------------------
(0 row affected)
1>

Sample Output for Checking the Physical Location of the SQL Server Master Database

In this example, SQL Server Version 2000 is installed in C:\MSSQL2K, and the default data folder is C:\MSSQL2K\data.

1> sp_helpfile master
2> go
name filename filegroup size maxsize growth usage
----------------------------------------------------------------------
master
       C:\MSSQL2K\data\master.mdf
       PRIMARY
       15744 KB           Unlimited 10% data only
1>

Sample Output for Attaching the MPWEB Database

1> sp_attach_db 'MPWEB','data path\MPWEB.mdf','data path\MPWEB.ldf'
2> go

Sample Output for Exiting osql

1> exit
C:>

Relocating the Database

You may want to relocate the database and put the Cisco Unified MeetingPlace application and databases onto different servers. Examples are if the server you are using is running out of disk space, or for performance or backup considerations.


Note Do not uninstall the local SQL Server if you are using remote SQL Server 2005. If, however, you are using remote SQL Server 2000, then you may choose to uninstall the SQL Server software and delete the MPWEB SQL database files from the Cisco Unified MeetingPlace Web Server.


Procedure


Step 1 Detach the MPWEB SQL databases on the existing (for example, local) SQL Server:

Follow the instructions in the "Detaching the Database" section.

Step 2 Attach the MPWEB SQL databases to the new SQL Server:

Follow the instructions in the "Attaching the Database" section.

Step 3 Change the Database Connection settings on your Cisco Unified MeetingPlace Web Conferencing server to point to the new SQL Server:

a. Double-click the orange door icon in the System Tray.

b. Select Web Conferencing.

c. Enter the new SQL server name in the Server field.

d. Enter the new Username and Password.

e. Select OK.


How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

During installation, a MPWEB database is tied to a specific Cisco Unified MeetingPlace Web Server through a unique GUIDWebID that is generated by the Cisco Unified MeetingPlace Web Conferencing installer. This GUIDWebID is stored in the registry and SQL database. Therefore, if you want to transfer the MPWEB SQL database and all attachments from the old server to a new server, the new server must use the same GUIDWebID as the old server. This requires preparing the following three components from the old server to the new server:

The whole \MPWEB\Meetings folder (including all sub-folders) in zipped or unzipped format.

The GUIDS.reg file with modifications to add the GUIDWebID and the mpweb slave database filename information. The GUIDS.reg file, as well as the GUIDWebID and DBName registry values, come from the old server.

A backup of the MPWEB database and mpweb slave database(s) from the old server.

Complete the following procedures in the order shown to replace an existing Cisco Unified MeetingPlace Web Server with a new server and retain the attachments of past meetings so that they are accessible from the new server:

Preparing the Current Cisco Unified MeetingPlace Web Server

Installing the Replacement Cisco Unified MeetingPlace Web Server

Building the Replacement Cisco Unified MeetingPlace Web Server

Preparing the Current Cisco Unified MeetingPlace Web Server

Procedure


Step 1 Stop all Cisco Unified MeetingPlace Web Conferencing services, including the Gateway SIM service.

Step 2 Detach this Cisco Unified MeetingPlace Web Server from the Cisco Unified MeetingPlace Application Server.

a. Open the Gateway SIM Agent.

b. From the Gateway SIM tab, write down the hostname or IP address of the Cisco Unified MeetingPlace Application Server for future reference.


Note You must use the same server reference when you install the new Cisco Unified MeetingPlace Web Server. If the Application Server is specified as a hostname, you will enter that same hostname; if it is specified as an IP address, you will use an IP address later.


c. Select Delete Unit to detach this Web Server from the Application Server.

Step 3 Make a copy of the entire \MPWEB\Meetings folder and its contents.

Step 4 Make a copy of the GUIDS.reg file.

You can find this file where Cisco Unified MeetingPlace Web Conferencing application files are stored.

Step 5 Open regedit and obtain the registry values for GUIDWebID and DBName.


Caution Ensure that the registry values are correct. Compare the values that you obtained in Step 5 against what you enter in Step 6.

Step 6 Open GUIDS.reg in a text editor and add the GUIDWebID and DBName registry paths and key values.

Step 7 Save the file with these changes.

Step 8 Make a backup of the MPWEB database and the mpweb slave database(s).

Step 9 Copy the attachments, GUIDS.reg and the MPWEB backup, to the new server.


Related Topics

Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

Opening the MeetingPlace Gateways Configuration Utility in the Configuring the Cisco Unified MeetingPlace Gateway System Integrity Manager module

How to Back Up and Restore MPWEB SQL Database

What to Do Next

Proceed to the "Installing the Replacement Cisco Unified MeetingPlace Web Server" section.

Installing the Replacement Cisco Unified MeetingPlace Web Server

Replacement installations of Cisco Unified MeetingPlace Web Conferencing must match the version that was running on the old server. For example, if you are running Release 7.1 on the old server, you must install Release 7.1 or a later release on the new server.

Before You Begin

Run GUIDS.reg on the new server to add the following four keys in to the registry: GUID IDs for Site, System, Web, and mpweb slave db filename. To run GUIDS.reg, right-click GUIDS.reg, then select merge.

Have the "Preparing the Current Cisco Unified MeetingPlace Web Server" section available to assist you with this procedure.

Procedure


Step 1 Install Cisco Unified MeetingPlace Web Conferencing.

Step 2 Reboot the server when you are prompted at the end of the installation.

After the initial reboot, the installation program continues and may reboot a few more times to complete the installation.

Step 3 When you are prompted for the Cisco Unified MeetingPlace Application Server information, enter the value that you wrote down in Step 2 of the "Preparing the Current Cisco Unified MeetingPlace Web Server" section.

Step 4 After the installation completes, verify that Cisco Unified MeetingPlace Web Conferencing is functional.


What to Do Next

Proceed to the "Building the Replacement Cisco Unified MeetingPlace Web Server" section.

Related Topics

See the "Installing the Cisco Unified MeetingPlace Web Conferencing Server" section in the Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

Building the Replacement Cisco Unified MeetingPlace Web Server

Before you Begin

Verify that the release of Cisco Unified MeetingPlace Web Conferencing that is installed on the new server is either the same or later than the release installed on the old server. For example, if you are running Release 7.1 on the old server, you must be running Release 7.1 or a later release on the new server.

Know how to use Enterprise Manager or the osql drop database command.

See the "Restoring the Database" section for more information about the osql command.

Procedure


Step 1 Stop all Cisco Unified MeetingPlace Web Conferencing services.

Step 2 Use Enterprise Manager or the osql drop database command to delete the MPWEB SQL database.

This database was created automatically during the Cisco Unified MeetingPlace Web Conferencing installation.

Step 3 Use either Enterprise Manager or the osql restore database command to restore the old MPWEB database on to the new server.

Step 4 Delete all contents in the \MPWeb\Meetings\ folder.

Step 5 Delete all contents in the \MPWeb\Web\WebConf\Content\7 folder.

Step 6 Restore all the files and attachments from the old server in to \MPWeb\Meetings folder.

Step 7 Restore all the files and attachments from the old server in to \MPWeb\Web\WebConf\Content\7 folder.

Step 8 Reboot the server or restart the Cisco Unified MeetingPlace Web Conferencing service.


Note When you restart the Web Server, all manual changes made to the registry are lost.


Step 9 Update the Cisco Unified MeetingPlace Web Administration page.

a. Sign in to the end-user web interface with a System Manager profile.

b. Select Admin.

c. Select Web Server.

d. Update appropriate fields, such as the Web Server Hostname.


Related Topics

Changing the Web Server Hostname From an IP Address to a Hostname

Setting Your Web Server Options

Stopping All Web Conferencing Services

Updating the Indices on the SQL Database

The SQL database needs regular maintenance. If the SQL database is running slowly, or if the SQL database is running on a remote SQL server, then you should run this procedure on a nightly or weekly basis.

Procedure


Step 1 Launch SQL Enterprise manager.

Step 2 Select the Cisco Unified MeetingPlace Web Conferencing database, which is named something similar to MPWEB_<GUID_ID>_<Location>.

<Location> can be either 1 or 2, depending on whether this is an internal or an external Web Server.

Step 3 Select Tools > Wizards from the menu options at the top of the window.

Step 4 Expand on the Management option.

Step 5 Select Database Maintenance Plan Wizard.

Step 6 Select Next on the Welcome to the Database Maintenance Plan Wizard page.

Step 7 Select the database on the Select Database page, then select Next.

Step 8 Check Reorganize data and index pages on the Update Data Optimization Information page, then select Next.

Step 9 (Optional) Change the schedule on which this maintenance procedure runs.

Step 10 Select Next on the Database Integrity Check page.

Step 11 Uncheck Backup the database on the Specify the database backup plan page, then select Next.

Step 12 Select Next on the following pages:

Specify backup disk directory page

Specify the transaction log backup plan page

Reports to generate page

Maintenance Pan History page

Step 13 Select Finish on the Completing the maintenance plan wizard page.


How to Use a Custom TCP Port for the SQL Server Connection


Note All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be "remote" in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.


Customizing the Port for an SQL Database

Customizing the SQL Port for the "Remote" SQL Database

Switching to the "Remote" SQL Database on the Custom Port

Customizing the Port for an SQL Database

Procedure


Step 1 In the SQL server network utility, perform the following:


Note To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.


a. Select TCP.

b. Select Properties

c. Change the default port from 1433 to the desired port, then select OK.

Step 2 Stop the SQL server.

Step 3 Start the SQL server.

Step 4 Edit the registry:

a. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.

b. Create a registry key of type DWORD named SlaveDBPort.

c. Set the created entry to your desired value for the port.

Step 5 Restart the Cisco Unified MeetingPlace Web Conferencing service.


Note When you restart the Web Server, all manual changes made to the registry are lost.



Customizing the SQL Port for the "Remote" SQL Database


Note All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the replication. SQL Servers can be "remote" in that they are installed on separate machines within a local data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.


Procedure


Step 1 Install Cisco Unified MeetingPlace Web Conferencing as usual, choosing remote database (this will install with the default port, 1433).

Step 2 Use the SQL server network utility to change the port on the remote database:


Note To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.


a. Select TCP.

b. Select Properties.

c. Change the default port from 1433 to the desired port, then select OK.

Step 3 Stop the SQL server.

Step 4 Start the SQL server.

Step 5 Edit the registry:

a. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.

b. Create a registry key of type DWORD named SlaveDBPort.

c. Set the created entry to your desired value for the port.

Step 6 Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).

Step 7 Select System DSN.

Step 8 Select MPWEB.

Step 9 Select Configure.

Step 10 Select Next on the Microsoft SQL Server DSN Configuration screen.

Step 11 Select Client Configuration.

Step 12 Uncheck Dynamically determine port box.

Step 13 Enter your custom port number, then select OK.

Step 14 Close ODBC.

Step 15 Restart the Cisco Unified MeetingPlace Web Conferencing service.


Note When you restart the Web Server, all manual changes made to the registry are lost.



Switching to the "Remote" SQL Database on the Custom Port

Procedure


Step 1 Start with the local database on default port 1433.

Step 2 Stop the Cisco Unified MeetingPlace Web Conferencing service

Step 3 Use the SQL server network utility to change the port on the remote database:


Note To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.


a. Select TCP.

b. Select Properties.

c. Change the default port from 1433 to the desired port, then select OK.

Step 4 Stop the SQL server.

Step 5 Start the SQL server.

Step 6 Edit the registry:

a. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.

b. Create a registry key of type DWORD named SlaveDBPort.

c. Set the created entry to your desired value for the port.

Step 7 Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).

Step 8 Select System DSN.

Step 9 Select MPWEB.

Step 10 Select Configure.

Step 11 Change the "Which SQL server do you want to connect to" field to the remote SQL server name.

Step 12 Select Next on the Microsoft SQL Server DSN Configuration screen.

Step 13 Select Client Configuration.

Step 14 Uncheck Dynamically determine port box.

Step 15 Enter your custom port number, then select OK.

Step 16 Close ODBC.

Step 17 On the web server, open the MeetingPlace Gateway Configuration utility and select Web Conferencing.

Step 18 Change the database name from (local) to remote database.

Step 19 Enter the user name and password for the remote database.

Step 20 Select Apply, then OK.

Step 21 Start the Cisco Unified MeetingPlace Web Conferencing service.