dmmckinn 1200006SCS Visits (150)
Looking for guidance in planning your deployment?
The Deployment planning: Where to start? article in the Jazz.net deployment wiki outlines several key planning and design considerations for designing a Rational development environment. The considerations focus on the environment and non-functional options that typically effect how successful your deployment and ultimate adoption will be.
Topics covered in the article include the following:
Kiran Byrappa 270001YMWT Visits (344)
You may come across situation where you do not want a user in your Project Area to view data in a particular stream.
dmmckinn 1200006SCS Visits (358)
Looking for some of those special little tidbits to help with your use of Rational Integration Tester? Check out the following most recently published content which may offer some assistance.
This document will be helpful to users who have constructed a Custom Function previously for RIT and may wish to repeat the process without working through all the instructions in the manual again. The document may also assist users reviewing the process undertaken when troubleshooting.
Provides details about how you can pretty print XML from IBM Rational Integration Tester that may be desirable in cases such as logging.
Rajeshavanthi 2700022MCX Visits (432)
There are various performance testing tools in market and it's advisable for a tester to do a sort of comparison in-terms of the product functionality.
Under Load Runner you could see following options made available
So there could be questions as to whether RPT provides similar functionality or how would the virtual user execution gets handled in RPT.
What happens if you specify 100 virtual users in the RPT schedule. Say, you have 10 user groups each one has an unique script with it. So10 users per user group, totally 100.
RPT does not require a thread per test not it does require a thread per virtual user. When an individual action is being executed one thread is used.
One example of an action is an HTTP request. One thread is required to open a connection, if necessary, and write the request. Reading the response from the server is non-blocking. When data is available one thread is required to read the data and perform any processing required. Another example of an action is Custom Code. During the execution of the Custom Code exec() method one thread is required.
In general, For the HTTP protocol the RPT engine will create a thread as needed up to a maximum of 500 threads. The need to execute an action (eg request send or response) and unavailability of a free thread is what controls creation of additional threads.
Unless there is some specific problem it is highly recommended to let RPT control the creation and deletion of threads.
So, if you are looking it specifically from RPT perspective, then the agent starts execution with 10 worker threads
However if you are interested to control the threads, then the following system properties can influence thread control. These apply to the execution engine (ie location or agent) so a general property for the location must be created to set these system properties. For each location you must create a property called RPT_VMARGS and set it accordingly.
The default values are
-DrptThreadCount=10 (Initial number of worker threads)
RohitBalduwa 2700066W8H Visits (444)
The external help desk is the way Service Desk integrates with Rational Team Concert. When Service Desk users publish an incident to this external help desk, the integration creates a work item in a Rational Team Concert project area.
Note: ClearQuest was the first Rational Configuration Management tool supported by the Rational Connector. When support for Rational Team Concert was added, SAP did not update the SPRO documentation. This will be corrected in a future release of Solution Manager.