A lot of reorganization work has been happening lately within IBM/Rational and, as one of them, it was with a mix of sadness and mission accomplished feelings that I received the news that Jazz Jumpstart Team was to be disbanded. As a result of that reorganization I have joined the Rational Emerging Technologies Team (aka RETT). You can have some more insight on these changes and what the new team means in the blog post Everything Changes – Change is the Only Constant from Dan Toczala’s Blog. He is the manager of this new team where I am joining some old and new colleagues in this RETT initiative.
What does that mean for me and this blog? Well, not much, as in my new role I am focused on Rational Team Concert for System Z development, so still RTC and the Jazz platform :). I’ll try to focus a bit more my posts on RTC for developing for this platform: how to take the most of Enterprise Extensions, adoption tips, …; or my little solutions for common customizations/extensions that I find for the adoption of RTC for that particular development area. I am keeping here links to other colleagues’ blogs where you will still find cool stuff in other CLM areas that I will be no longer focused on.
During a recent review of the Process Enactment Workshop Lab 5 materials in a 4.0.3 test environment I had the opportunity to try some good enhancements and new features in the Attribute Customization configuration editor for script based customizations. I think these enhancements are pretty cool and maybe not as advertised as deserved, so I wanted to blog about them.
Back from Innovate, it has been a great time meeting lots of Jazz practitioners and buddies; most of them it was the very first time I was meeting in person, after long time working together. After the usual time for catching up with tasks that were waiting for me, I am back to my blog. I have been recently working in an engagement helping building a custom asynchronous scheduled task, so I wanted to write about it.
I have had some difficult time trying to find an example of such a task that was both simple enough and yet close to a real case; so finally instead of complicating myself, I decided to use as basis the example from the Query Dev Guide wiki page with some little modifications, but with focus on the details of building such an async task.
The Jazz Jumpstart Team will be attending the Innovate 2013 in Orlando, Florida, June 2-6. We will be presenting in different sessions covering a variety of topics around Jazz platform and CLM. The schedule of all the sessions in which we are participating has been nicely consolidated by my colleague Rosa Naranjo; check it out in her blog entry here.
I will be personally participating in the following Innovate sessions:
- Building Mainframe Applications with RTC (June 6th: 9:45-10:45): Nicolas Dangeville and I will be describing the mechanics of the Dependency Build, to help you gain an understanding of how the feature works. But it’s not just about it and its details; we will also describe some additional dependency build feature options and supporting RTC features for building in system Z.
Beyond all the sessions in which we participate, feel free to reach out to us; it’s always fun to share thoughts and ideas, and meet Jazz practitioners.
See you at Innovate 2013!
During the past week, some new RTCEE videos have been published on jazz.net:
I hope you enjoy them!
From some time I wanted to try the new Project Process Sharing feature called “Fine-grained Customization of Configuration Data”. This feature provides great flexibility in how process consuming project areas can tailor the inherited process configuration data section. The feature main documentation wiki page can be found here.
While more customization possibilities will come in the future, the supported customizations in RTC 4.0.1 documented in the wiki page supported customizations section, already provide a set of cases I usually find working with customers. In this post I am going to model a simple typical scenario and, based on the Delta Configuration Examples page, document my steps.
Project Process Sharing is a great feature that allows an organization to keep a consistent process specification across different projects. It leverages getting the process definition from a central managed project area, and to pick up process changes automatically. This feature for standardization still allows individual projects to perform some customization of the inherited process to accommodate individual process particularities. A good introductory tutorial can be found here.
I have been recently working on extending the Rational Team Concert Bugzilla Importer functionality and I wanted to take some time to blog about it. Rational Team Concert provides an Import wizard to migrate Bugzilla Bug Reports to RTC. The details of such feature are described in this jazz.net article and this InfoCenter topic.
Update Feb 11 2013: I have updated the shared code to be able to ignore the Bugzilla bugs’ attachments.
The post content is the original one but you will find in the wizard the option to ignore the import of attachments, which may be useful when you are migrating old bugs information for traceability but you don’t want to carry all the attached files to your RTC database.
From some time ago I wanted to post a chunk of code to enable to launch a build as a result of a deliver operation. I have found myself in some situations in which this kind of automation has been asked, and I wanted to play a bit wit the SCM part of RTC SDK, so in this post I want to publish some code sample that I hope will be useful for people having this or a similar need.
One of the decisions you face when you are planning the deployment of the Rational CLM solution is the selection of the database vendor you will use. Although most of the times the decision is based on your organization’s corporate solution , and this deployment decision remains stable in time; there may be circumstances in which you want to change the database vendor you use for your CLM deployment.