Filenet capture statistics not updating
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 File Net was not a long term direction.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 File Net as it continues to not be a major focus of IBM.Like pulling a lose thread, upgrading File Net 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.To prevent the main script from going into the function body, the main script should either exit beforehand or should skip the functions block by using GOTO command.
Typically in regards to upgrades for stable clients, TSG will typically recommend: Since the client was using a third party tool to access File Net, that tool at a minimum would also require upgrading.
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.
In the end, the team reached a preliminary decision to continue to run on their existing File Net 5.2 unsupported.
If the temporary option is set to false, which is the default setting, the setting that Installation Manager uses in the current silent installation session is persisted.
You must use the IBM Installation Manager uninstaller to uninstall IBM Installation Manager on a client computer.
The following fragment uses the uninstall Installation Manager function to uninstall the IBM Installation Manager.