Java Enterprise System in a Zone
By John Clingan on Feb 15, 2005
Matt and I chit-chatted a bit about how he had done it, so I thought I would take a whack at it. Hey, this is The Clingan \*Zone\* after all. I installed much of the Java Enterprise System in a zone. I say "much of" because I am focused on the portal, app server, and web server pieces (and development tools) for two reasons. The first is my own nefarious purposes, the second is to help out a starbucks buddy. If you are interested, there is documentation on how to install in a zone. Be sure to read the documentation for some installation tips.
FYI, the resident set size of the app server in this configuration is roughly 200MB (pmap -x gives pretty good detail). That includes the application server's administration application, the portal server and the access manager. With portal and access manager disabled, the resident set size goes down to 137MB. Throw that in a classroom setting with a team of students per zone, and you see where I am heading (using portal for sizing is overkill ... I doubt any student can write that much code in a semester :) ). On top of the appserver there are web server instances (12MB/each). By default, one for SSL, one for open connections. Only one at a time is really necessary for students, I would think.
Well, that's a quick look at things for my education-focused starbucks buddy. It's a little more complicated than that, but it's time to get some sleep.