Hi All, 

Not sure if this is the correct fourm but out of the choices listed it seemed most appropriate. 

I working on coming up with a way of establishing WebSphere Application Server demand metrics based on industry standards (an example in it's simplest form would be: How many WAS instances or WAS app JVM's per WAS Admin).  So if my team supports approx 180 WAS applications - based on industry - how many WAS Admins should I have and at what point do I onboard additional resources?  Was wondering if anyone has done this and can share their experiences?

Thank you,
Greg

There is no general recommendation, as each environment is different.  Some factors that affect # of administrators:
- complexities of the environments:
   - some have few, while other have many stages in the life cycle of the application from development to test to production.
   - some only have web apps and JDBC, while others use all the programming models including messaging, dyna cache, Scheduler, etc.
- how much automation is in place: obviously the more automation the fewer administrators needed.
-self service: the more the users can self manage the environment, the fewer administrators are needed.  Some have invested in infrastructure to automatically create/destroy environments quickly to facilitate self service for test organization. Others are still building custom environments by hand.
- monitoring: some have monitoring products used in conjuction of WebSphere to proactively identiy issues before they become problems. Others do not.
- Qualities of the applications: some have mature applications, others have fast changing and potentially buggy apps that cause problems

By the way, here is the thread for websphere administration:
www.websphereusergroup.org/go/forum/view...