Original Message:
Sent: Thu March 20, 2025 11:55 AM
From: Jay Bowen
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Sure.... Indexing Content Platform Engine databases - IBM Documentation and Database indexes for index jobs - IBM Documentation. Those are quick google searches to 5.2.1.x they are still relevant for current version of the product. Indexing for IBM FileNet P8 Content Engine Searches is another good link those are for CPE and CSS. This link is for ICN Creating database indexes to improve performance - IBM Documentation
------------------------------
Jay Bowen
www.bowenecmsolutions.com
Medina, OH
Original Message:
Sent: Thu March 20, 2025 11:47 AM
From: Hector Casals Mendez
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Hi Jay, thank you very much again for your help. Could you share the links to where those recommendations are?
------------------------------
Hector Casals Mendez
Original Message:
Sent: Thu March 20, 2025 10:52 AM
From: Jay Bowen
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Hector that's a great approach, sounds like you have it. Some additional suggestions if you are using PE there are additional steps you need to perform and double check DB indexes for the upgrade. Some indexes are suggested temporarily when CSS updates if there is a re-index under those patch levels. Other item worth mentioning since the patient is on the table is ensure all custom indexes are using the TO LOWER function on DB side, if you want to go all out there are optional indexes IBM recommends for search templates and such that will speed up rendering of the ICN search listing.
------------------------------
Jay Bowen
www.bowenecmsolutions.com
Medina, OH
Original Message:
Sent: Wed March 19, 2025 11:48 AM
From: Hector Casals Mendez
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Thank you Jay for your time and well-explained response.
We are going to perform a migration with a hardware change.
We will have two new environments, one intermediate 5.5.8 and the other final 5.6.
We will have a clone of the database.
We will export the Oracle 12c database to upgrade it to version 19.
We will install CPE 5.5.8, use the 5.5.3 profile, and perform the upgrade.
Then, in the 5.6 environment, we will install CPE and perform the final upgrade, after connecting to the database used in version 5.5.8.
In parallel, we will update CSS to version 5.6 with its interim fixes 5.6.0-P8CPE-IF001 and 5.6.0-P8CPE-IF002 (before the CPE update) and install IBM CN 3.1 with its interim fixes IF001, IF002, and IF003.
Then, we will perform final testing.
Thanks again!
------------------------------
Hector Casals Mendez
Original Message:
Sent: Wed March 19, 2025 10:00 AM
From: Jay Bowen
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Hi Hector, both of those upgrades will process the GCD first then asynch your object stores. Some of those tasks do modify docversion but definitely reprocess security IDs. Aside from many documents if you have very granular security it may take a little bit more time. Usually the GCD upgrade is immediate and about 10 minutes for small object stores and .5-1 hour on larger >100m object stores. Are you doing an in place upgrade? For major upgrades I will clone the existing environment by taking a prod db backup + content (some or all) and spin up a new environment. This allows me to build out a mirror copy of production, sort out any issues, dry run as many times as desired then use the new environments as a prestaged upgrade now cutover tasks are super simple. Since you are using new hardware in this scenario rollback plan is super easy as you didn't meddle with existing production servers. Lastly if you perform the upgrade to new hardware you can pinpoint exactly how long it is going to take.
Going back to timings and entries for your project plan. An in place upgrade for CPE 5.5.8 would take about four hours which includes installing software, performing upgrade tasks, deploying. That's a low side estimate. Immediately repeat that process for 5.6 should take the same amount of time or less. If you have content search (CSS) those upgrades can be lengthy but occur as background tasks. After CPE is upgraded you can then update ICN/ Navigator which should take about an hour or two for someone that upgrades FileNet often or up to four hours for someone reading the deploy steps. If you are using JDBC ssl, load balancers, patching websphere the time only goes up from there. For business planning you will want at least a day to have FileNet offline for these tasks and work through any issues that may arise.
------------------------------
Jay Bowen
www.bowenecmsolutions.com
Medina, OH
Original Message:
Sent: Tue March 18, 2025 04:40 AM
From: Hector Casals Mendez
Subject: Upgrade Content Plantorm Engine from 5.5.3 to 5.6
Dear Experts,
I'm generating the project plan to migrate FileNet from version 5.5.3 to version 5.6, first going through version 5.5.8. I need to know how long it takes to migrate each of the client's numerous object stores. I know it depends on the hardware, network, number of documents per object store, etc. Is there a formula available to help me calculate the time, please?
Thank you.
------------------------------
Hector Casals Mendez
------------------------------