• 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 Support to End in 2019

You are here: Home / ECM Landscape / FileNet Support to End in 2019

October 29, 2018

IBM has formally announced that it is dropping support for FileNet version 5.2.X on April 30th, 2019.  FileNet customers on 5.2.X need to decide whether to upgrade to the 5.5 version, run unsupported, or migrate to another option.  This post will present our thoughts from talking with a FileNet customer working through the decision process.

Upgrading FileNet – Not an easy decision

For FileNet customers, the decision to upgrade or migrate is not a simple decision.  Like pulling a lose thread, upgrading FileNet might lead to other portions of the infrastructure that should be upgraded as well.  For our customer, the upgrade included at least an upgrade of Oracle as well as other application and server components.  Many times, upgrades can be difficult and risky and could result in a variety of costs and issues that, to the end users, don’t necessarily add value.  Typically in regards to upgrades for stable clients, TSG will typically recommend:

  • For a major .0 release, wait for the first service pack or .1 release to let other new installs work out the issues with the newest release.
  • For a minor .X release, consider waiting and potentially skipping releases unless there is substantial value for getting on the new release.
  • For any release, consider what other components of the ECM stack (DB, Application Server, hardware….) should be upgraded as well.
  • For most environments, never upgrade in place as fall-back can be an issue. TSG recommends a new environment to allow for addressing issues without user interruption.  Typically either virtual or new hardware should always be considered.  TSG typically recommends delta migrations over blackout days if possible when considering migrating to the new environment.

For our FileNet customer, the decision comes down to:

  1. Upgrade to FileNet 5.5
  2. Migrate to something different
  3. Run on FileNet 5.2 unsupported

Upgrade to FileNet 5.5

As already mentioned above, upgrading to FileNet 5.5 involves:

  • Potential need to upgrade hardware and Servers
  • Upgrading Oracle
  • Upgrading FileNet

Since the client was using a third party tool to access FileNet, that tool at a minimum would also require upgrading.  All of the above would provide no additional capabilities to the business users and introduced the risk that some of the business might be interrupted during the upgrade process.  Our client wasn’t sure that any support from IBM on the 5.5 version would be better than their current support on the 5.2 version.

Migrate to something else

Given a third party tool to access FileNet, the team felt the migrating to something else would be a substantial effort.  Not only would the migration introduce a new ECM system but also potentially a new interface and require all of the integrations to both the old interface and FileNet to be moved.  See our previous post on why migrations will never be easy.

While the team had a desire to begin moving the cloud, they felt strongly that the IBM cloud with FileNet was not a long term direction.  In regards to the cloud, the client was more focused on Amazon or Azure and could not justify the move from a running a stable on-premise system to the cloud or a new platform.

Run unsupported on FileNet 5.2

In the end, the team reached a preliminary decision to continue to run on their existing FileNet 5.2 unsupported.  Reasons include:

  • FileNet/IBM Support – The team felt they were not getting great support from IBM on their current version and didn’t think it would get any better on FileNet 5.5.
  • System Stability – The team felt the system was very stable currently and did not want to risk the upgrade process that could introduce instability as well as some downtime with no perceived benefit to the business user.
  • Cloud – Client is considering the cloud in the future and would tie any upgrade or migration to that future decision.

Summary

While a vendor like IBM dropping support on a version might seem like a requirement to either upgrade or migrate, often the most practical decision from a risk and cost perspective can be to run unsupported.  Many vendors will often use the “off of support announcement” to offer additional charges for continued support while clients continue to pay their maintenance.  TSG typically doesn’t recommend these additional charges as we have often found vendor support for out of support products can be very lacking and not worth the cost for a stable system.

As we have said at this site often, clients should start to plan for migrating away from FileNet as it continues to not be a major focus of IBM.  For many implementations of FileNet, there are simple ways to leverage cloud vendors as we mentioned in our article on how FileNet for one customer can be replaced with just AWS S3 while giving the customer all the benefits of a modern browser for viewing and annotation as well as replacement of proprietary components like TIF files with more flexible PDF and modern document formats.

Let us know your thoughts below:

Filed Under: ECM Landscape, FileNet

Reader Interactions

Comments

  1. MukundVishy says

    January 20, 2019 at 6:41 am

    Ha..Ha…best decision made!! That is how many customers think and decide at the end.

    But most corporate are worried on running such a huge content management system without support or post end of support which is where IBM tries to cash in. As on date I doubt if IBM have a stats on how many of their customers have moved (or ready to move) to Filenet 5.5.x – I believe majority of their customers still run in 4.5.x and 5.1.x and not even moved to 5.2.x.

    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

  • The Deep Analysis Podcast – The 11 Billion File Benchmark
  • FileNet and CMOD – Will IBM finally sell them and potentially buy Box?
  • FileNet and Content Manager (CMOD) Migration to Amazon Web Services – Why Now?
  • FileNet – Adding a Modern Interface to a Legacy ECM
  • EFFS Promises and Legacy ECM Vendors – ECM Article Roundup
  • FileNet – Is IBM planning on selling it?
  • ECM Roadmap – Thoughts on Planning for the Future
  • 2017 ECM Thoughts and Predictions as well as recap of 2016 postings
  • The Future of ECM
  • ECM Implementations – Why do some fail?

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