innovate2011 devops tsrm rtc

June 5–9 Orlando, Florida

Open Services for Lifecycle Collaboration

Steve SpeicherOSLC Technical Lead, IBM [email protected]

Improving Collaboration between IT Operations Support and Development with IBM Innovations

John ArweOSLC Lead,IBM [email protected]

CDO-1071B

Trevor LivingstonSRM Development,IBM [email protected]

The Premier Event for Software and Systems Innovation

2© 2011 IBM Corporation

Please Note:

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.



Outline

Background on problem space

Need for open solutions

Open Services for Lifecycle Collaboration

IBM Tivoli Service Request Manager + IBM Rational Team Concert



Questions asked every day

When will a fix be

available?

Are my tickets

linked to dev?

Why do people keep asking me for status?

How do I request more

traces so I can find a fix?



Problems Present in Dev-Ops Environments

Complex application support requires multiple silo'd teams to work together in concert.

Specifically, these problems need to be addressed in today's support organizations:

Time wasted communicating between teams

Time wasted duplicating tickets across tools

Lack of visibility into the status of work items



No consensus driven approachNo external reviewNo visibility into solution

Built after the fact with limited product APIsSolution focuses on 2 tools in hand

License feesFear of giving up IPForces alternative solutions

Limited Participation

Restrictive Participation

Need for Open Collaboration on SolutionsPast Integration Approaches Have Fallen Short

No open process for others to join inLimits solution to particular use cases and technologies

Limited to small set of business partners

Solution design goals and approach Restrictive licenses and intellectual property

Point-to-point integrations



Universal metadata standard

“How did I ever think all those vendors would be able to agree?”

Single repository

“Can I really expect one vendor to provide all the functionality I need? And what about my existing tools?”

Point-to-point integrations

“How can I ever upgrade one tool without breaking everything else?”

Standard implementations

“Did I really believe that every vendor would rewrite their tools on a single framework?”

Limited choice and coverage

Slow to emerge and disruptive to adopt

Need for a Better SolutionPast Integration Approaches Have Fallen Short



8

Identify Scenarios

Iterate on working drafts

Call it a spec

Gain technical consensus, collect non-

assert statements

Minimalist/additive approach Not a “complete” definition for a given area

Scenario driven scope

Co-evolve spec and implementations

Open participation around active core group

Open Services for Lifecycle Collaborationopen community. open interfaces. open possibilities

OSLC and Open CommunityIterative Specification Authoring



OSLC Community

Eleven workgroups operating at open-services.net

Domain focused workgroups (e.g. CM, QM, RM) Common issues and patterns (Core) Solution oriented workgroups (e.g. PLM/ALM)

Range of interests, expertise, involvement 400+ registered community members (up from

70 people at RSC 2009)

Individuals from 34+ different companies have participated in OSLC workgroups (up from 5 companies at RSC 2009)

Worthy of note PLM/ALM Workgroup

Siemens leadership Open source

Eclipse Lyo Project Proposal Eclipse Mylyn project restructuring and

positioning of OSLC Mantis, Forges

Customer and integrator involvement GM, Northrop Grumman, Tieto, Integrate

Systems

AccentureAPGBlack DuckBoeingBSD GroupCitigroupEADSEmphasys GroupEmpulsysFokus FraunhoferGalorathGeneral MotorsHealth Care Services CorpIBMInstitut TELECOMIntegrate Systems

Lender Processing ServicesNorthrop GrummanOracleQSMRally SoftwareRavenflowShellSiemensSogetiSourceGear/TeampriseState StreetTasktop (Eclipse Mylyn)ThalesTietoTOPIC Embedded SystemsUrbanCodeWebLayers

9



10

Linked Lifecycle DataData Integration for the 21st Century

Inspired by Internet principles, implemented with Internet technologies: simple interfaces for exchange of resources

Loosely coupled: everything is a “resource” linked together with URLs

Technology neutral: treats all implementations equally

Minimalist: defines no more than necessary for exchange of resources

Incremental: deliver value now, add more value over time

Openly published standards: free to implement and irrevocable

If the entire Web can connect like this, would the same idea work for ALM?



DevOps: A Shared Integration Approach - OSLC

Lifecycle ToolLifecycle ToolChange Change ManagementManagement

Lifecycle ToolLifecycle ToolQuality ManagementQuality Management

Lifecycle ToolLifecycle ToolRequirements Requirements ManagementManagement

Service ManagementService ManagementHelp DeskHelp Desk

Service ManagementService ManagementDeploymentDeployment



