Soumya Y Shanthimohan 270004GAQS Visits (1795)
With the rise of Ajax powered sites, it is becoming very important for the websites to load the data quickly, asynchronously and without any delay.
For AJAX applications, JSON is faster and easier than XML.
Difference between JSON and XML
Does RPT support JSON inputs?
Yes. JSON inputs are supported since the version RPT 8.2.1.
How to pass JSON inputs into RPT?
JSON inputs can be passed into RPT using the below two methods -
I. Proxy recording
The procedure is the same as recording a http test.
The use case would be:
1. [RPT Recording Wizard] Start a 'New test from Recording'
2. [RPT Recording Wizard] Select the option 'http test'
3. [RPT Recording Wizard] Record an "unmanaged application"
4. [RPT Recording Wizard] Selection of an available port on the machine, and then start of the recording.
5. [SoapUI client ] Launch SOAP UI > File > Preferences > Proxy settings
6. [SoapUI client ] Populate the 'Host' flied with the value 127.0.0.1. The Port number should be the one that you selected during recording (as in Step 4)
7. [SoapUI client] Manual tests until the end of a given scenario.
8. [Rpt Recording Wizard] Stop the recording.
Once the recording is stopped, a SOA extension test should be created in RPT with all the JSON information.
II. Manual test suite creation
1. Launch RPT
2. File > New Web service Test > Empty Test
3. Once an Empty test is created, you can add 'Text requests'
4. The URL should have the JSON information.
5. Add a 'http header'
Name - 'Content-Type'
Value - 'application/json'
6. Lastly, paste the JSON Content to be sent in the test suite -
Some JSON Samples
vjagadeesh 2700063KJN Visits (1466)
The main bar graphs that the default RPT reports shows, does not include script aborts which may occur during execution.
An RFE ID 42720 has been raised for the same.
GRUC Webcast on August 21: What's in your (e) Wallet? Transforming payments and transactional capabilities.
JackSchneiderCO 270007HB0G Visits (1268)
Date & Time: August 21, 2014, 011:00 AM to 12:00 PM (Eastern Daylight Time)
LIVE TWEETING DURING THE WEBCAST! USE #GRUCPAYMENTS TO FOLLOW AND SUBMIT QUESTIONS AND COMMENTS TO OUR SPEAKERS.
Payments and transactional services present multiple ‘moments of truth’ for demanding clients who are often interacting with us anytime and anywhere. For financial services organizations, the 24/7 nature of the industry and its intense competition have made innovation and optimization of these capabilities critical. In this session, you will learn about the experiences of IBM clients in transforming their payments and transactional services with IBM Rational DevOps capabilities.
Learn how banks, brokerages and insurance firms are aligning the life cycles of legacy back offices with the agile sprints of the mobile payments development shops and value-added technology partners.
Bruce Baron, Financial Services Sector Offerings Leader, IBM
Peter Eeles, Financial Services Sector Industry Lead, IBM Rational Worldwide Tiger Team, IBM
***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 EDT (sender is info
AcdntlPoet 2700019V2G Visits (1698)
Troubleshoot the error "No successful contact, Check Agents Failed" in RPT 8.5- This video shows you you can troubleshoot this error message in IBM Rational Performance Tester V8.5: "Agent ... not ready, time of last contact: No successful contact. Check Agents Failed"
RohitBalduwa 2700066W8H Visits (1742)
Web UI Theming feature gives a Jazz Team Server administrator the ability to modify the look and feel of the Web UI for all users of that Jazz Team Server.
A theme can contain any number of *.css files. The *.css files in the theme can create new CSS rules, or they can override existing rules. If a CSS rule defined in an active theme exactly matches a CSS rule defined by the Jazz Team Server, the CSS rule defined by the theme will take precedence.
Tip: If you would like to alter the appearance of a certain UI element, use a tool like Firebug to inspect the DOM node and see what CSS rules are affecting its appearance. You can then create a theme that overrides those rules in order to alter the element's appearance.
I am listing examples where a logo can be modified either using a 'publicly accessible' image or an image file on a local machine.
Using a 'publicly accessible ' image. You can replace the hyperlink with your custom logo and modify the dimensions in css as per your requirement.
Similarly, upload the step 3 zip file for ccm and qm applications.
Using an image file(smiley.gif) from a local machine.