GlennSkinner 110000DAAT Visits (709)
Everyone has them, you know, those ages old ClearQuest records with a never ending string of history records. Records so long that you go for coffee while the record is loading. We all know them far to well. They are the bane of ClearQuest admins world wide. Well not any more. Beginning with the release of feature level 9, now we have choices.
We now can:
* Turn off history all together.
* We can turn it off for some actions and not others
* We can defer loading the history until we need it.
All of these new features opens a whole new world of management options. My favorite is simply defer loading the history. If we are making an update to a record, most of the time we don't need to see the history, so why wait for it to load. With this feature there will be a load history button on the history tab. if you need to see the history, simply click on the button. Any modification to the record, or refresh will cause the history to be discarded from memory and you will again be presented with the button.
Simple clean and neat.
For more information on these new features see the following links:
GlennSkinner 110000DAAT Visits (811)
You just upgraded WAS 8.5.x to the latest fixpack and after restarting the services, ClearQuest can no longer be accessed through port 80. You discover that you can reach it on port 12080. On closer examination, you realize the plugin-cfg.xml that is referenced by the httpd.conf file has been overwritten. How do you fix it? If you follow these simple steps below, you should be back to normal before you know it.
It turns out the httpd.conf file is not pointing to the plugin-cfg.xml being used by WAS. The file specified in httpd.conf has incorrect server paths. Propagation will fix this mismatch.
To fix this:
1) login to the WAS admin console http
2) On the left of the console expand Server -> Server Type -> Web Server
3) When the propagation is finished, Click on "<yo
4) navigate down the page and click on "Copy to web server key store directory"
Should you still have issues after performing the above, check the plugin log file for any errors.
dmmckinn 1200006SCS Visits (919)
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 (958)
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 (852)
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 (961)
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 (1015)
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 (912)
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 (1006)
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 (973)
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: