• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

FileNet Migration – Best Practices and Client Experience

You are here: Home / ECM Solutions / FileNet Migration – Best Practices and Client Experience

August 18, 2016

Whether it is a trend, just coincidence, or the fading of IBM’s influence in content management, recently we have had multiple clients request migration of FileNet images and documents as part of a long term plan to remove the FileNet/IBM solutions from their infrastructure.  This post will share our experience and thoughts around migration from FileNet with OpenMigrate.

FileNet Background

FileNet was originally founded in 1982 with a goal of commercializing optical disk technology.  FileNet shipped the first image management system in 1985.  In the 80’s, hardware infrastructure components needed for image processing included state of the industry, at the time, image processing boards in PC’s, proprietary servers, scanners as well as optical disk technologies.  In 1992 FileNet moved away from proprietary hardware to focus on software but still leveraged a core component called an “optical disk jukebox” capable of holding multiple laser disks.

With the purchase of Saros in the mid-90’s, the Panagon release in 1998 as well as the P8 release in 2003, FileNet has evolved their solution to move away from the hardware components to a software model that leverages the improved storage and display technologies available as commodities today.  Panagon brought the beginning of document management (rather than just image management) and P8 extended that capability.  FileNet was purchased by IBM in 2006.

FileNet Migration

For our clients, the history of FileNet is particularly relevant.  See our initial thoughts on FileNet migration in a previous post.  For various reasons consolidations had been delayed, resulting in multiple repositories including:

  • FileNet Image Services complete with OSAR jukeboxes and optical disks. One client had approximately 1 million documents stored and was continuing to add new documents.  Images are stored as single and multiple page TIFF documents and MS Office files.
  • FileNet Document Services/Panagon – 100,000 digital content files (Microsoft Word, PDF, etc…)
  • FileNet P8 – 2.75 million documents stored including multiple page TIFF and HTML files.

Most clients want to consolidate all of their FileNet instances into one modern ECM instance.

FileNet Image Services

The most difficult aspect of migrating from FileNet Image Services deals with the Optical Storage and Retrieval (OSAR) jukebox.  One client’s unique components, in addition to the jukebox, included:

  • Optical disks were stored in the jukebox but also loaded manually as the system had evolved past the 200 that could be stored in the jukebox to exceed 2,000 platters.
  • The jukebox included four drives in each library but only 2 working drives per library.
  • Care had to be taken to migrate documents in platter order to minimize disc swapping.
  • Content needed to be changed from single page TIFF to a multi-page PDF. PDF/A configuration was also available for archive.
  • Needed to balance migration with current production storage and retrieval.
  • Metadata, stored in the FileNet database, had to be migrated as well

Working with the client, we were able to migrate the bulk of content from FileNet to a File System in preparation for the move to the new ECM system.   By leveraging one of the three jukeboxes for migration, we chose to load one jukebox with 100 platters at a time and run that migration leaving the other 2 jukeboxes available for production needs.  Some issues that arose included:

  • Periodic failures during FileNet IS migration – whether it was just FileNet or other issues, we leverage OpenMigrate to automatically retry failed documents. This was critical as the FileNet system was often unreliable during our OpenMigrate runs.
  • Command line requirement – unlike the later FileNet products and versions, FileNet IS did not have a clean API to access images from the OSAR jukebox. We built an IS source connector for OpenMigrate that put a wrapper around its command line interface.
  • Multi-threading – while the source (jukebox) needed to be single threaded (one platter at time), the target ECM instance could have multiple threads to improve the performance of the document loading.
  • Additional metadata – large components of the target ECM instance’s attributes were stored in a variety of other systems. OpenMigrate had to take into account the other systems that would require access to store that metadata with the associated images.

FileNet Document Services

A FileNet Document Services (DS) migration was much easier than Image Services.  Simplification components included:

  • DS database contained direct pointers to file locations (on magnetic rather than optical disk).
  • File content was not single page TIFF so documents could just be migrated without any conversion.

OpenMigrate for DS could utilize the existing database and metadata to load content from the file system.  By leveraging OpenMigrate’s ability to connect to any database, we did not require a custom connector for DS.

FileNet P8

The P8 migration was a combination of the DS and IS migrations in that:

  • P8, like IS, leverages multi-page TIFFs that were combined into single page PDF or PDF/A.
  • File locations were not easily determined from the data in P8 so we needed to call a native Java API to extract content.

Other components that were similar included both multi-threading into target ECM instance as well as extraction of metadata from external relational databases.

Summary

All three instances of FileNet had their own quirks. Working through those challenges, combined with pulling metadata stored in different databases, required extensive understanding of the existing environments as well as mapping to match attributes in the destination repository.

If you have any thoughts or questions, please share with us below.

Interested in learning how we migrated from FileNet in 6 weeks? Be sure to download our case study detailing a recent client migration.


Free FileNet Migration Case Study



Filed Under: ECM Solutions, FileNet, Migrations, OpenMigrate

Reader Interactions

Trackbacks

  1. Migrating from FileNet in 6 Weeks – Case Study Available – Technology Services Group says:
    August 22, 2016 at 10:25 am

    […] mentioned in previous posts, TSG has seen an uptick in clients choosing to finally move from legacy FileNet implementations to […]

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • FileNet Migration – Not as hard as you think?
  • FileNet Support – Migrating to mitigate the risk of an unsupportable product
  • FileNet Migrations – Best Practices for Large Migrations
  • File Formats Lessons Learned – Legacy ECM Migrations
  • FileNet COLD Migration – Cracking the proprietary format issue
  • FileNet Migration – Recorded Alfresco/TSG Webinar – 05/29/2019
  • FileNet – How to retire in weeks rather than months
  • Migrating to Alfresco – Reducing Risk, Stress and Cost with a Rolling Migration
  • FileNet Migration to Alfresco with OpenMigrate
  • Alfresco Webinar – Benefits of a Rolling Migration versus a Big Bang – October 21st

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT