Arun K Sriramaiah 2700076GE8 Visits (710)
This article is regarding Rational CLM integration with JIRA, able to get the information that JIRA can be integrated with CLM containers (RRC, RTC and RQM) with Rational Adapter for JIRA.
Advantages of RTC and JIRA Integration
Following are some of the benefits that an organization will get by integrating RTC with JIRA:
As per the topology, JIRA application is installed on a single application server and the CLM applications are also installed on a single application server.
For example: Standard Topology
The JIRA application server communicates with the CLM application server through server friend relationships. The adapter resolves links from CLM work items back to the JIRA server.
As long as the JIRA application can connect or ping to the repository you may install it on the same machine or another server
RPT Schedule execution on local machine results in error: com/ibm/lang/management/OperatingSystemMXBean
Rajeshavanthi 2700022MCX Visits (479)
IBM Rational Performance Tester (RPT) supports schedule execution to be carried out on a separate controller machine (Agent machine), which in fact is a recommended way of script execution. It also supports, to an extent, executing the minimal amount of user load execution locally on the workbench machine (not recommended for production level testing).
When executing a schedule under RPT
The following attempts were made to debug this further:
dmmckinn 1200006SCS Visits (570)
We'll be back tomorrow with more great content focused on helping you get the most out of IBM Rational Support and your IBM Rational products!
As we begin to wind down from our summer season activities and our children return to school, it is time to celebrate this American federal holiday. This is a day where we recognize the contributions of the American worker. It is a day where we take some time off to relax and enjoy the company of our family and friends while sharing our favorite backyard barbecue.
While we are off for the day we want to share with you a list of videos that have been posted on this blog. Enjoy this CLM video collection.
GlennSkinner 110000DAAT Visits (533)
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 (601)
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.