To echo Romain's point and add some advice from the trenches: All pool configuration is done in a very simple file, largely negating the need for a console. I think most of the functionality you're asking for is available via JMX. TomEE also has an API for writing your own JMX mbeans to do anything the container doesn't offer by default: http://tomee.apache.org/examples-trunk/mbean-auto-registration
However, TomEE has a different design philosophy than Weblogic. We value minimalism to maximize speed and have only a few MB of RAM overhead per app. Combine that with it's fast boot times, I've always encouraged people run one app per TomEE/JVM instance and leverage your operating system's existing service management facility (systemd, smf), or something like LXC/Docker instead. Weblogic is designed to be a service manager itself, so it comes from a different philosophy of thinking. Monitoring your apps is extremely important for any business. If you'd like to store the JMX information of TomEE, I suggest deploying/securing Hawtio in the JVM and using the TICK stack; Hawtio to expose JMX metrics, Telegraf to poll/transmit those to Influxdb, then graphing them out with Chronograf. Adding Kapacitor allows you to script alerts. I've been meaning to write a blog post about this for awhile since it works exceptionally well. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