Tivoli Service Request Manager is a unified solution that improves productivity across a number of key processes

•Advanced work management processes•Flexible and easy to configure, no coding required•Dashboards and reports•Multi-customer support•Based on leading standards-based technology – J2EE, SOA, XML

•Process integration, built from the ground up on ITIL •Single user interface•Data integration•Underlying platform supports multiple products to provide unified solution

Users

Service Desk

Service Catalog

ServiceRequests

ServiceRequests

Shopping RequisitionOrder

ManagementOrder Tracking

OMP/PMPIntegration for

automation

SRM Service Provider Solution

integration

KnowledgeManagement

Incident Management

Problem Management

Asset/CI Integration

OMP/PMPIntegration for

automation

SRM Service ProviderSolution

integration

Service Request Manager 7.2.1



Operations Development

IBM Tivoli Service Request

Manager(SRM)

IBM Tivoli Monitoring (ITM)

IBM Tivoli Composite Application Manager

(ITCAM)

Data Center

S e rv e r

S e rv e r

S e rv e r

S e rv e r

S e rv e rS e rv e r

OSLC Interactions

IBM Rational Team Concert

(RTC)

• Align IT operations and development teams• Allow teams to work seamlessly with the tools

they are familiar with• Remove the need to synchronize data across

tools

Tracing Problems from Operations into Development



Integrating TSRM with RTC

Link TSRM Problem Management with RTC Defects, using OSLC

OSLC allows Operations Team to create RTC defects directly from TSRM problem tickets quickly using a familiar UI.

High Level Use Cases Ability to create and associate an RTC defect with TSRM.

Ability to associate an existing RTC defect with TSRM.

Ability to quickly view the status of an associated defect from TSRM.



www.ibm.com/software/rational



ProblemsDefects

Leveraging the Power of OSLC (TSRM and RTC Integration)

Development Operations

Create Defect, Find Defect, Display Defect

Defect linked to problem as URL (http://defect/1254)(March 2011)

Linked Data

REST-ful URL reference returns data for UI

Manages

When problem is closed, REST-full call closes the linked defect

(Future)

Changes

Development can create a changeTo deploy the tested fix with a REST-ful call

(future)

WEB-proven flexibility and scale

Manages

Manages



Business Values

Better insight

Brings awareness of business impacts to the development team, resulting in faster responses.

Increases visibility of fix schedule for support staff, enabling agents to better manage customer expectations.

Increases visibility of available fixes, leading to faster problem resolution.

Working effectively together

Enables development team and Operations to work together through an integrated tool set.

Assists in defect prioritizing and leads to efficient utilization of development resources.

Provides affective management of applications after deployment.

Managing enhancements, defects, and problems with traceability and automation.



Roadmap

Phase 1 (2Q 2011)

Integration of TSRM -> RTC Defect Management

Released via ISML (Integrated Services Management Library)

Next Phases (Timeframe not determined)

Expanding support to generalized OSLC-CM consumer

Integration of RTC -> TSRM Problem Management

Integration of Change Management and RTC Defects

TSRM ticket tracking of known RTC defects



Conclusion

Exploring new model for open integrations

TSRM and RTC integrations available NOW for use

Looking to get additional customer feedback to drive next phases

Give us your feedback and scenarios!

Come see us in the Exhibit Hall booth (in Jazz Interoperability Center)

June 5–9 Orlando, Florida

Jazz Interoperability Jazz Interoperability CenterCenter

{ In collaboration with… }

Exhibit HallJune 6: 5 - 8 PM June 7: 11 AM - 2 PM & 4:30 - 7:30 PM June 8: 11 AM - 2 PM

Come see Jazz and OSLC at play integrating IBM, 3rd party, and home-grown tools across the lifecycle!



OSLC Home Pagehttp://open-services.net

Video explaining OSLChttp://www.youtube.com/watch?v=B2vqL8fujgE

Whitepaper: The Business Value of OSLChttp://open-services.net/html/opencollab.pdf

Useful OSLC links



Daily iPod Touch giveaway

Complete your session surveys online each day at a conference kiosk or on your Innovate 2011 Portal!

Each day that you complete all of that day’s 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!

SPONSORED BY



© Copyright IBM Corporation 2011. 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, 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.




RTC Configured for TSRM

TSRM is configured with

RTC



RTC Defect Creation Dialog in TSRM

Create Defect Form from RTC



RTC Defect Preview in TSRM

Preview of Defect from RTC



RTC Defect with TSRM Ticket Link