SAPERION ELM Server Exchange Edition Version

5.5 Release Notes

Copyright © 2016 Lexmark. All rights reserved.

Lexmark is a trademark of Lexmark International, Inc., registered in the U.S. and/or other countries. All other trademarksare the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in anyform without the prior written permission of Lexmark.

Table of Contents

1 Important ............................................................................................................. 1

2 New Features and Improvements ...................................................................... 1

3 Known Issues ...................................................................................................... 2

4 Update Notes ...................................................................................................... 3

4.1 Important Note ................................................................................................... 3

4.2 Updating from v 5.1 ............................................................................................ 3

4.3 Updating from 4.x .............................................................................................. 3

4.4 Updating from 3.7 or higher ............................................................................. 4

4.5 Updating from 3.6000 and earlier ..................................................................... 5

1

SAPERION ELM Server Exchange

Edition Version 5.5 Release Notes

1 Important

+ Before planning an update, please contact SAPERION Professional Services.

! Due to licensing changes, a new SAPERION key is needed with version 5.5. The new key

must be requested from SAPERION Sales Support.

+ Version 5.5 only works with SAPERION version 7.1.3.66779 and higher.

+ Before upgrading ELM or the SaStore, make sure that all administrative tools, especially the Services

window and MMC console, are closed.

+ We recommend stopping all ELM Services before upgrading.

+ You must have a Java Core Server installed in order for ELM version 5.5 to work.

+ Make sure that you have both .NET 2.0 SP2 and .NET 4.0 installed.

+ JRE 1.7 or higher must also be installed.

+ Direct update is only possible from ELM v5.1. Afterwards the Outlook forms must be published

again.

+ If more SAPERION ELM products are present on the same server, or use the same components in

a distributed architecture, all products have to be updated to version 5.5.

+ If you are installing ELM on a computer with BlackBerry server installed (any version), please

note that ELM requires Outlook, while BlackBerry requires Exchange MAPI. These components

can't coexist on the same computer. Please contact SAPERION Professional Services for update

possibilities.

+ After the installation, please ensure that the MCSWS handler mapping is configured as follows (for

more details, please see the documentation):

Apply to '*.*'

Apply to files and folders

On IIS 7 the application pool is set to "Classic" Managed Pipeline Mode

+ On IIS 7: make sure that the ISAPI and CGI Restrictions allow for ASP .NET v4, for both the x86

and x64 platforms.

2 New Features and Improvements

+ Performance improvement

ELM 5.5 was optimized to use a direct Saperion Store access, which has substantially improved the

archiving speed. The Outlook AddIn was optimized for offline synchronisation so the time needed

for syncing has been shortened as well.

3 Known Issues

2

+ Virtual Archive Mailbox

Enables you to access your email archive regardless whether you are online or offline. Just browse

into your archive mailbox as you would in the normal mailbox access from Outlook. VAM is fully

integrated into Outlook and accessible as an additional mailbox.

+ Rebranding

There has been a complete rebranding of the product to use SAPERION naming conventions.

+ Licensing model

The licensing model has been changed to the standard SAPERION Licensing. Full support of the

new model is available with the version 7.1.3.66779 SAPERION Server.

+ Databases

SAPERION ELM Server Exchange Edition v5.5 now supports the following databases:

Microsoft SQL Server 2005 - 2012

Oracle 9.0 and higher (up to 11gR1)

Installing and configuring the software with an Oracle database as the back-end is now very simple

and straightforward.

+ .NET Framework

The minimum .NET Framework requirements for this version are .NET 2.0 SP2 and .NET 4.0.

3 Known Issues

+ OWA extensions: If a larger attachment (> 15 MB) is retrieved using the OWA extension, IIS could

run out of kernel memory resources after a long run. IIS requires a continuous fragment of kernel

memory to transfer data. If the memory is fragmented, IIS is not able to transfer large amounts

of data. Please note that this fragmentation is caused by other 3rd party software, but affects the

OWA extension functionality. A workaround in the form of a patch is available for customers if this

exact case is detected.

+ Gatherer: Due to security changes, the HTTP channels used for gatherer-PST import server

communication must be securable. This means that an SSL certificate must be assigned to the web

site on each computer, client and server. Since this is a very strong requirement, a TCP channel can

be used for communication. This doesn't require an SSL certificate. Installing the 5.5 gatherer setup

over an existing installation automatically changes the protocol from HTTP to TCP.

+ ELM Search: The hit limit configuration key limits the total number of search results (including

deleted documents). However if the deleted documents are filtered out, the final result might

contain fewer results than the defined hit limit.

+ Enterprise Manager: Post-processing statistics might throw a database timeout exception. There is

no workaround for this problem yet.

+ Due to a change in MAPI profile handling, by default only 1 MAPI profile is created per Exchange

