any gotchas I should of aware of when installing unidata?

I am working on an RPM that will install unidata, so as I start down this journey, are there any gotchas other who have gone down a similar path that anyone would care to share?

there will be 2 types of installations .....

1. on a system WITHOUT unidata installed
2. an upgrade of system with unidata

I am going to use the parameter file to automate the installation in both cases and when doing #2 I will stop unidata  before preforming the upgrade

my main question is about the license file (while developing I will be usings the PE version of unidata so no license issue) but in both cases how do I handle the license?

1. do they have to enter  it manually?
2. is there a way to "move" the license from version 8.x.x to 8.2.4?

also on #2 is there an easy way to tell if unidata is installed and running, I suppose I could look for the unidata daemon to see if its running, but if the system is stopped since I do not know what version of unidata is installed is there something I can look for to see if unidata is installed (to try to automate the moving or the license from version X to version Y).

like I said I am just starting this process but any advice is appreciated.

thank you

dougc

Doug,

I don't want you to spend time reinventing the wheel. A couple of releases ago we moved all of the unidata install / upgrade to a script called udtstep (the old methods of updatesys and udtinstall have been removed). Have you reviewed the latest installation manual, as the install and upgrade of UniData is done by a script called udtsetup. The script for udtsetup is in $UDTBIN. The highlights are below.

It allows the 3 type of UniData installs, Upgrade, New and Concurrent  (I noticed you only mentioned 2).
It already allows for a parameter file, with 40 or so parameters you can supply for a silent install.
It has the ability to perform a backup of an previous install for quick restoration. 
There is an optional config file so you can you run your own commands at the end of install.
It works out if UniData is running and shuts it down (also has logic for the unirpcd if UniVerse is installed on the same machine as well)
It also gives you a choice of licencing options including the ability to talk to the RBC licence authorization process.

From reading your post it appears udtsetup is already going to provide you with everything you are aiming to do (and more).

Regards,