kellypuffs 06000168YK Visits (3031)
The new IBM Service Request tool will continue to provide the world-class IBM technical support and features from ESR including:
Q. How will I access the new SR system?
You may access the new SR system the same way they currently access ESR. System. Re-directs are now live, expiring in 2010.
Q. What is the advantage of using SR?
The new tool provides our Customers a single registration and a common interface to support IBM software. The SR tool has capabilities and functional enhancements over both of the previous ESR and SSR tools. Additionally, SR will be deployed in IBM's highest availability infrastructure to improve system availability.
Q: Will I have to register to access the new SR tool?
A: No. You will use Your existing ESR ID/Password to access SR.
Q: Will all of my current PMRs and Authorized Caller lists still be available in the new SR tool?
A: Yes, however draft PMR's in ESR will not be migrated to SR.
Q: How is SR GUI similar to ESR?
A: Most of the SR interface will be very familiar to previous users of ESR. Some of the ESR submission forms have been redesigned or renamed (such as site technical contact capabilities are referred to as "relationship". There will be virtually no learning curve for current ESR Clients.
KiranChikkanna 270005HX17 Visits (3029)
Rational Solution for Collaborative LifeCycle Management 2012(CLM 2012) was released in June 2012.
In this post, I have tried to capture the changes in CLM 2012 from a licensing perspective. I have outlined the licensing requirements for the clustering requirements and covered the implementation changes in the Jazz token licensing for CLM 2012. Also, there is a small section answering the most frequent questions asked in the context of deployment of CLM 2012 licenses under “FAQ section”. So watch out for those tips!
Ok, lets get started now. To begin with let me broadly list the changes which have been brought in CLM 2012 from the licensing perspective.
What's New in Licensing for CLM 2012:
Licensing in High avai
There are 2 types of HA/Clustering available with CLM 4.0:
Both the setups do not require extra CAL ( Client Access Licenses ) for the applications hosted on the JTS, Since there will be only one repository. Both the setups do not require the extra server licenses as well ( JTS ). They need the WAS and freely available key file from support to activate capability, which is not a license file and customers need to contact the product support in order to obtain the same.
Design Management Licensing
Design Management is a collaborative web-based tool that enables a broad set of stakeholders to contribute to and influence the design of products, software, and systems. Rational Software Architect Design Manager ([Beta] and Rational Rhapsody Design Manager [Beta] use the Design Management (DM) application, which includes the Design Management capability.
Important: The integration with Design Management is considered beta functionality and is for evaluation purposes only.
There are no extra licenses available as of now for the Design Management tools. As of now the following client license types: Contributor (RTC, RQM, RRC), Developer (RTC), Quality Professional (RQM), and Analyst (RRC) have been provided with only the Read-access capabilities to Design Management [Beta]
License Compatibility with 3.0.x appl
The 4.0 licenses work with 3.0.x applications but 3.0 licenses do not work with 4.0 applications. This compatibility allows for a topology where not all applications have to be upgraded to v4.0 at the same time.
You can upgrade JTS and one of the applications and continue to work with the other applications at the 3.0.x level. You can upgrade Jazz Team Server and support both RTC 3.0.1 and RTC 3.Next clients. You can upgrade one CLM application at a time (rather than having to do all at once). Allows RTC, RQM, RRC to upgrade incrementally. 4.0 CALs would require the JTS version to be at 4.0. However 3.0 CALs can be imported into JTS 4.0 without any problem.
When Jazz Tokens are used as licenses instead of CAL's and when the version of CLM is upgraded to 4.0, we have incompatibility issues with the Jazz Tokens.
In order to resolve the reported error apply the steps below:
Different Types of reports in the RLKS Admin and reporting tool:
Reports display valuable statistics about how users are using the assets and repository.
Managing software assets goes beyond submitting them to a repository and managing them through consumption. Over time, looking at the changing elements, the models and trends of asset details, consumption use cases, and users information can help companies evaluate the needs of their current business strategies.
Lets understand the different types of reports available and the insights they provide...
Peak usage : This metric represents the maximum number of license requests that were granted by the selected license servers for the selected products. If more than one license type is selected in the report definition (floating and token as license type), the peak usage report shows multiple numbers in the bar graphs. The following example shows a peak distribution report with two counts per bar.
Peak denial : This metric represents the maximum number of license requests that selected license servers denied for the selected products during the specified time.
Note: In certain reporting scenarios, the tool can report inaccurate license denials. For more information, see the "Known limitation in license denial report" technical document.
License usage per user : This metric presents information about product usage by a user from a license server at a specified time. This list includes the user and the host server name for the selected products for the specified duration.
Available Licenses : This metric presents the total number of licenses for a product that are available in the license files that are used to start the license server.
License expiration : This metric presents the expiration date of licenses for each of the selected products. This information is collected from the license file.
Token distribution : This chart presents the number of token licenses that are issued in the specified time for various products in an organization.
Chargeback report : This metric represents a simple chargeback policy for product licenses that are used in an organization. The report for this metric is like an invoice, where the number of licenses that are used by each user during a specified time is listed. The number of license hours is multiplied by the unit costs that are associated with each license hour of that kind of license for that product. This product gives the value in currency to be charged for that user.
Note: For the Collaborative Lifecycle Management (CLM) products, the following metric types are supported:
Jazz.net is live with a completely reworked and improved website
The new Jazz.net site includes the addition of Rational Requirements Composer, Quality Manager, and Focal Point for Project Management. We have done what you asked for and made much more of our Jazz Development open and transparent. Now clients and community members will be able to enjoy the benefits of transparent development but no longer just for Rational Team Concert. Now you can participate with us in shaping plans, prioritizing fixes, and interacting directly with our expanding Jazz Development Team for three new Jazz Products. See http://jazz.net/ for the complete details
eGuide now on Jazz.net
IBM Rational support has taken all the best links from our RSDC eGuide mini-CD and posted them online at http
Check it out!
Sumant Renukarya 270002B42N Visits (3021)
Here is another good lesson, among many that I happened to learn, while working with a customer using IBM Rational Team Concert (RTC). While this may not serve as a supported solution for the issue reported, perhaps it can serve as a pointer or guide on the types of things to look for.
I hope this gives some idea for users and the steps that can be taken, in case of a similar situation.