AcdntlPoet 2700019V2G Visits (2175)
We're back from Innovate, IBM's Technical Summit and on the tails of our mid-year release cycles. Even with the busy schedules this past month, our authors are still committed to getting you the best information we can to help you be successful with our products an in your daily work. To that end, here's the articles, featured downloads and upcoming webcasts that went live on developerWorks Rational recently:
New capabilities from IBM put developers in the spotlight
Capture multiple tooltips in one image automatically with IBM Rational Functional Tester
Find out for yourself: 7 new video demonstrations
What's new in IBM Rational Rhapsody 8.0.3 and Rhapsody Design Manager 4.0.3
Ensure effective administration and security in Rational ClearCase 8.0.1
Simplify user management for Collaborative Lifecycle Management applications
Automate deployment of an IBM Worklight customized WAR file with Rational Automation Framework
Server-side mobile application development with IBM Worklight: Parts 1-4
Configure Rational Team Concert to build ISPF Dialog Tag Language components
Using PHP and cURL for server-side caching of dynamic web pages
Now available from IBM Press: Transform your business with a winning mobile strategy: IBM's Dirk Nicol helps you navigate the mobile landscape with ease. Order now and save 35% with coupon code: IBM4916
IBM developerWorks LIVE! Jam: The jam opened June 11. Come share your ideas for developerWorks.
IBM Rational Rhapsody software's specialized editions help systems engineers and embedded software developers analyze, design, develop, test, and deliver embedded, real-time systems and software.
The Rational solution for Collaborative Lifecycle Management is a set of seamlessly integrated applications that work together as one: IBM® Rational Team Concert, IBM® Rational® Quality Manager, and IBM® Rational® Requirements Composer.
Rational Application Developer for WebSphere Software on the cloud: http
Rational Team Concert on the cloud: http
Rational Developer for System z on the cloud: http
AcdntlPoet 2700019V2G Visits (2174)
Here's three new videos for your educational benefit! The first will guide you through portfolio management using Rational Focal Point and Rational System Architect, while the next two will discuss the hierarchy of objects and linking & traceability in Rational DOORS. Good stuff here!
Application Portfolio Management with IBM Rational Focal Point and System Architect- This video demonstration by Jog Raj of IBM Rational looks at how IBM Rational Focal Point and System Architect are used for application portfolio management: IBM Rational DOORS - Hierarchy of objects- IBM® Rational® DOORS is a requirements management solution optimized for the needs of systems engineering, product development and enterprise I.T., with capabilities to capture, link, trace, analyze, and manage changes to requirements. In Rational DOORS, a requirements document is represented in a formal module. A formal module is a collection of objects. Learn more about object organization in this demo: IBM Rational DOORS -- Linking and traceability- This IBM Rational DOORS demo focuses on standard DOORS Links and external links. Links are created, deleted, and transversed. Dynamic traceability views are created for the purpose of impact, gap analysis, and scope creep. And finally suspect links are identified and cleared. This demo does not cover collaboration links:
IBM Rational DOORS - Hierarchy of objects- IBM® Rational® DOORS is a requirements management solution optimized for the needs of systems engineering, product development and enterprise I.T., with capabilities to capture, link, trace, analyze, and manage changes to requirements. In Rational DOORS, a requirements document is represented in a formal module. A formal module is a collection of objects. Learn more about object organization in this demo: IBM Rational DOORS -- Linking and traceability- This IBM Rational DOORS demo focuses on standard DOORS Links and external links. Links are created, deleted, and transversed. Dynamic traceability views are created for the purpose of impact, gap analysis, and scope creep. And finally suspect links are identified and cleared. This demo does not cover collaboration links:
IBM Rational DOORS -- Linking and traceability- This IBM Rational DOORS demo focuses on standard DOORS Links and external links. Links are created, deleted, and transversed. Dynamic traceability views are created for the purpose of impact, gap analysis, and scope creep. And finally suspect links are identified and cleared. This demo does not cover collaboration links:
AcdntlPoet 2700019V2G Visits (2174)
Have you found technotes faqs on IBM.com that solved your issue? Technotes which you knew could be improved? Let us know; we value your input!
Using the "Rate this page" feature, found at the bottom of every support technote/faq, you can let us know how we're doing, and suggest specific ways to improve our published content:
Yes, we WILL see it. All comments are reviewed as they come to us, and when applicable, the appropriate changes are made to the documents against which they were submitted. But remember: requests for assistance should always be submitted through your normal support channel.
Through your ratings and comment participation, you can help drive better, more timely content that will help you solve problems faster and more efficiently utilize your Rational tools! We really do appreciate and listen to your feedback!
AcdntlPoet 2700019V2G Visits (2172)
Our Jazz.net authors have been quite productive recently writing and publishing a slew of blog posts on the topics of DevOps and Continuous Delivery. Check out a selection of posts below from the subject matter experts themselves as they discuss deep technical topics that can help you improve your own release cycles, performance, and efficiency in deployments!
DevOps Culture - Retrospectives and continuous improvement- In the Collaborative Lifecycle Management (CLM) project we have declared three imperatives for improvement in order to increase our agility with a goal of continuous delivery: culture, process, and tools. Of these three things, culture is, in my opinion, the most difficult thing to change because it’s less tangible than processes and tools and because culture is often deeply ingrained in an organization and a team. Consequently, cultural changes can take a long time to implement. This is the first in a series of posts where I’ll discuss some of the important cultural issues and changes that we’ve tackled in the CLM project.
DevOps for Dummies now available!-You have probably heard about DevOps but you want to cut through the hype and understand more about this approach. That is the genesis of DevOps for Dummies, authored by IBM’s Sanjeev Sharma. It is written to appeal to both practitioners and managers and to show you how you can apply a new DevOps approach to more rapidly deliver innovative applications and services that solve real business problems.
Rapid build deployment using IBM UrbanCode Deploy- Previously I have focused on build performance in posts like Speeding up the pipeline by slowing down builds and Rethinking personal builds, but there is a lot more to a continuous delivery pipeline than build times. Once a build produces artifacts, you need to do something with them. Often the next step is to install the product onto a machine for either testing or production use. The installation is typically a process such as copying a zip to a machine and unzipping it or running an install program, but can sometimes be more complicated when special configuration is required. Below I describe how we have started using IBM UrbanCode Deploy to allow builds to easily and automatically install, configure and invoke server applications onto machines in the cloud before an application installer has even been created.
Working towards continuous deployment in Jazz.net- I have worked for IBM for about 20 years, moving back and forth between development, customer support and IT operations roles. Working in these different roles helped give me perspective for my current role as the manager for Jazz Continuous Deployments/DevOps. In this role I am responsible for ensuring that our multiple staging and self-hosting environments are stable and always using the latest driver or sprint of the Collaborative Lifecycle Management (CLM) products. We are not yet at the point where we can automatically deploy a new driver daily to production, but we are working towards that goal.
Unify your test automation for continuous delivery- This is the second article about testing in our Continuous Delivery series to share practices we have adopted in our own development team within Rational Team Concert (RTC). The presented techniques are used to control software evolution and to improve the quality of our code base. Since there is a variety of IBM and open source tools we are using, we focus here on the practices and techniques rather than on particular tools.
CLM Continuous Deployment Pipeline: Reporting on the state of affairs-The following is the third posting in my Collaborative Lifecycle Management (CLM) Continuous Deployment series of blogs on Jazz.net. The earlier two blogs can be found at Improving throughput in the deployment pipeline and Behind the scenes of the CLM Continuous Deployment pipeline. In Behind the scenes of the CLM Continuous Deployment pipeline, I had mentioned a mechanism we have developed on the Jazz Collaborative ALM project to gather progress and status data of phases that make up our deployment and test execution pipeline. In this post, I will show you how we use the gathered data for reporting on the overall state of the pipeline and narrow down on the root causes upon its failure. Additionally, the data allows us to create trend reports that help us assess the overall quality of our builds, tests and product code over a period of time.
From ‘use what we sell’ to ‘practice what we preach’- This is part three in our blog series describing the transformation of our internal ALM development organization toward a Continuous Delivery model. In this series, we describe the motivations behind adoption of a Continuous Delivery model and the many challenges we faced as we embarked on this transformation from both the planning and execution perspectives.
Role of the run team in our Continuous Delivery process- I am one of the developers in the Rational Collaborative Lifecycle Management (CLM) project contributing to the Tracking and Planning (TAP) functionality of Rational Team Concert (RTC). I have been part of the TAP team from last four years and involved in delivering RTC in longer and shorter release cycles. You would have read posts written by my colleagues on how we changed our processes and organized our teams for adapting to the Continuous Delivery lifecycle. This blog is the continuation to these posts, in which I’ll be talking about the "Run Team" and its necessity and role in delivering quality values to our product. We have been running the Run Team from the last four releases (since 4.0.1) and I was part of the team for three releases and led the team during two releases.
Rational Team Concert source control makes continuous delivery easier- Rational Team Concert (RTC) has started releasing quarterly. Since large features rarely fit into such short cycles, we’re making heavy use of RTC’s branching and merging functionality. That could result in merge hell, but it doesn’t. This post will give you an idea of how the RTC team uses our own source control management system, and show how its design helps large teams maintain many branches without nightmarish merging.
How does Rational ‘do Continuous Delivery?’- This is part two in our blog series describing the transformation of our internal ALM development organization toward a Continuous Delivery model. In this series, we describe the motivations behind adoption of a Continuous Delivery model and the many challenges we faced as we embarked on this transformation from both the planning and execution perspectives.
Organizing our teams for Continuous Delivery- You may have been reading the blog posts of my colleagues around continuous delivery including the motivation behind it, our focus areas as we transformed from annual to quarterly releases, and some process improvements that we implemented. Continuing this theme, in this blog I’ll write about one of the most dramatic changes that we underwent as a development team to support continuous delivery - the restructuring of the team itself into a new avatar that we like to believe is more agile and more user focused than it was earlier.
AcdntlPoet 2700019V2G Visits (2171)
In the first dW Rational update of the new year, here are the new items that went live on developerWorks Rational this past week:
Integrate a Rational ClearCase UCM stream with Rational Team Concert 3.0
Combine Rational ClearCase with Cadence Design Framework for more flexibility
Save time with this reusable Rational Functional Tester automation framework
We are pleased to feature Contributing Author Fariz Saracevic (email@example.com):
This week we are also highlighting the following items on the developerWorks Rational page and product pages that you may find of interest: