dmmckinn 1200006SCS Visits (866)
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.
GRUC Webcast on August 13: IBM Static Analyzer – Taking your Application Security Analysis to the Cloud
JackSchneiderCO 270007HB0G Visits (818)
Chat with us live during the webcast! Join the CrowdChat to interact and network with fellow webcast attendees!
In this session we will introduce IBM Static Analyzer (now in beta) and show how it greatly simplifies static analysis (or white box) security scanning. We will discuss and demonstrate how it can easily integrate into the development lifecycle, as well as how it uses advanced analytics to produce targeted/actionable results to enable you to remediate security vulnerabilities.
***Dial in codes will be sent a few minutes before the webcast and posted in the online meeting. Please check your email before 12:00 PM ET (sender is
By registering for this webcast you are allowing the GRUC to provide your information to IBM and/or webcast sponsors for direct contact regarding IBM products and promotions. You will also receive a complimentary membership to the Global Rational User Community.
SunilKumarR 270001XXSY Visits (1125)
If you are looking for a simple tool to perform GET operation(s) on IBM Rational Quality Manager (RQM), then you are looking at the right post.
The RQM artifacts are exposed in XML format through the RQM's Reportable REST (REpresentation and State Transfer) API's. If you are in need to perform a quick GET (get XML) of the RQM artifacts without having to worry about the REST syntax and other nitty-gritties, then the "RQM GET" utility is a good option. This utility is built on the basis of the RQMUrlUtility and provides an interactive way to download the artifact XML using the artifact web IDs.
RQMGET requires a Java 6 (1.6) or greater.
-password : Login Password
-url : Https Url for the RQM application
Here is a sample command line trace of events on the RQM GET utility used to download artifact from an RQM server.
C:\>java -jar rqmget.jar -user clmadmin -password clmadmin -url http
You can download the RQM GET utility by clicking on RQMGETUtility.zip.
Rajeshavanthi 2700022MCX Visits (979)
You could see the 'Additional delay' under Client processing delay section for each request, under Advanced tab.
What happens if you make this delay to zero??
Does the play back show much difference in overall response time?
Generally, the time taken to load the entire page outside IBM Rational Performance Tester (RPT) cannot be mapped to the time taken to load the same page when invoked via RPT recorder. There are lot of parameters that RPT, as a load performance testing tool, accounts for (such as the traffic and connection information).
Also, RPT processes these Client side delays in parallel or sequentially depending on how the application server returns them. Sometimes if you try modifying/disabling the client processing delay value, it may also disable the immediate transaction under Rational Performance Tester. Because, practically speaking, when you disable a request, you potentially invalidate some delays because in theory the disabled request could have been the basis for a delay. Therefore, RPT automatically recalculates the delays on the page when you disable a request. That is, if a later request used the disabled one as a base, the later delay request should be adjusted.
Now, let's come to your question about why such discrepancy between the response in the browser and RPT...
Often times when you see response times that are inaccurate it is because of recording your actions too fast and so you end up with more than one page being combined together. When recording, you need to be mindful and make sure to pause between mouse clicks. Do an action and wait 5 seconds before continuing on to the next action. You also need to pay attention to where your mouse is and make sure you have no "hover gifs" that you accidentally cause to be sent to the server while recording.
To see if you have these problems you have two things you can look at.
1. Open the test and click on the name of the test under test Contents in the tree. Click Select->Request. On the right hand side you will see a table of all requests in your test. Look at the delay column and look for really large delay values. If you have these, they are usually caused by recording too quickly, and act as an "embedded" think on the page. The Client Delay is supposed to simulate how long your client took to process the data from the server before sending the next piece of data. When you record too quickly, these values can be skewed. You can also go to a specific page that is taking too long and look at those specific requests. You can use the same Select button, or you can go to the Advanced tab of each request and look at its delay.
2. If you find the delays are your problem, then you can split the page where the delays are long since this was probably supposed to be two pages. This will move that delay to be the think time of the page which would be more accurate. You can also go to Wind
Also remember that when doing recording, we will capture each connection that was used and will send out the requests on the same connection that they were sent on originally. If you had two connections sending requests at record time, we will send requests on two connections at execution time. If you see a really long client delay, then look at that request in detail to determine if it was something that was sent by a user gesture or as a result of the primary request.
Arun K Sriramaiah 2700076GE8 Visits (964)
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).