As an alternative to IM compliance, you
can integrate IM and Presence with a third-party compliance server. With
this solution, IM and Presence only delivers messages to users after it
successfully logs the message to a third-party compliance server. If the
compliance server is unavailable, IM and Presence does not deliver the
message to the recipient.
Third-party IM compliance requires these components:
IM and Presence Service Release 9.0(1) - IM and Presence uses the Event Broker component to send messages to the third-party
Third-party compliance server - You require a third-party
compliance server for each node in the cluster.
IM Client - Supported clients include Cisco clients such as Cisco
Jabber, third-party XMPP clients, and other third-party
clients used in federated networks.
The IM and Presence Service does not provide a secure TLS/SSL connection
between IM and Presence and the third-party compliance server.
To use the third-party compliance solution you must configure
a third-party compliance server for each node in the cluster. IM and Presence passes all messages that are sent to or from any users associated with
a node to the designated third-party compliance server for that node. The
third-party compliance server applies any relevant policy or filtering to the
message, and then passes the message back to IM and Presence. IM and Presence delivers the message to the recipient. Note that you may
potentially experience performance delays in your network because of the volume
of messages that pass between IM and Presence and the third-party
compliance server. If IM and Presence loses its connection to the
third-party server, all IM traffic stops.
The following figure highlights these components
and message flow.
Figure 1. Third-Party IM Compliance