How do I run ProTop to monitor resources that use different versions of OpenEdge?
For instance, I have an existing installation of ProTop running under OE11.7, monitoring multiple resources like dbs, app servers, etc. We are testing a new PASOE instance, but it and the database it runs against run under OE12.2. How do I tell my existing ProTop installation to run the correct version of OpenEdge for the PASOE instance and its database?
Or, I need to be able to specify a particular set of r-code for ProTop to execute because I have multiple applications that have different DBAUTHKEY requirements.
Do I need to install ProTop a second time to handle these situations? In a word, no.
Starting in version 327, ProTop can invoke resource-specific versions of OpenEdge and provide resource-specific code paths (PROPATH under UNIX or INI files under Windows) for each resource you'd like to monitor on your server.
To allow this, the dblist.cfg file now has a new seventh field called codePath. For Unix this is the PROPATH to use, for Windows it is the name of a .INI file containing the PROPATH (and DLC). Combined with the DLC (fifth) column, this tells ProTop which version of OpenEdge and which set of code to use when starting ProTop Real-Time and when starting the pt3agents that monitor your resources.
The resource definition in etc/dblist.cfg now looks like this:
friendlyName | /dbpath/dbName | serverName | monitor [ | dlcPath [ | type [ | codePath ] ] ]
*NIX example:
test12db|/data/db12/test12|pttestsrv|yes|/usr/dlc122/dlc|?|protop-v12.pl:.
To set this up, add a new line for your resource to your etc/dblist.cfg and specify the dlcPath and codePath columns. Save the file, and the dbmonitor should start a pt3agent shortly.
Here is an example for Windows:
sports117|c:\db\117\sports|WIN10SRV|yes|c:\progress\OE117\||etc\sports117.ini
NOTE: codePath for Windows can be explicit, i.e. c:\protop\etc\sports117.ini or relative to %PROTOP%, i.e. etc\sports117.ini
To set this up:
1. cd %PROTOP%\etc
2. copy protop.ini to a unique name, e.g. sports117.ini
3. Edit sports117.ini and modify DLC and PROPATH in the WINCHAR stanza to specify your custom settings.
4. Edit your etc\dblist.cfg and a line for your resource
5. Specify the dlcPath and set codePath to point to the *.ini you created above. Save the file, and the dbmonitor should start a pt3agent shortly