IBM Email Manager 4.0.2 Fix Pack Readme: 4.0.2.6-EM-FP006

© Copyright IBM Corporation 2010. All Rights Reserved.

Readme file for: IBM Email Manager
Product/Component Release: 4.0.2
Update Name: Fix Pack 6
Fix ID: 4.0.2.6-EM-FP006
Publication date: 24 February 2010
Last modified date:

Contents:

About this fix pack:
 Download location
 Required products needed before installation
 New in this fix pack
 Known Issues

Installation information:
  Prior to installation
  Installing
  Uninstalling if necessary

List of fixes
Additional Information
Copyright and trademark information
Document change history


Download location:

Download Email Manager Version 4.0.2 Fix Pack 6 (4.0.2.6-EM-FP006) from the following location:
Fix Central site: http://www.ibm.com/support/fixcentral  New!

Select Product Group: Information Management
Select Product: FileNet Email Manager

 

Below is a list of products/components names, platforms, and file name(s) that apply to this readme file.

Product/Component Name:

Platform:

File Name:

UFI Server

Windows

update_ufi_402.006.244.msp

EM Server

Windows

update_em_server_402.006.244.msp

EM Shortcut Client

Windows

update_em_shortcut_client_402.006.244.msp



Required products needed before installation:

Product/Component Name:

Platform:

Email Manager 4.0.2 GA and Fix Pack 1

Windows

 

 

New in this fix pack:

 

As of EM 4.0.2 Patch 6 (4.0.2.6-EM-FP006) the following components are now supported:

 

·         Oracle 11g (support only for Oracle 10g Client connecting to Oracle 11g Server)

·         Content Engine (P8CE) 4.5.1

·         Records Manager 4.5.1

 

As of EM 4.0.2 Patch 4 (4.0.2.4-EM-FP004) the following component is now supported (for Exchange and Lotus Notes connectors only):

 

·         Windows 2008

 

As of EM 4.0.2 Patch 3 (4.0.2.3-EM-FP003) the following components are now supported:

 

·         IBM Lotus Notes/Domino 8.5

·         IBM FileNet P8 4.5

·         Microsoft SQL Server 2008

 

 

Known issues:

 

Defect No.

Description

784412

Creating a large number of active collectors or task routes can cause the Email Manager server to run out of available threads and stop processing emails.  IBM recommends using one collector per task route and configuring no more than 8 active task routes per Email Manager server.  This recommendation does not impact the number of locations that can be monitored as each collector can contain multiple monitored locations and the task route architecture can allow for multiple branches within a single task route.

784406

Email Manager does not support the use of a separate database for storing duplicate hash keys.  Duplicate hash keys must be stored in the same database as the Email Manager configuration data.

760083

Performance counters for Exchange emails are incorrect.

 

 

Installation information:

 

Prior to installation:
 

1.      Back up the EM database

2.      Back up the following EM registry keys:

·         HKLM\SOFTWARE\IBM\EMRC\* (all keys)

·         HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\ibm.ctms.* (all keys that begin with “ibm.ctms.”)

3.      Back up the following EM xml configuration files:

·         On the EM Server, back up all xml files in UFI_4.0.2 folder.  These may include but are not limited to: UFIConfig.xml, P8Config.xml, DominoConnector.xml

·         Back up all xml files for the EM Client on client machines. These may include but are not limited to: P8WSConnector.xml, ClientGUI.xml, Catalog.xml, ClientGUI.lang.en-US.xml

 

Installing this patch:
  

1.      Extract the fix pack zipped file to the local file system.

2.       Stop all UFI, Email Manager and Records Crawler services (if installed):

·         UFI Task Routing Engine

·         UFI File System Connector

·         UFI Filesystem Repository Connector

·         UFI FileNet P8 Content Engine 3.x Connector

·         UFI FileNet P8 Content Engine 4.x Connector

·         UFI Microsoft Exchange Connector

·         UFI PST Connector

·         UFI GroupWise Connector

·         UFI Lotus Notes Domino Connector

·         UFI Services Components

·         UFI FileNet IS Connector

·         UFI Utility Service

3.      Stop any other applications that are running, including the Configuration Manager.

4.      In the directory where the zip file was extracted access the folder "UFI Server" and run:  update_ufi_402.006.244.msp

·         Note: 4.0.2.6-EM-FP006 and 4.0.2.6-RC-FP006 contain the same update for “UFI Server”.  If both EM and RC are installed on the same system, this update only needs to be run once.

