| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
I am preparing an upgrade plan for my Exec Office of President customer going from ALL-IN-1 V2.3 and ALL-IN-1 V3.0. This customer has a lot of customizations in the base kit as well as standalone customizations on their current V2.3 system. They have never upgraded before and are very sensitive to any system down time. Fortunately the customer has a test VAX system, where I have been moving all the customizations and making modifications to the base kit. I read Tony Redmond's book concerning upgrades. He stated that if you build your system on a test system. You can bring over the new V3.0 system to your operational system and then run the post install (A1$POSTINSTAL) procedure on the operational system to update user profiles... printer tables, etc. Question: 1. We started with a new ALL-IN-1 V3.0 system on the test VAX and have been moving over customizations from operational system as well as recustomizing site elements for elements with required and recommended changes via the CART which we ran on their V2.3 system. My question can I move over this ALL-IN-1 installation (ie all the scripts, files, forms for the customizations) and then run a post install that I modify to reflect differences in disk names etc? Any experience with this? Any other guidelines? Tony Redmond said you can do this however he indicated that you need to do an upgrade on the test system and move the upgrade over and then run post install. Can I do this with a fresh installation? 2) Or do you recommend an upgrade on the operational system and moving over the modified site log etc? Any recommendations? 3) The customer is very sensitive to down time. ANd since we are doing this over a weekend window, I need as smooth a upgrade path as possible. They will also need time to check out their customizations before going live on Monday morning. Any guidelines here? A successful upgrade plan that someone has used? Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2496.1 | Upgrade strategies a bit like religious beliefs | AIMTEC::WICKS_A | Oscar the Grouch is an Optimist! | Tue Mar 30 1993 17:46 | 23 |
Reda,
will Tony be providing weekend coverage for this upgrade? (:==:)
I would strongly recommend that you call your friendly local CSC for
advice on this upgrade or if you have access to STARS search the OA1
database for articles on v3.0 upgrades particularly an excellent
article written by Sam Burgess on things to watch out for
that has has been updated in light after all upgrades we have witnessed.
we also have articles and information on transferring customisations from
the test system using Package Application and then using Restore
Application on the newly upgraded production system which has proved
successful for a number of customers.
As always you can call us before the upgrade or as i'm sure you will
during and after the upgrade (:==:) - or as it's you you may call me
or mail me directly since I am now once again restored to ELF as a listed
employee.
Regards,
Andrew.D.Wicks
| |||||
| 2496.2 | The author replies | SIOG::T_REDMOND | Thoughts of an Idle Mind | Wed Mar 31 1993 13:39 | 31 |
I hope Mr. Clinton is happy after the upgrade, and no, I am not
available to support the upgrade as I am not technically allowed
anywhere near the site (not being a U.S. citizen).
Anyway, I hope that the book was useful (even as a paperweight). My
view is that you should get all the customizations working on the V3.0
test system, just like you are doing now, then package them all up
using CM. You're now in position to restore the customizations when
the target system is ready.
To prepare the target, perform an upgrade as normal, making sure to
move all the mandatory changes out of the way first. Then delete all
of the customizations from CM, and recompile the TXLs. You should now
have a V3.0 system that has access to all the data but is in an
uncustomized state. Exit from ALL-IN-1 to make sure that you're not
picking anything up. Of course, you also want to make sure that you've
installed all the patch kits!
Enter ALL-IN-1 again, and go into CM. Import the packaged saveset that
you prepared on the pilot system, and then use the Restore Application
functionality to unpack all of the customizations and receive them onto
your system. After the restore is finished you should find that all of
the customized elements have been created from scratch in CM. You must
move them into the live area before users can access them.
Differences in disk names shouldn't be a problem, because CM uses logical
names everywhere.
Does this make sense?
Tony
| |||||