locked
Conferencing Content RRS feed

  • Question

  • What will happen to conferencing content after a live meeting session? Will it grow bigger after each live meeting session? Is housekeeping required?
    Tuesday, June 5, 2007 4:39 AM

Answers

  • From the Technical Overview document:

    A meeting expires when the meeting data record is deleted from the backend meeting database and all content data associated with the meeting are deleted. After expiration, no participants, including the organizer, can join the meeting.

    In Office Communications Server, meeting expiration is controlled by two processes running on the front-end server and the Web Conferencing Server. The processes are automatic and based on an expiry time received from clients when the meeting is created. The expiry time is based on the criteria:

    ·         For a one time scheduled meeting, the expiry time is the scheduled end time plus 14 days.

    ·         For a recurring scheduled meeting with an end date, the expiry time is the scheduled end time of the last meeting occurrence plus 14 days.

    ·         For an ad hoc IM or A/V conference, the expiry time is 8 hours.

    ·         For a recurring scheduled meeting without a specified end date, no expiry time or the expiry time. Recurring scheduled meetings without a specified end date expire 6 months after the last meeting activation.

    The expiration process running on the front-end server deletes the meeting data record from the backend database after the expiry date if the conference is not currently active. The expiry time is communicated to each conferencing server involved at conference activation time. The Web Conferencing Server will delete all conference content data (including uploaded slides, whiteboard session, and shared notes) from the presentation file share, after the expiry time plus a 14 day grace period. This setting is configurable, see the Office Communications Server 2007 Administration Guide for details.

     

    Office Communications Server 2007 maintains meeting state in a separate database from presence. The database resides either on a Standard Edition Server or on the Backend Database server for an Enterprise Edition Pool.

    The conference database stores information about each meeting currently configured on a server. This information includes the conference ID, associated security keys, expiration time, and user roles and privileges. The conference database also includes information about each meeting running on a server, so that if a meeting should fail its state can be quickly restored and the meeting resumed without loss of content. The conference database is implemented as a separate table in the same database that contains information about user registration and presence.

    Meeting content, unlike meeting state, is not stored in the Back-End Database. Instead, meeting content is stored on a dedicated file share created by the administrator. In Standard Edition deployments, this file share is normally created on the Standard Edition Server. In Enterprise Edition deployments, this file share is normally created on a separate computer from the Front End Servers.

     

    Wednesday, June 13, 2007 9:36 PM