Deployment topologies
Jazz® Team Server and the associated IBM® Engineering Lifecycle Management applications have three typical deployment topologies and a topology for teams that work and manage their projects independent of each other.
A typical installation consists of the Jazz Team Server and one or more Engineering Lifecycle Management applications. The applications can be deployed on the same application server for small-scale evaluation purposes, or on different application servers for greater scalability and flexibility for future growth. There is one database for the data warehouse and one for each application, including the Jazz Team Server.
To integrate the Engineering Lifecycle Management applications, all of the applications must share a common Jazz Team Server. By using a shared Jazz Team Server, collaboration can occur among applications and a common set of users. A shared server also provides common license administration and common email and LDAP settings. For more information about the advantages of sharing a server, see How many Jazz Team Servers to use.
There are three typical Engineering Lifecycle Management deployment topologies and a fourth topology for teams that work and manage their projects independent of each other. In all scenarios, if Jazz Security Architecture is selected as an installation option, a Jazz Authorization Server must be deployed as well.
Deployment topologies
- Departmental topology
-
Departmental topology is the minimum topology that is suited to any production environment. In this type of installation, databases such as IBM Db2® are installed on a dedicated database server, while Engineering Lifecycle Management applications are installed on an application server except DCC and LQE. This topology uses IBM WebSphere® Liberty. DCC and LQE applications need to be installed on separate application servers. Requiring less hardware and being easier to deploy, you can choose this topology for smaller projects and smaller-sized teams. If you want to expand the deployment essentially, start with a modified departmental pattern.
A modified departmental pattern is a combination of application servers that serves each application with other servers hosting multiple applications. This topology pattern can be used initially or as an interim step towards full enterprise deployment topology based on the application usage and resource availability.
- Enterprise topology
- In enterprise topology, applications are on separate application servers with a single shared Jazz Team Server. This topology provides enterprise-wide support for midsize and large teams that collaborate in a distributed environment. This topology uses WebSphere Liberty server and an enterprise database management system, such as Db2 .
- Federated topology
-
Federated topology meets the needs of the larger enterprises who want to deploy Engineering Lifecycle Management suite applications by their product line or organizational division. The organizations also want to be able to pull together a program-level or enterprise-wide view of their entire portfolio of work, which is achievable by using the federated topology.
The modified federated topology is similar in intent to the federated topology and is implemented with a single Jazz Team Server instance.
Deployment of multiple instances of applications
You can deploy multiple instances of an application, such as the Change and Configuration Management (CCM) application. If you deploy multiple instances of the same application in the same application server, you must give each instance a separate context root. For example, the context roots for two Engineering Workflow Management instances might be ccm1 and ccm2. To connect multiple instances of the Engineering Workflow Management application to a shared Jazz Team Server, the instances must all be authenticated from the same authentication realm and thus share the same users.
Alternatively, refer to Engineering Workflow Management clustered environment to see if the approach to clustering meets your needs.
In any deployment, the licenses are managed by Jazz Team Server. For more information about licenses, see Client access license management overview.
Choosing a topology of your deployment requires considering the future needs as well. Although you can move the applications to other application server later on, the shift requires using a proxy server to maintain links of the applications.