AcdntlPoet 2700019V2G Visits (1268)
Stéphane Leroy (Unleash the Labs CLM, IBM Software Engineer) has created a wonderfully simple table to outline the Test Lab mana
And don't miss Stéphane's most recent posts surrounding his expertise in RTC and enterprise modernization!
Rajeshavanthi 2700022MCX Visits (1501)
Under IBM Rational Quality manager (RQM) v3.x release onwards, during the course of creating a new defect work item, you are allowed to select the record type. Below are 2 such scenarios where the record types differ between older (2.x) and newer versions (3.x onwards) of RQM.
The functionality to select record types ( RQM/CQ integration) was added via RFE 25717 in version 4.0.1; this is the current default behavior (i.e. functioning as intended).
Add Dashboard viewlet in process template with image and text formatting for reuse in IBM Rational Team Concert (RTC)
Shradha_S 270007543G Visits (2470)
You can refer the below technote to perform the basic pre-requisite steps in IBM Rational Team Concert (RTC) before beginning with adding a viewlet/widget.
3) Click the Browse button to select available widgets and select Headline
4) Click on Add Memento
4.1) To have a viewlet without Title Bar, you can set the Trim option -> No Trim
5) Add a Property to the memento.
6) Add 2 more Property named "text" and "image"
8) For property "image"
Paste the copied Image Location on a notepad for editing.
The URL that gets copied will look something like below example:
Without Trim set (Step 4)
With Trim Set (Step 4.1)
Rajeshavanthi 2700022MCX Visits (1665)
Under IBM Rational Quality Managerv4.0.3, When adding default reporting widgets to RQM dashboard you might encounter the following error:
In order to validate if these default reports are working fine, you may execute the etl jobs for QM applications. However in this scenario, you could notice that the etl job execution was showing no specific errors pertaining to these reports or widgets. You can navigate to the QM and ETL jobs to find if any error gets logged. In most of the cases, you can find an error message :
This fragment is the one that extends the foundation reporting functionality to use specific tools designed in RQM. It acts like a "bridge" between foundation and RQM reporting functions. Since the bundle couldn't be loaded, the reporting functionality in RQM is not working as expected.
To confirm , you can navigate to this URL to see if he bundles are activated for the application.On the left pane of the window, click on Internal Tools >> Component Status. All the components listed there are expected to be displayed with green status. Pay special attention to the com.
Since the bundle that acts as a bridge between the BIRT engine and specific RQM reporting functions can't be resolved, you might encounter such errors. The primary reason could be that the .jar files (com
First thing you could try is replacing the problematic bundle mentioned above with a clean one while troubleshooting advances, as it is easy and may actually fix the issue. Get a copy of the above mentioned .jar files from a fresh installation of similar version of RQM and perform the below steps.
2. Shut down RQM
Exporting dateTime (timestamp) values into Rational Quality Manager through the RQMExcelWordImporter plugin
SunilKumarR 270001XXSY Visits (2419)
This blog entry is to provide suggestions to users who are surprised at incorrect / mismatched date attribute (TIMESTAMP) values seen in RQM artifacts while the data is exported from Excel using the RQM Excel Exporter.
In most cases, the excel export will succeed but you might see that the "date attribute" field, is not in accordance with what is exported.
The dateTime (Date/Time which translates to TIMESTAMP) values in Rational Quality Manager artifacts like Test Case, Test Plans and execution artifacts like Test Case Execution Record undergo translation when the data is coming from excel through the "Export to Repository" option in the RQME
A dateTime value passed through the excel sheet should follow a format yyyy
More details on the syntax are available at the date
RQM Client and RQM Server in same time zone: If the RQM client (where excel is used) and server are on machines in the same time zone? the TIMESTAMP value specified in the sheet is exported into RQM as is.
RQM Client and RQM Server in different time zone: If the RQM client and server are on different machines? the TIMESTAMP value specified in the sheet is converted to the time on the RQM server and used. to avoid this (i.e., to ensure the TIMESTAMP value is as per client time zone) you should use dateTime (TIMESTAMP) string as 2014
For example: 2014
If the excel exporter is on a machine in a different time zone, replace the timezone string highlighted above with the relevant value.
You can use a Java Applet online like a sample one here to get the timeZone string : http