Cisco Unified MeetingPlace, Release 7.0 -- How to Use a Custom TCP Port for the SQL Server Connection

From DocWiki

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration

Contents 1 Customizing the SQL Port for the Local SQL Database 1.1 Procedure 2 Customizing the SQL Port for the Remote SQL Database 2.1 Procedure 3 Switching from the Local Database to the Remote Database on the Custom Port 3.1 Procedure

Customizing the SQL Port for the Local SQL Database

Procedure

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.

   1. Select TCP.
   2. Click Properties
   3. Change the default port from 1433 to the desired port.
   4. Click OK.
2. Stop the SQL server.
3. Start the SQL server.
4. Edit the registry:
   1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
   2. Create a registry key of type DWORD named SlaveDBPort.
   3. Set the created entry to your desired value for the port.
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

Procedure

1. Install Cisco Unified MeetingPlace Web Conferencing as usual, choosing remote database (this will install with the default port, 1433).
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.

   1. Select TCP.
   2. Click Properties.
   3. Change the default port from 1433 to the desired port.
   4. Click OK.
3. Stop the SQL server.
4. Start the SQL server.
5. Edit the registry:
   1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
   2. Create a registry key of type DWORD named SlaveDBPort.
   3. Set the created entry to your desired value for the port.
6. Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).
7. Click System DSN.
8. Select MPWEB.
9. Click Configure.
10. Click Next on the Microsoft SQL Server DSN Configuration screen.
11. Click Client Configuration.
12. Uncheck Dynamically determine port box.
13. Enter your custom port number.
14. Click OK.
15. Close ODBC.
16. 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 from the Local Database to the Remote Database on the Custom Port

Procedure

1. Start with the local database on default port 1433.
2. Stop the Cisco Unified MeetingPlace Web Conferencing service
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.

   1. Select TCP.
   2. Click Properties
   3. Change the default port from 1433 to the desired port.
   4. Click OK.
4. Stop the SQL server.
5. Start the SQL server.
6. Edit the registry:
   1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.
   2. Create a registry key of type DWORD named SlaveDBPort.
   3. Set the created entry to your desired value for the port.
7. Select Start > Programs > Administrative Tools > Open Data Sources (ODBC).
8. Click System DSN.
9. Select MPWEB.
10. Click Configure.
11. Change the "Which SQL server do you want to connect to" field to the remote SQL server name.
12. Click Next on the Microsoft SQL Server DSN Configuration screen.
13. Click Client Configuration.
14. Uncheck Dynamically determine port box.
15. Enter your custom port number.
16. Click OK.
17. Close ODBC.
18. On the web server, open the MeetingPlace Gateway Configuration utility.
19. Click Web Conferencing.
20. Change the database name from (local) to remote database.
21. Enter the user name and password for the remote database.
22. Click Apply.
23. Click OK.
24. Start the Cisco Unified MeetingPlace Web Conferencing service.