IBM Rational Software IBM Rational Software
Total Page:16
File Type:pdf, Size:1020Kb
® IBM Rational Software Development Conference 2008 SDP30: Jazzing Up IT Best Practices from Internal Deployment of IBM Rational Team Concert Doug Weissman – IT Architect, Rational Software [email protected] Cathy Col – Manager, Rational Engineering Services [email protected] © 2007 IBM Corporation IBM Rational Software Development Conference 2008 Agenda Goal of presentation Why did we centralize deployment of Rational Team Concert? A Simple RTC Configuration Considerations for deploying Rational Team Concert Rational Software’s RTC Deployment Benefits, Best Practices, and Lessons Learned SDP30 – Jazzing Up IT 2 IBM Rational Software Development Conference 2008 Goal of Presentation Help you think about how to deploy Rational Team Concert Give you some suggestions as to possible architectures and configurations Discuss some benefits, best practices, pitfalls, and lessons learned SDP30 – Jazzing Up IT 3 IBM Rational Software Development Conference 2008 Agenda Goal of presentation Why did we centralize deployment of Rational Team Concert? A Simple RTC Configuration Considerations for deploying Rational Team Concert Rational Software’s RTC Deployment Benefits, Best Practices, and Lessons Learned SDP30 – Jazzing Up IT 4 s ent rem qui r re rve l se ima Min IBM Rational Software Development Conference 2008 e Grassroot movement to adopt new technology s u e d bl n si “Jazz” adoptiona was rampant ats Rational! ce d y ac e lo ly s p ee a e fr -b d ad ” o lo ne t n g y ow pa s D rt m a o a E p ch p n dly u w frien e s r o , team iv s u ndly t s o r frie 5 a e y lope r c k Deve o o rin b r D a p “ l e l il o g C A Support for distributed development SDP30 – Jazzing Up IT IBM Rational Software Development Conference 2008 Pros and cons of grassroot adoption of RTC PROS CONS People get a feel for how Isolated islands of data easy it is to set up and Lack of security and business administer controls Great as a sandbox learning Harder to impose standards environment Harder to develop continuity plans Appropriate for workitems or Variance in versions of SW across non-source-code assets teams Fewer restrictions in security Lack of centralized administration puts burden on owning team – Control over upgrade backup and restore, 7x24 support, schedule etc. No economy of scale on hardware Decentralization of support requests SDP30 – Jazzing Up IT 6 IBM Rational Software Development Conference 2008 Project Growth Rate at Rational SDP30 – Jazzing Up IT 7 IBM Rational Software Development Conference 2008 RTC Adoption at Rational SDP30 – Jazzing Up IT 8 IBM Rational Software Development Conference 2008 Agenda Goal of presentation Why did we centralize deployment of Rational Team Concert? A Simple RTC Configuration Considerations for deploying Rational Team Concert Rational Software’s RTC Deployment Benefits, Best Practices, and Lessons Learned SDP30 – Jazzing Up IT 9 IBM Rational Software Development Conference 2008 A Simple RTC Configuration Server Web Application Server client RTC Repository RTC Project Area Eclipse client Database SDP30 – Jazzing Up IT 10 IBM Rational Software Development Conference 2008 Initial Rational RTC Deployment Architecture RTC Server DB2 Server Tomcat (1) RTC Repository Port 90439443 Version x Client 1 Unique IP address RTC Project Area (1) RTC Component (1.1) DB2 RTC Component (1.2) RTC Component (1.3) DB2 Instance Port 50000 RTC Database (1) Tomcat (2) RTC Repository Version y Port 90439443 Client 2 Unique IP RTC address RTC Project Area (2) Database (2) RTC Component (2.1) RTC Component (2.2) RTC Component (2.3) SDP30 – Jazzing Up IT 11 IBM Rational Software Development Conference 2008 Agenda Goal of presentation Why did we centralize deployment of Rational Team Concert? A Simple RTC Configuration Considerations for deploying Rational Team Concert Rational Software’s RTC Deployment Benefits, Best Practices, and Lessons Learned SDP30 – Jazzing Up IT 12 IBM Rational Software Development Conference 2008 What to take into consideration Before Deployment Repositories vs. Project Areas Authentication/Authorization Roles and Types of access Hardware and Software Considerations Working with existing repositories Connecting with ClearCase and ClearQuest What edition of Rational Team Concert do you need? SDP30 – Jazzing Up IT 13 IBM Rational Software Development Conference 2008 Repositories vs. Project Areas RTC Repository RTC Project Area A Server Team Area(s) Workitem Categories Application Server RTC Project Area B RTC Repository Core Team Core Application RTC RTC Project Area C Project Area Web Team Web Application Server Team Server Database SDP30 – Jazzing Up IT 14 IBM Rational Software Development Conference 2008 RTC Repository A RTC Repository B Repositories vs. Project Areas RTC Project Area A RTC Project Area A RTC Project Area B TIP Determine whether to create single or multiple RTC Project Area C project areas per repository Single Project Area per repository Multiple Project Areas per repository Tighter controls Looser controls Keep source code confidential Source code is viewable to all users of Each repository has its own security the repository (but write is restricted) domain A user can attach to any Project area Can’t share workitems across Can copy or move workitems between repositories project areas within a repository Multiple repositories with a single Uses fewer server resources project use more server resources than multiple projects per repository Team controls its maintenance All teams must agree to RTC version & schedule maintenance schedule Appropriate for a large team working Appropriate for multiple smaller teams on a single code base - up to 250 working on related projects – limit is still users per repository 250 user per repository Rational has both single and multi-project repositories depending on needs of team SDP30 – Jazzing Up IT 15 IBM Rational Software Development Conference 2008 Authentication vs. Authorization Application Server Authentication = Mechanism to RTC Repository verify identity RTC Project Area Repository Team Area(s) Workitem Category(s) Authorization = Permission to Core Team Core Application access a repository Web Team Web Application Client Access License (CAL) Process-Level Server Team Server Authorization = Permission to access Team Area resources SDP30 – Jazzing Up IT 16 IBM Rational Software Development Conference 2008 Authentication Tomcat Supports authentication using either Tomcat Users or LDAP (but not concurrently) Tomcat Users Less secure Stores account passwords in plain text on the server Other forms of authentication require custom code WebSphere Application Server (WAS) Enterprise level authentication Provides federated repository capability Can authenticate with more than one authority (i.e. LDAP(s), AD and local operating system accounts) concurrently Rational Relies on Tomcat application server to provide authentication with IBM’s Corporate LDAP directory SDP30 – Jazzing Up IT 17 IBM Rational Software Development Conference 2008 Repository-level Authorization Repository Roles and Access Can I get into the server? Each role maps to one or more groups in the external registry JazzAdmins JazzDBAdmins JazzUsers JazzGuests Licensing What can I do when I get there? Developer License Contributor License Licenses for system processes like Build and Connectors Rational Uses internal Account Request database to request access to RTC projects Combination of Developer and Contributor licenses per repository SDP30 – Jazzing Up IT 18 IBM Rational Software Development Conference 2008 Team-Level Authorization Process Roles and Access Within my repository and license permissions, what can I do when I get there? More refined access control to components and functionality Configured in process specifications per project Summary – Types of PermissionsTHIS IS A QUIZ !!! What Authentication controls these situations? You…Client Access License (CAL) Repository-level authorization get a message that your user id is invalid Process-level authorization have permission to create new project areas can close a work item for Core Applications but not for Web Applications can create work items but cannot check in code have permission to modify process specifications SDP30 – Jazzing Up IT 19 IBM Rational Software Development Conference 2008 Hardware and Software Considerations Supportability What Hardware and Operating Systems are you comfortable supporting? Corporate Standards Existing Database Infrastructure Software Licenses Operating Systems Applications Servers Database Capacity Disk Memory CPU IP address space SDP30 – Jazzing Up IT 20 IBM Rational Software Development Conference 2008 Rational Environment Hardware 2 pSeries 9133-55A for both application and database server 8 GB memory – 1 4-core 1.65GHz P5+ Processor Card – 8 146.8GB 10K RPM SCSI Drives (~1.2 TB/600GB mirrored) Software Server – AIX 5.3 (not officially supported) Application Server – Tomcat 5.5 Database – DB2 9.1 Clients – Windows & Linux Allocations for Users Diskspace Baseline of 1 GB of disk space per repository for application files 250 MB of disk space per user Memory 1 GB per repository SDP30 – Jazzing Up IT 21 IBM Rational Software Development Conference 2008 Working with existing repositories Other RTC Repositories You Can Copy and paste any process specifications or synch rules Copy source code Change application servers Migrate repositories from Derby to DB2 or Oracle Move or copy work items between project