Rajeshavanthi 2700022MCX Visits (103)
There are many instances where you get reports indicating higher page response times in the IBM Rational Performance Tester (RPT) generated reports. You tend to correlate these metrics against the usual time behavior noticed when accessing the application under test outside RPT. It could be a case as well where even if you add all the page elements listed in report, the response time is much less compared to overall response time for the transaction.
The page is considered to begin when the first action (typically a request) associated with the page starts execution. If this request needs to make a connection, the page response time will include the connection time. The page ends when the last action (usually a response) of the page completes. RPT would adjust the page response time to remove the time spent in client delays. In RPT 8.2 this changed after determining it was more representative of the real-world response time to leave the client delays in the page response time. Thus, in RPT 8.2 and later, the page response time does include client delays.
However the Think Time value set in the schedule is not included in the page response times displayed in the Performance report. It should be noted that there are potential "delays" in the script that could increase page response times. Think times are associated with pages and are intended to represent human pauses during recording - these don't impact page response times. For individual page elements (requests), there may also be delays which are intended to represent client (browser) delays (processing time for example). These will be reflected in page response times
Questions could arise such as: How does RPT calculate the Page level response time as compared to Request level response time for a given page?
In case the first request used a new TCP connection, it calculates the difference between the timestamp when the connection for the first request in the page was made and the timestamp of when the last byte was received for the last request in the page. In case an existing connection was reused, the timestamp of when the first request was sent is used. All these timestamps are available in the test log if full logging is on. If a existing TCP connection is re-used, the value "Time to Connect" in the test log will be 0 .
Arun K Sriramaiah 2700076GE8 Visits (309)
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 (322)
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.
Shradha_S 270007543G Visits (323)
In IBM Rational Reporting for Development Intelligence (RRDI) or Insight, custom enumeration attributes and values are not stored in the same tables and need other joined queries to access the values in your report.
To create an enumeration report, follow the below steps.
1) Launch Report studio, select create new report, from the package select Blank template and move to Query Explorer.
2) Create three queries for Work-item, Enumeration and Enumeration literals.
2.d) To filter against a specific Enumeration, add a filter to Name field and use the value of Enumeration ID in Enumeration literals value query.
3) Now from the Query Toolbox use Join option to join the above created queries.
Click on Join button to link the common key select "Request ID" from Workitem and Enumeration literal queries.
3.b) Create a join query and name it "Enumeration". Join the query for "Wor
Click on the Join button to link the common key, select "Value" from "Wor
Select the fields from both the queries "Wor
4) Now insert the columns of query 3.b in report and run the report.
Additional information can also be found in the Repo
GRUC Webcast on May 28: Making the Business Case for Mobile Application Security: Practical Examples from IBM's Analysis of Major Mobile Applications
JackSchneiderCO 270007HB0G Visits (326)
LIVE TWEETING DURING THE WEBCAST! USE #GRUCMobile TO FOLLOW AND SUBMIT QUESTIONS AND COMMENTS TO OUR SPEAKER
Does your company test its mobile applications for security vulnerabilities? A recent Ponemon Institute report found that 77% of organizations believe that it's hard to secure mobile applications. That's one of the primary reasons why fewer than half of organizations actually test their apps for security flaws. But, at what cost?
In this session, we'll examine vulnerabilities that were detected by the IBM X-Force security intelligence team in real-life mobile apps and frameworks, and we'll dig deeply into results from our recent research that was conducted on vulnerabilities associated with more than 40 top online dating applications.
We'll also conduct a live demo that shows you how you can conveniently scan mobile applications, and utilize results to fix detected vulnerabilities and integrate best practices into your Secure Software Development Life Cycle (SDLC).
Eitan Worcel, Product Manager - AppScan Cloud Services
Eitan Worcel is an experienced software developer, with years of experience in the Application Security field. His development expertise is currently leveraged in his role as Product Manager for IBM Security AppScan Cloud-based Services. Throughout his career, Eitan's worked with a wide range of customers, supporting them in their quests to build secure web applications. The IBM product line he manages helps users to protect their valuable web and mobile applications.
***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 (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.