Instant IMtegrity Product Documentation

Deploying IMtegrity

Before you install IMtegrity, you should have an understanding of the various components and the design and configuration decisions you will need to make. This document helps you plan for and deploy IMtegrity.

IMtegrity 3.x consists of 2 major components:

  • IMtegrity Chat Logging Service for IBM Lotus Sametime
  • IMtegrity Proxy Server service for AOL AIM
IMtegrity Chat Logging Service for IBM Lotus Sametime

The Sametime chat logging module is implemented via the native Sametime SPI (Service Provider Interface) and is installed as the "stchatlog.dll" file in your Sametime server's program directory. The IMtegrity installer automatically deploys this file and configures the Sametime server to correctly use it.

To effectively log all IBM Lotus Sametime chats, you need to install IMtegrity on every Sametime server in your organization, otherwise only chats from users which are connected to a Sametime server running the IMtegrity software will be logged.
 
Note: You need to purchase a separate IMtegrity licence for every Sametime server you plan on installing the IMtegrity software on.
 
 
IMtegrity Proxy Server service for AOL AIM
 
The IMtegrity Proxy Server is implemented as a native Windows service, acting as a proxy between all AOL AIM clients and the public AOL IM network. The IMtegrity installer automatically registers, configures and starts the IMtegrity Proxy Server service with default values.
 
Note: If you want to log native Sametime chat messages only, you can stop and remove the IMtegrity Proxy Server service (either directly using the Windows Control panel or via the IMtegrity Configuration tool's "Service" tab). However, the service only consumes very little system resources (~8MB of memory and virtually no CPU cycles) when in idle mode.
 
Since the IMtegrity proxy server needs to establish a TCPIP connection to the internet for AOL AIM connections, you need to pay special attention to firewall and proxy server configurations.
 
If you have multiple Sametime servers but don't expect a lot of users to use the AOL AIM clients, you might want to run the IMtegrity Proxy Server on just one single Sametime server, and stop and remove the IMtegrity Proxy Server NT service on all other Sametime servers, or you might want to run it on every Sametime server for load distribution and performance reasons.
 
If you have lots of AOL AIM users, it is recommended to assign different servers running the IMtegrity Proxy Server to different groups of AOL AIM users.
 
AOL AIM Rate Limits per single IP address
 
The public AOL AIM servers impose a standard rate limitation that restrict the number of simultaneous AIM sessions that a given IP address can establish. When your internal users connect to the AIM service through the IMtegrity Proxy Server, the AOL AIM service will treat these connections as originating from the same IP address. It is not known what maximum rate number of simultaneous sessions is.
 
Note: If your users previously accessed the public AOL IM network from behind your firewall and not reached/exceeded the rate limit in the past, it is unlikely that they will hit the limit because of IMtegrity. All sessions will appear to come from your company's firewall, regardless whether the IMtegrity Proxy Server runs behind that firewall or not. The IMtegrity proxy server itself is entirely transparent to the AOL servers.
 
 
For IBM Lotus Sametime Connect Client and AOL Instant Messenger Client configurations, see  Client configuration.