Preparing for FileNet's April 2025 End of Fix Support Deadline
In December 2023, IBM announced new versions of FileNet, Business Automation Workflow (BAW) and Cloud Pak for Business Automation (CP4BA). No matter what version you are on as of today (05/07/2024), if you do not upgrade by the April 2025 deadline, you will miss out on crucial security patches, software fixes, and vulnerability notifications. This lack of security patches may increase the chances of your FileNet system falling victim to breaches or ransomware attacks.
Let's dive into why upgrading is crucial, some things to know before upgrading, and how to effectively plan your upgrade to ensure the security and efficiency of your FileNet system.
Support Models
As of this December release, IBM has modified its support model. Traditionally, IBM has used a continuous delivery model for its software releases, rolling out new versions of FileNet every six months in June and December. This was complemented by a Long-Term Support Release (LTSR) every few years. Recently, however, IBM has decided to phase out LTSR in favor of more straightforward support options: standard support and extended support. Under the new policy, standard support guarantees a minimum of two years covering security and defect fixes, which is the same as the prior LTSR offerings.
Once standard support has ended, IBM will offer extended support for an additional fee. The first year of this extended support phase, termed initial extended support, will include critical defect fixes, with a provision for security updates deemed critical by IBM. After the year of initial extended support, IBM will no longer offer security or defect fixes. IBM will however, offer ongoing extended support for years two through four, but it will not include any new security updates or bug fixes that haven't already been released. If keeping your system protected from vulnerabilities is important to you, then this means planning to upgrade approximately every two to three years.
Note: A prerequisite for receiving standard and extended support is that you must have an active software subscription and support agreement.
Understanding Licensing Updates for FileNet, BAW, and CP4BA
IBM has also made licensing updates for users of FileNet, Business Automation Workflow (BAW), and Cloud Pak for Business Automation (CP4BA), particularly in how the Content Navigator (ICN) is licensed across these platforms. Here's a closer look at what these updates entail:
FileNet Licensing Updates
A notable change in the FileNet licensing model is that the Content Navigator (ICN) will no longer count towards your capacity licensing if you're licensed based on the number of CPUs or cores of your server. This means you can deploy as many Content Navigator servers as you like, without worrying about exceeding your licensed capacity. This flexibility applies to both traditional server installations and containerized environments on platforms like OpenShift or Kubernetes.
Business Automation Workflow (BAW) Licensing of ICN
Licensing for BAW does not change so the Content Navigator will continue to count against your capacity licensing, regardless of whether it's installed traditionally on a server or within a container.
Cloud Pak for Business Automation (CP4BA) Licensing Information
We have recently found that many of our customers were not aware of some of the licensing options and limitations with CP4BA. ICN will only impact your capacity licensing if installed on a traditional server. In contrast, deploying ICN on a container does not count towards your capacity licensing. This offers an advantage for those looking to leverage container technology for their CP4BA deployment, allowing for more scalable and cost-effective solutions.
One great option to be aware of is that the CP4BA licenses include WebSphere Network Deployment (WASND) as a bundled application, providing added value. This inclusion means that you can use WASND with the FileNet Content Engine and Content Navigator without incurring the additional cost of licensing WASND. WASND's features include load balancing along with high availability and can be leveraged to enhance your FileNet deployment's performance and reliability.
Exploring the Latest Features
From cloud storage enhancements and process automation to simplified licensing and improved security measures, there are several exciting updates. For more detailed information on all the new features, IBM's knowledge centers are the go-to resource.
Cloud Pak for Business Automation (CP4BA) Licensing Information
- Enhanced support for Amazon S3 storage with transient credentials for improved security and flexibility.
- New capabilities for repairing replicas and updating storage statistics, offering better management and optimization.
- Content Search Services can now be replaced with Elastic or Open Search. If your FileNet system is capacity based, this could reduce your total number of PVUs or VPCs. Note: While there has not been a change in the FileNet licensing for Content Search Services as of this writing, IBM may be changing the licensing model for the indexing of documents even if ElasticSearch or OpenSearch is used.
Business Automation Workflow (BAW) Latest Features
There are a significant number of updates in particular around process improvements. None of these enhancements stood out by themselves, but I would recommend that you view the Whats New section to see what they have enhanced.
Cloud Pak for Business Automation (CP4BA) Enhancements
- IBM Storage Essentials is now included without requiring a separate license. This was a much needed component and I am glad to see this change simplifying the licensing model and adding value.
- BAW now supports more than one Target Object Store (TOS). I would have expected to see this within the BAW features, but it is not showing there while it is in the CP4BA knowledge center.
- New deployments will have internet access restricted by default to enhance security, with options to modify settings as needed.
Planning Your Upgrade
Starting your upgrade planning now is crucial, especially considering IBM's support policy requiring upgrades every two to three years to stay on top of security vulnerabilities. Here are some key steps to get started:
- Evaluate and Plan: Begin with a thorough assessment of your current system and not just FileNet versions. Now is the time to think about updating your hardware, OS and Databases. Understand the April 2025 deadline's implications and how IBM's support policy affects your upgrade timeline.
- Strategize for the Future: Decide whether to move to the cloud or adopt containerization with Kubernetes or OpenShift. This is also the time to choose between a lift-and-shift upgrade or an in-place upgrade if your system is on a recent version.
- Consult and Decide: If upgrading isn't a regular task for your team, consider consulting with experienced partners. Decide on the upgrade path that aligns with your strategic goals and infrastructure needs.
- Organize and Schedule: Assemble your project team, including key roles such as IT, security, and database administrators. Together, create a detailed project schedule to ensure a smooth and timely upgrade.
If you're looking for expert guidance through your upgrade process, don't hesitate to reach out to us at enChoice. We bring over thirty years of experience supporting FileNet and can offer invaluable assistance, from basic consulting to managing and hosting your entire system.
Watch Our Webinar
To complement the insights shared in this blog, we've included a recording of our recent webinar where we discuss strategies and key considerations for upgrading your FileNet system ahead of the April 2025 End of Fix Support deadline. This session provides practical advice and expert insights to help ensure your transition is smooth and secure.
Questions?
If you have questions or would like to chat further about your IBM FileNet, Business Automation Workflow (BAW), or Cloud Pak for Business Automation (CP4BA) system(s), please feel free to reach out to me using the form below.
Ask Us A Question
About the Author
Robert Short
Vice President, Cloud Services at enChoice
Robert Short began working with FileNet software in 1997 as a Technical Consultant, installing, upgrading, and supporting FileNet Content Services, Image Services, P8 Content Platform Engine, and Case Manager. Robert served as an Implementation Project Manager for FileNet, creating standard implementation processes for the installation and upgrade of IBM ECM products. Robert is VP of Cloud Services at enChoice and has built a team to deliver Digital Transformation Services to our customers, both on-prem and in the public cloud, utilizing Amazon Web Services, Armor, Azure, IBM Cloud, and Rackspace.
About enChoice
Founded in 1993, enChoice®, Inc. is an award-winning Enterprise Content Management (ECM) and Digital Transformation solutions company, with nearly 30 years of experience helping customers improve business processes and protect critical information with software and solutions that accelerate their path to digital efficiency.
Visit www.enchoice.com and discover why over 1,000 leading companies, including many in the state government sector, have chosen enChoice as their trusted experts in enterprise content management and digital transformation.