The oemanager app in a PASOE (Progress AppServer for OpenEdge) provides information about instance and the ability to manage a running PASOE instance. The oemanager webapp needs to be deployed in order to use the following scripts. Please refer to the OpenEdge documentation for details.
In Consultingwerk/Studio/bin you'll find the following scripts:
|scl-pasoe.cmd||Main script and is used by all the following wrapper scripts|
|scl-pasoe-trim.cmd||Wrapper script that trims the agents.|
|scl-pasoe-query.cmd||Wrapper script that shows all information of the following scripts.|
|scl-pasoe-metrics.cmd||Wrapper script that shows the metrics.|
|scl-pasoe-agents.cmd||Wrapper script that shows information about the agents.|
|scl-pasoe-sessions.cmd||Wrapper script that shows information about the sessions.|
|scl-pasoe-clients.cmd||Wrapper script that shows information about the clients.|
|scl-pasoe-applist.cmd||Wrapper script that shows all applications.|
|scl-pasoe-trackablobjects.cmd||Wrapper script that shows all ABL trackable objects|
|scl-pasoe-agentrequests.cmd||Wrapper script that shows all Requests for a given Agent|
|scl-pasoe-agentsessions.cmd||Wrapper script that shows all Sessions for a given Agent|
(The LINUX scripts equivalent are available too in Consultingwerk/Studio/bin)
The scripts support both http and https connections. The scripts will first try to establish a connection to the appserver using http, if that fails, the scripts will retry using https. There is no need to supply a parameter for a secure connection.
-s is mandatory the other parameters are optional. If not supplied the default values used are -h=localhost, -a=root, -u=tomcat and -p=tomcat. The parameters can be supplied in any order, have to begin with the indicated letter and are not case-sensitive.
When -debug is added to the script's parameters, the script will display the PROPATH on startup.
Tracking ABL Objects
scl-pasoe-trackableobjects.cmd has additional parameters, because the Appserver Agent PID needs to be specified as well as the tacking options [on|off|status|report]
Trackable Objects has to be explicitly turned on before usage. The status can be queried with -tracking status
A report about all trackable ABL objects is opened in the default browser to display the ABL Trackable Objects information in Json format.
When -tty is specified the console is used for output.
Please take a look at https://knowledgebase.progress.com/articles/Article/New-ABL-Objects-Tracking-REST-API-under-PASOE for more information on ABL Object Tracking.
Trim agents of a local PASOE running on port 1234, in application 'develop'.
Show all available information of the 'root' application on the PASOE that's running on port 9876 on server with ipaddress 126.96.36.199. The oemanager username is 'admin' and password is 'welcome'.
Display Active PASOE Sessions.
Display active Agents.
Display Agent Sessions.
Display Agent Requests.
Activate tracking for PID 20140
Deactivate tracking for PID 20140
Console report on used objects per session
When -console is not supplied at the command line, the default browser is opened to display the ABL Trackable Objects information in Json format.
How does it work
The script calls Consultingwerk/Studio/Pasoe/scl-pasoe.p which is a wrapper for class Consultingwerk.Studio.Pasoe.PasoeManager.
When a command is used which uses the -a parameter (application name) the available applications will be queried on the pasoe instance.
When for instance there was a problem with the deployment of the instance and no applications are deployed the script returns the error :
"No applications deployed on pasoe instance"
When an application was supplied with -a but it's not found on the instance the following error is returned:
"Could not find application '<name>' in available applications: (With a list of available applications)"
When the user name and password are not correct the following error message is returned:
"Not authorized, check user name and password"
When the oemanager.war is not deployed (like on a production system) the following error message is returned:
"Please check if oemanager.war is deployed"
When a command is executed which uses the -agentpid parameter to identify a process the process ID is verified before executing the command.
If there are no agents available the script will return error:
"Could not find any agent"
When the script could find agents but not the chosen one the script will return error:
"Could not find agent '<agentpid>' for application '<name>', available agents: (With a list of available agents)"
In all other error situations the http response status code and reason are displayed.
Please note that the scripts will first try to establish a connection using http, when that is not a success, the request is repeated using https.
This is shown in the error message:
Error (0): Trying http connection:
Error (0): Connection failure for host localhost port 4812 transport TCP. (9407)
Error (0): http://localhost:4812/oemanager/applications
Error (0): Http failed, trying https connection:
Error (0): https://localhost:4812/oemanager/applications
Error (9318): Secure Socket Layer (SSL) failure. error code 0: Unknown SSL error (9318)
Error (9407): Connection failure for host localhost port 4812 transport TCP. (9407)
During initialization of the scripts there is a check if <DLC>/tty/netlib/OpenEdge.net.pl can be found, if this is not the case the script returns the following error:
"Cannot locate OpenEdge.Net.pl in '<DLC>/tty/netlib/OpenEdge.net.pl' please check your OpenEdge installation"
First it's checked if <DLC>/gui/netlib/OpenEdge.net.pl is available on the system. When that is not the case then it's checked if <DLC>/tty/netlib/OpenEdge.net.pl is available on the system.
If both are not available on the system the following error is returned:
"Cannot locate OpenEdge.Net.pl in ''<DLC>/gui/netlib/OpenEdge.net.pl' or ''<DLC>/tty/netlib/OpenEdge.net.pl' please check your OpenEdge installation"
If either one is found on the system, this library will be used by the scl-pasoe scripts.