Server. It is mandatory to install Outlook (2003, 2007 or 2010 - 32-bit versions only). If the mailboxes

can't be opened in ELM Enterprise Manager, it is necessary to adjust the MAPI profiles manually

using Outlook.

+ If for some reason the single profile per Exchange Server does not allow opening additional

mailboxes, it is necessary to switch the application to use one profile per mailbox. In this case, the

"profile guard" must be turned off in the guard service.

4.1 Important Note

3

+ To connect to Exchange 2007 or Exchange 2010, it is necessary to use at least Outlook 2007. This will

ensure that the "Encrypt data between Microsoft Outlook and Microsoft Exchange" profile setting

is used by default.

+ If the PST import is not able to configure the MAPI profile (MAPI_E_UNCONFIGURED or

similar), we recommend setting the "DS Server" or "Closest GC" registry key for Outlook (http://

support.microsoft.com/kb/319206).

+ The Guard service should not be used in version 5.5, but it is enabled by default. Therefore we

recommend turning off the "profile guard" feature, or at least setting the maximum number of

profiles to a value higher than the number of mailboxes synchronized in the address book.

+ It is currently not possible to apply one ACL to all e-mails in SAPERION ELM.

i If more ELM products are present on the same server or use the same components in a distributed

architecture, all must to be updated to version 5.5 or higher.

4 Update Notes

4.1 Important Note

After updating to 5.5 (or higher), make sure that your ELM DDC contains a SYSROWID column with a

value. Without this column, there may be problems when reading/writing using the SAPERION Classic

Connector.

Use the SQL statement appropriate for your server:

+ SQL Server

UPDATE ELM SET SYSROWID = Replace(NEWID(),'-'")+'000000000000' WHERE SYSROWID IS

NULL

+ Oracle

UPDATE ELM SET SYSROWID = SYSGUID() || '000000000000' WHERE SYSROWID IS NULL

i Depending on the number of records in your database, the SQL command may need several

minutes to run.

4.2 Updating from v 5.1

A direct update to 5.5 is possible after all software prerequisites are fulfilled.

4.3 Updating from 4.x

When updating from 4.x, ELM must be updated to version 5.1 first. A direct update to 5.1 is possible

without additional requirements.

4 Update Notes

4

There are changes in the database model: it is necessary to calculate in a small downtime. Depending

on the number of archived folders, the database update can take up to 1 hour (The number of folders

can be calculated from the database table EXCHANGEPAMFOLDERS).

Please note that the services should not be started until the database is fully updated. If you have

additional retrieve servers connecting to the updated database, it is possible to use them during the

update; however some features might not be available, or the retrieve might be slowed down because

of the heavy load on the database server. If possible, stop the retrieve servers as well during update.

It is necessary to stop all PST import servers in the organization prior to update. The update sequence

should be the following, for one archive node:

1. Update the archive server to ELM version 5.1.

2. Update the database objects.

3. Start up ELM services on the archive server.

4. Update additional retrieve servers to ELM version 5.1.

5. Do not update the database objects on the retrieve servers.

6. Update the PST import servers to ELM version 5.1

7. Do not update the database objects on the PST Import servers.

8. An Outlook Add-In update is not necessary.

9. An update of Outlook forms is not necessary.

10. We recommend updating the gatherer installations with Gatherer client version 5.1.

4.4 Updating from 3.7 or higher

i A direct upgrade to version 5.1 is not possible; ELM must be updated to version 3.9 first.

The installation of version 5.1 uninstalls the previous setups, but it preserves all the configuration

information.

If the ELM setup contains HSM, it will be installed separately, and will be listed as a new product in

add/remove programs. If you have user ELM Search in your 3.x setup, this will be uninstalled. You can

continue to use the ELM Search engine (also referred to as “legacy fulltext”), however you have to select

the correct fulltext engine at installation. Please refer to the documentation regarding ELM Search engine

configuration, as there are some manual tasks required in order to use this engine.

If you have used HDD HSM stores in the 3.x setup, the HSM store service will be re-created again;

however, it is possible that the service startup type will be reset to Manual during installation. After

installation, you must change the service startup type to Automatic. We recommend updating Outlook

forms after the upgrade. OWA extensions do not need to be updated on the Exchange Servers.

Older Gatherer applications are not compatible with 5.1. In order to use the gatherer functionality, all

the gatherer installations should be updated to 5.1. If multiple PST import servers are installed in the

4.5 Updating from 3.6000 and earlier

5

organization, these should be stopped during the update of the archive server. All PST import servers

must be updated to the same version as the Archive Server.

4.5 Updating from 3.6000 and earlier

We recommend updating to version 3.9006 before upgrading to version 4.x or 5.1.

i A direct upgrade to version 5.1 is not possible; ELM must be updated to version 3.9 first.