What's new in Content Collector 4.0.1

Edit online

Content Collector 4.0.1 introduces new features and other enhancements with each release. Learn what's new and what changed in each release in this topic.

The Content Collector 4.0.1 fix packs provide the following new features:

New in fix pack 15

IBM Content Collector for SharePoint
On-premises: Site collection level deployment
  • You can install the apps with a site collection URL as input.
  • You can choose either tenant or site collection as the deployment level.
On-premises and Online: Added support for Lookup, LookupMulti, and MultiChoice lists.
Changes in iccViewerPlugin deployment and password encryption
Instead of IBM Content Navigator, the iccViewerPlugin.jar is deployed on the IBM Content Collector server.
The password to communicate between IBM Content Navigator and IBM Content Collector is encrypted. For information on the modifications required in the configuration, refer to Configuring the IBM Content Collector Viewer plug-in.
Added support for operating systems
  • Microsoft Windows 11
  • Microsoft Windows 2022
For more information, refer to the Readme file (embedded) in the Download document.

New in fix pack 14

Introduced new encryption algorithm: AES128
The DES3 encryption algorithm that was used in Content Collector, is replaced with a stronger encryption algorithm, the AES128.
  • Content Collector now stores the credentials and configuration data that is required for processing in its database, with the AES128 encryption.
  • All the existing user data is encrypted with AES128 after the installation and first configuration of this fix pack.

For more information, refer to the Readme file (embedded) in the Download document.

Removed support for the Transport Layer Security (TLS) 1.1 and earlier
All the HTTPS connections in Content Collector are established using only TLS 1.2. The earlier TLS versions are no longer supported.

New in fix pack 13

Support of Db2 Text Search (Db2TS) indexing
The software now supports indexing with Db2 Text Search indexing engine of Content Manager for the Email, SharePoint, and File Systems. The new item types created with initial configuration will be enabled with Db2TS indexing. The existing email item types which were created with Net Search Extender (NSE) indexing are supported for searching using the Federated search functionality.
The support for Indexing in Content Collector using Net Search Extender indexing engine of Content Manager is deprecated in this release. So, newer versions of CM8 Text Search Support installer will not be released. However, for indexing with CM8, a DB2 Text Search Support installer will be released. For more information, refer to the following links:
NuGet packages and required dynamic link libraries (DLL) in Global Assembly Cache (GAC)
The Microsoft DLLs required for SharePoint Online support are not included with this fix and is deprecated too. As a prerequisite, you need to run the PowerShell script ICC_SPO_Prerequisite_NuGetPackages_Installer.ps1, which is included with this fix pack to install the NuGet packages.

Note: This script is a prerequisite for ICC WebApp for Link Handler installer and ICC App for SharePoint Online installer.

Domino as a source system with Content Collector
For using Domino as source system, you need to install the Notes client 12 on the IBM Content Collector Server instead of the Domino Server. This change is applicable as the Domino server 9.0.1 fix pack 10 and later, which are scheduled for end of service (EOS), will no longer support the 32-bit Server APIs that were used with Content Collector. So, Content Collector now uses the 32-bit APIs that are available only with the Notes client 12.

New in fix pack 12

Added support for Microsoft Exchange Hybrid
Starting with Content Collector 4.0.1.12 interim fix 2, the software now supports configuring and selecting Microsoft Exchange Hybrid as the Email collection source. For more information, refer to the following links:
Deprecated support for Content Collector Legacy Support component
Starting with Content Collector 4.0.1 fix pack 12 (4.0.1.12), support for Content Collector Legacy Support component is deprecated and will be removed in future releases. For detailed information on what's new in fix pack 12, refer to the Readme file in the Download document.

New in fix pack 11

Added support for Microsoft SharePoint Online
The software now supports configuring and selecting Microsoft SharePoint Online as the collection source. For more information, refer to Deployment footprint of Content Collector for Microsoft SharePoint Online.

New in earlier fix packs

Added support for Microsoft Exchange Online
Starting with Content Collector 4.0.1 fix pack 9 (4.0.1.9), the software now supports configuring and selecting Microsoft Exchange Online as the Email collection source. For more information, refer to IBM Content Collector for Microsoft Exchange Online.

Microsoft Exchange email archiving: Improved archiving performance
The IBM® Content Collector Email Connector service can now create child processes, which results in higher throughput and better scalability on a single machine when archiving Microsoft Exchange email.
SMTP Connector: Force archiving using Failed Message Envelopes
If processing SMTP and MIME email fails because of an invalid document structure, you can now force archiving by using Failed Message Envelopes. However, forcing archiving might cause limitations when users search for content in those documents.
Added support for Outlook Web Access (OWA) in Office 2013
The Content Collector OWA app for Office 2013 enables users to mark documents for archiving or stubbing, to search, view, or restore archived content, or to add additional archiving information using a browser as their mail client. The Content Collector OWA app for Office 2013 can be configured and deployed for specific users or for everyone in your organization.
Additional filtering options for Microsoft SharePoint collection sources
The SharePoint Connector now provides additional options for filtering collection sources: site property and list query filtering. These features require Microsoft SharePoint 2010 or 2013 and are not available on Microsoft SharePoint 2007 servers.
Added support for null values
Content Collector now allows property mappings and expressions to evaluate to null.

The File System Source Connector can now treat missing property values as null values. For new task routes, this option is enabled by default. Task routes that were created before Content Collector 4.0.1 are not changed to avoid breaking the inherent logic.

In the FileNet® P8 property mappings, you can now choose to allow null values for property mappings. In this case, a property can be explicitly set to a null value.

Handling of default values for IBM Content Manager attributes
Content Collector now supports default values for all types of IBM Content Manager attributes. Default values are displayed in the Content Manager property mappings tables. Default values are no longer set by Content Collector but by IBM Content Manager.
Allow for searching archived email by folder name
Users often organize their mailboxes by using different custom folders. For email that was archived into a FileNet P8 repository and indexed with IBM Content Search Services, Content Collector now allows for using a folder name as search term to find all archived email that was located in that specific folder.
New expression operators
The set of prototype expression that can be used with the Expression Editor was extended by new expressions for adding time units, for filtering values, for converting data, and for working with null values. Furthermore, the following expressions now support additional data types: DynamicMetadataReference, Element, Equal, GreaterThan, and LessThan.
TLS 1.2 enablement
Content Collector now supports TLS 1.2 connections.