5.      Upgrade Options (Note: “EM Server” update is available in the 4.0.2.6-EM-FP006 fix pack, while “RC Server” is included in the 4.0.2.6-RC-FP006 fix pack.  If both EM and RC are installed on the same system, upgrade UFI Server first, and then the specific RC Server and EM Server upgrades)

·         To upgrade Email Manager - In the directory where the zip file was extracted access the folder "EM Server" and run:  update_em_server_402.006.244.msp

6.      Restart the server

7.      Start the UFI Task Routing Engine service which will start all other required services


    Installing the Email Manager Shortcut Client patch:

 

1.      On any system with the Email Manager Shortcut Client installed, run: update_em_shortcut_client_402.006.244.msp

2.      Copy back onto the client systems the client xml files that you previously backed up.

     

   Installing the Email Manager Shortcut Client silently:

 

There are two components of the Email Manager Shortcut Client: The Server Component and the Client Component.

 

The Server Component should only be installed on the Email Manager server after UFI and Email Manager have been installed.  Do not install the Server Component on client machines.

 

The Client Component should be installed on each client machine.

 

Specific ADDLOCAL parameters are used to customize the installation:

 

Component Required

ADDLOCAL Parameter

Outlook Server Component

OutlookServ

Lotus Notes Server Component

LotusNotesServ

Outlook Client Component

Outlook

Lotus Notes Client Component

LotusNotesManual

Lotus Notes Client Component Advanced Shortcut with P8 4.X Support

P84X

Lotus Notes Client Component Advanced Shortcut with P8 3.X Support

P83X

 

Installing the Server Component silently:

 

On the Email Manager server, run the “IBM Email Manager Client.msi” installer from the GA media with the specific ADDLOCAL parameters indicated in the table above.  Standard Msiexec options may be used. 

 

Examples:

Microsoft Outlook Environment:

 

msiexec /i "\\Server\EmailManagerInstall\EM Shortcut Client\IBM Email Manager Client.msi" ADDLOCAL=OutlookServ /qn

 

Lotus Notes Environment:

 

msiexec /i "\\Server\EmailManagerInstall\EM Shortcut Client\IBM Email Manager Client.msi" ADDLOCAL=LotusNotesServ /qn

 

Patching the Server Component silently:

 

On the Email Manager server, run the “update_em_shortcut_client_402.xxx.xxx.exe” (patch 1 and 2) or the “update_em_shortcut_client_402.xxx.xxx.msp” (patch 3 and later) installer. 

 

Examples:

Patch 1 and 2:

 

"\\Server\EM-4.0.2-001\EM Shortcut Client\update_em_shortcut_client_402.001.169.exe" /S /v /qn

 

Patch 3 and later:

 

msiexec /update "\\Server\EM-4.0.2-003\Patch\EM Shortcut Client\update_em_shortcut_client_402.003.199.msp" /quiet /norestart

 

Installing the Client Component silently:

 

On the client machines, run the “IBM Email Manager Client.msi” installer from the GA media with the specific ADDLOCAL parameters indicated in the table above.  Standard Msiexec options may be used. 

 

Examples:

Microsoft Outlook Environment:

 

msiexec /i "\\Server\EM Shortcut Client\IBM Email Manager Client.msi" ADDLOCAL=Outlook /qn

 

Lotus Notes Environment with P8 4.x:

 

msiexec /i "\\Server\EM Shortcut Client\IBM Email Manager Client.msi" ADDLOCAL=LotusNotesManual,P84X /qn

 

Lotus Notes Environment with P8 3.x:

 

msiexec /i "\\Server\EM Shortcut Client\IBM Email Manager Client.msi" ADDLOCAL=LotusNotesManual,P83X /qn

 

Patching the Client Component silently:

 

On the client machines, run the “update_em_shortcut_client_402.xxx.xxx.exe” (patch 1 and 2) or the “update_em_shortcut_client_402.xxx.xxx.msp” (patch 3 and later) installer. 

 

Examples:

Patch 1 and 2:

 

"\\Server\EM-4.0.2-001\EM Shortcut Client\update_em_shortcut_client_402.001.169.exe" /S /v /qn

 

Patch 3 and later:

 

msiexec /update "\\Server\EM-4.0.2-003\Patch\EM Shortcut Client\update_em_shortcut_client_402.003.199.msp" /quiet /norestart

 

   Uninstalling this patch:
  

1.      In Add/Remove Programs, remove IBM Email Manager

2.      In Add/Remove Programs, remove IBM UFI

3.      Restore the EM database from backup

4.      Install IBM UFI from Email Manager GA media

5.      Install IBM Email Manager from Email Manager GA media

6.      Install IBM UFI Patch 1

7.      Install IBM Email Manager Patch 1

8.      Restore EM xml configuration files to EM installation directory

9.      Restore EM registry entries from backup

10.  Install desired patch



List of fixes:

 

APAR No.

Defect No.

Severity

Abstract

 PJ37409 

ecmdb00864740

4

LOTUS PANIC ERRORS ARE NOT DETECTED OR HANDLED GRACEFULLY BY EMAIL MANAGER

PJ37406 

ecmdb00864724

4

ADDED AN ADDITIONAL COMMAND LINE OPTION INDICATING THE TYPE OF TASK GROUPWISE CHILD PROCESSES ARE PERFORMING

 PJ37407 

ecmdb00864722

3

ADDED A NEW GROUPWISE CONNECTOR LOG FILE

 PJ37408 

ecmdb00864717

3

GROUPWISE COLLECTOR STOPS RUNNING AT THE END OF A COLLECTION INTERVAL AND DOES NOT SUBSEQUENTLY RUN WHEN NEXT SCHEDULED

PJ37405

ecmdb00851663

2

LOTUS CONNECTOR DOES NOT RECOGNIZE MIME ATTACHMENTS IN EASYLINK FAXCOURIER MESSAGES

PJ37343

ecmdb00857269

2

EMAILS INTERMITTENTLY NOT PROCESSED, MAPI_E_NOT_FOUND ERROR IN THE EXCHANGE SERVICE LOG

PJ36659

ecmdb00774777

4

AUDIT LOG TASK ERROR IF INVALID VALUES FOR DELIMITER AND MUTLIVALUE

  PJ37382

ecmdb00848674

3

CHANGES  NOT SAVED TO THE "REPLACEMENT STRING" WHEN EDITING REGULAR EXPRESSIONS FOR FOLDERS

PJ37118

ecmdb00854047

3

BACKPORT OF ISSUE FOUND IN ICC - INCORRECTLY VALIDATING WINDOWS EVENT LOG NAMES

PJ37342

ecmdb00857194

3

UFI SERVICES COMPONENTS DOESN'T START

PJ36912

ecmdb00844931

3

IMPORT OF TASK ROUTES FAILS WHEN THE EXPORTED TASK ROUTE HAS

AUDIT LOGGING ENABLED

PJ37374

ecmdb00843817

3

EMAILS PROCESS VERY SLOWLY AT EXACTLY 30 SECONDS PER EMAIL

PJ36526

ecmdb00829825

3

ERROR DUE TO A NULL POINTER FOR A TASK ROUTE METHOD

 

 

Additional Information:

 

As of EM 4.0.2 Patch 6 (4.0.2.6-EM-FP006)

 

Items

Descriptions

EMAILS PROCESS VERY SLOWLY AT EXACTLY 30 SECONDS PER EMAIL

By default, Exchange Connector will retry for 30 seconds (30,000 milliseconds) if it cannot find the specified email in monitoring location for processing. This default value can be overridden by setting the registry key KEY_LOCAL_MACHINE\SOFTWARE\IBM\EMRC\4.0\ExchangeConnector\KeepRetryingTimeout to the desired value, in milliseconds.

 

To create the registry key to overwrite the default retry time-out for Exchange Connector:

 

1. Start Registry Editor and go to the following sub-key:

 

   HKEY_LOCAL_MACHINE\SOFTWARE\IBM\EMRC\4.0

 

2. On the Edit menu, click New Key.

 

3. Enter the following values:

 

   Key Name: ExchangeConnector

   Class: REG_SZ

 

4. Go to the following sub-key:

 

   HKEY_LOCAL_MACHINE\SOFTWARE\IBM\EMRC\4.0\ExchangeConnector

 

5. On the Edit menu, click New DWORD Value.

 

6. Enter the following values:

 

   Name: KeepRetryingTimeout

   Type: REG_DWORD

   Data: milliseconds

GROUPWISE COLLECTOR STOPS RUNNING AT THE END OF A COLLECTION INTERVAL AND DOES NOT SUBSEQUENTLY RUN WHEN NEXT SCHEDULED

