Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Migrating from CE10 to BOEXi

Status
Not open for further replies.

eo

MIS
Apr 3, 2003
809
Hi

A few years back we migrated from CE9 to CE10. The board process followed by the consultancy which did the migration was to load the application to the new server, copy the File stores from the CE9 env to the CE10 env, and pointing the file input server and file output server to this file store.
We now need to do the same from CE10 to BOExi. I am just not sure when the most effective route is to follow.
If I follow the same route as above, does it simply create reports, and historical instances from the old system within the new?
How to get the remaining set-up into the new system (such as folders, groups, access, etc)?
Will the fact that reports are CR10 not matter when opening in BOExi?
Is the import wizard generally a preferred option?
Is there an easy way to migrate all the system ODBC connections?

Any help or advise greatly appreciated.



EO
Hertfordshire, England
 
Hi,
I am surprised that the process you followed before worked at all..
The information about reports ( including the ID, the folder it is in, what access rights are granted, etc - in other words, all the stuff you see in the CMC) is stored in the CMS ( the database formerly known as the APS ) so just 'pointing' the Input and OUtput servers to the correct file system location should not have worked unless you also copied/reused the same database..( I have to assume you did, since it worked)..

The same process can be followed to move to XI, but I would rather create the new system and a new CMS database, establish a new set of FRS locations ( for Input and Output servers to 'point to' ) and then use the Import Wizard to bring in the information from the existing system.

After testing by you and your users,if all is well, you can then take down the original one..

As for the ODBC stuff, they are server-specific ( that is one reason to avoid them where at all possible to do so)so you will need to recreate them on the new server ( use the same DSN names to avoid having to do a 'verify database' or 'set datasource location' on every report whose DSN name no longer exists)




[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
You are correct. The Database was copied as well. I just though they followed the non-standard route because the import wizard did not bring all across.
Thanks for the advise.

EO
Hertfordshire, England
 
Hi

Assuming the best route to follopw is via Import wizard, I have a related challenge.

We set up a secondf server as a test environment. I am in no "mood" to re-do the who installation when we move this test environment to a live environment. How do I clear down everything except the "shell".
I.e. delete all reports, users, groups, etc, and reimporting a more updated set from using the Import wizard? Although I can manually delete this all, does it remove them from the Xi database?

Many thanks,

EO
Hertfordshire, England
 
Hi,
Just create a new CMS database for the 'live' system..recreate the various servers and then import from the source..



[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
One of the things that I've run into with the Import Wizard is that if I use it to copy our whole system from one server to another, the report files don't get copied to the destination file repository - whether I do the import server-to-server or through a .biar file. I've had to break it down into sets of about 100 reports.

However, with the exception of that issue, I've had really good results with using the Import Wizard to copy the setup from the Dev server to the QA server (we're not in Production yet...)

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top