ibm content collector v4.0 whats new · information lifecycle governance •2 ... • ibm content...

IBM Content Collector v4.0 Whats new ?

© 2013 IBM Corporation

Information Lifecycle Governance

•2

Embedded Database

• An embedded database resident on the ICC server is now used (SolidDB)

• Dependency on external database (DB2/Oracle/SQL Server) for configuration data

storage removed

• Simplifies installation and configuration and is seamless to the administrator

• In ICC v4.0 a Catalog is like a Data Store in previous versions of ICC. It holds a complete

set of configuration data. ICC will only use one of these sets at a time. Configuration data

is stored in the file solid.db

• Works across multiple ICC nodes

As part of this change two services have been added

• IBM Content Collector Configuration Store

• Responsible for storage of configuration data

• IBM Content Collector Configuration Store Manager

• Monitors/Manages above service

Changes to the following services, dependencies and users

• IBM Content Collector Configuration Access and Task Routing Engine



•3

Unified Search across ALL messages

Search email database and archive from one entry point and get one result list

Keyword search

Extended keyword search using Boolean operators

Support of advanced search options, for example, extending the

scope to include date, addressees, subject, or body and attachment

information

Supported Mail Clients

Outlook ≥ 2010

Notes ≥ 8.5.1 Standard Client



•4

Enter search criteria

Location where

the content resides

Unified Search (Mailbox and Archive) for Notes



•5

Search bar

Search results

Single Search across Exchange and archived email repository



•6

Unified Search - Live



•7

Use case: users want to consolidate local archive and active mailbox and have

single point of access for all archived content

Domino server

Active mailbox

User's PC

Local NSF

ICC server

+ backend

File server

Local NSF

Mailbox archiving Stubbing life cycle

NSF migration

Domino: Move stubs from local NSFs to active mailbox after archival

Works analogue to existing functionality in Microsoft Exchange Connector



•8

Email Connector

Domino/Notes

Added support for IBM Domino 9

Added support for IBM Notes Client 9

Added support for iNotes 9

Exchange/Outlook

Added support for Microsoft Exchange Server 2013

Added support for OWA in Microsoft Exchange Server 2013 (provided with fixpack)

Added support for Outlook 2013 (Outlook Extension)

• Support added for Windows 8

• Only 32-bit Version



•9

Improved config. Management: Task Route Enhancements

Invalid decision points detection (multiple always-true rules)

Nested decision points

Task Route Explorer Filtering



•10

Improved config. management for multi-tier landscapes

What changed? • Multiple task routes can be exported at once into a single file (instead of one file

per export)

• Filtering and multi-select of task routes

• Task route dependencies (lists and custom metadata) are included into the

file and can be recreated automatically on the target system

• Drag and drop support 'to' and 'from' the task route explorer

multi-tier (dev/QA/production) landscapes

Improve migration scenarios

• Configuration manager can be used simultaneously by multiple users in parallel to create/edit/update/delete selected configuration data (with focus on different task routes)

• Helps in the case a large number of task routes need be configured



•11

Audit trail for configuration changes

• Changes made to ICC configuration are tracked and viewable in the UI



•12

ICC Config Mgr: Support for “User Account Control”

What changed?

Configuration Manager can run now without requiring “RunAsAdmin”

Files that were previously created/written by Configuration Manager are now

managed by the ICC windows service “Configuration Access”

Configuration Manager makes use of user's personal folder to store local user

settings or log files

All UI components are writing to the UI.log, its accessible with the shortcut

CTRL+SHIFT+D



•13

Statistics Collection

Customers asked for functionality – basically two use cases:

• 1st use case: end to end reconciliation

– Ad-hoc ingestion

– Requirement to archive all emails from local NSFs

– litigation request triggers collection of mailbox snapshots of affected users

– 100s to 1000s of mailboxes to ingest

– When is ICC done?

– Do mailbox counts match with ingest counts?

• 2nd use case: overview to monitor system health and data distribution

– Mailbox management

– Transition of users from “ramp-up” to “regular” processing

– Is ICC working normally? Does lifecycle work as expected?



•14

Statistics Collection

• New Email Collector functionality: Create statistics for the collector

• Statistics can be requested using different collectors

• EC Collect Email by Rules (Tab Collection Sources)

• EC Process Email Stubbing Life Cycle (Tab Collection Sources)

• Two sets of counters: Base / All

• Different counters for Domino and Exchange

• Output: <InstallDir>\ctms\log\statistics\afu_<collectorName>_<n>.log



•15

SMTP Archiving for MS Office 365

• Office 365 allows journal forwarding of emails to an extern mail contact. With that, Office365

email communication can be archived by IBM Content Collector SMTP Receiver.

• To achieve that, customer need to configure in Office 365

– a global journal rule that sends all incoming an outgoing email to the defined IBM Content

Collector mail contact.

– an outbound connector that routes all mails send to the IBM Content Collector mail contact to

the IBM Content Collector SMTP Receiver.



•16

Motivation:

• Deploying multiple nodes requires redundant entry of same information (potential

for trouble, error prone)

Goals:

• Eliminate any redundant information that is entered during installation

• Hide deployment complexity

• Simplify installation steps for secondary nodes (current screen-flow)

• Manually entering all information is still supported

Solution:

• Installer finds other nodes via SLP and consumes information

• Simplified secondary node installation (4 steps less)

Installation: Enhanced cluster setup



•17

Retention: New Option added

Customers have now 3 options:

1. ICC manages Retention

Uses ICC's native Expiration Manager

•Calculate expiration date as part of the task route

2. IER manages Retention

IER responsible for setting retention period

•Retention set as part of task route OR at the container level in IER

•Container settings can be syndicated from Atlas

3. ICC applies instructions syndicated from IBM Policy Suite

ICC applies instructions received from IBM Policy Suite

•Retention setting applied per task route

•Changes syndicated down into ICC and applied day forward

•Support ICC Email and ICC for Files



•18

Dynamic Retention

Archive documents (files or email) based on rules from the source system and

associate a retention schedule with each archived document.

Rules are based on attributes of a document

Examples:

• All files in the folder “contracts” are assigned schedule ID 124

• All *.rtg files are assigned schedule ID 200

• All manager email (Max Sample, Hans Example) is assigned schedule ID 198

Rules are created using regular expression syntax.



•19

Dirk Jahn

SME for IBM Content Collector

& eDiscovery Products

Pan-IMT Team Europe

IBM Deutschland GmbH

Hechtsheimer Str.2

55131 Mainz

Mobile : +49 (0) 172-7406593

[email protected]

Phone : +49 (0) 6131-843639

e-Mail :

Do you have any questions ?

There are much more new features More Details in IBM Knowledge Center: http://www-01.ibm.com/support/knowledgecenter/SSAE9L_4.0.0/com.ibm.content.collector.doc_kc/overview/c_afu_whats_new_40.dita?lang=en

Install IBM Content Collector v4.0 and try it out !

There are much more new features More Details in IBM Knowledge Center: http://www-01.ibm.com/support/knowledgecenter/SSAE9L_4.0.0/com.ibm.content.collector.doc_kc/overview/c_afu_whats_new_40.dita?lang=en

Install IBM Content Collector v4.0 and try it out !

http://www-01.ibm.com/support/knowledgecenter/SSAE9L_4.0.0/com.ibm.content.collector.doc_kc/overview/c_afu_whats_new_40.dita?lang=en










•20

Journaling support for non Domino/Exchange

• IBM Content Collector 4.0 provides a set of custom MIME headers that can be used to add journal information to email.

• Customers with non Domino/Exchange mail systems can implement a custom server application that adds IBM Content Collector custom journal headers to their email.

• Custom Journal information supports at least as much information as Microsoft Exchange Journal reports do.

ibm content collector v4.0 whats new · information lifecycle governance •2 ... • ibm content...

Documents