May 26, 2004
Cisco MeetingPlace Web Conferencing
Note: This Field Notice is a legacy Latitude Field Notice that has been converted to the Cisco format so the information would remain available to their customers.
We advertise that MeetingPlace Web Conferencing gateway can be used as archive to store MeetingPlace meeting records and MeetingNotes, while the same information are purged from MeetingPlace server.
Two parameters that control the purging of meeting records and MeetingNotes on the MeetingPlace server are:
Number of days to retain, which controls when MeetingNotes are purged. This is typically set to a low number so that MeetingNotes are purged and disk space freed to allow users to continue to schedule meetings with attachments and recordings.
Days until meeting stats are purged, which controls when the meeting records are purged. When a meeting whose stat is purged from MeetingPlace, its existence is completely erased from MeetingPlace server and you will not be able to find it in MeetingTime. This parameter has a maximum limit of 180 days.
Two parameters that control the purging of meeting records and MeetingNotes on the WebPublisher gateway are:
Purge meetings held before, which controls when MeetingNotes are purged. For customers interested in archiving, this parameter is typically set to a very large number, or to a distant past date. This prevents MeetingNotes from being deleted on the NT server.
Delete purge meetings, which controls whether meeting records will be purged at the same time that MeetingNotes are deleted. For example when meetings' MeetingNotes are purged due to the above "Purge meetings held before" parameter. For customers interested in archiving, this parameter is typically not selected. For example it is unchecked.
By correctly setting the two parameters on the WebPublisher gateway, it is possible to continue to build up a database that will contain meeting records and MeetingNotes dating back a long time.
Unfortunately, when you try to review very old meetings through the web browser, MPAgent will try to find that meeting in MeetingPlace servers' database instead of in WebPublishers' database. As a result, you will not see your meeting in the Past Meeting page, and will not be able to access MeetingNotes despite the fact that the meeting records and MeetingNotes for that meeting are still on the NT server.
Customer who have setup their WebPublisher to archive MeetingPlace meetings and MeetingNotes can only review meetings that are less than six months old.
The 180 day limit of "Days until meeting stats are purged" on the MeetingPlace server will most likely not be changed. If meeting records is allowed to grow too big on the MeetingPlace server, it could cause the server to fail or cause future server upgrade to fail.
Engineering to re-code MPagent so that it can retrieve historical records from MPWeb's SQL database. Fix will likely be incorporated into MeetingPlace Web Conferencing 4.2.7.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.