Arun K Sriramaiah 2700076GE8 Visits (713)
The RTC workitem id, which is generated automatically from the system, also assigns an internalID.
When a customer has multiple teams, such as developers and a management team, simultaneously working on projects,
how can you identify which work item ids belong to which projects or departments?
RTC Workitem id's can be prefixed with the project\department names + internalID in attribute customization calculated value script.
You can use this customization if the value of an attribute must be calculated instead of entered by the user. Optionally, the calculated value can depend on the value of other attributes in the same work item. An attribute configured with a calculated value customization should use a read-only presentation. Here are all Calculated Value customizations that you can configure using the Eclipse client:
1) Enable scripts: Go to administrative page of your RTC server : http
5) Save the workitem and verify that the Newid attribute value should be ( "IOT Banking "+in
dmmckinn 1200006SCS Visits (697)
Our peeps have been busy creating videos to help you get the most out of our products. Check out these recently published educational videos.
Arun K Sriramaiah 2700076GE8 Visits (1097)
This article is regarding Rational CLM integration with JIRA, able to get the information that JIRA can be integrated with CLM containers (RRC, RTC and RQM) with Rational Adapter for JIRA.
Advantages of RTC and JIRA Integration
Following are some of the benefits that an organization will get by integrating RTC with JIRA:
As per the topology, JIRA application is installed on a single application server and the CLM applications are also installed on a single application server.
For example: Standard Topology
The JIRA application server communicates with the CLM application server through server friend relationships. The adapter resolves links from CLM work items back to the JIRA server.
As long as the JIRA application can connect or ping to the repository you may install it on the same machine or another server
Arun K Sriramaiah 2700076GE8 Visits (949)
This article explains how to reduce the number of Rational Team Concert component flow displays in the pending changes window.
By default, all components in a Repository workspace (RWS) use the current flow target. You can use the Repository workspace editor to add flow targets or change their scope so that not all components use them. Refer to Flow targets for further details.
For example, you can specify in flow targets for some of the components in a Repository workspace (RWS) display, or decide that a specific component must display in pending changes window.
Note: You can use the Flow Only components checked below option in RWS\Stream Flow Target to make the Pending Changes view more manageable. This helps more when streams or workspace have 10++ and which might not be all needed in the pending changes window.
You can use the above scenario where in you can avoid unwanted components display in the pending changes.
Arun K Sriramaiah 2700076GE8 Visits (1000)
Here is a collection of some of the Basic Rational Team Concert Source code management links from IBM Rational Support. We hope you will find them as helpful as we have.
RTC Source Control Basics
RohitBalduwa 2700066W8H Visits (995)
The external help desk is the way Service Desk integrates with Rational Team Concert. When Service Desk users publish an incident to this external help desk, the integration creates a work item in a Rational Team Concert project area.
Note: ClearQuest was the first Rational Configuration Management tool supported by the Rational Connector. When support for Rational Team Concert was added, SAP did not update the SPRO documentation. This will be corrected in a future release of Solution Manager.
dmmckinn 1200006SCS Visits (1146)
In continuing on the topic of Performance testing, Vaughn Rokosz takes a look at some of the common reasons performance tests can fail, and suggests ways of tuning your servers to avoid the common issues.
Take a look at his latest article that includes the following:
For your convenience, here is the link to the previous article on the subject: Creating a perf
dmmckinn 1200006SCS Visits (941)
Looking for information about how to build performance simulations?
Building a good simulation of a user population requires expertise at many levels, including:
In the following article Vaughn Rokosz, a technical lead for the CLM performance team, shares some of his experiences with building performance simulations of the Jazz products. He walks through a simple example demonstrating how to build a simulation of a user population that is creating work items in Rational Team Concert. He also shares some of the things used to make the development of performance simulations simpler by attaching the Rational Performance Tester project that he used when working through the example.
Stay tuned for part 2...
dmmckinn 1200006SCS Visits (864)
A new article “Rational Team Concert essentials: A developer's perspective: Part 2. Delivering Work Contributions” has been published. It is a continuation of the conversation started in the Part 1 article published earlier this year.
This article series describes many operations a developer is responsible for from the time they join the project to the time where they are ready to deliver their features and fixes. This series is meant to be a helpful collection of "developer's cheat sheets."
A developer's perspective: Part 1. Joining a new team project Explore the main concepts behind Rational Team Concert's change management mechanisms, joining a team project, creating a repository workspace and loading your project components and artifacts. In Part 1 of this series, you will learn how, step-by-step, to join a team project, create a workspace to contribute to your project, and load existing artifacts from your team’s project components.
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.
Arun K Sriramaiah 2700076GE8 Visits (963)
The idle standby configuration enables recovery from failover to help ensure minimal impact on business operations during planned or unplanned server outages and Idle standby deployment for crash recovery.
Refer to Impl
Important: Jazz Team Server applications allow only a single server to be active at any one time to a repository; therefore the backup (or Idle) server is configured to never run asynchronous (or background) tasks. If a switch is made to the backup server, you must plan to bring the primary server back up as quickly as possible.
Index corruption can be caused by Network, database or application server issues, to name a few. Below are the steps to fix the index corruption issue on active server, using the idle standby server.
Index corrupted occurred on the Active server and you were unable to fix it by running the repotool command on it. So we can still fix the index issue by running a repotool command on the idle standby server.
Fixing the index issue on active RTC server using the Idle standby server.
Below are steps to fix the index problem, using the IDLE standby server. The standby server is on a different machine (and pointing to a different jazz_home than the active one).