Note Regarding Versions
SAPERION ELM Server Exchange Edition Version 6.1 is compatible with both SAPERION ECM versions 7.5.0 and 7.5.1. You do not need to update your 7.5.0 version of SAPERION to be able to use ELM 6.1.
New Features and Improvements
- The SAPERION ELM MailApp was implemented to allow users to work with email and archived emails in the MS Exchange OWA 2013 Web Application. Installers and the configuration tool were updated to support the new technology introduced in the MS Exchange 2013 server.
- MailAppInstaller2013 (formerly known as OWAInstaller2013) was introduced to manage the deployment of SAPERION ELM MailApp on MS Exchange 2013.The following operations are possible:> Installing the MailApp on MS Exchange Server 2013> Configuring and enabling the MailApp on MS Exchange Server 2013 on a global level> Enabling/Disabling ELM MailApp in user mailboxes by the administrators. User mailboxes can be filtered using Distribution Groups defined on the MS Exchange Server.
- Support for Macintosh mail clients was updated to cooperate with ELM 6, in the form of an add-in. Supported mail clients are:> Entourage> Outlook:mac
- Archive Web has a new look, using SAPERION graphics and color schemes.
- The database model has been extended to support Unicode characters in the following:> Folder selection in PST import settings> Custom scheduler scripts used in scheduler jobs.
- Improved MS Exchange distribution group handling in Addressbook Manager when EWS mode is used. Users included in this type of group are synchronized automatically in defined time periods, similar to groups defined in Active Directory.
- The notification mechanism used to inform users when they do not have the necessary permissions to perform Archive, Delete or Restore operations (defined in the Outlook addin permissions dialog in Enterprise manager) has been improved.
- Sub-group processing by normal (archive) jobs was not working properly on ORACLE database servers versions 9 and 10. This has been fixed.
Configuration Tools
- Forms Installer was extended to support 32-bit MS Outlook installations.
Store Access Changes
- Classic Connector proxy selection in the configuration plugin was extended to include supported versions of the SAPERION Java Core servers in the proxy description.
Installers
- A new, combined, StoreAccess installation package was created, including both x86 and x64 installers. This package allows users to choose between x86 or x64 StoreAccess installers within a single executable.
Known Issues
OWA extensions If an attachment larger than 15 MB is retrieved using the OWA extension, IIS may eventually run out of kernel memory resources.IIS requires a continuous fragment of kernel memory to transfer data. If the memory gets fragmented, IIS is not able to transfer large amounts of data. Even when the fragmentation is caused by third-party software, it affects the OWA extension functionality.We provide a patch as a workaround if this exact case is detected.
Gatherer Due to security changes, the HTTP channels used for the Gatherer-PST import server communication must be securable. An SSL certificate must be assigned to the web site on each computer (both client and server).The TCP channel can be used for communication, which does not require an SSL certificate. Installing the 5.1 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, which can include deleted documents. When deleted documents are filtered out, the final result may 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.
MAPI Profile Handling Due to a change in MAPI profile handling, only one MAPI profile is created per Exchange Server by default. Installing Outlook is mandatory (2003, 2007 or 2010 – only 64-bit versions). If the mailboxes can’t be opened in Enterprise Manager, it is necessary to adjust the MAPI profiles manually using Outlook.
Single Profile per Exchange Server If the single profile per Exchange Server does not allow opening additional mailboxes, the application must be switched to use one profile per mailbox. To do this, the “profile guard” must be turned off in the guard service.
Connecting to Exchange To connect to Exchange 2007 or Exchange 2010, you must use Outlook 2007 or higher. This ensures that the “Encrypt data between Microsoft Outlook and Microsoft Exchange” profile setting is set by default.
MAPI Configuration 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
Guard Service The Guard service should not be used in version 6.0, however it is enabled by default. 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.
Update Notes
- When updating to version 6.0, make sure that .NET 2.0 SP2 and .NET 4.0 are installed.
- 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 ServerUPDATE ELM SET SYSROWID = Replace(NEWID(),'-'")+'000000000000' WHERE SYSROWID IS NULL
- OracleUPDATE ELM SET SYSROWID = SYSGUID() || '000000000000' WHERE
SYSROWID IS NULLNote: Depending on the number of records in your database, the SQL command may need several minutes to run.
- If multiple ELM products are present on the same server, or use the same components in a distributed architecture, all products have to be updated to the same version number (version 6.0 and higher).
- If you are installing ELM on a computer with Microsoft SharePoint installed (any version), the ELM web applications will be installed to different ports (9981 for web services, 7781 for ArchiveWeb). Remember to include the port number when you configure access to the archive and retrieve servers.
- If you are installing ELM on a computer with a BlackBerry server installed (any version), note that ELM requires Outlook, while BlackBerry requires Exchange MAPI. These components can’t coexist on the same computer. Please contact SAPERION support regarding update possibilities.
- After installation, ensure that the MCSWS handler mapping is configured as follows:> Apply to ‘*.*’> Apply to files and folders.> On IIS 7, the application pool must be set to “Classic” Managed Pipeline Mode.More details are included in the documentation.
- On IIS 7: make sure that the ISAPI and CGI restrictions allow ASP .NET v4 for both x86 and x64 platforms.
Update from version 5.x
A direct update to 6.0 is possible once all software prerequisites are fulfilled.
Update from Older Versions
Please see the ELM v5.5 Release Notes (SAPERION v7.1) for information on how to update ELM from earlier versions.