Message Queuing Architecture and Configuration for Archiving
Dernière rubrique modifiée : 2009-03-11
The archiving and CDR agent uses Message Queuing to receive notifications from the Archiving and CDR Server destination queue. (Message Queuing also serves as a local temporary transmission queue if the Archiving Server is unavailable.) Message Queuing must be installed on all computers that participate in archiving, such as the following:
- An Office Communications Server with an archiving and CDR agent that connects to the Archiving Server.
- The Office Communications Server that is running the Archiving Server.
- You must install Message Queuing on each server that you want to associate with the Archiving Server. If you want to archive an Enterprise pool, you must install Message Queuing on each server in the pool.
- Because Message Queuing relies on the Active Directory Domain Services for encryption to the destination queue, Message Queuing must be installed with the Active Directory integration component, which is the default configuration during Message Queuing installation.
.gif "Dd572527.note(fr-fr,office.13).gif") Remarque : |
|---|
| In a two-tier topology where the Archiving service component and the message queue are on a separate computer from the archiving database, automatic setup of encryption is not supported for the messages that are sent by the Archiving service component to the archiving database. Instead, encryption of the link between the Archiving service component and the archiving database must be configured manually by using SQL Server SSL encryption. For details about configuring SQL Server SSL encryption, see the Microsoft Knowledge Base article 276553, How to enable SSL encryption for SQL Server 2000 if you have a valid Certificate Server, at https://go.microsoft.com/fwlink/?LinkId=144421. For information about configuring the registry to establish and help enforce SQL encryption, see the Microsoft Knowledge Base article 841695, How to establish and enforce encrypted multiprotocol connections in SQL Server 2000, at https://go.microsoft.com/fwlink/?LinkId=144422. |
Do not set the destination queue (that is, the private queue) privacy level to None on the server that is running the Archiving Server. The privacy level must be set to either Body or Optional. The default setting is Optional.
Do not set the privacy level to Body when the Archiving Server and the Front End Server are installed on the same computer. When the Archiving Server and the Front End Server are installed on the same computer and the privacy level on the destination queue is set to Body, messages are not archived and the server stops running if archiving is running as a critical service.
The Enterprise pool, Standard Edition server or the Proxy Server, if configured for archiving, activates the archiving agent. The archiving agent then checks all outgoing SIP messages on the Office Communications Server to determine whether it should be archived and in what form. This requires the archiving agent to look up the archiving settings for the sender and receiver of the message (set per user). Based on these archiving settings, the archiving agent takes one of the following actions:
- Do not archive.
- Send message for archiving.
When messages are sent for archiving, the archiving agent queues the message to the configured MSMQ. The Archiving service is listening to the destination message of the MSMQ and on receiving this message, it writes it to the designated SQL Server.
Note that in Office Communications Server 2007 R2, the Archiving and CDR agent will not archive a message if it does not receive a SIP response from another client. For example, if client 1 sends a message to client 2, and if the SIP response from client 2 fails to reach client 1 due to a network glitch or a machine shut down, that message will not be archived.