G
Gareth Vincent
Guest
Thanks for the feedback. After spending quite some time playing around with PASOE there are a few tips I would like to share for those that don't know. Firstly you can monitor and manage the PAS instance with mbeans which is a plugin to Jconsole ($DLC/jdk/jconsole). I discovered this by stumbling across a Power Point presentation that David Cleary compiled. It took me a while to figure out how to get mbeans to talk to PASOE so I thought I would share. Firstly you need to enable a feature called JMXLifecycle by executing the following tcman command: ./tcman.sh feature JMXLifecycle=on or you can edit the server.xml file directly. After enabling the feature you can then use jconsole to connect to a remote or local process with the following string: service:jmx:rmi://10.3.12.16:10002/jndi/rmi://10.3.12.16:10001/jmxrmi. The port numbers are the psc.as.jmxserver.port and the psc.as.jmxregistry.port under the advanced tab of the property configuration of the pas instance. the default login and password is jmxadmin:jmxadmin One of the concern I had was if you are running multiple ABL applications under one instance and you wish to shutdown one of the databases how will this effect the session manager and would you be able to bring up the DB again and re-attach the agents. It turns out this was not a problem. After shutting down then bringing up one of the DB's the agents re-attached after the first client request. There also seems to be a bug in OE Mangement if you try and enable "collect metrics" under the APSV Transport properties. For some reason it doesn't save the new config. As a work around I was able to enable this by editing the openedge.properties file directly and simply add the collectMetrics=1 parameter under .APSV
Continue reading...
Continue reading...