This content has been marked as final. Show 5 replies
This is the official product documentation:1 person found this helpful
and this is the migration guide:
P.S.: if you don't have other 'constraints' I strongly suggest you to quickly move to a more recent version (ODSEE 220.127.116.11 or even OUD)
Thanks very much !!
I can not move to the latest release since there is a dependency on the Websphere Application Server(WAS) version.
Please let me know if there is a tried an tested approach for this migration process apart from that mentioned in the migration guide
Moving to Patch 6 is tested and more than recommended approach due to inherent security holes in Patch 4. I believe this was suggested long back, and various organizations have already performed it. Go ahead and apply this patch w/o any further delay.
The steps as outlined in the doc are pretty straight forward, stpes might vary based on environment setup, however as far as patch is concerned, everyone has to follow the basic as suggested.
Edited by: John Prince on Oct 15, 2012 10:09 PM
I've done this migration quite a few times, including for some large customers.1 person found this helpful
First off, I'm a big believer in not using the migration scripts at all. This is for several reasons:
1) Look at the release notes and migration guide. Find the list of stuff the migration tools don't migrate. If you have anything configured in that list, you're doing a manual migration anyway. You may as well go soup to nuts and do it right.
2) Can you configure your current Directory installation from scratch, parameter by parameter? If not, you shouldn't be doing anything to it besides studying it. If you can, then you should be able to configure the new version similarly.
3) New version means new features. How can you assess which new features will benefit you if all you do is blindly migrate your old configurations?
That's my $.02.