Cisco Unified MeetingPlace, Release 6.x -- Outlook Integration Changes for Cisco Unified MeetingPlace Release 6.0, Maintenance Release 5

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m
m
Line 114: Line 114:
# Open the .TXT file in Microsoft Word.
# Open the .TXT file in Microsoft Word.
# Perform a series of Find and Replace’s in the following order. Note that quotes should not be entered in the Find and Replace text boxes:
# Perform a series of Find and Replace’s in the following order. Note that quotes should not be entered in the Find and Replace text boxes:
-
#* Replace &gt;!--with <!--
+
#* Replace <nowiki>"&gt;!--" with "<!--"</nowiki>
-
#* Replace --&lt;with -->
+
#* Replace <nowiki>"--&lt;" with "-->"</nowiki>
-
#* Replace ^p” with “ “ (a space)
+
#* Replace <nowiki>"^p" with " "(a space)</nowiki>
-
# Save the file as plain text by choosing the Plain Text option in the "Save as type" box and change the extension of the file to .TPL.  
+
# Save the file as plain text by choosing '''Plain Text''' in the "Save as type" box and change the extension of the file to .TPL.  
# Select '''Save'''.
# Select '''Save'''.

Revision as of 16:44, 20 August 2009

Cisco Unified MeetingPlace, Release 6.x


This page describes changes to the Microsoft Outlook integration for Cisco Unified MeetingPlace Release 6.0 Maintenance Release 5 (MR5).


Contents

iCalendar-Based Back-End

This is a one-way process of getting meeting notifications from the Audio Server to the Microsoft Outlook integration, through several Cisco Unified MeetingPlace components. The MPWeb database is the only one used to both store and retrieve data; this is required to support update notifications with iCalendar. When sending an updated meeting notification, you need to have information about the previous notifications sent for the same meeting.


Supported Configurations

Both the front-end and the back-end notification mechanisms for the Microsoft Outlook gateway depend on the MPWeb, but in different ways. The front-end notification mechanism requires MPWeb to be present on the machine that runs the gateway. This is because ASP logic in the front end relies on MPAgent / MPX (which are part of the MPWeb) to do template processing.

The new iCalendar back-end notification mechanism requires a connection to the MPWeb SQL database to keep information about delivered notifications. Since ODBC is used to connect to the MPWeb database, the back-end does not require that the MPWeb is on the same machine, just that it is accessible via TCP/IP.


Front-End and Back-End, Connecting to Local MPWeb Database

You can install both the front-end and back-end notification mechanisms on a machine, and configure the back-end to connect to the local MPWeb SQL Database. By default, the installation program will attempt to use this configuration by examining the Windows registry. This is a common configuration suitable for most users.


Back-End Only, Connecting to Remote MPWeb Database

During the installation, you can select to install the back-end notification mechanism only. You will be prompted to enter the name of the MPWeb machine which runs the SQL database that you want to use. Once installed, you can change the MPWeb machine you connect to by using the MP Control Panel. This configuration is useful if you want to support only back-end notifications, and keep the MPWeb server load low.


Front-End and Back-End, Connecting to Remote MPWeb Database =

You can install both the front-end and back-end notification mechanisms on a machine, and configure the back-end to connect to the database on a different MPWeb server. You can configure this during installation, or by using the MP Control Panel after the installation has finished. This configuration might be suitable for clustered environments.


Front-End Only

You can install only the front-end notification mechanism on a machine. You can configure this during the installation. This configuration is suitable for users that only use Outlook to schedule their MeetingPlace meetings. Invitations for meetings scheduled through MPWeb will not be delivered to Outlook users.



Migrating to Cisco Unified MeetingPlace Release 6.0 MR5 and the iCalendar-Based Back-End

When installing Cisco Unified MeetingPlace Release 6.0 MR5 on a machine that previously did not have an older version of the Microsoft Outlook integration, no special steps are required. Just run setup.exe and follow the instructions on the screen.

If you have an older version of the Microsoft Outlook integration installed on the machine, you must run the migration tool, to migrate information about delivered notifications from dedicated calendar in Exchange to a table in MPWeb database.


Upgrading to Microsoft Outlook for Cisco Unified MeetingPlace Release 6.0 MR5

  1. Upgrade Cisco Unified MeetingPlace Web Conferencing and Gateway SIM to MR5. See Upgrading to Cisco Unified MeetingPlace Release 6.0.
  2. Run the migration tool, called MPOLMig.exe, (see below). This may take a while if there are a lot of meetings in the calendar.
    This migration tool does the following:
    • Moves all the scheduled meetings to the MPWeb database.
    • Uninstalls the old version of the Microsoft Outlook integration.
    • Reboots.
    • Automatically installs Microsoft Outlook for Cisco Unified MeetingPlace Release 6.0 MR5.
  3. Reboot the machine.
  4. Customize your notification templates. (Because this is a new version of the Microsoft Outlook integration, the customized templates use a new format. If you customized any templates in your previous release, you will have to customize them again. Templates from previous releases will not work and will result in corrupted notifications.) See Customizing the Microsoft Outlook Templates.
  5. Check your anti-virus rules, as they may need to be adjusted. (McAfee will give you more protection than you need here.)



Running the Migration Tool

The migration tool is a file called MPOLMig.exe, which is shipped with each version of the Microsoft Outlook integration installation program for MR5.


Migration Tool Syntax

MPOLMig.exe [-e <eprofile> [<epwd>]] [-s <shost> [<suser> [<spwd>]]] [-i <ipath>] [-?]


Migration Tool Arguments

  • -s: Use to supply the name of the remote MPWeb database and the log on credentials (if you are not using the local MPWeb database).
  • -i: Use to specify the path of the migration toll if you are running the migration tool from a directory other than the one containing the setup.exe file.
  • -e: Use to skip the prompt for choosing the mail profile to use to connect to the Exchange.


Migration Tool Inputs

  • eprofile: The name of the mail profile to use to connect to the Exchange Server.
  • epwd: The password for the eprofile.
  • shost: The SQL Server which stores the notification information.
  • suser: The account name to use to connect to the SQL Server.
  • spwd: The password for the suser.
  • ipath: The path to the new installation executable file.


NOTE: If the Exchange profile information is not entered, the system prompts you to log in. If the SQL Server information is not entered, this tool will attempt to discover it automatically.


Customizing the Microsoft Outlook Templates

Follow these steps to customize the templates.

  1. Open Microsoft Word.
  2. Open an RTF-formatted TPL file.
  3. Choose File > Save As.
  4. Choose Web Page, Filtered in the "Save as type" box.
  5. Select Save.
  6. Close the file.
  7. Using Microsoft Explorer, change the extension of this new .HTM file to a .TXT extension.
  8. Open the .TXT file in Microsoft Word.
  9. Perform a series of Find and Replace’s in the following order. Note that quotes should not be entered in the Find and Replace text boxes:
    • Replace ">!--" with "<!--"
    • Replace "--<" with "-->"
    • Replace "^p" with " "(a space)
  10. Save the file as plain text by choosing Plain Text in the "Save as type" box and change the extension of the file to .TPL.
  11. Select Save.

Rating: 0.0/5 (0 votes cast)

Personal tools