WELCOME!!!
Welcome to a new forum here on Jazz.net. This forum is dedicated to the BIG issues around the deployment of the Jazz technologies. I expect a conversation and discussion of topics that are important to Jazz solution architects, Jazz Administrators, and people looking at how Jazz can benefit their organization at a big picture level.
We have created this forum because our other forums tend to focus on issues at a user level, or maybe even at a project leader level. We felt that it was important to capture the comments, questions and discussion around some of the enterprise issues. I fully expect to see posts on things like:
So dive right in and start posting your questions and observations on Enterprise Jazz deployments!!
We have created this forum because our other forums tend to focus on issues at a user level, or maybe even at a project leader level. We felt that it was important to capture the comments, questions and discussion around some of the enterprise issues. I fully expect to see posts on things like:
How to deploy Jazz applications in secure environments
Use of reverse proxy servers
Use of SCM content caching servers for remote users
Discussion of HA and DR scenarios, use cases, and solutions
Discussion and contrast of different deployment solutions (WAS or Tomcat?)
Backup and restore scenarios
Planning your URI names
Use of virtual solutions to support a Jazz solution
Reporting support
So dive right in and start posting your questions and observations on Enterprise Jazz deployments!!
2 answers
With just RTC a load of 500 developers can be deployed on a single server with no issues, assuming that the server is not under-powered. For CLM (RTC+RQM+RRC) I would suggest working with your IBM sales team to get a good sizing through Techline. Depending on usage models and plans for later growth it might be advisable to deploy on more than one server.
If you are deploying on a single server, it is always a good idea to use a reverse proxy so each application (JTS, CCM, RM, QM) has it's own unique base URI. That way even if you deploy on a single server, your base URI's would make it look like the applications are deployed on different machines. This allows you to break things apart later if you need to.
If you are deploying on a single server, it is always a good idea to use a reverse proxy so each application (JTS, CCM, RM, QM) has it's own unique base URI. That way even if you deploy on a single server, your base URI's would make it look like the applications are deployed on different machines. This allows you to break things apart later if you need to.