Quick HealthScanner Setup:
1) Create a regular PAS instance, for example using the command:
$ pasman create -f -p 8820 -P 8821 -s 8822 %WRKDIR%\oepas2
(the pasoe instance can also be created in the OpenEdge Explorer/Management web interface, or an existing pasoe instance can also be used)
2) Enable HealthCheck feature
$ cd oepas2\bin
$ tcman feature HealthCheck=on
$ tcman feature HealthCheck (this should confirm that the HealthCheck feature is enabled by returning 'HealthCheck=on')
$ tcman config psc.as.healthcheck.port=6899 (otherwise the default HealthCheck port 8899 will be used, the healthcheck port need to be unique for each pasoe instance on the used machine)
3) Enable the data collector in {CATALINA_BASE}\conf\appserver.properties, to read results from the probes from conf\health.config:
$ tcman config psc.as.health.enabled=true
4) Start the PAS instance
$ cd health\bin
$ tcman pasoestart -restart
$ tcman env (this should show a line like: 'manager health port: 6899' confirming that the HealthCheck feature is being used)
5) Run the PAS Health Check web app:
$ {CATALINA_BASE}/bin/oehealth[.bat | .sh] -D
The healthCheck feature requires the manager.war file to be deployed, if not already deployed it would need to be installed as well with a command like:
tcman.bat deploy %DLC%\servers\pasoe\extras\manager.war
./tcman.sh deploy $DLC/servers/pasoe/extras/manager.war
Instances created using the -Z pas or -Z prod security model do not include the needed manager.war by default.
The healthCheck feature can only be used on a pasoe instance created using the -Z pas or -Z prod security model, like this:
pasman create -Z pas -p 8840 -P 8841 mySecuredInst
after an additional webapp is added to that pasoe instance, for example using a command like:
tcman deploy -v -a public %DLC%/servers/pasoe/extras/oeabl.war oeapp1
The different pasoe security models are described on https://docs.progress.com/bundle/pas-for-openedge-management/page/About-security-models.html
If a pasoe instance was created using -Z dev and the installed oeabl.war was later on replaced with noaccess.war using commands such as:
tcman.bat undeploy ROOT
tcman.bat deploy %DLC%\servers\pasoe\extras\noaccess.war
or on Linux:
./tcman.sh undeploy ROOT
./tcman.sh deploy $DLC/servers/pasoe/extras/noaccess.war
Then an additional webapp will need to be added to that pasoe instance as well
Example healthCheck URLs:
http://localhost:6899/health?view=summary
http://localhost:6899/health?view=details
http://localhost:6899/health?view=config
http://localhost:6899/health?view=summary
http://localhost:6899/heatmap.html (this link does not return json data but a graphical representation of the health of the pasoe instance)
Further details about OpenEdge HealthScanner usage are available in the HealthScanner documentation on Progress Documentation HUB.
Manage Progress Application Server (PAS) for OpenEdge: Monitor PAS for OpenEdge instances - Use OpenEdge HealthScanner:
https://docs.progress.com/bundle/pas-for-openedge-management/page/Use-the-OpenEdge-HealthScanner.html
