There are many configurations that you can use when deploying the CLM products on a single web application server.
When you are doing this, there are a number of best practices to consider:
When you are doing this, there are a number of best practices to consider:
- Create separate virtual hostnames for each of the application instances so that the publicURL can be preserved when that application instance needs to be split out on to its own separate hardware server.
- Although it is possible to host multiple IBM WebSphere application server profiles or multiple tomcat servers (each running its own JVM on a separate port), these applications can all be run on a single profile or tomcat server and share the JVM resources. This is much more memory and CPU efficient than running four JVMs and having the operating system schedule and switch among them.
- If you are stuck with multiple applications having the same host name in their respective publicURL, there is a way using a HTTP server as a reverse proxy to steer the application requests to separate back-end application servers. In fact this is a common configuration for very large Jazz installations such as the one hosted on jazz.net.
When you are starting with a concurrent active user load of under 100, you can comfortably deploy all of the applications on a single mid-range 64-bit hardware server with multiple CPUs and 6-8GB of memory on a 64-bit operating system. This assumes that the Rational Reporting for Development Intelligence and all of the databases are hosted on other servers. As your concurrent active user load increases you can split out the CCM (Change and Configuration Management) application if the growing segment of user load is using work items, planning, or source management functions. You can split out the QM (Quality Management) application if the growing segment of user load is authoring tests, doing test planning, or executing manual or automated tests. You can split out the RM (Requirements Management) application if the growing user load is defining requirements, story boarding, business process diagramming, managing requirement collections, and setting requirement attributes and link types. As the total concurrent user population increases across the board, you may want to host the JTS (Jazz Team Server) on its own hardware server to permit full capacity growth.
The bottom line is that you can start small on a single application server and migrate to larger and more distributed hardware as your user load increases.
See the CLM 2011 Sizing Guide for more information ( CLM 2011 Sizing Guide ).
