Kiran Byrappa 270001YMWT Visits (134)
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 (283)
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.
Arun K Sriramaiah 2700076GE8 Visits (387)
This article explains how to reduce the number of Rational Team Concert component flow displays in the pending changes window.
By default, all components in a Repository workspace (RWS) use the current flow target. You can use the Repository workspace editor to add flow targets or change their scope so that not all components use them. Refer to Flow targets for further details.
For example, you can specify in flow targets for some of the components in a Repository workspace (RWS) display, or decide that a specific component must display in pending changes window.
Note: You can use the Flow Only components checked below option in RWS\Stream Flow Target to make the Pending Changes view more manageable. This helps more when streams or workspace have 10++ and which might not be all needed in the pending changes window.
You can use the above scenario where in you can avoid unwanted components display in the pending changes.
Arun K Sriramaiah 2700076GE8 Visits (369)
Here is a collection of some of the Basic Rational Team Concert Source code management links from IBM Rational Support. We hope you will find them as helpful as we have.
RTC Source Control Basics
Rajeshavanthi 2700022MCX Visits (423)
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)