Rajeshavanthi 2700022MCX Visits (916)
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 (1010)
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.
RohitBalduwa 2700066W8H Visits (976)
The logical port specifies the server on which IBM Rational SAP Connector is installed. It is used to transfer data to the external Defect Management Tool. The Web AS HTTP or HTTPS port is used, depending on the information in the URL.
Each logical port is attached to a consumer proxy. These ports are used by Solution Manager and Service Desk when they need to call the Rational Connector.
Steps to setup the logical ports:
dmmckinn 1200006SCS Visits (909)
If you are looking for some help in getting started with integrations supported in the CLM and SSE solutions, you may want to check this article: Integration: Where to start?.
The Integration topics in the article (and in related sections) are intended to provide information about integrations supported in the Collaborative Lifecycle Management and Systems and Software Engineering solutions in terms of technology, maturity, and ability to support some high priority usage scenarios. It will focus initially on the ALM Core solution set of products, ensuring that the integrations are accurately and completely documented and validated for the scenarios identified. The focus will grow over time to include integrations with other IBM tools in the context of, and with third-party tools that have been identified as high priority by customers.
It starts with a description of ALM Core and continues on from there:
RohitBalduwa 2700066W8H Visits (910)
More on the CLM SAP integration...
Create an initial identity for web services calls before the Rational Connector can exchange data with Solution Manager and Service Desk. This user is completely internal to the SAP Solution Manager configuration.
References:Setting up the Rational Connector to work with the SAP Solution Manager