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.
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 (18.104.22.168) for 7.1 - IBM Rational Synergy Fix Pack 22.214.171.124 has been made gener... http://ow.ly/1dhwlR
IBM Rational Synergy 7.1 Fix Pack 0.3 Windows - This Fix Pack solves 126.96.36.199 problems with Synergy CLI, G... http://ow.ly/1dgcgf
IBM Rational Synergy 7.1 Fix Pack 0.3 UNIX - This Fix Pack solves 188.8.131.52 problems with Synergy CLI, GUI,... http://ow.ly/1dgcgg
IBM Rational Synergy Interim Fix 1 for 7.2 - IBM Rational Synergy 184.108.40.206_iFix001 has been made generally ava... http://ow.ly/1ddt4b
IBM Rational Synergy 220.127.116.11 iFix001 UNIX - This Interim Fix solves 7.2 problems related to DCM clusters ... http://ow.ly/1daUF5
IBM Rational Synergy 18.104.22.168 iFix001 Windows - This Interim Fix solves 7.2 problems related to DCM cluste... http://ow.ly/1daUF4
IBM Rational AppScan Standard Edition-Windows-22.214.171.124-Rules-Update-1282-Recommended http://ow.ly/1dlhR6
IBM Rational AppScan Standard Edition-Windows-126.96.36.199-Rules-Update-1279-Recommended http://ow.ly/1dfQbN
IBM Rational AppScan Standard Edition-Windows-188.8.131.52-Rules-Update-1273-Recommended http://ow.ly/1ddaX8
IBM Rational Systems Tester 184.108.40.206 - 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 220.127.116.11 - IBM Rational Insight 18.104.22.168 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)!
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:
There have been a few queries asking why organizations should use at least one Team Area with all same members as in a Project, using IBM Rational Team Concert (RTC).
The requirement for end users maybe something similar:
We have small projects only about 20 members per each and we don't need separate project members into teams.
Is there any reason why we should use at least one team with all same members as is in project?
Or can we just use only project without creating teams at all, if we don't need more than one team?
Is there like some reporting or source control aspect which might be missed if at least one Team Area is not used in projects?
--> The following details provide some basic information about Team Areas and their usage in RTC:
Creation of Team Areas is optional and not mandatory. It is up to the discretion of the users to analyze and see if having a team area is required or not.
Having at least a single team area or not will not have any impact on either reporting or source control aspects of RTC.
Team Area is more of an encapsulation model sorts to encapsulate users into a particular team and a specific iteration/Release.
Assume the Product Development team consists of a Development line and Maintenance line.
Here one might want to create two teams and add users accordingly, such that Development line users will have access to Development Project
Area and Maintenance line users will have access to Patch/Fix-Pack Project Areas only. In such cases, using Team Areas will help.
Otherwise based on the need, users can go ahead and use the single Project Area for an entire team of small size.
The advantage of this is, it will reduce the overhead on the administration aspects for a Team Area.
--> Here is what the Team Area serves:
Having a team area is optional, but most projects of moderate to high complexity will have one or more team areas.
A team area serves these functions:
Defines the users (team members) on the team and specifies their roles.
Defines the timeline in which the team is participating.
Customizes the project process to the needs of the team.
Rational Team Concert allows for a hierarchy of team areas to accommodate more complex projects and large teams with varying needs
within the project. Any contributor to a project can participate in one or more team areas.
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
If there is a need to know the cipher used by CLM applications or RTC and the level of encryption used for web-clients, this blog should be of some help.
Cipher refers to the algorithm used for performing encryption and decryption of the data.
Generally, SSL (Secure Socket Layer) is used for data encryption, decryption and transmission using certificates or smart cards. However, this also depends on the kind of Application server being used. Based on the kind of application server in use, the respective product documentation should have the details on the cipher used.
Websphere Application Server, Apache Tomcat
a. For Internet Explorer, login to RTC and then right click on the web-page --> Properties;
This displays the connection details with the encryption data for the URL.
b. For Firefox web-browser, if one hovers and clicks on the padlock symbol prior to URI in the address bar, say before https: //hostname:9443/ccm/web in the address bar, it gives the following information:
Connection Encrypted: High-grade Encryption (RC4, 128 bit keys)
So, if the RTC/CLM installation is based on Websphere Application Server (v7.0), the site supports a minimum cipher strength of 168 bit encryption. This, can be confirmed by looking into the properties for ccm application web-page and the application server documentation.
By default, using the Apache Tomcat application server the site supports a minimum cipher strenght of 128 bit encryption.
The cipher indicates that the data is encrypted between the Internet browser and the Server. It doesn’t encrypt the data on the database itself.
This is what is behind the HTTPS protocol and is managed by the Application server. RTC is only an application installed on top of Jazz, which is installed on WebSphere.
Here is another good lesson, among many that I happened to learn, while working with a customer using IBM Rational Team Concert (RTC). While this may not serve as a supported solution for the issue reported, perhaps it can serve as a pointer or guide on the types of things to look for.
A user starts IBM Rational Team Concert (RTC) Eclipse client and sees that his personal preferences were lost.
I asked user to send metadata.zip file located in the Eclipse workspace path. For example: C:\Users\Administrator\workspace\.metadata
Here were a few significant messages in the .metadata/.log file:
!ENTRY org.eclipse.core.resources 4 567 2013-04-15 10:48:06.160
!MESSAGE Workspace restored, but some problems occurred.
!SUBENTRY 1 org.eclipse.core.resources 4 567 2013-04-15 10:48:06.160
!MESSAGE Could not read metadata for
at java.io.DataInputStream.readInt(Unknown Source)
at org.eclipse.core.internal.resources.MarkerReader.readVersionNumber(Unknown Source)
at org.eclipse.core.internal.resources.MarkerReader.read(Unknown Source)
at org.eclipse.core.internal.resources.MarkerManager.restoreFromSave(Unknown Source)
at org.eclipse.core.internal.resources.MarkerManager.restore(Unknown Source)
at org.eclipse.core.internal.resources.SaveManager.restoreMarkers(Unknown Source)
at org.eclipse.core.internal.resources.SaveManager.restore(Unknown Source)
at org.eclipse.core.internal.resources.SaveManager.startup(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.startup(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.open(Unknown Source)
at org.eclipse.core.resources.ResourcesPlugin.start(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Unknown Source)
Based on the message, it was clear that the user was using a particular workspace and when he tried to launch Eclipse client using this, he sees that his personal preferences were lost.
He tried to start the Eclipse client fresh and saw this issue.
The user did not try to change the workspace of the RTC Eclipse Client prior to this.
I got a confirmation that the user had the default Eclipse installed with RTC client and did not have a separate installation of Eclipse. Just one instance of RTC Eclipse client.
I did verify the total physical RAM on the machine where the user saw this problem and they had enough RAM. (8 GB)
I wanted to verify the heap memory allocated to the Eclipse client, the details which were in the eclipse.ini file.
Example: For default RTC Eclipse client, the location is:
I wanted to know the values for the entry "-vmargs -Xms100m -Xmx512m" here. They were using the default entry here for the heap memory allocation and was good enough. They had the room to increase this though, since the available physical RAM was 8 GB.
I asked the user to get the build details of the Eclipse client; Go to Help --> About Rational Team Concert. This lists the RTC version along with the build details.
After analyzing the .metadata\.log file and the errors in there, we found that for some reason the preferences were lost due to workspace
corruption. What caused this, I am not aware yet though.
Normally, here are the steps users should try in case of lost preferences and to avoid loss of preferences:
In the Eclipse client, navigate to File --> Switch Workspace --> Choose the current one in use; In the Workspace Launcher --> Copy Settings --> 'select' Workbench Layout; Then point to a new Workspace path and verify the outcome.
The RTC client is built on Eclipse and the user preferences are backed up, like in Eclipse client, by going to File --> Export --> General --> Preferences and saving this file.
In case of any corruption or loss of personal preferences, just import this file to restore the preferences.
Apart, all settings are stored in the .metadata/.plugins/org.eclipse.core.runtime/.settings directory. The .metadata/.plugins directory might have many more directories with settings, but they are generally project specific.
So if you want to create a new Eclipse workspace and preserve all your settings, simply copy the .metadata/.plugins/org.eclipse.core.runtime/.settings directory into your new workspace directory.
Lastly, it is also a good practice to do a full backup weekly, with corresponding incremental backups daily of the user's workspace. This provided, it's critical for the user to restore their complete previous workspace. Yes, backing up of the workspace is not a light procedure but a good practice, if there is a need.
I hope this gives some idea for users and the steps that can be taken, in case of a similar situation.
Here is an example requirement that one of my clients was looking for in IBM Rational Team Concert who asked: "Is it possible to select an enumeration value for an attribute and this in-turn based on the value selected, display text area in RTC?"
There is an attribute named 'Location' and the enumeration values for this attribute are 'USA, UK, India'. Now if the users select any of these enumeration values, say 'USA', they should get a field next to this selected enumeration value displaying a text, say 'Miami' or so a field where users can write the location manually.
Is this feature available in RTC 4.0.1, 4.0.2 or 4.0.3? At the time of writing this article, there is no straight forward way to achieve this requirement for the RTC versions mentioned.
--> This requirement can essentially be broken into 2 sub-requirements:
Attributes with values dependant on another value.
Here is a jazz.net article which should help one in customizing the requirement:
'Read-only control for Work Item attributes in Rational Team Concert 4.0' https://jazz.net/library/article/997/
--> However, there are a few RFE's which are in discussion for CLM 4.0.x, as mentioned below:
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) 22.214.171.124 server running on JFS 126.96.36.199 on server machine 'A'.
Rational Quality Manager (RQM) / Rational Requirements Composer (RRC) 188.8.131.52 running on JTS 184.108.40.206 on server machine 'B'.
Each having their own database servers, running on their respective server machines.
They were able to successfully register RQM 220.127.116.11 application on the RTC 18.104.22.168 server, however, trying to register RTC 22.214.171.124 on RQM 126.96.36.199 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 188.8.131.52 to RTC 184.108.40.206, 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 220.127.116.11 at RQM 18.104.22.168 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 22.214.171.124 the integration for RQM, RQM must be 2.0.1 or 126.96.36.199. 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 188.8.131.52 in RTC 184.108.40.206 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 220.127.116.11 and RQM 18.104.22.168 at RQM 22.214.171.124 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.
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:
Integrations between Rational Team Concert and Rational ClearQuest
There are various types of integration capabilities between IBM Rational Team Concert (RTC) and Rational ClearQuest: the bridge, the synchronizer, and the importer. If you are looking for help in deciding which integration capability best suits your current deployment or your future deployment plan, read on to get a better understanding about the technologies that are available to you, as well as some of the deployment considerations.
The Rational ClearQuest Bridge provides a bi-directional traceability link from records in Rational ClearQuest to work items in Rational Team Concert. It is a linked-data type integration based on the Open Services for Life-cycle Collaboration (OSLC). It provides a seamless user experience with rich hover UI preview, and delegated dialogs including advanced selection dialogs, and fully functional creation dialogs. These dialogs support ClearsQuest record form layout and hooks. The bridge integration also enables ClearQuest live data on a Rational Team Concert dashboard.
Rational ClearQuest Bridge is primarily for users who want to continue to use Rational ClearQuest as a change management system, but also want to take advantage of other features of Rational Team Concert, such as agile planning and dashboards. You do not have to change your current usage of Rational ClearQuest, but you can enhance your Rational ClearQuest deployment by using Rational Team Concert in a complementary fashion. It provides a ClearQuest shop with a fast path to realize the value of Rational Team Concert.
It is implemented as a function of the ClearQuest Web and uses the ClearQuest OSCL REST API interface. ClearQuest is an OSLC Change Management(CM) provider and a consumer. It provides OSLC CM v1 and v2 interfaces, and also consumes OSLC CM services provided by other tools. ClearQuest OSCL REST API is also a desired interface if you want to integrate your own application to ClearQuest. Since it is HTTP-based, you can call it from any program that supports HTTP, and it does not require the ClearQuest client to be installed on the machine where you execute your application.
Through the same bridge integration technology, you can also integrate ClearQuest with other Rational tools, such as Rational Quality Manager (RQM), Rational Requirement Composer (RRC), and Rational DOORS, and with 3rd party tools, such as HPALM and Git.
Rational ClearQuest Synchronizer
The Rational ClearQuest Synchronizer is a data replication between Rational ClearQuest records and Rational Team Concert work items. It supports flexible bi-directional or one-directional synchronization between a Rational ClearQuest record and a Rational Team Concert work item. Changes in one application are applied to another using synchronization rules, which provide the mapping and transformation information.
It is primarily for the customers that want to incrementally adopt Rational Team Concert by having different teams use different tools. Some projects/teams (for instance, a development team) can choose to start using Rational Team Concert while other teams (for instance, a support team) continue to use ClearQuest. The teams using Rational Team Concert and the teams using ClearQuest have access to the same data (duplicated by the Synchronizer based on the configured sync rules). Reports can also be run in either system since the data is consolidated.
The ClearQuest Synchronizer is implemented as an application of the general Jazz item connector framework. It is a separate component of the Rational Team Concert offering, and requires setting up a Gateway service. It uses ClearQuest CM API interface to communicate with ClearQuest. It can also be used between Rational Qualify Manager (RQM) and ClearQuest.
Please note that there is a high maintenance and support cost associated with the Rational ClearQuest Synchronizer. Conflicts can occur when two users make nearly simultaneous changes to a ClearQuest record and its corresponding work item, and an administrator needs to constantly monitor these conflicts and resolve them manually by selecting the appropriate value. It is highly recommend that you evaluate the Rational ClearQuest Bridge integration before jumping into the Synchronizer integration.
Rational ClearQuest Importer
The Rational ClearQuest Importer provides a one-way data migration from Rational ClearQuest records to Rational Team Concert work items. It imports ClearQuest records based on a user specified query, and uses a mapping file to declare how fields and values are mapped from a ClearQuest scheme to a Rational Team Concert process definition. It supports importing stateful record types, Users, Notes, Attachments, Work Item Relationships (duplicates, parent / child, blocks / depends on, and related), and creates missing objects, such as Contributors, categories, and iteration, on the fly.
The Rational ClearQuest Importer is primarily for the customers that want to move from using ClearQuest to Rational Team Concert as the change management system instead of maintaining both applications, and want to bring over certain ClearQuest records to Rational Team Concert.
It is implemented as a function in the Rational Team Concert eclipse client. It is based on the Bugzilla Importer, and uses the ClearQuest CM API to communicate to ClearQuest. You must install ClearQuest client on the machine you run the ClearQuest Importer.
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:
These are ten of the most recent How-To technotes for IBM Rational Team Concert (RTC). We know you will find them as helpful as we do, especially since they were all created based on client calls/ emails that have come in to our Support Engineers and the answers from which have been reused to solve even more PMRs than just the initial call...
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.
Ralph Schoon has posted a great reference, tutorial, and code on his personal blog which provides for A Rational Team Concert WorkItem Command Line! He provides code for a simple Work Item Command Line Client and explains the usage in a detailed but easily understood manner. Of course, noting that the post contains published code derived from examples from Jazz.net as well as the RTC SDK, we need to state that the usage of code from that example source code is governed by this license andas stated in the disclaimer, this code comes with the usual lack of promise or guarantee.
Since we have seen many requests to be able to create and update work items from a command line in the forum, as well as enhancement requests and a story for it in the RTC development repository, we wanted to highlight Ralph's work as a great starting point for creating these solutions. This WorkItemCommandLine should provide access for most of your automation needs when creating work items, as well as standing as a resource for the RTC work Item API.
So, go ahead and check out Ralph's blog post; we think you may find it stands as a hugely valuable resource as you move forward with your own RTC work!
Did you notice the hubub yesterday? No? Missed the excitement, eh? Well have no fear, we're here to help!
Collaborative Lifecycle Management 2011 (CLM 2011 for short) went live yesterday, amid some fanfare over on Jazz.net. To help you navigate and find some of the new and relevant CLM information, following are some outstanding resources for all your CLM 2011 needs!
And because we know you all love your pointers to the downloads:
Rational Requirements Composer 3.0.1: IBM Rational Requirements Composer 3.0.1 has been made generally available as part of the Rational solution for Collaborative Lifecycle Management (CLM) on PPA and Jazz.net.
Rational Team Concert 3.0.1: IBM Rational Team Concert 3.0.1 has been made generally available as part of the Rational solution for Collaborative Lifecycle Management (CLM) on Passport Advantage (PPA) and Jazz.net.
Rational Quality Manager 3.0.1: IBM Rational Quality Manager 3.0.1 has been made generally available as part of the Rational solution for Collaborative Lifecycle Management (CLM) on PPA and Jazz.net.
Don't miss the Jazz blog post for even more information around the CLM release and downloads pus common installation info and tips!
One of the queries that I received, while working on IBM Rational Team Concert (RTC) is this:
I would like to change the configured Active Directory (AD) location (domain controller) of the Jazz Team Server.
Can we just change the LDAP Registry Location setting in the Advanced Properties in JTS and do we have to restart the server?
Firstly, I asked the user to confirm that by changing the configured AD location, it does not involve a change in the public URI for the Jazz team server.
(i.e. change in either the fully qualified domain name in the URI or the hostname).
He did confirm that they only want to change to another domain controller running Active Directory and containing the same user information.
No changes in the Jazz Team server location or the hostname.
==> Essentially to achieve this, you must do the following:
1. Change the LDAP location in the Jazz Server properties.
Login to JTS as admin: https: //<host_name>:9443/jts/admin
Go to server --> Advanced Properties;
Look for these two services and update with the latest parameters: -----
2. Change the LDAP host in Websphere Application Server (WAS).
3. Redo the Security role to user/group mappings in WAS because of the realm change.
I have been asked by a couple of customers using IBM Rational Team Concert (RTC) to see if there is a way to make 'Links' as a required attribute with regards to RTC Work Items. A sample scenario they've noted, where having 'Links' as required attribute being useful, is something like this:
A user creates a Work Item, say a defect, in RTC and the work flow demands that any newly created defect be linked to a requirement artifact. In such case, having 'Links' as required attribute will help the users, so that they do not skip on adding the link to another artifact.
This self-guided workshop will walk you through process enactment in Rational Team Concert including the interaction between RTC and Rational Method composer, as well as describing the process to your team members.
The workshop also contains labs around the following topics to help you learn by doing:
Lab 1: Set Up the Process Enactment Environment
Lab 2: Understand the Process Development Lifecycle
Lab 3: Configuring Work Items
Lab 4: Work Item Customization
So why not take this opportunity to build your personal knowledge base and become even more familiar with process enactment for CLM by clicking over to Jazz.net and starting this new workshop and associated labs. You'll be glad you did!