AcdntlPoet 2700019V2G Visits (9766)
The Introduction to Configuration Management with IBM CLM video series on developerWorks is a great beginning to working with the various CLM components and features to improve your engineering streams and manage change:
Introduction to Configuration Management with IBM CLM: CLM global configuration - The video builds on the concept of a lifecycle project in IBM's solution for Collaborative Lifecycle Management (CLM) by introducing concepts and terminology introduced in version 6.0 of the IBM Jazz applications. These concepts include baselines, steams, configurations, global configurations, components and other. These capabilities are useful when reusing requirements or components in product variants, in product line engineering, and in everyday project development.
Introduction to Configuration Management with IBM CLM: What is Product Line Engineering? - IBM Rational offers solutions to support each phase of the product line engineering (PLE) lifecycle. PLE is a methodology that lets you deliver and evolve entire product lines more efficiently.
Introduction to Configuration Management with IBM CLM: Managing Requirement Changes with DOORS Next Generation - In this short demonstration you will see how changes to requirements can be made in an isolated stream, captured in change sets and linked with work items and then shared and delivered for reuse in other streams.
Introduction to Configuration Management with IBM CLM: IBM Rational DOORS Next Generation: Working with baselines - In this video we learn how to work with baselines in IBM Rational DOORS Next Generation V6.0.
Introduction to Configuration Management with IBM CLM: Effectively Manage Changes, Baselines and Engineering streams - In this short demonstration you will see how global configurations can be used to help you effectively manage changes across the engineering lifecycle. We will start off by examining a new defect that has recently been submitted against an Automated Meter Reader system. This system helps automate collection of water usage in residential and commercial buildings. The project planning and change management component of the IBM Continuous Engineering Solution allow us to coordinate amongst team members using releases and work items. Work items are typically small chunks of work carried out by team members on a project and can represent tasks like enhancements, defects and system change requests.
Introduction to Configuration Management with IBM CLM: Effectively Manage and Reuse Components - In this short demonstration you will see how global configurations can be used to help you effectively manage, organize and reuse components that contain artifacts across the development lifecycle.
Romain_Barth 2700076HKB Visits (10158)
There is a documented procedure to install the DOORS client in silent mode and when you install a new DOORS client the old one is automatically uninstalled.
But, since the release 9.6.1, DOORS client is only a 64 bit application. That means if you have a DOORS client 32 bit installed, installing a new DOORS client 64 bit won't uninstall automatically the old release. This is a problem when you want to install DOORS in silent mode as having a DOORS client 32 bit and 64 bit installed on the same machine is unsupported by IBM.
To uninstall DOORS client 32 bit in silent mode, you need first to find the GUID of your release. To find the GUID, you can use WMIC, here is a sample script (.bat) to retrieve that information:
In this example, I am trying to find the GUID of a DOORS 9.5 client.
Once you get the GUID, you can use this command to uninstall your DOORS client:
AcdntlPoet 2700019V2G Visits (10033)
What’s new in Team Concert Jenkins plug-in 18.104.22.168 - We are pleased to announce that Team Concert Jenkins plug-in 22.214.171.124 is here! The Team Concert Jenkins plug-in integrates Jenkins with Rational Team Concert’s (RTC) SCM and Build capabilities using the richer features of the build toolkit. It provides options to configure Jenkins jobs to use RTC source control. Jenkins jobs can also be configured to use the source control options specified in an RTC build definition, facilitating Jenkins builds to be managed from RTC and take advantage of the traceability provided across RTC work items, builds, and change sets. The plug-in also publishes the changelog information in the Jenkins builds and supports polling....
An overview of the different build configurations supported by the Team Concert Jenkins plug-in - Using the Team Concert Jenkins plug-in, you can configure your Jenkins jobs to use Rational Team Concert (RTC) source control and, optionally, report information back to Rational Team Concert builds. The plug-in integrates Jenkins with RTC using the richer features of the build toolkit. This plug-in is different from the other Rational Team Concert plug-in for Jenkins which uses SCM CLI to integrate with RTC. This article provides an overview of the different build configurations supported by the Team Concert Jenkins plug-in 126.96.36.199. For instructions on how to setup and configure the plug-in, refer to Team Concert Jenkins plug-in wiki....
Loading symbolic links correctly when using the Rational Team Concert/Jenkins integration - When using the Jenkins plugin to load files from Jazz SCM it is possible that the symbolic links in the Jazz streams will not be loaded correctly. The problem is that the default Java runtime for Jenkins will not know how to deal with the symbolic links. It is necessary to manually include the .dll/.so files into the Jenkins library path so the symbolic links will load correctly. This article will detail how to setup Jenkins to get the symbolic links to load correctly....
Note: This post and related articles describes a usage or software configuration that is not supported by IBM.
AcdntlPoet 2700019V2G Visits (9452)
The goal of this article series is to serve as a helpful collection of "developer's cheat sheets." Some of the operations outlined are ones you might use infrequently. While others, you'll use often enough for them to become second nature to your normal development routines.
Rational Team Concert essentials: A developer's perspective, Part 1: Joining a new team project - In Part 1 of this series, learn how to join a team project, create a workspace to contribute to your project, and load existing artifacts from your team’s project components.
Rational Team Concert essentials: A developer's perspective, Part 2: Delivering work contributions - Learn how to use Rational Team Concert to identify your project development commitments, carry out your development activities in a team environment, and deliver your work to your team project.
AcdntlPoet 2700019V2G Visits (6392)
This series of articles presents two mechanisms for integrating IBM Rational Team Concert™ and IBM® UrbanCode Deploy to create a continuous delivery process. The first approach included in Part 1, is a packaged out-of-the-box implementation that is easy to set up. The second approach, presented in Part 2 and Part 3, uses extensions to the Ant build.xml file.
Continuous delivery with Rational Team Concert and UrbanCode Deploy: Part 1. An out-of-the-box implementation - Learn how to create a continuous delivery process using IBM Rational Team Concert and IBM UrbanCode Deploy. You will learn how to extend an existing build processor to create a new build process from scratch that will seamlessly integrate the products to provide a flow of content in a highly traceable manner.
Continuous delivery with Rational Team Concert and UrbanCode Deploy: Part 2. How to extend the build process - This article shows how to extend a build process to push newly built objects from the Rational Team Concert build process to the UrbanCode Deploy repository so that it is ready for deployment.
Continuous delivery with Rational Team Concert and UrbanCode Deploy: Part 3. How to use extensions to the Ant build.xml file - This article presents the final part of an alternative approach using extensions to the Ant build.xml file which is often at the center of the build process used by Rational Team Concert.
AcdntlPoet 2700019V2G Visits (7680)
Guide to Git for Rational Team Concert users - This article is for users of Rational Team Concert who want to learn more about Git. Find out how these two powerful source control systems differ in terms of capabilities, concepts, and commands, then get tips for successfully migrating a project workflow to Git.
Migrate your CMVC workflow to Rational Team Concert, Part 1: Set up and configure your migration path with CMVC-RTC Connector Plugin 2.3 - Configure the CMVC-RTC Connector Plugin to synchronize work items and source code between CMVC and Rational Team Concert.
Migrate your CMVC workflow to Rational Team Concert, Part 2: Configure the Defect/Feature Importer to migrate CMVC work items to Rational Team Concert - Configure the CMVC-RTC Connector Plugin's Defect/Feature Importer to successfully migrate CMVC work items to Rational Team Concert.
Migrate your CMVC workflow to Rational Team Concert, Part 3: Extract and import your source code to Rational Team Concert - Configure the CMVC-Rational Team Concert SCM Importer to extract and import your source code to Rational Team Concert.
Romain_Barth 2700076HKB Visits (6254)
Is there a way to delete multiple linksets from a link module including all the contained links?
The DOORS UI does not provide that feature but it is possible by using DXL.
Here is a sample that will delete all the linksets and links contained in a specific project:
First, open your link module in Exclusive Edit mode, then run the script above.
Romain_Barth 2700076HKB Visits (9431)
By using DXL, however, you can do this task quickly. Here is a sample of code to help you perform it:
Romain_Barth 2700076HKB Visits (12981)
From DOORS 188.8.131.52 and RQM 6.0.1, it is possible to use link discovery instead of back linking.
With link discovery, links from RQM to DOORS are only stored in RQM. When opening a module in DOORS, it will query RQM to display the links.
With this feature, RQM does not need to acquire a lock on requirements to create a link, so it reduces conflict between RQM users and DOORS users.
In this article, you will learn how to enable this feature.
1-Case of a new installation
You just installed DOORS/DWA 184.108.40.206 and RQM 6.0.1.
2- Case of an upgrade
After upgrading DWA to 220.127.116.11 or/and RQM to 6.0.1, you have to perform the following steps :
paulellis 270001KTVW Visits (10958)
On April 25th 2016, IBM released Collaborative Lifecycle Management 6.0.2. In Moshe Cohen's blog
One of those highlights was:
And Moshe said:
Maybe it's a coincidence, but a lot of upgrades have occurred in the last few months.
Unfortunately, not all of them have gone as smoothly as they could have done.
Why are people finding that their upgrades are not wildly successful?
This, for me, is particularly frus
We also published a useful blog post "Planning your CLM upgrade?" to help find information about the latest available fixes and system requirements; and Dan Toczala wrote a
All of which was great, but do we just have too much information in too many places?
What we have missed all this time is a single entry point to our expansive library of information relating to your specific upgrade - in a single page!
In order to have a positive upgrade, where success is planned in from the start, a simple, handy checklist is required.
One, simple, must
This checklist includes simple links to assist with obtaining all the information required for each of the key areas of an upgrade:
* Upgrade Testing
* Software Licenses
* Server, infrastructure and performance considerations
* Latest Upgrade flashes and news per CLM application
* Ways to contact us so we can help
* Additional pertinent links/information
We are strongly recommending that this be the starting point of every CLM upgrade. Please also give us your feedback if you believe something is missing.
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (11092)
Are you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)?
Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki
Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati
There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details:
Sizing Guidelines for Rational DOORS Next Generation 6.x
Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration
Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations?
The guidance is clearly aimed for the general use cases and is very much our strongest recommendation.
It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.
Romain_Barth 2700076HKB Visits (6213)
In DOORS 9, it is not possible via the user interface to manage the "baseline power" for users.
But it is possible to modify the original behavior of DOORS by editing a DXL file and by creating a "special" group for those users.
When a user attempts to create a baseline from the UI, this code will be executed and only users in the group will be able to create baseline.
Romain_Barth 2700076HKB Visits (10848)
DOORS 9 - RQM integration : How to update link properties in DOORS after renaming a test case in RQM
After creating a link from RQM artifact to DOORS requirement, if you change the name of the RQM artifact (test case or step of test script), this change is not updated in DOORS : the link description and title in DOORS are still referring to the old name of the RQM artifact.
This is working as designed when the integration between DOORS and RQM uses back-linking (in other words: 2 links are created, 1 in DOORS and 1 in RQM)
There are 2 ways to correct this issue :
- Manually edit the link description in DOORS
- Run a DXL script on your DOORS module that will query RQM to gather the name of the RQM artifact for each link to RQM in the module. Then it updates the description and title of those links.