I just finished setting up ProTop on server1. It was time-consuming and painstaking, but everything is working great now. How do I make the next install faster? After all, server2 is pretty much the same as server1.
Prerequisites:
- DLC points to the same OpenEdge installation on both boxes
- ProTop is to be installed in the same directory on both boxes
- ProTop is already installed, configured, and running on server1
Steps:
- On server2, start a proenv session
- create the same protop folder as on server1 (i.e. C:\protop)
- cd to your new protop folder on server2
- On server1, zip up your protop folder
- Copy your protop zip from server1 to your protop folder on server2
- On server2, expand your protop zip/tar into your new protop folder
- del tmp/*
- del log/*
- del rpt/*
- del dbanalys/*
- pt3inst
- select (down arrow then enter) the option to install for an existing custid
- If not presented with your custid, enter it
- You will not be prompted to discover running databases, so to discover them run:
pro -p util\xdisc.p
- Edit your custom etc\*.*.cfg files and correct names contained in them to match the names of the resources on this server
- Test each subsystem as you make corrections
Other considerations
SSL - see this ProTop KBase entry on SSL / Secure Sockets Layer for ProTop
Configure any additional monitors for OpenEdge features that were not configured on the server this zip file came from (e.g., replication is used in prod but not in dev/test)
UNIX adjustments:
1. Once you've executed the above steps, persist the running of $PROTOP/bin/dbmonitor.sh in your crontab with a line similar to this:
*/5 * * * * [protopdir]/bin/dbmonitor.sh > /[protopdir]/tmp/cron.dbmonitor.err 2>&1