A customer's question:
How do I know when my Jazz server is reaching its capacity?
By the way, although this question was answered specifically for capacity expansion of the IBM Rational Team Concert product, it would generally apply to the other Collaborative Lifecycle Management products as well.
There are actually several things in play when trying to decide when to split off yet another CCM (Change and Configuration Management) application instance.
1. Can I start all new component developments, projects and activities that are loosely coupled from those resident on other CCM instances:
This is because sharing of components, plans, and work items is harder and less visible across CCM project area and server boundaries.
You need to take into account when new project areas should originate on a new server rather than be a part of an existing project area or server.
2. Can I merely grow the current CCM by moving it to a more powerful virtual or physical system and maintain and grow my current project area structure?
Remember the application server HOSTNAME and publicURL has to be maintained but otherwise you can change out the actual physical and virtual hardware (renamed to the same HOSTNAME) and keep on expanding your current CCM system.
3. Do I also need to expand my number of JTS (Jazz Team Server) application servers at the same time because its capacity has also been reached?
There is a limit of ~2000 concurrently active users that can share a single JTS server (on a midrange server) as well that must be considered.
I would monitor the CPU utilization and the java heap utilization on the CCM and think about creating the next project area on a new CCM server when you have reached a high water mark (averaged across several minutes) of 50 to 70% CPU utilization depending on how dynamic your utilization is. The more volatile it is, the sooner I would stop adding additional projects to that server. Just make sure that the allocated heap memory is much smaller (by 1-2 GB) than the physical server memory (assuming only a CCM server is running on that system) and is staying no more than 70-80% allocated.REMEMBER that project area movement from one CCM server to another or from one JTS server to another is not supported. Growth should be done as you are adding project areas and keeping room for internal project growth as you allocate projects to servers.