DCTM to LL Migration Project

Hi,

We are soon going to initiate a migration project wherein we will be pushing content from Documentum into Content Server 10. We will be having a XML feed that will contain object metadata and content mappings. This XML will be parsed and using webservices API, we intend to upload them into the content server.

My question is, is using web services the best method to migrate content or is the Object importer or Syntergys bulk loader a better bet?

If we do zero down on the WS way, any risks we need to pre-meditate?

Regards

Prasad Rao

Find more posts tagged with

Comments

Appu_Nair1

With having no disrespect to WS here's what you will find if you go the WS route

It will work with almost all kinds of just document aspects like folder creation,doc creation a starting livelink company will use nothing mature
You or your developers will have to code for anything other than that like cats/atts,classifications anything relatively concerned with metadata
You will run into serious mapping problems of object types for e.g if DCTM was having Physical Objects you will need to run syntax for those ,mostly you will drive your developers crazy.

WS/LAPI/Oscript cannot be approached without understanding the business rules of livelink.No black box approach hereYou will have to handle errors,retrials counts in counts out all yourself.Not to mention resource allocation of livelink servers you can run your code against.WS/LAPI or OI will finally become oscript and compiled language before livelink will add the objects.If you have a team of strong developers who can understand javadocs and program it away then it may work for you.

Come to OI,OI documentation has easy to understand xml examples any prog language can create XML load files similarly syntergy.Both will continue after failure and expect you to correct error and re-process.Most of the migration projects that I have seen/undertaken alaways amounts to enough head aches on assumptions

I have also used Document Pipelines for LES in which you make proprietary files and uses lapi to pump it in.Comes from the archive side of things and a little more setup to do but it also re-tries on errors.

There is the Genio or OTIC wich I think either uses lapi(or maybe CWS) now..OI is by fars the easiest to setup and run.

Never approach the migration project as a technical problem,you will have the surprsise of your life.

Prasad_Rao

Hi Appu

Thanks for the information provided.

We are looking at using OI module as the primary method of going about importing content.

Other approaches are fallbacks in case of any business decisions made.

We have made a object type mapping which makes this relatively easier for us at this point to proceed, but i understand your point.

Thanks for your inputs, will study this a bit more

Regards

Prasad Rao