Rajeshavanthi 2700022MCX Visits (218)
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 (243)
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).
Arun K Sriramaiah 2700076GE8 Visits (417)
Rational Team Concert server is expected to have a common user base management. In order to correctly perform process enforcement for Git operations by Rational Team Concert it is imperative that the identity of the Git user be known to Rational Team Concert. Therefore, the need to have a common user base across Rational Team Concert and Git server (Apache HTTP server) via a different LDAP arrangement.
We can still get the integration done using a common user name with different user base across Rational Team Concert and Git server via an different LDAP arrangement.
Example: Git is configured with Apache DS LDAP and RTC configured with different LDAP registry.
Note: Common user id used for both GIT and RTC using different registry (with different password) and provide all necessary permissions.
Below are checkpoints for verifying the integrations:
1) Verify the GIT login, just to ensure GIT login is fine
$ git remote show origin
2) Verify the GIT GIt repo configuration
Update respective "repokey" and "repourl" information
3) Verify the GIT GIt repo configuration
Update respective "pre-receive" and "post-receive" hooks information
Note: The above configuration will give a clear understanding about RTC-GIT integrations and using a common user name with different user base across Rational Team Concert and Git server via different LDAP arrangements.
Kiran Byrappa 270001YMWT Visits (376)
Post upgrade of your CLM application you may come across the below error while trying to access any Project Areas in Rational Quality Manager.
The error occurs when QM is not deployed correctly which could be the result of an incomplete / improper upgrade process and when WebSphere cache was not cleaned prior to deploying 5.0.2 war file.
Checking the logs reveals the below error:
You may follow the below steps to redeploy QM:
3. Re-deploy QM.war
4. Redo the group mapping in WebSphere by following the below steps:
Map security roles to a user or repository group:
a) Go to Applications > Application Types > WebSphere enterprise applications.
e) Enter a search string to return your group names from the LDAP server. Click Search to run the query.
Kiran Byrappa 270001YMWT Visits (499)
Post upgrade of CLM your attempt to login to Rational Quality Manager instance displays an error indicating that your server appears to be in bad state.
You may want to check the following to ensure that the required services are setup properly and are up and running.
naomimg 060001F9C7 Visits (459)
As we (Naomi Guerrero and Denise McKinnon) assume ownership responsibility for this blog from our esteemed colleague Jason (acdntlpoet: http
To the faithful followers of this blog, we promise to continue to provide you with the meaningful content and posts that help you to be successful. We want to encourage open collaboration with our followers and appreciate new ideas about topics you want to know more about. Find out a little bit more about us below!
Joined Rational support back in 2000, holds a BA in Information Systems and has over 35 years experience in IT (for those who remember programming on Punch Cards). I've held various positions as a Technical Support Engineer, Knowledge Engineer and most recently as a Social Business Analyst where I am most excited to be delivering support messages through this blog.
About Naomi :
Joined Rational Support in 2006 as a Software Engineer. I have nearly 15 years experience in IT and hold a Computer Science degree. In August, I will begin pursing an MBA advance degree. I am currently a Social Business Analyst for a subset of products within IBM.
We look forward to collaborating with you!
dmmckinn 1200006SCS Visits (402)
New video published to the IBM
Kiran Byrappa 270001YMWT Visits (562)
This article discusses how you can identify the "Actual Start and End Dates" in Rational Quality Manager.
There will be instances where a testing effort would be delayed and one needs to capture the actual date it started as apposed to the planned date it was supposed to be started.
The planned start and end dates are inherited from the dates in the timeline, as are the actual dates that are shown in brackets next to the iteration name.
The following steps lists the steps you will need to perform to edit the Actual dates:
1. Navigate to 'Test Plan > Test Schedule'
3. Edit the dates under the Planned Start Date and enter the description as required
Also, the other way is to define the "Custom attributes" in the test plan where you will need to manually enter the Proposed / Actual Start / End dates.
When you are defining the custom attributes you may mark the 'Planned/Proposed Start and End Dates" as "Required" so that one cannot save the test plan without specifying the planned dates.
While creating the test plan this should look like below:
You can use the "Browse Test Plans" and compare the 'Actual Start / End Dates' Vs 'Planned / Proposed Start / END Dates".
vjagadeesh 2700063KJN Visits (637)
Correlation of cookies is not mandatory in RPT. During playback some values which are recorded during scripting are sent to the server to be processed, but these values most of the time are dynamic in nature, and they do not form the page content during response from the server. Cookies are usually cached to be reused by the page, but these do not give the correct response time for the page content. Hence, some times the test is run by disabling the cache. To summarize, no it is not necessary to correlate cookie in RPT, as they do not form the basic contents of the page.
AcdntlPoet 2700019V2G Visits (648)
It is somewhat of a bitter-sweet day for me as I hand off ownership of this blog to a new team of colleagues to take this space and bring it to even higher levels of value. I'm letting go of this blog as part of my transition in to the IBM IoT support organization where I am working on social business strategy and logistics like I did for Rational Support all these years.
As you may have already noted from the about section to the right side here, I am leaving this blog in the very capable hands of Denise McKinnon and Naomi Guerrero. I couldn't be more pleased to leave this institution in their hands, much like Kelly Smith did for me a few years back. Rest assured, you will get the same if not better information and value from this blog moving forward as you did previously.
But now I hear you asking... What IS IBM IoT Support? And THAT, my friends, is a great question!
IBM IoT Support is a team of IBMers who are now part of the new IBM Internet of Things organization supporting the tools makers like you need to build components and connected devices. IBM IoT Support is focused on helping you, the makers, with your product questions by providing content relating to the various products covered by our new division.
Through our focused support of asset management and continuous engineering tools, we are here to provide you with the best support in the industry; to help you be successful with the applications and components to ensure your work on the connected devices in the Internet of Things brings you the right value.
The products we support here include:
There's no change in the way you will obtain support for the products you already own, the only change you'll likely see is the addition of a few new social channels like our blog, our new Twitter account, and our new Youtube channel to help get you the right content at the right time. Our technotes can all be found in their same locations per product, and the process for contacting support to open a Problem Management Request (PMR) remains the same as well. We hope you'll follow us in our new spaces!
Cheers to you all!