When a Web Conferencing Server needs to create a metadata folder for a conference, after the server has created or identified the appropriate organizer folder, the server extracts the conference ID from the XML in the C3P addConferencerequest, and then searches the subfolders below the organizer folder for a folder with the same name as the conference ID. If a matching folder does not exist, the Web Conferencing Server creates a new folder below the organizer folder.

The conference folder contains all the information that is used by Web Conferencing Server to recreate the content of a conference. The following figure shows the structure of the files that are stored in a conference folder.

The conference folder has one subfolder named for presentations. In this subfolder, the Web Conferencing Server creates all the conference files.

Conference.xml File

For each conference, a conference.xml file is created. The conference.xml file contains the following information about the conference:

  • Conference ID. The same as the conference folder name.

  • Organizer URI. The same URI used to build the organizer hash.

  • Conference expiration time. The time and date used by the clean-up mechanism to determine when the content should be removed.

  • Encryption key. The master encryption key. The Web Conferencing Server randomly generates an encryption key using Advanced Encryption Standard (AES) as the encryption algorithm. This key is used to encrypt the metadata XML files for the slide sets in the conference. This encryption is an additional layer of protection on top of the access permissions on the root metadata folder.


Each slide set has a unique identifier. In the preceding illustration, the identifiers start with aaaand end with zzz. The SSMaxId file stores the latest allocated ID for saved slide sets. The file is updated by the Web Conferencing Server when a new slide set is created. The file is read by the Web Conferencing Server when the content of the conference needs to be recovered.