Cisco Unified MeetingPlace, Release 7.0 -- How to Replace a Cisco Unified MeetingPlace Web Server and Retain the SQL Database

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration




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 and \MPWeb\Web\WebConf\Content\7 folders (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:



Contents

Preparing the Current Cisco Unified MeetingPlace Web Server

Procedure
  1. Stop all Cisco Unified MeetingPlace Web Conferencing services, including the Gateway SIM service.
  2. Detach this Cisco Unified MeetingPlace Web Server from the Cisco Unified MeetingPlace Application Server.
    1. Open the Gateway SIM Agent.
    2. 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.
    3. Click Delete Unit to detach this Web Server from the Application Server.
  3. Make a copy of the entire \MPWEB\Meetings folder and its contents.
  4. Make a copy of the entire \MPWeb\Web\WebConf\Content\7 folder and its contents.
  5. Make a copy of the GUIDS.reg file.
    You can find this file where Cisco Unified MeetingPlace Web Conferencing application files are stored.
  6. 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.
  7. Open GUIDS.reg in a text editor and add the GUIDWebID and DBName registry paths and key values.
  8. Save the file with these changes.
  9. Make a backup of the MPWEB database and the mpweb slave database(s).
  10. Copy the attachments, GUIDS.reg and the MPWEB backup, to the new server.


Related Topics


What to Do Next

Proceed to Installing the Replacement Cisco Unified MeetingPlace Web Server.




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.0 on the old server, you must install Release 7.0 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.


Procedure
  1. Install Cisco Unified MeetingPlace Web Conferencing.
  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.
  3. When you are prompted for the Cisco Unified MeetingPlace Application Server information, enter the value that you wrote down in Step 2 of Preparing the Current Cisco Unified MeetingPlace Web Server.
  4. After the installation completes, verify that Cisco Unified MeetingPlace Web Conferencing is functional.


Related Topics


What to Do Next

Proceed to Building the Replacement Cisco Unified MeetingPlace Web Server.


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.0 on the old server, you must be running Release 7.0 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 for more information about the osql command.


Procedure
  1. Stop all Cisco Unified MeetingPlace Web Conferencing services.
  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.
  3. Use either Enterprise Manager or the osql restore database command to restore the old MPWEB database on to the new server.
  4. Delete all contents in the \MPWeb\Meetings\ folder.
  5. Delete all contents in the \MPWeb\Web\WebConf\Content\7 folder.
  6. Restore all the files and attachments from the old server in to \MPWeb\Meetings folder.
  7. Restore all the files and attachments from the old server in to \MPWeb\Web\WebConf\Content\7 folder.
  8. Reboot the server or restart the Cisco Unified MeetingPlace Web Conferencing service.
  9. Update the Cisco Unified MeetingPlace Web Administration page.
    1. Sign in to the end-user web interface with a System Manager profile.
    2. Click Admin.
    3. Click Web Server.
    4. Update appropriate fields, such as the Web Server Hostname.


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


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools