IBM Rational Software

Transcription

1 IBM Rational Software Development Conference 2008 Introduction to the Jazz Technology Platform: Architecture Overview and Extensibility Alfredo Gutiérrez Program Director, Technology Events, IBM Rational Copyright 2008 IBM Corporation. All rights reserved.

2 Agenda and Objectives We will cover: Jazz Objectives Jazz Platform Architecture Jazz Platform Extensibility Future thoughts. We re not done yet Introduction to Jazz Architecture 2

3 Objectives/Architecture Requirements No boundaries between people Data and tasks from one tool are seamlessly visible in others Creative Collaboration across geography and organization Tools live the process Capability is strong but unobtrusive Support wide range of configurations Need modular, composable solution Stay flexible Introduction to Jazz Architecture 3

4 Think differently Current approaches for building tools don t go far enough "We can't solve problems by using the same kind of thinking we used when we created them." A. Einstein Introduction to Jazz Architecture 4

5 Think differently Desktop/Database Integration Global Integration Function First Team First Manual Process Aware & Transparent Pre-determined Tool Function Dynamically Extensible Proprietary infrastructure Internet Standards Rigid Process Creative Collaboration Introduction to Jazz Architecture 5

6 Jazz Architecture Eclipse Client Platform (RPC) Project and Team Structure Event Notification Process Enactment Web Client Platform (AJAX) Storage Security and Access Jazz Collaboration Server Visual Studio Client Platform Search Conversation Rational ClearCase Defects Requirements Use-cases,.. Jazz Repository Items and relationships Event history, Item history trends.,builds Source code, Test-cases Test results Rational ClearQuest Introduction to Jazz Architecture 6

7 Extending the Jazz Platform Understanding jazz.war App Server /jazz/* Jazz.war Jazz Server Provisioner Equinox Framework /jazz/service/*../iworkitemservice../ifilesystemservice../iplanrestservice /jazz/web/*../workitemview.js../planview.js Equinox Bridge Servlet Team Services Team Web WorkItem Services Planning Services WorkItem Web Planning Web SCM Services Introduction to Jazz Architecture 7

8 Jazz Server Kernel Team Repository Services Provides the basics for querying, fetching, and updating repository data Provides a platform for extensible AJAX Web UIs Provides support for change events and feed rendering Provides access to and manages component services Process component. Provides: projects, teams, and process. Runs in an OSGI environment Web UI Jazz Server Extensions Jazz Server Kernel Eclipse Equinox Jazz Team Server Container (Jetty, Tomcat, WAS) You can create a process aware services that enables itself to be governed by process. Introduction to Jazz Architecture 8

9 Jazz Platform - Service programming model It s stateless services all the way down Services are contributed by bundles Statelessness is key to scalability All state is in the DB, all client interactions are atomic Clusterable and restartable No session state (clients are stateful) Introduction to Jazz Architecture S 9

10 Jazz Platform repository data model three logical DBs in one An open-ended item store Stores structured items as XML Stores arbitrary content as BLOBs Operational DB A declarative indexing story to support query Lucene text index to support full-text search A snapshot framework for extracting summary data for reporting Cognos BIRT get put Item store (private) indexer Highly Optimized Relational DB Index data (extracts queriable portion) extractor Data Warehouse (public reporting DB) Data warehouse DB Introduction to Jazz Architecture S 10

11 Jazz Team Server - Self-Serve Administration Introduction to Jazz Architecture 11

12 Jazz Team Server - Authentication and Permissions App Server Authentication Corporate Directory server LDAP import Jazz Team server Repository Permissions: (Managed by your IT department) -Admin -Writer -Reader Process Permissions - team-managed - role-based - dynamic Repo DB Introduction to Jazz Architecture 12

13 Process basics Teams work on projects Each project follows a process Work inside the scope of a team follows the team s process Team members play roles defined by the process Process manifests itself through artifacts types, operations manipulating the artifacts, and artifact change events Introduction to Jazz Architecture 13

14 Configurability through Process Allows team specific work products and behavior Allows team specific conditions under which client-side and server-side operations are allowed to proceed Allows team specific participants for client-side and server-side operations Allows team specific reactions to server-side change events The Jazz Platform itself is artifact and process neutral Its the components that explicitly introduce the specifics of process configuration Enabled Rational ClearQuest Rational ClearCase Enabled Rational Team Concert Enabled Rational Build Forge Enabled Subversion Introduction to Jazz Architecture 14

15 Example: Finding the Right Process (the Jazz Process) 1 Jazz Project area defines process 2 Jazz team area does not customize the process 3 Process team area customizes the process Myth: Developers hate process. Truth: Developers are ok with process if they defined it and it helps them get their work done. Introduction to Jazz Architecture 15

16 Process Execution Flow Client Server Component Process Component Process Client Request Handle Request Preconditions Permissions Server Request Preconditions Permissions Handle Request Follow-ups Request Response + Process Reports Follow-ups Process Hints Enforced Process Rules Introduction to Jazz Architecture 16

18 The Jazz SDK and Jazz Labs Two evolving sources of information for Jazz extenders on Jazz.net SDK is the primary source, the essential stories for extending the platform (wiki RtcSdk ) Jazz Labs is more experimental (wiki JazzLabs ) Introduction to Jazz Architecture 18

19 Anatomy of a Jazz Component Jazz Wiki Component wiki.client.jar wiki.common.jar wiki.server.jar wiki.web.jar Client library Services / REST* Storage model extension Web extension Any of the three or any combination *Representational State Transfer Jazz Eclipse Client Bundle based programming model. Jazz Web Client AJAX based Jazz Team Server Introduction to Jazz Architecture S 19

20 Client Applications Java Client Jazz Client Extensions Jazz Client Kernel Jazz Client Kernel Provides access to and manages repository connections Provides the basics for querying, fetching, and caching repository data Provides access to and manages feed subscriptions and feed data Provided access to and manages client libraries Provides the notions of projects, teams, and process Runs in OSGI environments such as eclipse RCP and in plain java clients Jazz UI Foundation Basic UI building blocks for Jazz Eclipse Client Jazz client extensions Jazz Client Extensions Client libraries UI or UI extensions Jazz UIF Jazz Client Kernel Eclipse Platform Introduction to Jazz Architecture 20

21 Plain Java Extension Java Client Jazz Client Extensions Jazz Client Kernel It is a normal plain Java application Establishes one or more connections to Jazz repositories Uses (and provides) client libraries TeamPlatform.startup(); ITeamRepositoryService srv = TeamPlatform.getTeamRepositoryService(); ITeamRepository repo = srv.getteamrepository(myrepositoryurl); repo.login(progressmonitor); IQueryClient qryclnt = repository.getclientlibrary(iqueryclient.class); IQueryResult result= qryclnt.findall(myqueryexpression); processworkitems(result); Introduction to Jazz Architecture 21

22 What are Client Libraries? A bundle that provides a sophisticated façade for a component s functionality A service running on the Jazz Team server Looks like you re just invoking client side Java API Hides complexity of transport Instantiated only once per repository connection may have state and allow for listeners Talks to Jazz platform and component specific services on the server Can leverage smart, optimized communication patterns Manages the caching of the component s repository data Can depend on and talk to other client libraries Interesting client side applications are possible by using the Jazz Client Kernel and existing client libraries Introduction to Jazz Architecture 22

23 Other key extensibility stories for RTC 1.0 Create a new report Use the BIRT report editor and the RTC data warehouse schema to provide custom reporting (sample reports provided) Extending the Build system Templates driving Ant based builds provided. Provide a new build template, e.g. Maven support Create a new process template Process component provides XML schema for templates Includes process-specific work item types, supporting reports, process guidance Templates are then used to launch projects using that template See examples in RTC Introduction to Jazz Architecture 23

25 JRS Experiment: Implement tools like an internet application Programming model Specified in Open Services For Lifecycle collaboration HTTP GET/PUT/POST/DELETE Index Build on Jazz experiences in Web UI Data specified independently of tools All data are resources with URLs Ubiquitous access Tools access data through HTTP/APP Multiple tools same data Data integration without forcing same tool for multiple roles References are embedded URLs Cross technology/location Resources have representations XML encouraged, not required Search and query through structured indexes, independent Standard analysis, query, reporting Introduction to Jazz Architecture 25

26 Summary: Ongoing Architectural Innovation The Jazz Platform is the plumbing inside Rational Team Concert 1.0 product The platform and products built on it are open to extensibility, Jazz.net wiki will be the place to go for details The Jazz Core team continues to innovate on the Platform, improving Capability Scalability Configurability Connectivity Introduction to Jazz Architecture 26