AcdntlPoet 2700019V2G Visits (8904)
As seen on the Jazz.net blog: A DevOps transformation
Mario Maldari and Albert Tabachnik take you through the journey of a system test organization in transforming itself into a continuous delivery, DevOps model. In a DevOps Continuous Engineering environment, with accelerated timescales, it is ever more important to focus testing efforts on those features and platforms that are most critical to your customers. The Collaborative Lifecycle Management (CLM) system test organization challenged itself to transform to meet the demands of our business and our clients. We started off by analyzing our time investment, and shifting our focus to areas that needed greater investment. We optimized and standardized on a set of “Golden Topologies” that represent a core set of topologies used by our customers. We invested in our automated deployments, effectively streamlining our server setup and deploy process. We moved to a “solution test” model and streamlined our resources and test scenarios. Once the foundation of our transformation was laid down, we began automating our scenarios and running them daily in the pipeline, while allowing testers to focus on other areas. Overall, our transformation has allowed us to better react to how our development teams operate, as well as align our testing with how our customers deploy and use our solution...
AcdntlPoet 2700019V2G Visits (9907)
Link Validity — Coming in CLM version 6.0.1: As part of the Rational solution for Collaborate Lifecycle Management (CLM) version 6.0.1 we are introducing Link Validity, a new feature in DOORS Next Generation, Quality Manager, and Design Manager. In projects that have configuration management enabled, Link Validity can take advantage of the features that multi-stream development brings to the table.
dmmckinn 1200006SCS Visits (11900)
Are you planning an upgrade of your CLM products? Looking for information about the latest available fixes, system requirements and alerts or security bulletins that may impact your upgrade decisions?
CLM Fix list
A list of CLM releases (4.0.7 and later) and details about the latest available fixes has been organized in Fix list for IBM Rational Collaborative Lifecycle Management. This document contains a complete listing of releases, refreshes, fix packs and interim fixes sorted by version for IBM Rational Collaborative Lifecycle Management. It also contains a list of APAR fixes that are included in each release broken down by individual product/component.
When planning your upgrade, you should also review your existing systems and software for potential compatibility issues. Refer to the Detailed System Requirements reports which include details about supported operating systems, related software, hypervisors and hardware requirements; including component-level details. Links to individual reports for the latest versions are included below:
Alerts and Security Bulletins
Details about Alerts and Security Bulletin updates are also import to consider when upgrading and can be found in the Flashes, alerts and bulletins for Rational Collaborative Lifecycle Management section of the IBM Support Portal.
Additional information about upgrading can also be found in the
RohitBalduwa 2700066W8H Visits (12560)
With the new CLM 6.0.1 and upcoming IBM Rational Collaborative Lifecycle Management (CLM) releases, IBM WAS Liberty has replaced the Apache Tomcat application server. The current documentation will not assist you to configure the WAS Liberty to run as a Windows service.
There is an existing Enhancement Request for the same:
As a workaround, you can use the Apache Commons Daemon as an option.
Steps to create the service using Apache Commons Daemon to run CLM 6.0.1 in IBM WAS Liberty:
dmmckinn 1200006SCS Visits (12312)
In an effort to continuously deliver product enha
Check out the following downloads which include information about product enha
dmmckinn 1200006SCS Visits (11751)
The Jazz architecture allows for multiple instances of specific application servers, such as the Change and Configuration Management (CCM) application (Rational Team Concert), Quality Management (QM) application (Rational Quality Manager) and Requirements Management (RM) application (DOORS Next Gen). These application servers are registered to a common Jazz Team Server (JTS) to form a CLM Instance. The architecture further allows multiple CLM Instances to be formed. You should be aware of the tradeoffs and architectural considerations when multiple instances are needed in order to scale to support your user population/load.
The following article on jazz.net provides details about application, server and architectural considerations in addition to functional differences that you should review while planning: Planning for multiple Jazz application server instances
RohitBalduwa 2700066W8H Visits (11751)
You might encounter some problems where the Lifecycle Project Administration (LPA) projects and templates are missing, or application dashboards are not loading post upgrade activities or any sudden database or application failure.
The direct solution is to run re-index for the application. This will regenerate the metadata (query triple store and Lucene text store indexes) required to load the page.
Error instantiating the template....
Error deploying predefined templates....
Example (click the images below for larger views):
In-case the indices are corrupt or missing, error seen on LPA admin page:
Post jts reindex done, the LPA templates and projects will be visible now.
For LPA templates, the metadata is in the jts application, so just reindex of jts will help.
Note: Collecting logs will not help you and either run the firebug to troubleshoot further.
For Dashboards, run it for JTS and the corresponding application.
Important: You must shut down the server before you run the command.
dmmckinn 1200006SCS Visits (10093)
Have you been looking for CLM-specific performance datasheets and sizing guides? Well, look no further. Below is a list of performance related articles that our CLM folks have pulled together and published on the
Deployment wiki on jazz.net.
The datasheets below are updated when performance testing shows a significant change. The 6.0 datasheets apply to the 6.0.1 and 6.0.2 releases. Note that there were major updates to the performance datasheets between the 5.x and 6.x releases.
A more complete list is available at Performance sizing guides and datasheets.
paulellis 270001KTVW Visits (11333)
On April 25th 2016, IBM released Collaborative Lifecycle Management 6.0.2. In Moshe Cohen's blog
One of those highlights was:
And Moshe said:
Maybe it's a coincidence, but a lot of upgrades have occurred in the last few months.
Unfortunately, not all of them have gone as smoothly as they could have done.
Why are people finding that their upgrades are not wildly successful?
This, for me, is particularly frus
We also published a useful blog post "Planning your CLM upgrade?" to help find information about the latest available fixes and system requirements; and Dan Toczala wrote a
All of which was great, but do we just have too much information in too many places?
What we have missed all this time is a single entry point to our expansive library of information relating to your specific upgrade - in a single page!
In order to have a positive upgrade, where success is planned in from the start, a simple, handy checklist is required.
One, simple, must
This checklist includes simple links to assist with obtaining all the information required for each of the key areas of an upgrade:
* Upgrade Testing
* Software Licenses
* Server, infrastructure and performance considerations
* Latest Upgrade flashes and news per CLM application
* Ways to contact us so we can help
* Additional pertinent links/information
We are strongly recommending that this be the starting point of every CLM upgrade. Please also give us your feedback if you believe something is missing.
dmmckinn 1200006SCS Visits (8983)
Are you waiting to start a monitoring program in your IBM Collaborative Lifecycle Management (CLM) environment?
Monitoring should be incorporated during times of peace and not considered only as an after-thought once a crisis hits and when time is of the essence.
The article Monitoring: Where to Start? provides information about how to get started with monitoring. It also provides reasons for doing so such as: avoiding issues, identifying tuning opportunities, or optimizing daily and long-term operations.
More detailed information about monitoring different servers (CLM, jazz, web and application) is available in the Monitoring section of the Deployment wiki on jazz.net.