Edit
Attach
P
rintable
r5 - 2013-05-11 - 16:23:49 - Main.sbeard
You are here:
TWiki
>
Deployment Web
>
DeploymentPlanningAndDesign
>
HowManyJazzTeamServersToUse
<sticky><div id="container" > <div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"/> How many Jazz Team Servers to use %DKGRAY% Authors: Main.MichelleDeArmas <br> Build basis: CLM and SSE %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> This topic will help you decide how many Jazz Team Servers to deploy and how to distribute applications among them. ---++ Jazz Team Server options A Jazz Team Server that has more than one application connected to it is considered to be a shared server. Using a shared Jazz Team Server for multiple applications has these advantages: * Central user and license administration * Lifecycle project administration * Improved web-application navigation between applications * A common data warehouse * Fewer administration and configuration duties Use a single, shared Jazz Team Server in these circumstances: * When all users and groups are aligned in a single authentication realm. * When all applications are centrally managed. All of the example departmental and enterprise topologies illustrate the use of a single, shared Jazz Team Server for multiple distributed applications. However, in some conditions, the use of more than one Jazz Team Server might be preferable. Use separate Jazz Team Servers in these circumstances: * When users of different applications must be isolated * When separate authentication realms are used. Each authentication realm must have its own Jazz Team Server because user identities are based on the user accounts in an authentication realm. * When applications would otherwise be widely distributed from the Jazz Team Server, thus resulting in performance degradation. *Restrictions:* * After an application is connected to a Jazz Team Server, the application cannot be connected to a different Jazz Team Server. * Two instances of the Requirements Management (RM) application cannot share the same Jazz Team Server. If you have multiple instances of the RM application, deploy them on separate application servers, each with its own Jazz Team Server. ---+++++!! Related topics: [[DeploymentPlanning][Deployment planning: Where to start?]] ---+++++!! External links: * None ---+++++!! Additional contributors: None <sticky></div></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r9
|
r7
<
r6
<
r5
<
r4
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.