What's new?
Version 3.4.0
Changes:
-
Critical Fix:
Version 3.4.0 uses a unique GUID as part of each log filename to
ensure such files can successfully be created. Previous versions used the
Sametime chat ID as part of each log filename, which could prevent some
chats from being logged if the chat ID would contain illegal characters for use
on the OS filesystem.
-
Fixed a bug with illegal ASCII control chars in chat logs which would
prevent such logs from correctly imported into the chat log database.
-
Fixed a formatting bug with chats consisting of multiple consecutive lines (no
extra empty lines anymore)
-
Fixes a bug where default registry settings would not get written during a new
installation.
-
All .exe and .dll files are now digitally signed by Instant Technologies.
New Features:
-
Chats from Sametime 7.5-based clients are now imported without HTML formatting
by default for easier reading. To revert back to the prior default of importing
all HTML formatting, set IMTEGRITY_STRIPHTML=0 in the NOTES.INI file of
your Domino/Sametime server.
Version 3.3.1
Changes:
-
Version 3.3.1 contains an updated installer which fixes some rare installation
errors on certain Domino 6.x and 7.x server installations.
New Features:
Version 3.3.0
Changes:
-
Version 3.3.0 contains an updated installer which correctly installs Instant
IMtegrity on IBM Lotus Sametime 7.0 servers.
Bugfixes:
New Features:
Version 3.2.1
Changes:
-
Version 3.2.1 contains an updated installer which correctly installs Instant
IMtegrity on existing IBM Lotus Sametime 6.51 servers (with or
without) IBM Lotus Sametime 6.51 Fix Pack 1. See upgrading
for details.
Bugfixes:
New Features:
Version 3.2.0
Bugfixes:
-
Fixed a CSS style sheet error which prevented the chatlog database UI from
correctly displaying. In previous versions, if the Domino web
server's "Make this site accessible to web search site crawlers"
setting was set to "Disabled", errors about a missing style sheet would show on
the domino server console.
-
All time/date data in the chatlog database "imtchatlog.ntf" UI are now
international aware (proper sorting, display, etc.)
-
Fixed a network packet fragmentation bug in the IMtegrity proxy server which
resulted in certain premature disconnects for AIM connections.
-
Fixed a network timing bug in the IMtegrity proxy server which prevented
Trillian or GAIM
clients from successfully logging in.
-
Fixed a problem with incoming AOL chat messages from
GAIM clients causing invalid XML log files which could not be
successfully imported into the chat log database.
New Features:
-
Automatic fault recovery of the IMtegrity windows service: If the core
IMtegrity proxy server terminates abnormally, the windows service will
automatically restart it.
-
Improved runtime error handling: Instead of stopping the entire proxy server
and disconnecting all active AOL sessions in the event of a network protocol
error, only that single affected user session will be disconnected, all
other sessions will continue to run.
-
The IMtegrity installer has been split into 2 modules, the "IMtegrity OS
Component Updates" and the main "IMtegrity Installer". This makes it easier
going forward to distribute fixes and updates.
-
New "imtegrity_chatlog=" notes.ini variable: By default, all chat logs
will only be imported into the database called "imtchatlog.nsf". If you
rename the file name to a different name, importing will stop for
this database. This is done to prevent backup copies etc. of chatlog
databases to continue to actively import chat logs. If you want to use a
different database file name instead of the default "imtchatlog.nsf" for the
main chat log database, you need to set the "imtegrity_chatlog=" variable to
the new database file name. For example: imtegrity_chatlog=chats\june\chatlogs.nsf
-
Experimental support has been added to run the IMtegrity proxy server outside a
firewall on a publicly hosted server. To enable this feature, you need to add a
new key ServerInternalWANAddress to HKEY_LOCAL_MACHINE\SOFTWARE\IMtegrity\Server
and set the REG_SZ value to the server's fully qualified DNS name or IP
address. AOL clients then need to set the AOL login server address to that DNS
name or IP address. This feature has not been extensively tested nor documented
but is known to work. Official support will be added in the next version.
-
All MSI installer files are now digitally signed with Instant Technologie's Authenticode
signature.
Version 3.1.2
Bugfixes:
-
AOL AIM network sessions now get properly closed in case the AOL
connection is being terminated (either due to network errors or if a user logs
on from a different workstation) and users can successfully re-login
again. Previously, if the AOL network connection terminated
unexpectedly, the user would not be able to re-login again without starting and
stopping the proxy server service.
-
The IMtchatlog.ntf and IMtchatlog.nsf database now gets correctly signed with
the Server's ID on Lotus Domino R6.x servers. Previously, the import agent
would not run by default on R6.x servers due to a wrong signature.
-
The IMtchatlog.nsf database's REPLICA ID now gets correctly set on Lotus
Domino R6.x servers.
New Features:
-
Support for multi-homed systems with multiple Network interface cards ("NICs").
You can now specify the IP address the
IMtegrity proxy server will bind to for AOL AIM connections.
Version 3.1.0
Bugfixes:
-
Multi-user conference chats are now correctly marked and identified
as conference chats in the chatlog database
.
-
AOL screen names are now uniquely identified in the chat logs regardless of
their case and formatting. In previous versions, custom formatted AOL screen
names sometimes resulted in duplicate names recorded in the chat logs.
-
Authenticated user names
are now shown in a user-friendly common name format (ie. John
Taylor/IMtegrity). In previous versions, the authenticated user names were
shown in the LDAP canonicalized format (ie CN=John
Taylor/O=IMtegrity)
-
AOL IM messages from remote mobile devices (cell phones, etc.) are
now correctly detected and logged. In previous versions, sometimes the message
text couldn't be correctly detected, resulting in no incoming text being logged
from that remote mobile device user.
New Features:
-
"Hot" upgrade
feature for high-availability servers: Upgrade to the latest version without
server or OS downtime.
-
Inbound disclaimer messages
are now supported. In previous versions, only outbound disclaimer messages were
available.
-
Dynamic configuration changes without the need to restart the server: Most
configuration options can now be changed during runtime without the need
to stop and restart the service(s). If a certain option does require a
service(s) restart, the administrator will be prompted.
-
Log levels
to control output during chat imports: 4 log levels (Nothing, Errors
only, Summary, Details) to specify how much information should be displayed on
the server console/logfile during chat imports.
-
Ability to notify administrator via email
when import errors occur.
-
All imtchatlog.nsf databases now automatically replicate within your domain via
a specially assigned replica ID. In previous versions, an administrator needed
to manually create replica copies of the imtchatlog.nsf database in order to
have them replicated.
-
The design of the imtchatlog.nsf database is
now automatically refreshed at installation time, independently of the "design"
task of the Lotus Domino server.
Enhancements:
-
The IMtegrity configuration tool now paints correctly on Windows XP when
using native visual themes.
-
Empty chat log files are now immediately discarded by the server. In previous
versions, empty chat log files accumulated in the log directory until the
chat log import agent ran.
-
All disclaimer messages are
now displayed underlined
in chat logs to distinguish them from regular chat text messages.
-
Color coding
has been extended to the entire text message, instead of just the name of the
sender.
-
The UI has been updated for both browser and
Lotus Notes access.
Version 3.0.2
Bugfixes:
-
IBM Lotus Sametime XML logs now correctly support intl. characters.
In previous versions, intl. chars were not encoded correctly, resulting in
garbled log text and bad reader fields in the imtchatlog.nsf database (if
usernames included intl. chars)
-
IBM Lotus Sametime logs now correctly format all canonicalized names in the
CN=xxx/OU=xxx/O=xxx format when using an LDAP directory. In previous versions,
if Sametime uses LDAP as the directory, user names were formatted in the
CN=xxx,OU=xxx,O=xxx format (commands instead of slashes), resulting in bad
readerfields in the imtchatlog.nsf database and incorrect abbreviated name
formatting in the UI.
New Features:
-
Directory authentication now supports mapping of AOL screen names to corporate
authenticated user names via the
client's network address (IP/DNS name).
-
Ability to start/stop
the IBM Lotus Sametime Chat Logging service directly from the configuration
tool.
-
Integrated F1 online help for IMtegrity Configuration tool.
|