IBM Rational Software

Size: px

Start display at page:

Download "IBM Rational Software"

Justina Ross
6 years ago
Views:

IBM Rational Software Development Conference 2008 Architecture and Customization of the IBM Rational Team Concert Connectors for ClearCase and

1 IBM Rational Software Development Conference 2008 Architecture and Customization of the IBM Rational Team Concert Connectors for ClearCase and ClearQuest John Vasta ClearQuest Connector Lead, IBM Geoffrey Clemm Distinguished Engineer, IBM CRMA38

2 Rational Team Concert: Components Static Analysis Code Coverage Iteration Planning Other Repositories Source Control Team Build Work Items Project Health Connectors Kernel Process Repository Collaboration CRMA38 2 2

3 IBM Rational Software Development Conference 2008 Rational Team Concert: Integrated Workflow Based on Eclipse IDE Integrated SCM Supports parallel development Team Central View Support for iteration plans based on Work Streams for items projects CRMA38 Support for RSS and Atom Feeds Integrated with Work Items Process Entactment Integrated entry level WebUI for Work Build System Items 3 3

4 ClearQuest Connector Architecture RTC Client App Server App Server RTC Client Jazz Team Server HTTP ClearQuest Connector Gateway CQ Client Jazz Repository CQ Database CQ Client CRMA38 4

5 Multiple Team Concert Islands Jazz Team Server Atlantic Nantucket Project ClearQuest Connector Gateway Project Area Filters Nantucket queries Hawaii queries Maui queries Trinidad queries Jazz Team Server Pacific Hawaii Project Maui Project CQ DB Jazz Team Server Caribbean Trinidad Project Tobago Project CRMA38 5

6 ClearQuest with Multisite Jazz Server Atlantic CQ Gateway Project Area Filters Jazz Server Pacific Jazz Server Caribbean CQ Replica 1 CQ Replica 3 CQ Replica 2 CRMA38 6

7 ClearQuest Connector Deployment Apply enablement package to CQ schema Adds record types used for connection metadata Adds hooks to create change event records on commit of connected records Install CQ Connector Gateway Installed on a machine with ClearQuest Only one gateway allowed per user database (across all replicas) Can sync records from any replica (once replicated to gateway replica) Create synchronization rules for connected record types Information from CQ schema available in synchronization rule editor CRMA38 7

8 Mapping Records to Work Items Primary mappings connect CQ stateful records to work items May connect multiple record types to distinct work item types Secondary mappings connect related records Work item categories, attachments, and user accounts CQ record fields map to RTC item properties Flow direction may be in (to RTC), out (to CQ), both, or neither Various data transformations allowed for values None (verbatim copy) Enumeration mapping References to connected objects References to fields in other records Comments and notes CRMA38 8

9 Mapping may be Incomplete CQ is much more flexible than Team Concert Cannot define new Team Concert data types Minimum required fields must be satisfied Some amount of flattening supported by indirect mapping of referenced record fields Different roles for CQ and TC users allows for non-identical data CRMA38 9

10 Synchronization Rules Synchronization rules are defined in Team Concert One synchronization rule per CQ record type Declares corresponding TC item type (if any) Defines mappings between CQ fields and TC properties May be exported and imported Helpful if connecting multiple TC project areas to the same CQ database CRMA38 10

11 Mapping Best Practices Align CQ schema and work item configuration as much as possible Ideally, 1-to-1 mapping between record types and work items types, with same state transitions Determine which CQ record types will be enabled for synchronization One or more stateful type for work items, and stateless types for extra fields Apply the enablement package and start the CQ Gateway first Information about sync-enabled record types will be available in the sync rule editor Start small minimum required properties first Get work item creation working with required properties Get CQ record creation working with required properties Add mappings for non-required properties, incrementally CRMA38 11

12 Mapping to Work Item Categories Category ( Filed Against ) is a required property of work items Categories indirectly identify the team that owns a work item, and therefore the team and project process that will apply to the work item Categories are hierarchical For flexibility, there are three different kinds of mappings: Connection of analogous CQ record (e.g. Project) where the a string-valued field corresponds to a Category path Identify a string-valued field in the work item record where the value corresponds to a Category path Identify references to one or more stateless records having string-valued fields corresponding to Category path segments CRMA38 12

13 Category mapping: corresponding record CQ Records Sync Rules Work Items Defect CQ456 Project: Project_1 WorkItem-Defect WorkItem 123 Category: Category_2 Category_1 MyProject Name: Project_1 MyProject/UI Category-Project Category_2 UI CRMA38 13

14 Category mapping: string field in primary record CQ Records Sync Rules Work Items Defect CQ456 Project: MyProject/UI Category Value Transformer WorkItem 123 Category: Category_2 Category_1 MyProject Category_2 UI CRMA38 14

15 Category mapping: referenced record fields CQ Records Sync Rules Work Items Defect CQ456 Project: Project_1 SubProject: SubProject_1 Category Value Transformer WorkItem 123 Category: Category_2 Name: Project_1 MyProject SubProject_1 Name: UI Category_2 UI Category_1 MyProject CRMA38 15

16 Enumerated Value Mappings Fields and properties with dissimilar enumerated values can be mapped Value mappings need not be 1-to-1 A default value must be specified for ambiguous mappings CQ Priority Work Item Priority Low Medium High CRMA38 16

17 Mapping to Work Item Custom Attributes Work items can be extended with custom, primitive-valued properties String, integer, boolean, timestamp, enumeration, etc. Presentation of custom attributes in the work item editor can be defined CQ fields can be mapped to custom attributes Direct mapping: field in work item record corresponds to custom attribute Indirect mapping: field in referenced record corresponds to custom attribute Display-only aggregate mapping: multiple fields from referenced record mapped to single custom attribute CRMA38 17

18 State Transition Mapping States are mapped as enumerated values State transition graphs must be pretty similar Work Item States New Submitted CQ Record States In Progress Assigned ReOpened Resolved Resolved Opened Closed Closed Verified CRMA38 18

19 ClearCase Architecture UCM Base ClearCase VOB Server Multisite ClearCase VOB Server CCRC/Web View Snapshot View Dynamic View Dynamic View CRMA38 19

20 Rational Team Concert Architecture Jazz Team Server Jazz Team Server Rational Team Concert Client Rational Team Concert Client Rational Team Concert Client Rational Team Concert Client CRMA38 20

21 ClearCase Connector Architecture UCM Base ClearCase VOB Server Multisite ClearCase VOB Server CCRC/Web View Dynamic View Connector Dynamic View Snapshot View Connector Jazz Team Server Jazz Team Server Rational Team Concert Client Rational Team Concert Client Rational Team Concert Client Rational Team Concert Client CRMA38 21

22 Deploying the ClearCase Connector The primary consideration when deploying the ClearCase Connector is performance 2-10 seconds to synchronize a file or directory from ClearCase to Team Concert ClearCase deployment remains unchanged Identify teams interested in using Team Concert Assign each team to a particular Team Concert repository Up to 250 developers in a single repository Assign a set of components to a particular Team Concert team Synchronize each component into the appropriate Team Concert repository CRMA38 22

23 Selecting the ClearCase Stream to Synchronize When possible, synchronize with an integration stream No human actions are then required to make the changes from Team Concert available to the ClearCase developers CRMA38 23

24 Synchronizing with an Integration Stream Jazz ClearCase Synchronized Stream Synchronize Integration Stream Accept Deliver Rebase Deliver Repository Workspace Development Stream CRMA38 24

25 When to synchronize with a development stream If there are stringent pre-op checkin triggers on the integration stream. If a pre-op checkin triggers causes the checkin to fail, the entire synchronization is aborted. If process requires that changes be compiled and test before being delivered to the integration stream (e.g., the rebase before deliver policy is on). If there are a large number of changes being made to the component. The ClearCase stream is locked during synchronization. If the synchronization is with the integration stream, this would prevent the ClearCase developers from delivering during synchronization. But this then requires that the synchronization development stream be periodically rebased and delivered, for the changes to be seen by the ClearCase developers. CRMA38 25

26 Synchronizing with a Development Stream Jazz ClearCase Synchronized Stream Integration Stream Synchronize Accept Deliver Rebase Deliver Repository Workspace Development Stream CRMA38 26

27 Selecting Files to Synchronize Because of the cost of synchronization, by default, a software component in ClearCase used from a CCRC view. If a particular software component is being modified in both ClearCase and Team Concert, select the root directory of that component for synchronization. If a component contains a large number of files: Select a set of sub-trees of that component to be synchronized. When all sub-trees have been successfully synchronized, select the root directory of the component to be synchronized When the root directory has been successfully synchronized, the sub-trees can be de-selected. CRMA38 27

28 Current Status of the ClearCase Connector Compatibility: 7.0 CC Base CC and UCM CC Granularity of Connection: Stream or Branch-Type Frequency of Synchronization: commonly daily or hourly Issues for 1.0: Performance No support for CCLT CRMA38 28

29 QUESTIONS CRMA38 29

30 THANK YOU Learn more at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management Rational trial downloads Leading Innovation Web site developerworks Rational IBM Rational TV IBM Rational Business Partners Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, the ondemand business logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. CRMA38 30

Getting Started with Rational Team Concert

Getting Started with Rational Team Concert or RTC in 16 Steps Kai-Uwe Maetzel IBM Rational Software kai-uwe_maetzel@us.ibm.com SDP 20 2009 IBM Corporation This Presentation is Good for You if You know