Like all the prior top content posts month-to-month, these technotes are the most often cited and shared in our Support Engineers' PMR notes all used to help you solve or prevent issues with your Rational products. Last month the following technotes were the most heavily reused for Rational Team Concert. We hope that highlighting them here will help others encountering the same or similar issues also find quick resolution:
There have been few queries from clients asking if it is possible to import work items by e-mail into IBM Rational Team Concert. This is a somewhat complex topic as it isn't currently supported, but there is a potential work around. Let's take a look at the information:
A. There are the following properties in Advanced Properties page of the CCM application in RTC:
Online Help for this says: "A periodic task runs on the server that checks for mail received for work item creation. This property specifies the time in seconds between runs of this task."
B. Here is a brief on this feature from Jazz.net wiki: https://jazz.net/wiki/bin/view/Main/WorkItemEmailImport
However, as the link says, it's still in experimental stage and not supported, at least as of the RTC 4.0.3 version. This should perhaps be implemented in one of the future releases.
These are the top content reused during June to help solve your Rational Team Concert issues. Last month the following technotes were the most heavily reused when closing PMRs opened by you, our clients. We hope that highlighting them here will help others encountering the same or similar issues also find quick resolution:
I started working as a Technical Support Engineer, initially on Telelogic Synergy/Change products, later on IBM Rational ClearCase for the past couple of years, and lately with IBM Rational CLM (Collaborative Lifecycle Management) solutions.
Unlike with Telelogic Synergy or IBM Rational ClearCase, issues with CLM are so diverse, with less repetition of similar questions or difficulties. Here is one of the many interesting issues with CLM that I happened to work on.
Rational Team Concert (RTC) 184.108.40.206 server running on JFS 220.127.116.11 on server machine 'A'.
Rational Quality Manager (RQM) / Rational Requirements Composer (RRC) 18.104.22.168 running on JTS 22.214.171.124 on server machine 'B'.
Each having their own database servers, running on their respective server machines.
They were able to successfully register RQM 126.96.36.199 application on the RTC 188.8.131.52 server, however, trying to register RTC 184.108.40.206 on RQM 220.127.116.11 server failed with the following error:
CRJAZ2082E : An error occurred while attempting to access the Application
About service listed in the Discovery document for this application.
Please ensure that the application has been installed and provisioned correctly.
Unsupported RDFEntity Content-Type: text/html
--> They were in a situation where they did not have the option to upgrade from RTC 18.104.22.168 to RTC 22.214.171.124, due to IT and resource constraints. But they did want to get these products to work and roll out to users. Trying to register RTC 126.96.36.199 at RQM 188.8.131.52 server always failed with the errors as above.
--> Based on the error and configuration, we informed the customer that it is an unsupported scenario. With RTC 3.0 or 184.108.40.206 the integration for RQM, RQM must be 2.0.1 or 220.127.116.11. This was not the case in their set-up and hence would not work.
However, they had a concern in why there were able to link RQM 18.104.22.168 in RTC 22.214.171.124 server, whereas the reverse did not work. They were in a strange scenario, where the lower version (RTC) linked correctly to the higher (RQM), while the opposite did not happen. We understood in Support, that the combination they had is not supported and should not work.
However, the solution for their problem was to delete the existing server friend relationship between RTC 126.96.36.199 and RQM 188.8.131.52 at RQM 184.108.40.206 server and redefine them. This made the integration work and they were able to see the RQM Projects areas from RTC and the RTC project areas from RQM. They were then able to open defects from RQM to RTC.
While I haven't been able to reflect upon why the specific setup did or did not work here, I thought it's worth a time to write a note on this behavior and note the steps we saw achieve some success in this unsupported configuration.
I welcome any comments or suggestions on this article.
It's an RTC love-fest today! Hot off the reporting presses here in Rational Support, here are the top fifteen technotes used in March to help solve the Rational Team Concert PMRs you reported. As always, these are taken directly from our PMR reports and tabulated to help you solve the same issues which you may be encountering:
Over the past week, and particularly this past weekend, a few new downloads made their way through our tweet stream and Facebook wall. Seeing as these were posted during typically 'off' hours for most of us, we thought it would be of some benefit to highlight those recent releases here, to raise visibility in the case that you may have missed and need one or more of these downloads:
IBM Rational Application Developer Standard Edition for WebSphere Software, Version 8.0.3 http://ow.ly/1djSf7
IBM Rational Synergy Fix Pack 3 (220.127.116.11) for 7.1 - IBM Rational Synergy Fix Pack 18.104.22.168 has been made gener... http://ow.ly/1dhwlR
IBM Rational Synergy 7.1 Fix Pack 0.3 Windows - This Fix Pack solves 22.214.171.124 problems with Synergy CLI, G... http://ow.ly/1dgcgf
IBM Rational Synergy 7.1 Fix Pack 0.3 UNIX - This Fix Pack solves 126.96.36.199 problems with Synergy CLI, GUI,... http://ow.ly/1dgcgg
IBM Rational Synergy Interim Fix 1 for 7.2 - IBM Rational Synergy 188.8.131.52_iFix001 has been made generally ava... http://ow.ly/1ddt4b
IBM Rational Synergy 184.108.40.206 iFix001 UNIX - This Interim Fix solves 7.2 problems related to DCM clusters ... http://ow.ly/1daUF5
IBM Rational Synergy 220.127.116.11 iFix001 Windows - This Interim Fix solves 7.2 problems related to DCM cluste... http://ow.ly/1daUF4
IBM Rational AppScan Standard Edition-Windows-18.104.22.168-Rules-Update-1282-Recommended http://ow.ly/1dlhR6
IBM Rational AppScan Standard Edition-Windows-22.214.171.124-Rules-Update-1279-Recommended http://ow.ly/1dfQbN
IBM Rational AppScan Standard Edition-Windows-126.96.36.199-Rules-Update-1273-Recommended http://ow.ly/1ddaX8
IBM Rational Systems Tester 188.8.131.52 - This is a planned fixpack that focuses on fixing APARs, for more de... http://ow.ly/1dabqy
IBM Rational Statemate 4.6.1 iFix for Windows X/Server 8.5 - Includes Patch & hotfix for X/Server 8.5 http://ow.ly/1derg3
IBM Rational Insight 184.108.40.206 - IBM Rational Insight 220.127.116.11 contain fixes and features including the migr... http://ow.ly/1de3ov
IBM Rational Team Concert 3.0.1 - IBM Rational Team Concert 3.0.1 has been made generally available as part o... http://ow.ly/1de3ou
IBM Rational Quality Manager 3.0.1 - IBM Rational Quality Manager 3.0.1 has been made generally available as ... http://ow.ly/1de3ow
IBM Rational Requirements Composer 3.0.1 - IBM Rational Requirements Composer 3.0.1 has been made generally a... http://ow.ly/1derg2
Want to make sure you never miss notifications like the ones listed above again? Then check out "MyNotifications" and setup a free subscription to receive only the products and document types which YOU are interested in, and in the manner you desire (RSS, web page, or direct daily/weekly emails)!
It may be interesting to know if a common timeline for all project area's in IBM Collaborative Lifecycle Management tool is possible.
The production level scenario is that a team has Requirements Management (RNDG), Configuration & Change Management (CCM) and Quality management (RQM) activities, using LPA. But the fact is that you have to create separate timeline/iteration schedule for all 3 project areas, and then remember to update all copies whenever you would make a change. This can be of tedious if your development activities demand timelines for all 3 phases to be the same.
Now let me take you through the current behavior of timeline/iteration usage in all 3 components for IBM Collaborative Lifecycle Management (CLM).
Requirements Management using Rational DOORS Next Generation (RNDG) :
There is no support for timelines in RDNG.
RDNG does however have the concept of baselines that can be used to snapshot the state of artifacts, and with the introduction of DNG 6.0, there is now support for configuration management
You might want to take a look here for the new configuration management support: Administering configurations
Scheduled Jenkin Build Should run only if there are "changes accepted "
The Rational Team Concert (RTC) / Jenkins setup for continuous integration. On the "Jazz Source Control" tab the check boxes labeled "Accept latest changes before loading" and "Build only if there are changes accepted" are selected.
The expected behavior for this config is: The build will run whenever new change sets show up in the stream selected as flow target for the build repository workspace. In reality the build is started every minute regardless if there are changes or no changes.
Its not supposed to catch CI builds on the RTC side. The builds have to be driven from the Jenkins side. It will use the information from Jazz SCM tab to do the CI part, but it has to be Jenkins figuring out if a build is necessary.
So set up a the build in Jenkins to do the Poll SCM for a build trigger and setup a schedule there, and everything should work.
2) Jenkins should be driving the build schedule using the plugin.
Enable the Poll SCM under Build Triggers, which takes the cron argument.
For example: so */5 * * * * * is every 5 minutes, looks the information that the change set is available and accept the changes and trigger the build
every 5 minute.
1. MINUTES Minutes in one hour (0-59)
2. HOURS Hours in one day (0-23)
3. DAYMONTH Day in a month (1-31)
4. MONTH Month in a year (1-12)
5. DAYWEEK Day of the week (0-7) where 0 and 7 are Sunday
If you want to schedule your build every 5 minutes, this will do the job : */5 * * * *
If you want to schedule your build every day at 8h00, this will do the job : 0 8 * * *
The scheduled builds have to be driven from the Jenkins side. It will use the information from Jazz SCM tab to do the CI part, but it has to be Jenkins.
Note: The above configuration will give us continues integration. On the "Jazz Source Control" using the Jenkins cron argument and also it will stop the scheduled build if there are no changes accepted.
One of the users using IBM Rational Team Concert (RTC) 4.0.1 were planning to move some work items to a different repository.
To do this, they were considering the following options along with some requirements:
a. Move the work items, preserving workitem ID and if possible history also.
b. Export workitems to CSV file and then import it into other repository.
Here is the information that should help users with similar queries:
One can move the work items to a different project area, only in the same repository. This, using the move functionality for the Work Items. Even with this, it is not possible to retain the work item ID and the history.
Users can export the work item and import the work items into other repository, but any references to the exported work item will continue to reference to work item in the original repository and not its copy in the other repository.
So those references would break if the work item is moved.
Even the export/import does not include the history of the work item.
Rational Team Concert has a simple set of defined roles to enable key solutions for your organization. With Rational Team Concert you simply acquire licenses to support the roles and solutions that you are interested in. This provides you with an unprecedented level of flexibility and cost efficiency to choose and use only what you are interested in to support your needs. Rational Team Concert allows you to implement individual components of RTC now and others later simply through licensing - and without your typical deployment and integration headaches and risks.
When you purchase a role-based license for IBM Rational Team Concert you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management application. In addition, there are three types of Developer client access licenses.
Client access licenses
Types of client access licenses
Types of Developer client access licenses
Client access licenses: When you install Rational Team Concert, you deploy the Change and Configuration Management application, in addition to the Jazz Team Server. You then use activation kits to install product client access licenses on the Jazz Team Server and assign these licenses to users so that they can access the capabilities provided by the Change and Configuration Management application.
With a role-based licensing scheme, when you purchase a client access license for a particular role you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management application.
You install the client access license activation kits in the License Key Management section in the Administration page of the Jazz Team Server. You assign the licenses to users in the Client Access License Management section of Jazz User Administration. See Installing and managing license keys for instructions.
Types of client access licenses:
Role-based client access licenses: The roles in this table correspond to the client access licenses you can purchase for Rational Team Concert in this release. A role-based license will give you access (read; read and write; or read, write, and comment) to some or all of the capabilities in the Change and
Configuration Management application.
Legend: RW = read/write R = read only (and "comment" if user has RW access to Jazz Foundation)
Functional user licenses: When you install Rational Team Concert, you receive, in addition to the client access licenses above, the following functional client access licenses. These licenses are not for actual users. Instead, they are used as account IDs to set up connections to other capabilities. None of these licenses adds to the server user limit.
Developer Client Access Licenses: This matrix shows how support and the level of cross-server SCM capability afforded by a currently installed Developer client access license are affected by subsequently installed CALs.
Note: Only the Developer-10-C Client Access License is free For both the Developer-10-C and Developer for Work groups Client Access Licenses, the following restrictions apply. Only 1 activation kit can be installed per server Only 1 activation kit can be installed across any set of servers sharing the same floating license server
Trial licenses: When installing the server, there are two Installation Manager packages available for installation: Jazz Team Server and CCM Application installs the server components Rational Team Concert Required Base License Keys, including Trials installs the functional user licenses and the trial versions of the role-based licenses, For any deployment topology, you must install the Rational Team Concert Required Base License Keys, including Trials package on any machine with a Jazz Team Server that has one or more registered instances of the Change and Configuration Management application.
Once a Jazz Team Server is installed, you may install additional license keys in the License Key Management section in the Administration page of the Jazz Team Server
FAQs: To help resolve some common Jazz errors in your day to day activities without relying on anyone else, you may follow the technical documentation written by experts from Rational Licensing team below:
A query consists of one or more conditions that must be met by each work item in the result set. Each condition references a work item attribute, an operator and one or more values.
Till date, Queries can only be shared among members of same Project Area, Team Area or with individual users. There is no feature to share the Queries across different IBM Rational team Concert(RTC) Project Area's.
There is an existing Enhancement Request 318474 raised for the same:
As a workaround, you can create a Master-Child Project Inheritance which will allow the sharing of the Process configuration with other Project Area's.
1) Create a Master Project Area and create the Work-Item Queries.
2. Under Overview Tab, Allow this Project Area process sharing with other Project Area's.
3. Create a Unconfigured Project Area( Child project Area) and select the process sharing option to use the Master Project Area.
Currently, this only way to share queries across different Project Area's , as different project Area's might have different level of customization (ex: different custom attributes), which might make a query incompatible across different Projects.
As a Jazz Administrator, it's important to know the count of active work-items in IBM Rational Team Concert (RTC).
This feature is not available Out-Of-The-Box, you will need to search for the internal dependent service for the IBM Change and Configuration Management (CCM) application.
Steps you need to follow to find the location and work-items count:
1) Login to the ccm/admin web page.
2) Change the Public URL as below:
3) A service page will open, search for 'IDBTableSizeHttpService' and click on it.
4) URL will change to below: https://<<hostname:port>>/ccm/service/com.ibm.team.repository.migration.internal.stats.IDBTableSizeHttpService/
Search for 'workitem' and it will show you the exact count of the active
Note: Even though the work-item is deleted, the counter still increases. Using the above service, you will get the accurate count of active work-items( excluding the deleted one's).
Example: You have 10 work-items. You create a work-item and save it, it will show 11. Next, delete the work-item 11 and create new work-item and it will show 12. So the count is the total of active plus deleted work-items.
Similar steps have been tested for the Quality Manager (qm) application and works fine( replace the 'ccm' to 'qm' application name).
...and for any of our followers who may have been born on February 29th : HAPPY BIRTHDAY to you!
Now on to the videos....
Rational Team Concert, Rational ClearCase, and Cadence Virtuoso – a 3 part series
A new 3 part series of videos was recently published. The videos discuss the environment of the Solution for Electronic Design and how you can use IBM Rational Team Concert (RTC) and IBM Rational ClearCase to implement a Change and Configuration Management (CCM) environment to track library cell components in the Cadence Virtuoso Library Manager environment.
RTC plugin and Work item perspective is visible only for the user that directly did the installation (regardless of the fact they are administrators or simple users).
The RTC 5.0.2 plugin is only visible to the user that installed the plugin directly and not to the other users that can run IBM Integration Toolkit 10.0.0.1 on the same machine.
As IBM Integration Toolkit 10.0.0.1 should be opened by different domain users on the same machine, is it possible to install RTC plugin only once and make it available to all users?
RTC 5.0.2 P2 plugin integration with IIB toolkit 10.0.0.0 doesn't display for other user profile login.
Since IIB is not installed with IM we don't know how it installs itself and what multi-user install scenario is available later (multi-user install scenarios are listed in the Eclipse doc: Eclipse multi-user installs.
Note: Each user needs to install the P2 for RTC. That is because each user has his or her own Toolkit configuration.
This is evident in the eclipse.ini file that resides in the directory <installDirectory>/tools. The following indicates that the configuration path is unique for each user - based on the user's home directory:
** Workaround Steps **
In the eclipse.ini file that resides in the directory <installDirectory>/tools. ( eg: C:\IBM\IIB\10.0.0.0\tools)
Note: It is possible to change this path in the eclipse.ini file to a hard coded path so that all users use the same configuration, but there are some caveats to this: there might be other side effects.
All users of the IIB Toolkit need to have write access to the configuration.