dmmckinn 1200006SCS Visits (618)
Continuing on the topic of Integrations as covered in our previous post Integrations with CLM and SSE solutions – where to start…
Our next article provides scenarios that were captured through direct collaboration with our customers. It includes pre-deployment install and upgrade scenarios for new inst
Check out the full article here: Integration: Customer Scenarios
Also, check back over the next few days for more on our “Integrations theme”.
GlennSkinner 110000DAAT Visits (536)
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 (607)
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 (709)
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 (744)
You may come across situation where you do not want a user in your Project Area to view data in a particular stream.