kellypuffs 06000168YK Visits (2189)
AcdntlPoet 2700019V2G Visits (2188)
Getting Started with Rational License Key Server Administration and Reporting Tool, v8.1.4- The new Rational License Key Administration and Reporting tool has rele
Some of the new administration features of the tool include:
For more information on downloading, installing, configuring, and using the new Rational License Key Administration and Reporting tool, see:
GRUG Webcast, Nov 17 - Addressing application security from beginning to end with Rational AppScan v8.0
kellypuffs 06000168YK Visits (2186)
Webcast: Addressing application security from beginning to end with Rational AppScan v8.0
Webcast date: Wednesday, November 17, 2010
Webcast time: 11:00 AM ET
Sign up for this webcast
Can't make this webcast? Register to attend to receive notification when the replay becomes available.
The Global Rational User Group Community
Exporting dateTime (timestamp) values into Rational Quality Manager through the RQMExcelWordImporter plugin
SunilKumarR 270001XXSY Visits (2185)
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
AcdntlPoet 2700019V2G Visits (2185)
As his blog says, Sanjeev Sharma is a DevOps, Mobile, Agile Transformation, ALM SME and Evangelist. He's also a Tech Sales Specialist, Solution Architect, DevOps SME, Agile Evangelist, Rational Software SME, IBMer, Inventor, Innovator, Blogger... and airline mile junkie. More importantly, however: he is also very active on twitter and other social sites like slideshare where he's helping others by sharing his experience and knowledge for everyone's benefit.
Following is his Slideshare deck on the session topic "DevOps for Mobile Apps" that he and Leigh Williamson, IBM Distinguished Engineer, Rational CTO Team delivered at IBM Innovate last month:
But don't stop there... Sanjeev is also a prolific blogger on the topic of DevOps. Check out his relevant posts below: