Moving from archiving using IBM CommonStore for Exchange Server to archiving using IBM Content Collector

Content

There are different methods of moving from IBM CommonStore for Exchange Server (CSX) to IBM Content Manager.

You can move to IBM Content Collector by installing Content Collector on a separate server or on the CommonStore server. Installing Content Collector on a separate server is the recommended method.

None of the CommonStore clients can access the IBM Content Collector client interface.

When you move from archiving using CommonStore to archiving using Content Collector, the two systems are not merged. The data model of the archived documents is different. This means that you can view and restore documents in CommonStore item types but you cannot archive into a CommonStore item type using Content Collector. Restored documents cannot be restubbed. Only item types for the document model BUNDLED and the archiving type ENTIRE can be previewed and restored by using the Content Collector Email Search.

To continue archiving, you must create new item types in Content Collector and configure the Content Collector task routes to suit your archiving requirements.

However, you can enable a CommonStore item type for indexing in Content Collector. You might want to reindex the items in CommonStore item types to improve the indexing quality and include the Content Collector indexing result strings that makes searching in a CommonStore item type comparable to searching in a Content Collector item type.

Installing Content Collector on a separate server implies:

• Installing Content Collector Legacy Support on the existing CommonStore servers. This disables archiving using CommonStore and starts the legacy support versions of the CommonStore server and the CommonStore for Exchange Server Task.
• Installing Content Collector Server on a separate machine and start Content Collector.

Installing Content Collector on the CommonStore server implies:

• Installing Content Collector Server on the existing CommonStore servers. The server package includes the Content Collector legacy support. This disables archiving using CommonStore and starts the legacy support versions of the CommonStore server and the CommonStore for Exchange Server Task.

Installing Content Collector on a new server and manually adding CommonStore functionality implies:

• Installing the Content Collector server on a new dedicated machine.
• Manually adding all CommonStore functionality instead of installing the legacy support software before shutting down the CommonStore servers.

Ensure that you do not remove the CommonStore servers until Content Collector is running properly, and do not delete any CommonStore configuration data.

To install Content Collector on a separate server:

1. Install IBM Content Collector Text Search Support V2.2 Fix Pack 1 on the IBM Content Manager server in a different folder to the folder in which the CommonStore text search user exit and fast indexer modules were installed. The Content Collector and the CommonStore text search components can be installed on the same Content Manager server, however the components must be installed in different folders.



2. Suppress all CommonStore archiving functionality on the CSX server by unassigning policies using the CSX System Manager. Select General Properties -> <None>, or set the mailbox properties for a specific user or group to <None> under Policies for Mailboxes -> Users -> <MailboxUser> .
3. Install IBM Content Collector Server V2.2 on a dedicated server and then apply the IBM Content Collector V2.2 interim fix 002.



4. Run the Content Collector Initial Configuration to create a Content Collector configuration database.



5. Install IBM Content Collector Legacy Support:
   
   1. Shutdown the CSX tasks.
   2. Shutdown the Commonstore Server (archpro).
   3. Install IBM Content Collector Legacy Support on each CommonStore Server. Specify the host name and port of the Content Collector server during installation.

   If CSX Outlook Web Access (OWA) Support was installed on a CommonStore server, remove CSX OWA Extension by entering the following command-line function: configOWA.exe /uninstall

6. Configure legacy support. For details, see Configuring Content Collector for CommonStore for Exchange Server legacy support in .
7. Start legacy support. For details, see Starting legacy support to view and restore documents archived using CommonStore for Exchange Server in .
8. Remove CSX OWA Extension on the server where Microsoft OWA resides by entering the following command in the CSX OWA Support installation folder:

configOWA.exe/uninstall .
9. Install and test IBM Content Collector Outlook Web App (OWA) Support. For details on which steps to take in which order, see Installing and configuring Content Collector Outlook Web App (formerly Outlook Web Access) support . Remember to apply the Content Collector OWA Extension configuration by running Apply Configuration.

Note: You can only restore messages archived by CommonStore in Content Collector OWA. Messages archived by CommonStore cannot be viewed in OWA.



10. Install IBM Content Collector Outlook Extension on the client machines. Before installing, remove the CSX Outlook Extension on the client machines. For installation details, see the topic Installing Content Collector Outlook Extension. If you enabled offline archiving to a local repository (Outlook PST file) in CommonStore, make sure that the mailbox on the server is synchronized before you install Content Collector Outlook Extension.


11. If IBM Content Collector offline repository support is enabled on a client machine, you can reuse the offline repository that you used in CommonStore for Exchange Server. Offline repository support functions for both documents archived by IBM Content Collector and documents archived by CommonStore for Exchange Server. This means that the original content that was stored in a local archive by CommonStore for Exchange Server can also be accessed by the IBM Content Collector offline repository support. To reuse the offline repository, set the location of the offline repository to the personal folder (PST file) that you used in CommonStore under IBM Content Collector -> Offline Repository -> Settings on the Outlook main window and initialize the local repository.


12. If you want to reindex all or some items in CommonStore item types to improve the indexing quality using the indexer for text search in Content Collector, carry out the following steps:
    
    • Run afuEnableItemType on the item type to enable processing the item type by the Content Collector indexer. For details, see the topic Enabling IBM CommonStore item types for processing by the indexer for text search. Only item types for the document model BUNDLED and the archiving type ENTIRE can be enabled for indexing in Content Collector.
    
    
    • After the item types are enabled, create a new configuration for each item type by running the afuCreate script. For details, see the topic Creating an indexer configuration file for the item type. If you defined your own attributes in the CommonStore user-exit configuration file called icmfce_config.ini, you must add these user-defined attribute entries to the new indexer configuration file using the appropriate indexer configuration syntax.
    
    
    • Using the new configuration, reindex all items in the enabled item types by running the afuIndexer script. For details, see the topic Indexing items in an item type. You do not have to recreate the full-text index after you have enabled the item types and before you begin reindexing. You can reindex items in the same index you used when you indexed items using the fast indexer or the standard IBM Content Manager indexer.


13. Before you can search, view, or restore archived documents in Content Collector, you have to adapt the search configuration file and the search archiving mapping file for accessing archived data in Content Collector. There is always one search configuration and one search mapping file per Content Collector installation.
    
    If you want to search in CommonStore item types and in new item types created in Content Collector, both the search files must include the settings for the CommonStore and the Content Collector item types.
    
    Only CommonStore item types for the document model BUNDLED and the archiving type ENTIRE/MSG can be searched, viewed, and restored in Content Collector. Document collections of other item types are not supported by Content Collector Email Search.
    
    Content Collector provides sample files that you can customize. Make a backup copy of the sample files before changing or adding any entries. To adapt the search files:
    
    • In the IBM Content Collector Configuration Manager, select General Settings->Archived Data Access and select Archived Data Access for Email.
    
    
    • On the Advanced tab, export a sample search configuration file, for example CS_CM_full_text_collection_search_config.xml, and a sample archive mapping, for example CS_CM_doc_type_collection_search_mapping.xml. Both files are stored in the directory <installDir>\AFUWeb\afu\config\templates, where installDir is the directory where you installed IBM Content Collector.
    
    
    • Edit the files as required. An example of how to combine the search configuration settings and the archive mappings for CommonStore and Content Collector is shown in the following sample files: and .
    
    
    • Import both files again by using the Configuration Manager and save your changes to the Content Collector configuration database.
    
    
    • Restart the Web Application service by clicking Start > All Programs > IBM Content Collector > Start Services > Start ICC Web Applications for the changes to take effect.
      
      Now you can search for documents in both CommonStore item types and in Content Collector item types by using Content Collector Email Search.