A time-out mechanism has been added to the GroupWise Connector to terminate GroupWise Connector child processes that do not stop in a timely manner. By default, this process will terminate GroupWise Collector processes that continue to run 5 minutes after receiving a signal to stop, and GroupWise Create File processes, Extract Attachment processes and Post-processing processes that run for more than 5 minutes.

The default timeout period of 5 minutes (300000 Ms) can be overridden by setting the system environment variable IBM_CTMS_GW_TIMEOUT to the required timeout interval in milliseconds. We do not recommend a value
smaller than 30 seconds (30000 Ms) as this may cause timeouts when rendering large email messages. It may be necessary to increase the default timeout period if you encounter timeout errors during normal processing.

ADDED AN ADDITIONAL COMMAND LINE OPTION INDICATING THE TYPE OF TASK GROUPWISE CHILD PROCESSES ARE PERFORMING

An additional command line option is now passed to GroupWise child processes to indicate the type of child process.  The command line can be displayed in Process Explorer for troubleshooting.

ADDED A NEW GROUPWISE CONNECTOR LOG FILE

A new GroupWise Connector log file has been added. In addition to writing to the Windows Event logs, a daily log file is created in the temporary folder specified in the GroupWise Connector configuration. This log file records all messages originating from the main GroupWise Connector process. These log messages have been expanded and improved to record details of service startup and shutdown, schedule configuration, beginning and end of a scheduled collection interval, and creation and termination of child processes (including process Ids for cross-referencing with Process Explorer and Windows Task Manager). This log will also record when collectors or tasks are stopped after a
time-out period. The GroupWise Connector child processes that actually perform collection and document oriented tasks will continue to write to the Windows Event logs only.

 

 

As of EM 4.0.2 Patch 4 (4.0.2.4-EM-FP004)

 

Items

Descriptions

SUPPORT FOR WINDOWS 2008

Edit the registry using the following steps:
1. Locate and navigate to the following registry
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
2. If a “Configurations Flags” value exists, right-click Configuration Flags, and then click Modify. If the    

    Configuration Flags value does not exist, create a new DWORD (32 bit) value called “Configuration Flags” and 

    then click Modify.
3. Type 10000, and then click OK.

FILES DO NOT INGEST IF THE VALUE SET FOR PROPERTY IS NOT FOUND IN P8 CHOICE LIST

To change functionality such that files are added successfully to P8 even when a property mapped to a P8 choice list contains a value not found in the list, add the following entry to the p8Config.xml file (typically located in C:\Program Files\IBM\UFI_4.0.2):

 
<p8Config>
...
<ignore_invalid_property_value value="true"/>
...
</p8Config>

Audit Log now includes column headers for greater readability

Note: Headers in audit log only available if the option “One log per context” is enabled in Configuration Manage

Registry Key to Enable Use of Alternative Lotus API during address book lookup

 

In some instances, the address book lookup function in Email Manager encounters a performance limitation in Lotus Notes. To change the Notes API call used by Email Manager for this function, add a registry entry to:

 

Path:

HKLM\Software\IBM\EMRC\4.0\ServiceDeclarations2\ibm.ctms.lotusconnector

 

Name:

AddressBookLookupMode

 

Type:

DWORD

 

Values:

0 = NotesView.GetAllEntriesByKey           (existing behaviour, default if no value set)

1 = NotesView.GetAllDocumentsByKey    (alternative method of looking up addresses to work-around Notes performance issue)

GROUPWISE EMAILS THAT ARE FORWARDED AS ATTACHMENTS ARE NOT CAPTURED BY EM AS ATTACHMENTS OR OTHERWISE.

Description

 

The GroupWise connector extract attachments task has been enhanced to provide optional support for processing attached messages.  This includes:

 

1. - Extracting attachments from attached messages.

2. - Rendering attached messages to .fngwEntity (xml) format and/or RFC822/MIME text. This functionality is shared with the existing create file task and offers the same options.

 

These options are enabled using specific registry keys.  If the registry keys are not set, the behaviour of the extract attachments task is unchanged from the previous version.

 

Registry Keys

 

All new registry keys for the extract attachments enhancement are configured in:

 

HKLM\Software\IBM\EMRC\4.0\Settings\ibm.ctms.groupwise.Connector\ibm.ctms.groupwise.extractAttachments

 

The extract attachments task recognises the following keys:

 

Key:                ExtractEmbeddedAttachments

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, the extract attachments task recursively scans attached messages for file attachments and extracts them.  Note that the extract attachments task makes no distinction between attachments of the original message and attachments of attached messages.

 

