The equivalent of the command line: wtbman -q or asbman -q for the multi-session agent no longer exists.
We have to change our way of thinking with the new Progress AppServer/WebServer; the agent is not a single session as with the classic AppServer/WebServer. For example, if you were to trim a multi-session agent you could stop many (hundreds even) of sessions supporting clients that are working just fine. The emphasis in our tools now moves from agents to
sessions in the multi-session agent.Our Documentation describes operations in terms of
sessions rather than threads:
Pacific Application Server for OpenEdge: Administration Guide, REST API Reference for oemanager.war, Agent management
While pasman/tcman provide information about sessions instead of agents, they don't cover a full roundtrip of how sessions then map to the multi-agent thread.
The management of OpenEdge resources for PASOE can be done either through the OE Browser Console (OEE/OEM), REST API's or JMX API's. The OE Console (AdminServer) uses the REST API tools.
The JMX interface is preferred compared to Manager / OE Manager war files shipped with OpenEdge for security reasons.
Refer to Article
How to monitor Progress AppServer Tomcat with JConsole The REST API depends on the
oemanager.war which should not be used in production, which is why the JMX interface should be preferred.
To enable REST API access:Option 1: The oemanager.war or tcmanager.war must be deployed. To verify this, navigate through the OE Console:
RESOURCES > PAS > <instance> > EXTRAS
Install Pacific Application Server OpenEdge manager web application
Option 2: From the deployed instance directory run:
$ pasman deploy /dlc/servers/pasoe/extras/oemanager.war
Which results in: $CATALINA_BASE/webapps/oemanager
Using REST API Calls in Production:
The default credentials to the
oemanager which you're accessing with curl are
tomcat/tomcat and should always be changed in:
$CATALINA_BASE/conf/tomcat-users.xml
Access to the URL can be limited with the Remote Address Filter in
$CATALINA_BASE\webapps\oemanager\WEB-INF\web.xml
For further information refer to Article
How to configure Tomcat to accept only localhost access for the Manager Application? The command structure is as follows:
/host_name:port/oemanager/applications/<ABL ApplicationName>/...
curl can be used employ the PAS for OpenEdge REST management APIs from command lines or scripts to transfer data.
Examples of REST API Calls using CURL:The most aligned PASOE can be to classic "ASBMAN -query"
curl -X GET -v http://localhost:8810/oemanager/applications/oepas1/metrics
{"errmsg":"","versionStr":"v11.6.4 ( 2017-07-25 )","versionNo":1,"outcome":"SUCCESS","operation":"GET SESSION-MGR METRICS",
"result":
{"requests":26745,
"writeErrors":0,
"reads":1684935,
"concurrentConnectedClients":26,
"maxQueueDepth":0,
"writes":53494,
"maxConcurrentClients":44,
"readErrors":0,
"reserveConnectionTimeouts":0,
"timesQueued":0,
"avgQueueDepth":0,
"type":"OE_BROKER",
"startTime":"2017-12-01T10:37:41.788-01:00",
"accessTime":"2017-12-01T11:01:12.096-01:00"}}
http://localhost:8810/oemanager/applications/oepas1/webapps/ROOT/transports/apsv/metrics
{"errmsg":"","versionStr":"v11.6.4 ( 2017-07-25 )","versionNo":1,"outcome":"SUCCESS","operation":"GET APSV TRANSPORT STATISTICS",
"result":{"statusRequests":0,
"connectRequests":27811,
"sessionErrors":0,
"connectErrors":0,
"disconnectRequests":27788,
"sessionRequests":27804,
"disconnectErrors":0,
"forbiddenErrors":0,
"type":"OE_APSV_TRANSPORT",
"startTime":"2017-12-01T10:37:41.784-01:00",
"accessTime":"2017-12-01T11:01:57.572-01:00"}}
All current Client Sessions in the Session Manager:
curl -X GET -v http://localhost:8810/oemanager/applications/oepas1/sessions
All MSAgent's ABL Sessions including session memory:
curl -X GET -v http://localhost:8810/oemanager/applications/oepas1/agents/22484/sessions
The MSAgent's status and all current requests in the MSAgent
curl -X GET -v http://localhost:8810/oemanager/applications/oepas1/agents/22484/status
curl -X GET -v http://localhost:8810/oemanager/applications/oepas1/agents/22484/requests
