LATEST NEWS

FileNet IS/CM Migration Services

img
Sep
01

 

Hi all, as a specialist in IBM FileNet Content Manager and IBM Datacap solutions, I can provide services to companies / individual that need assist on FileNet migration.

As per my experience, I had successfully migrated more than 20M+ images from legacy FileNet systems. These includes legacy FileNet IS/CS and the newer P8 Platform which later adapted by IBM as a new line of products called IBM Enterprise Content Manager.

As such, I have in depth knowledge about FileNet iS/CS solution after implementing it for more than 10 years. As for migration, I have done numerous system migration from content management system, which includes FIleNet/IBM ECM but not limited to these two.

In general, data migration can be very painful and always being overlooked due to the complexity. That is somewhat true, but only if you do not know what are you dealing with. And I always stood by this quote,

“If you know the enemy and know yourself you need not fear the results of a hundred battles.” – Sun Tzu

So, knowing what to expect when dealing with something is key. Each migration task can be very different, there will be a lot of variables to deal with and timelines to be met, but still, knowing is half of the battle.

A typical data migration consists of the three items below but I am limiting the scope to revolve around IBM solutions.

  1. source system
  2. staging environment
  3. target system

For example, input can be from various devices / medium. Some might also name this step as upload / import.

 

This setup usually for backfile conversion / old documents that require digitization. The process of migrating from common folder is almost straight forward. it is important to note that each image or folder must be accompanied by and index / listing of every item and their index values. The module will do the rest. It can also be setup to watch the folder for change.

The same methodology and process is similar for FileNet to FileNet migration. The key difference is architecture and software version. Each source / target will have specific version.

The figure shows data migration from previous FileNet version to the current version. The process is automated and require minimal user / operator intervention.

For the staging environment, I normally use Intel NUC Kits. If you are wondering why, it is because the small form factor, and the processing power of an i7 in a very small container. This enables me to stack up each NUC to minimize the physical space used. There is also a server to handle processing stuff. the SAN/NAS is the storage dedicated for the migration process. The capacity varies based on estimation of the total size from source.

Typical Setup

Intel NUCs

I will be updating this post from time to time as required. If you need the service, please pm me, thanks.

Share! Share!
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •