As you know, Rational Performance Tester (RPT) does support performance testing of Siebel applications. However in certain circumstances, there might be testers who might have web services developed in SOAP UI format, which they would like use for performance testing using RPT. So the question is how do you integrate such environments and engage in enabling the testers to run load and performance testing of such web services created in SOAP UI using RPT?
Note: Rational Performance Tester 64-bit workbench does not support testing Siebel applications
Performance testing of such services is like any other HTTP performance testing. However the only option for you is to select the 'Un-Managed Application" type in RPT while recording.
Below is a use case which you can follow:
- [RPT Recording Wizard] Start a 'New test from Recording'
- [RPT Recording Wizard] Select the option 'HTTP test'
- [RPT Recording Wizard] Record an "Un-Managed application"
- [RPT Recording Wizard] Selection of an available port on the machine, and then start of the recording.
- [Soap UI client ] Launch SOAP UI > File > Preferences > Proxy settings
- [Soap UI client ] Populate the 'Host' field with the value 127.0.0.1. The Port number should be the one that you selected during recording (as in Step 4)
- [Soap UI client] Manual tests until the end of a given scenario
- [Rpt Recording Wizard] Stop the recording.
Once the recording is stopped, a SOA extension test should be created in RPT.
If you have the wsdl files, you can create manually an SOA extension test suite and then use the wizards to create web services calls based on the wsdl methods.
When the calls are created this is possible, or manually to adjust the content generated (soap content ) to what was used into SOAP UI, or to copy paste the XML from SOAP UI.
If there are no wsdl files, the process could be to create XML calls into the soa extension test suite, and copy/paste the XML from SOAP UI.
Then take a look at the HTTP headers used into SOAP UI tool to add them to the HTTP transport configuration of the soa extension calls that are created.