We are migrating from 8009 to 8201m. The 8201m Migration guide talks about moving from 77 to 82- but does not talk about 80x to 82.

1. When moving from 80x to 8201m, should the migration utility be used, or should a CM package be used?

2. The examples in the Migration manual for the utility refer to domains and groups, which are WF77 and below MRE concepts- do these correspond to 80x (content) folders?

3. If the Migration utility is used, there appear to be three options for import: Skip (not sure why you would want this), Add new resources (do not update) and Add new resources, and update existing- anyone have any experience with these options?

Thanks in advance...

This message has been edited. Last edited by: FP Mod Chuck,

Hey sh98110,

Check this link out. It has upgrade planning for your scenario (close to it).

https://webfocusinfocenter.inf...om/wfappent/upgrade/

In regards to your other questions:

1. There are quite a few steps involved due to changes that happen in your repository, etc. I would see if IBI would be willing to do a remote session with you to help you get upgraded. Just get in contact with them.

2. The 7.x MRE domains and groups concept does carry over (sort of) to the 8.x era. In 8.x you'll manage user administration through applying roles to security groupings tied to your domain resources. I would read up on that.

3. If you are simply moving content from an 8.0.09 release to a new clean 8.2.01M release, CM packages should suffice for you. Keep in mind, you should be fully aware of how to configure your "Scenario" when creating your export package, and deciding on how to import what is contained within your import package when you are ready. I would read up on that too before attempting. Pay particular attention to when it is useful to "retain handles" in your scenario, etc. When importing, you'll probably what to choose add new/update existing if your new environment has content in it already and does need to be updated with what you are bringing over. If you choose add new only, you'll bring over your 8.0.09 content and not effect existing resources or rules in place.

Hope the above helps.

FYI - We used the migration tool to create our 8201m environment from 8009 and so far in testing, everything worked out.

One thing that got past me was that HTML Docs have a 2nd step in the migration. After the repository is migrated, each HTML Document must be opened and saved without making changes to them.

Open up the document, give it a few seconds to update the repository, you'll see the * show up in the tab when their internal update is complete. Then save the document without making changes and close it.

Then you are good to go.

i have been doing CM package's and moving content from 8.x and to higher versions and it worked fine. i have tried this in many projects and this seems to give me a good result.

if you are less than 8, then you can think of migration utility.

quote:

Each HTML Document must be opened and saved

An organization may have a couple of hundred HTML documents, with many in users private or shared folders...

Francis,

I'm with ya. Luckily, from what I've seen, if you are moving from an 8 release to another 8 release, HTML pages still work, they just can't be trusted to be edited after and you know what exactly the tool changed without telling you...

quote:

... One thing that got past me was that HTML Docs have a 2nd step in the migration. After the repository is migrated, each HTML Document must be opened and saved without making changes to them.

Open up the document, give it a few seconds to update the repository, you'll see the * show up in the tab when their internal update is complete. Then save the document without making changes and close it.

Just to be clear here- your are referring to HTML launch pages, that you must open in 8.2x AppStudio, and then SAVE without making changes (and not other types of HTML documents).

Thanks, Steve

quote:

Originally posted by CoolGuy:
Hey sh98110,

Check this link out. It has upgrade planning for your scenario (close to it).

I started with the doc- sadly, it seems 7x specific (see following note).

2. The 7.x MRE domains and groups concept does carry over (sort of) to the 8.x era. In 8.x you'll manage user administration through applying roles to security groupings tied to your domain resources. I would read up on that.

With 7x to 8x, you could check the properties, and get the HREF of the folder you wanted to a partial (single domain, for example) migration. There is NO HREF in 8x- it is all repository based: "IBFS:/WFC/Repository/madpoduc/std_reports/... blah blah"

Hey Chuck, do you know if this is possible, or should I open a case?

Thanks all that have responded thus far.

s

quote:

Just to be clear here- your are referring to HTML launch pages,

Right, any HTML doc that you expect to open in the GUI.

Steve

If I understand the question I think you can create a change management package where you navigate to the content folder and choose individual items whether it be html, fex etc.