A developerWorks learning circle is a community space where people come together to learn about a subject. The learning circle offers targeted resources and guided learning activities, selected by subject matter experts, that you can use to build your personal learning roadmaps.
Darrel Rader, a technical skills and development leader in IBM Rational has built this amazingly short (only 6 slides!) but robust presentation on slideshare.net to help explain what learning circles are:
Now that you know what a learning circle is, did you know we've got five of them currently rolled out (with more to come)? Check out the great learning circles below, choose one, and dive in! These learning circles focus on aspects of the product and application lifecycle:
Because you may not have time to browse all the resources and mingle with other learners in one sitting, learning circles help you create your own personal roadmaps, your pathways through the resources.
You can check off items as you complete them, break away whenever you need to, and easily return anytime. No guesswork; no wasted time trying to recreate where you were.
You can keep your progress confidential, of course. But you also have the option of easily sharing your progress with a mentor, your manager, or your team so you can all progress together.
0:14 - Integration with Build Forge 3:45 - Continuous integration servers working with UrbanCode Deploy 4:40 - Example Ant tasks to add different capabilities 8:53 - Verification of live systems 9:51 - Integration with RQM - prechecks 12:30 - Integration with RQM - steps
We're knee deep into fall now, and well into November already! How did that happen? I'm not sure of the time-space continuum shift that has truncated this year, but what I am sure of is that our awesome developerWorks authors have been steadily publishing their great articles regardless of how short or long the year has seemed... Here are the latest articles from the past few weeks which have gone live on Rational developerWorks:
Analyzing data in an agile world By: Scott Snyder, Senior Performance Architect, IBM
Learn to interpret test results in an adaptable way. Scott Snyder shows you the techniques and tooling that should make data analysis more interactive. Product: IBM Rational Team Concert
Develop a hybrid mobile application using Rational Application Developer By: Hamid Kalantari, Staff software engineer, IBM
Top 10 modeling hints for system engineers: #10: Forget 7 ± 2 By: Bruce Douglass, Rational Chief Evangelist, Systems Engineering, IBM
Bruce Douglass gives one hint a week to help you with modeling. This 10-week series starts with #10: Forget 7 ± 2 Products: IBM Rational Rhapsody, IBM Rational System Architect, IBM Rational Software Architect
Debugging optimized code By: Rajan Bhakta, Technical Architect, z/OS XL C/C++ compilers, IBM
Rajan Bhakta gives you ways to make the right tradeoffs to get the easiest possible debugging and fastest possible optimization. Products: IBM C/C++ Compiler
Adopting the IBM DevOps approach By: Paul Bahrs, Chief Architect, Emerging technologies, IBM
This practice-based framework will help you assess your current practices and build a roadmap to DevOps adoption.
Be smart with virtualization, Part 2 By: Mike Donati, ClearCase Performance Team Lead, IBM, Ryan Smith, Software Performance Analyst, IBM, and Grant Covell, Senior Development Manager, Rational Performance Engineering, IBM
Part 2 of this article series brings you even more best practices for using IBM Rational software in virtualized environments. Products: IBM Rational Team Concert, IBM Rational ClearCase
IBM SmartCloud Enterprise and V9 Rational IDEs simplify application development By: Jean-Yves B. Rigolet, Rational IDE Cloud Architect and Lead, IBM
The new Version 9 rational IDEs are now available on the Smart Cloud Enterprise. No more install and configuration, just continuous access to your development environment from multiple devices. Learn more from Jean-Yves Rigolet. Products: Rational Developer for System z, Rational Developer for Power, IBM Rational Software Architect, IBM Rational Application Developer, IBM Rational Team Concert
Server-side mobile application development By: Bhargav Perepa, WebSphere Architect and IT Specialist, IBM
A five-part article series that explains how to use IBM Rational Application Developer for WebSphere Software and IBM® Worklight together to develop applications for mobile devices. Bhargav Perepa walks you through the entire process. He provides application and sample configuration files to guide you through the steps. Products: IBM Rational Application Developer, IBM Worklight
Following is a list of the recently published Tech Notes on ClearQuest APIs. These scripts are really useful for ClearQuest Admins and Project Managers to get an instant information on Defects/Records. Further, these scripts can be configured to send the information through emails and can be scheduled to execute on a specific time using Windows Scheduler.
Tech Note ID
How to find Not Closed records using CQ APIs and SQL query
I'm constantly amazed at the great information our developerWorks authors produce on such a consistent basis. To prove that point, here are the latest articles from the past week that have gone live on developerWorks Rational:
Develop reliable software with DevOps
By: Bob Aiello, Consultant and Technical editor, CM Best Practices Consulting (Division of Yellow Spider, Inc) and Leslie Sachs, COO, Yellow Spider, Inc.
Bob Aiello and Leslie Sachs teach you how to create reliable systems using principles and practices that are emerging as part of DevOps.
Products: IBM Rational Requirements Composer, IBM Rational Focal Point
A macro-pattern for public sector systems architecture
By: Jan K. Gravesen, Executive Architect, IBM
Jan Graveson gives you a common systems architecture pattern to help you accelerate the design of new systems architectures for the public sector.
Product: IBM Rational System Architect
JazzHub: Collborate in the cloud in less than 10 minutes
By: Jean-Louis Maréchaux, Worldwide Technical Enablement Lead, IBM and Fariz Saracevic, Lifecycle Scenario Architect, IBM
Jean-Louis Maréchaux and Fariz Saracevic take you on a tour of Jazz Hub in this scenario-based article. With Jazz Hub your team will quickly and easily collaborate on projects.
What's new in IBM Rational Application Developer V9.0 Portal Tools
By: Mansi Gaba, Staff Software Engineer, IBM
Mansi Gaba introduces you to the new and enhanced features. Support for jQuery tooling, the Maven framework, Mac OS, and simplified Dojo mobile view creation are some of the top improvements.
Product: IBM Rational Application Developer
Rational Developer for System z added the CARMA Enhanced Edit feature for CA Endevor SCM users in the 8.5.1 release. This CARMA Enhanced Edit feature is RDz's implementation of CA Endevor's Fast/Quick Edit. This feature allows RDz users to edit elements in the Endevor repository without having to retrieve/extract element out of repository into external file. When performing changes to a program, user will start by selecting the "version" of program/element within Endevor that they want to change. This usually is the "production" version of the program/element. When working with RDz CARMA, user would select (right-click on) element to be opened and select Edit/'Edit with' from the context menu.
When the CARMA Edit Element UI screen appears, user indicates to CARMA where they want element copied. This would typically be the "entry" environment/stage where they are allowed to edit element.
So what Endevor "actions" does CARMA use to copy "production" element into entry/editing environment/stage? That is a very important question because there are several different Endevor "actions" to do this, but not all RDz users are authorized to perform all Endevor "actions". The Endevor "actions" to handle this copy are generated from the RDz host Endevor RAM. These "actions" are run in foreground mode because of the unpredictable nature of running "action" as a batch job (CARMA has no idea when job will run/complete). Below I've listed how this "copy" of the element to "entry" environment/stage is handled in the available 8.5 releases and 9.0.
RDz 8.5.1 Endevor RAM: This was the initial implementation of the CARMA enhanced edit feature. In this release, the copy of the element to "entry" environment/stage is done using the Endevor GENERATE ELEMENT "action", with the "copyback" option. We have found that foreground GENERATEs are not allowed or are problematic in some customer environments.
RDz 188.8.131.52/9.0 Endevor RAM: In these releases, the copy to "entry" environment/stage was changed to use the Endevor TRANSFER ELEMENT "action". The element is opened in the RDz editor after the foreground Transfer has completed. In many cases, when the element is opened, some/all dependencies are not resolved until a GENERATE is done for the element being edited in this Environment/stage. We have also found that some customer sites do not allow RDz users to run Transfer "action".
RDz 184.108.40.206 Endevor RAM: In this release, the default way that CARMA handles this "copy" is still with the Endevor TRANSFER ELEMENT "action", however, we also allow you to configure RDz to use the RETRIEVE ELEMENT (from "prod") and ADD ELEMENT (to "test") "actions" to handle this "copy". To configure CARMA to use RETRIEVE-ADD "actions" for program/element "copy", you need to un-comment the 'ENTRY-STAGE-COPY-MODE = RETRIEVE-ADD' statement in the appropriate RDz CARMA CRACFG file. The CRACFG file is allocated in carma.endevor.conf (CRASTART servers) or CRASUBCA (CARMA batch servers).
To resolve dependencies when an element is opened using CARMA Enhanced Edit, a GENERATE ELEMENT request was added (220.127.116.11) following the TRANSFER/RETRIEVE-ADD "actions", however, this has again caused problems for customers that don't allow users to run foreground GENERATEs. An internal APAR has been opened to provide the 'Bypass generate processor' option on the Edit Element UI screen that appears when doing CARMA Enhanced Edit.
When you select this option, keep in mind there is good chance all dependencies will not be resolved by the RDz editor until a GENERATE is done on the element being opened, in the Endevor environment it is being opened from. This option should only be selected if you have trouble running foreground GENERATEs.
The current versions of RDz are 18.104.22.168 and 9.0 (Nov. 2013). The APAR mentioned in the previous paragraph will be delivered in the 8.5.1.next and 9.0.next RDz host PTFs. To verify what CA Endevor "actions" are being used in your environment, you can view the Endevor "actions" used in the MSG3FILE. The MSG3FILE is allocated in the user's CARMA server who performed the CARMA Enhanced Edit on element.
The IBM Support Portal has a new look. You have suggested improvements for the IBM Support Portal. We've listened, and our new, simplified website is now available. The simplified design presents the most important content for your product to help you find the information you need, when you need it. After selecting a product from the top of the page, you'll find links to fixes, updates, best practices, product documentation, troubleshooting technical notes, social media channels, tools and resources, and so much more. Please visit the new site today at support.ibm.com!
At the IBM Electronic Support blogyou will find an overview of the main pages of the new IBM Support Portal and a description of how to navigate within this new design. Note:Clicking on the images in this linked article will open full-size images in a new browser tab for greater visibility to the discrete features.
APAR PM96642 is fixed in Rational Developer for System z (RDz) v22.214.171.124 fixpack. This APAR picks up a fix from the Rational Common Licensing (RCL) product, and is not listed as one of the APARs fixed in that fixpack since it is an internal APAR.
The problem described in this APAR will occur if you are using a floating license with RDz, and the Rational Common licensing logger configuration file was not configured when RCL was first installed. The fix for this APAR will allow a restart of the RCL so that the configuration file will be read.
Here's the most recent list of the latest and greatest downloads which have gone live from Rational Support since October 16th! These links below are provided to help you find the fixes you need in order to stay up to date and successful with your Rational products.... Plus, don't forget to check out the downloads tag to see any of the fixes you may have previously missed:
Rational DOORS v9 x: Requirements Change Management Options- IBM Rational DOORS v9 x: Change Management by Systems Engineer Steve Grossman. This video explores two options for Change management for requirements in IBM Rational DOORS:
1. The Change Proposal System or CPS, that is built into DOORS
2. Integration with OSLC-based change tools such as Rational Team Concert
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.
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.