CCM-2054 Transitioning From CC To RTC

Case Study: Transitioning from IBM
Rational ClearCase to IBM Rational

Team Concert
Alessandro Sartori Change Manager, Banca IntesaSanpaolo
Michele Pegoraro Business Consultant, Nexen
email: alessandro.sartori@intesasanpaolo.com
michele.pegoraro@nexen.it
Session Track Number: CCM-2054

The Premier Event for Software and Systems Innovation
About Intesa Sanpaolo
Intesa Sanpaolo is the banking group which was formed

by the merger of Banca Intesa and Sanpaolo IMI.
Intesa Sanpaolo is the leader in Italy in all business
areas, it is among the top banking groups in the euro
zone and it has a selected presence in Central Eastern
Europe and Middle Eastern and North African areas.
21.9 billion euro of market capitalisation
10.8 million customers and 5,600 branches in Italy
8.3 million customers and 1,600 branches out of Italy
2
2012 IBM Corporation
About Intesa Sanpaolo
3
About Intesa Sanpaolo Information and Communications Technology

System Department
The ICT Systems Department of Intesa Sanpaolo Group

Services is one of the greatest centers of ICT expertise in
Italy, that provide services to the great productive machine
that is today the Intesa Sanpaolo:
about 2,060 professionals (internal) spread across
9 different cities
a total of 15 sites
4
About Intesa Sanpaolo ICT
Mainframe platform with a processing capacity of about

80.000 MIPS
A server farm (Central Open Systems) with about 4.550
physical servers (450 Unix, 3.100 Intel, 1000 Linux and 3
AS400)
About 5200 physical servers distributed in the branches
45 million transaction each day
5
About Intesa Sanpaolo ICT
Number of applications
950 distributed
1500 components of branch applications
700 mainframe
50 iSeries
Requests for Change

A total of 19,000 in 2011.
Objects released in production environment

About 1,000,000 objects released in 2011
(distributed and mainframe platforms).
6
Evolution of Change Management in Intesa Sanpaolo
IBM Rational IBM Rational IBM Rational

ClearCase ClearCase Team Concert
Base UCM
Use of Use of
Use of label Change Set and
UCM Activity
Work Item
2003 2008 2012
7
Change and Release Management Architecture
Development free with virtual desktop Change Integration Operating

Governance Bridge Tools of
Governance layer (custom tool Change Layer Change
Console Integrata) control and automate the
transition to System Test and Production
environment.
Development System Test Production
Change Console Integrata

ClearCase
RTC
Endevor Mainframe iSeries

Distributed
ClearCase Endevor RTC
8
Why did we need to adopt Rational Team Concert?
Major needs from iSeries platform:

Lack of SCM tool for iSeries applications.
Difficult to implement the Change
Management process without tools support.
Manual application deploy.
Lack of role separation.
but also:
Upgrade the CM architecture to support new
integrations and automations.
Enable the platform to support different
development processes.
Optimize infrastructure of SCM for distributed
platform.
9
Why we want to migrate from ClearCase to Rational Team Concert?
Expected to have benefits in different areas
Improved SCM performance (checkin, deliver)

Functions Activity management (Work Item)
Dashboard and reporting
Repository based on standard RDBMS

Infrastructure
Centralized architecture
RESTful services
Architecture
Java SDK availability
10
Why do we need to customize RTC?
Strong Requirements Process Compliance Tools integration
11
Strong requirements
Developer work is free
Change is routed through governance tool
Change request code segregation
Environment organization and hierarchy
RTC used by end-users mainly for SCM
CM capability used for automations and controls
12
Process compliance
RTC implementation must be compliance with
DSI processes
The processes are standard and defined by a

specific Business Unit
Different kind of Change Unit has different

workflows
Different platforms have specific neededs
RTC and CC must coexist during rollout
13
Tools integration
Governance provided by an external custom
tool
KPI are collected using custom script
Data for reports are collected using custom

script
Several build type and requirements: ant,

maven, ivy repository
Binary versioning after build
14
How we customize RTC
Product Newly
provided developed
customizations customizations
15
Product provided customization
New work types
Custom attributes and editors
Workflow customization
Stream organization
Project and team area hierarchy
16
Product provided customization
New work types
Custom attributes and editors
Workflow customization
Stream organization
Project and team area hierarchy
17
Newly developed customization
Plug-in development (Server and Client side)
Plain API
REST API
Eclipse Client extensions
18
Different customization for different situations
Eclipse
Eclipse Client
Extensions
Governance
RTC
(Management Build Server
server
server)
REST API Plug-in Plain Java API
19
Server Side development
15 New Operation Advisors
18 New Operation Participants
6 New Event Handlers
8 New Link Types
18k lines of code
20
Server Side operation type
21
Plain Java API
Scripting Ant Task Asynchronous Operations
22
REST API operation type
23
Eclipse Extensions
Help users in long operations
Flaring projects
Rollout procedures
24
Focus points
Workflow Based Removing Change sets

SCM Actions Change sets dependency
25
Workflow based SCM actions
Work Items drive the change
Streams based on environments
Work Items state changes trigger delivery

between streams
Automations Controls
26
Removing Change sets
Change sets driven by Work Items
Static environment streams non modifiable by developers
If Work Items are rolled back, change sets have to roll back too
Discard of change sets from stream is not possible
We need to use replacement
Unthreading operation in pre-existing solution
27
Change sets Dependencies
Change sets can depend each other
Dependent change sets retrieved by file history
Automatic resolution of dependencies turns into a

requirement
Long operation with lots of files
28
Migration strategy
Actual ClearCase numbers

about 600 VOBs
for a total storage of 750 Gb
Migration strategy
Incremental roll-out
Migration of the last baseline released in production
Migration of the active changes (released in System Test)
VOB migrated are accessible in read-only for 6 months
VOB archived after 6 months from migration date
Migration plan
Start at the end of June 2012
End estimated at September 2013 (15 months)
29
www.ibm.com/software/rational
30
Imagery used in this presentation
These images are distributed with CC license by attributions
Slide 12 : John Keane http://www.flickr.com/photos/johnkeane/4351736116/

Slide 13 : Hobvias Sudeneighm http://www.flickr.com/photos/striatic/2135057566
Slide 14 : Brent 2.0 http://www.flickr.com/photos/brentinoz/4221291984/
Slide 15 : i_yudai http://www.flickr.com/photos/y_i/2330044065
Slide 18 : Jukka Zitting http://www.flickr.com/photos/jlz/5035746722
Slide 22 : zingyyellow http://www.flickr.com/photos/zingyyellow/3237480458, Yogendra Joshi
http://www.flickr.com/photos/yogendra174/4909104751, Patrick Hoesly http://www.flickr.com/photos/zooboing/4335531769
, Michele Pegoraro http://www.flickr.com/photos/mikyjpeg/432348753
31
Daily iPod Touch giveaway
Complete your session surveys online each day at a conference kiosk or on your
Innovate 2012 Portal!
Each day that you complete all of that days session surveys, your name will be entered
to win the daily IPOD touch!
On Wednesday be sure to complete your full conference evaluation to receive your

free conference t-shirt!
32
www.ibm.com/software/rational
Copyright IBM Corporation 2012. 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 IBMs 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, Rational, the Rational logo, Telelogic, the Telelogic 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.
33

CCM-2054 Transitioning From CC To RTC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCM-2054 Transitioning From CC To RTC

Uploaded by

Copyright:

Available Formats

Case Study: Transitioning from IBM

Rational ClearCase to IBM Rational

Session Track Number: CCM-2054

About Intesa Sanpaolo

Intesa Sanpaolo is the banking group which was formed

21.9 billion euro of market capitalisation

10.8 million customers and 5,600 branches in Italy

8.3 million customers and 1,600 branches out of Italy

About Intesa Sanpaolo

About Intesa Sanpaolo Information and Communications Technology

The ICT Systems Department of Intesa Sanpaolo Group

About Intesa Sanpaolo ICT

Mainframe platform with a processing capacity of about

About Intesa Sanpaolo ICT

Requests for Change

Objects released in production environment

Evolution of Change Management in Intesa Sanpaolo

IBM Rational IBM Rational IBM Rational

2003 2008 2012

Change and Release Management Architecture

Development free with virtual desktop Change Integration Operating

Development System Test Production

Change Console Integrata

Endevor Mainframe iSeries

ClearCase Endevor RTC

Why did we need to adopt Rational Team Concert?

Major needs from iSeries platform:

Why we want to migrate from ClearCase to Rational Team Concert?

Expected to have benefits in different areas

Improved SCM performance (checkin, deliver)

Repository based on standard RDBMS

Why do we need to customize RTC?

Strong Requirements Process Compliance Tools integration

Change is routed through governance tool

Change request code segregation

Environment organization and hierarchy

RTC used by end-users mainly for SCM

CM capability used for automations and controls

The processes are standard and defined by a

Different kind of Change Unit has different

Different platforms have specific neededs

RTC and CC must coexist during rollout

KPI are collected using custom script

Data for reports are collected using custom

Several build type and requirements: ant,

Binary versioning after build

How we customize RTC

Product provided customization

New work types

Custom attributes and editors

Project and team area hierarchy

Product provided customization

New work types

Custom attributes and editors

Project and team area hierarchy

Newly developed customization

Plug-in development (Server and Client side)

Eclipse Client extensions

Different customization for different situations

REST API Plug-in Plain Java API

Server Side development

15 New Operation Advisors

18 New Operation Participants