Key:                ExtractEmbeddedMessages

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, the extract attachments task extracts attached messages and uses the create file task functionality to create one or more files that represent the attached message.  GroupWise does not have a native file format for email messages, so messages are rendered in either .fngwEntity (xml) and/or RFC822/MIME text formats. Attached messages within attached messages are also extracted. 

 

Either the ExtractEmbeddedMsgToXML and/or the ExtractEmbeddedMsgToText registry entries must also be set for this option to have any effect.

 

Key:                ExtractEmbeddedMsgToXML

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, attached messages are rendered in .fngwEntity (xml) format.  ExtractEmbeddedMessages must also be enabled to use this option.

 

Key:                EmbeddedMsgIncludeAttachments

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, file attachments contained within attached messages will be rendered within the .fngwEntity (xml) file using Base64 encoding.  ExtractEmbeddedMsgToXML must also be set.

 

Key:                EmbeddedMsgIncludeEmbedded

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, attached messages within attached messages will be rendered as nested elements within the .fngwEntity (xml) file.  ExtractEmbeddedMsgToXML must also be set.

 

Key:                ExtractEmbeddedMsgToText

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

If enabled, attached messages are rendered in  RFC822/MIME text format.  ExtractEmbeddedMessages must also be enabled to use this option.

 

Key:                EmbeddedMsgTextExtension

Type:               STRING

Default:           .fngwText

 

If set, specifies the file extension for attached messages rendered in  RFC822/MIME text format.  ExtractEmbeddedMsgToText must also be enabled for this option to have any effect.

 

Key:                MetadataHierarchy

Type:               DWORD

Values:            1 - enabled, 0 - disabled

Default:           Disabled

 

This setting controls how containment relationships are represented in the metadata.  This option only has an effect if both ExtractEmbeddedAttachments and ExtractEmbeddedMessages are enabled.  If enabled, attachments and attached messages are linked to the message that contains them and multiple levels of attached messages are represented as a hierarchy.  If not enabled, the hierarchy is flattened and all attachments and attached messages are linked directly to the main message.

Disable folder references on any Notes databases that have them enabled.  This can be achieved:

- From the Domino Administrator by running the convert task on the server using the -m switch

- By creating a LotusScript agents that sets the NotesDatabase.FolderReferencesEnabled property to false

The server commands would be:

 

tell router quit

load convert -m <mailbox path>

load convert -m <mailbox path>

load router

 

The -m switch toggles folder references on and off, so you will only want to run it against databases that have folder references enabled.

 

You can use the -f switch to provide a list of mailboxes from a text file.

 

 

The other option is to create a LotusScript or Java agent.  The code would be something like (in LotusScript):

 

 

Sub Initialize

 

Dim session as New NotesSession

Dim db as NotesDatabase

 

Set db = session.CurrentDatabase

 

If db.FolderReferencesEnabled Then

  db.FolderReferencesEnabled = False

  MessageBox "Folder references have been disabled."

Else

  db.FolderReferencesEnabled = True

  MessageBox "Folder references have been enabled."

End If

 

End Sub

 

 

As of EM 4.0.2 Patch 3 (4.0.2.3-EM-FP003)

 

Items

Descriptions

ADDED OPTION FOR "RUN ONCE" SCHEDULE TO RUN IMMEDIATELY UPON SERVICE START IF START DATE IS IN PAST

If the following registry key is created on the Email Manager server:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\IBM\EMRC\4.0\Scheduler\RunOnceOption]

"RunOldDateTime"=dword:00000001

 

the “Run Once” schedule will run at service start if the date is set in the past. If the key is missing or if it is equal to 0 then it should not run at service start.

MIME MESSAGES CAPTURED IN DXL FORMAT CANNOT BE CONTENT INDEXED BY VERITY

P8’s Verity engine content-based indexing of DXL files uses a standard XML filter to extract the text from the file.  This works effectively with DXL files generated from Lotus Notes email messages in Notes Rich Text format (NRTF), but not for messages in MIME format, because the MIME body and headers are encoded in the DXL file in Base64 encoded elements.  The Lotus Connector can now convert MIME messages to Notes Rich Text format, resulting in a DXL file that can be content indexed and searched.

 

This feature is controlled by two new DWORD registry entries that need to be created in the following path:

 

HKLM\Software\IBM\EMRC\4.0\ServiceDeclarations2\ibm.ctms.lotusconnector\ibm.ctms.lotusconnector.rendertofile

 

ConvertMIMEToNRTF

- Set to a value of 1 to force MIME to NRTF conversion

- If missing or 0, no conversion occurs (current behaviour)

 

SaveConvertedMIME

- Only has an effect if ConvertMIMEToNRTF = 1

- Set to a value of 1 to force the converted MIME message to be saved in the original location in NRTF format.

- If set to 0 or missing, the conversion will be performed when exporting to DXL, but the original message will not be updated in the source mailbox.

 

The following caveats apply to this feature:

 

- Conversion is lossy.  Some embedded images and formatting may not be converted accurately.

- Using the conversion means the captured message is not exactly the same as the message the user received.

- The setting is global. You cannot enable MIME to NRTF conversion in some task routes and not in others.

- This setting is not compatible with the MIME export option 'Preserve MIME content' and export of MIME messages to text will result in a text file with reduced fidelity (e.g. no attachments, embedded images etc.).

GROUPWISE CONNECTOR IS UNABLE TO EXCLUDE "INBOX" AND "SENT ITEMS" FOLDERS IN MONITORED LOCATION

The GroupWise Connector has been updated to improve the handling of sub-locations (folders) within mailboxes.  Specifically, the GroupWise Collector now supports:

 

- Processing any system folders that may contain messages (e.g. Mailbox, Sent Items, Trash) as either include or exclude folders.

- Processing query folders (where the folder contents are dynamic, based on the results of a query) as either include or exclude folders.

- Using include folders in conjunction with the 'Collect from all accounts' option.  (Only messages in the specified folders are collected.)

- Using exclude folders in conjunction with the 'Collect from all accounts' option.  (All messages are collected except for those in the specified folders.)

- Using the folder depth setting with either include or exclude folders.

- Including or excluding the mailbox root. (Enter '/' as the folder name to refer to the mailbox root)

- Specifying folder paths without the leading slash (e.g. '/Clients/ACME' and 'Clients/ACME' are equivalent)

- Enhanced collector logging.

CE 4.0.1-002 fix for error when adding large documents to CE through the .NET API.

There was an issue in P8 Content Engine 4.0.1 related to adding large documents through the .NET API.  This issue was documented in APAR PJ32624 and resolved in CE 4.0.1 Fix Pack 2.  Note this fix also required a Microsoft fix for WSE described in KB943508.  After applying the Fix Pack to the CE server, the update must also be applied to Email Manager 4.x and Records Crawler 4.x servers.  Instructions for applying CE API updates on Email Manager and Records Crawler servers are below:

 

1. Install the CE Fix Pack on the CE server following instructions in the readme file.

2. Update any CE Client machines (for example, any machine with FileNet Enterprise Manager installed) by applying the CE Fix Pack following the instructions in the readme file.

3. On all Email Manager and Records Crawler 4.0.2 servers, back up the existing FileNet.API.dll in the UFI install directory.

4. Manually copy the FileNet.API.dll from one of the patched CE Client machines (for example: C:\Program Files\FileNet\ContentEngine) to the installation directory of Email Manager or Records Crawler (for example: C:\Program Files\IBM\UFI_4.0.2). 

Upgrading EM 4.0.1 to EM 4.0.2

If upgrading from EM 4.0.1 to 4.0.2 ensure that the following files in the installation folder C:\Program Files\IBM\UFI_4.0.2 are used from EM 4.0.2 Patch 1 or later:

 

  • UtilityConnectorMigration.sql
  • 401to402.exe

 

Contact IBM support for complete migration instructions.

Email Manager Shortcut Client Full Installer

Included in Email Manager 4.0.2 Fix Pack 3 is the full installer for Email Manager Shortcut Client. This full installer can be used if deploying the Client to new users without needing to install the GA and Fix Pack 2.

Installing the stand-alone DXL Viewer

Included in Email Manager 4.0.2 Fix Pack 3 is a stand-alone installer for the DXL Viewer application. Previously the DXL Viewer was only available on the Email Manager Server installation media.

 

 

 

Copyright and trademark information:

http://www.ibm.com/legal/copytrade.shtml

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: 

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: 

Intellectual Property Licensing 
Legal and Intellectual Property Law 
IBM Japan, Ltd. 
3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: 

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA  95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademarks

·             IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

·             Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

·             Microsoft, Windows, Windows NT, SQL Server, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

·             UNIX is a registered trademark of The Open Group in the United States and other countries.

·             Other company, product, or service names might be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

  • The Excluded Components are provided on an "AS IS" basis
  • IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  • IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
  • IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

 

Document change history: