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
- Support was added for MS Exchange Web Services (EWS). Additionally, support for hosted Exchange and Office 365 in SAPERION ELM means that the archive server is now capable of archiving mails stored on hosted MS Exchange servers, including Microsoft Office 365 (Exchange Online).
- Support for RPC over HTTP protocol was added. This protocol is a requirement for communication with MS Exchange 2013 servers, i.e. when EWS or Office 365 are used. (See the previous item.)
- ELM6.0 now includes support for Exchange Server 2013.
- The ELM application platform was changed to x64. This requires a 64-bit operating system.
- Advanced configuration options were added to the Installer wizard for MS Outlook Add-ins. Setting the “Auto-publish” flag configures the Add-In to install MS Outlook forms into the user’s Personal Forms Library.Configuration values entered via command line parameters are displayed here and can be overwritten.
- Forms publishing was made easier for environments without enabled public folders on MS Exchange server(s) using a Visual Basic (VB) script. The VB script can be distributed using GPO or other technologies. The user's default MAPI profile is used.
- LDAP path checking is now supported for multi-domain environments.
- You can now use the Addressbook Manager to add user credentials for LDAP paths in the “Favorites” tab. User credentials help avoid “access denied” issues in LDAP operations running in multi-domain environments.
- The ELM Handler service was integrated into the ELM Manager service.
Installation Package
- To avoid compatibility issues on new Windows versions, the MS SQL 2005 Express Edition database was replaced with MS SQL 2008 R2 Express Edition SP2.
- Windows PowerShell support was added for MS Exchange 2013. Once the Exchange Tools have been installed on the server, the PowerShell scripts are automatically executed by the installation package; you no longer have to prepare the Exchange 2013 server manually for archiving.
Store Access Changes
The following StoreAccess changes were made:
- Store Access version 6.0 has a new interface which reflects the new features. All ELM components must be updated to version 6.0.64 or higher in order to be able to communicate with the Store Access service.
- Log4net was added as the logging engine. The following two predefined appenders are configured by default:> Rolling file for error logs. This appender is enabled by default. The threshold level can be set in the configuration plug-in. The default level is “Error.”> Debug Output for extended debug outputs. By default, this appender is disabled; it can be enabled via the configuration plug-in.
- A “Revision by ELM” note was added for ELM document versions in the SAPERION store.
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 Server UPDATE ELM SET SYSROWID = Replace(NEWID(),'-'")+'000000000000' WHERE SYSROWID IS NULL
- Oracle UPDATE 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.