Home » discuss » Public forums » iMIS Community

eCM to WCM migration tool documentation

Posted June 28th, 2012 by etarasew
| |

We have a client who's moving from eCM to WCM (10.6 to 15.2). I'm running a migration test and running into a series of errors (some of which I've overcome/fixed, one I'm still stuck on). Outside of the information on iMIS docs, is there any other documentation on the tool?

I've run the tool a couple times (for multiple clients) and I think it has some wonderful, time-saving qualities. Each attempt has shown a different derivation of success. I would like to get some more background on it though and especially during these troubleshooting times, more information would benefit me tremendously.

I do have a ticket into ASI, but haven't heard anything back yet.

‹ How to Redirect User when Login for first timeExpirationDate column set up 5 yrs on new logins ›
login or register to post comments | printer friendly version

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Response... or was it?

On June 28th, 2012 etarasew says:

I did receive a response, however, it was severely lacking. A link to the 15.1 documentation was not what I was looking for... oooh, boy.

Hopefully, I can get some decent and useful responses from the imis community! Here are the questions I have specific to the migration tool:

  1. Where are the content, navigation and site definitions for WCM stored in the database (what tables)?
  2. Is there a search functionality within the content designer? (i'm pretty sure I know the answer to this one, but it doesn't hurt to ask)
  3. The migration tool is creating duplicate content items (in some cases many of them), this is a problem as they all have the same published content name (I will be creating a separate ticket for this issue).
  4. The initial error I ran into (and have seen a couple timses): "There is already a version of this document in the process of being published". what would be the cause of this error and how can it be avoided? I think this is just a case where the publishing service has two or more content items queued up from the previous issue.
  5. Can we skip over 'trouble' content items (addressed by name or id)?
  6. With regard to the error "String or binary data would be truncated". Is/are there a field(s) of eCM meta data that is larger than its WCM counterpart?

Thanks in advance for any assistance.

login or register to post comments

Yes it can be tricky

On June 29th, 2012 bswetnam says:

I have done several of these and they can be a pain. Gotta love the response from ASI.

So what version of sql are you trying and what version of IMIS.

You can start from scratch with you db. makse sure it is upgraded with no errors.

You can also purge the PUblish server requests from the DB, before you run your migration.

So for your questions.

1. DocumentMain is where the coontent resides, sites are in websites, Navigation is in the root heirarchy.

2. Unfortunately no

3. Try this from a fresh upgraded DB.

4. Purge all the  publish requests prior to Migration

5. No, they have to be resolved

6. No they should not be being truncated, unless the field lengths were modified in that past manually.

 

Let me know if you need more clarification

Broc

login or register to post comments

thank you

On June 29th, 2012 etarasew says:

Broc,
Thank you for your reply - very helpful information.

  1. This makes perfect sense! I would definitely be looking for WCM or CM content in a table named DocumentMain!</sarcasm> I actually see quite a few 'document types' here, is there a location holding a breakdown of the different DocumentTypeCodes and what they mean? (some i can gather)
  2. that's what I thought
  3. The database was freshly updated - this is my testing grounds, very little was done on this particular db
    • I left it alone, for a day, and today none of those duplicated content items are there.
    • I'm not aware of anyone who worked on the database/content
    • While pleased, I'm also quite baffled by this and will try it again soon
  4. you're referring to the publish requests on the eCM content? I'm not aware of anything that was outstanding - is there a way to set that via sql?
  5. I suppose once we identify any trouble content, we can note and delete the content prior to real migration
  6. I do not know what could've caused this error and the tool to stop running. After a closer look at the repeated messages, the ID was changing on subsequent runs, but the content name was the same. kicking off the tool a couple times and we've got a migration tool win!

Thanks for the help and giving me something to work with. (btw, I did get a more complete response from support once I pointed out that I had actually read through the limited documentation).

login or register to post comments