mccarron 060001KYG9 Visits (5975)
CLM 6.0.5 iFix002 was made available for download on January 26. This iFix contains fixes for 71 defects broken out for the following products:
For information about downloading this fix (and fixes available for other versions) please go here.
What else did we improve in Collaborative Lifecycle Management 6.0.5 - key updates for client experience
paulellis 270001KTVW Visits (7128)
On December 4th 2017, we announced Now
The list below focuses not on the new product features, but instead, the key wins in the 6.0.5 release which will make life better for users and administators in particular.
There were two main focuses to address the complexity of backup strategies. There is now an inte
Typically, like buses, two articles are now available. We wrote a specific article on back
We now strongly encourage you to backup your DOORS Next Generation indices so as to lessen the likelihood of needing to run a repotools reindex.
Windows VM users can now consider using alternative performance settings for DOORS Next Generation
We have focused on DNG backup strategy mentioned above, so as to ensure that we do not need to run repotools reindex. This was in part prompted by the desire for Windows Virtual Machine(VM) users to be able to use a DNG
Guidance on adopting IBM CLM configuration management across the lifecycle
During the same time frame, there was a large intiative to provide guidance on adopting CLM lifecycle configurartion management. Tim Feeney's blog explains the new Bes
Validating and documenting on WebSphere Liberty Profile and Jazz Authorization Server (JAS)
It is now possible to authenticate using Smart Cards, or certificates (.p12) with Liberty:
and with JAS, see related article: Conf
We have also improved the formal IBM Knowledge Center on these topics, cross-linking so you don't need to find these additional resources: Conf
Last but not least, Mul
In a preview, an expert guides you step-by-step through the various products in the IBM IoT continuous eng
Jazz Community sharing site:
A big thank you to the German User Group for creating a new public sharing site available to everyone - see Rolf Nelson's Intr
Arun K Sriramaiah 2700076GE8 Visits (10155)
RTC upgrade from 5.0.2 to 6.0.3
HTTP Status 404 - ProxyServlet: /cqconnector/
Workaround tomcat library for CQ synchronizer 603 upgrade.
1. Before upgrading the CQ synchronizer from 5.0.2 to 6.0.3, take backup of tomcat libraries present in gateway/tomcat folder.
Arun K Sriramaiah 2700076GE8 Visits (8678)
GIT RTC integration (How to clone repository via http, file size greater than 300 MB)
How to clone repository via http, file size greater than 300 MB.
Node.js based server for RTC and Git integration:
Tried with below scenario combination but was unable to clone repos, via ssh if the file size is more than 300 MB.
a. GIT RTC integration (how it's descibed in the officicial documentation for RTC 6.0.2):
1) set the value (--m
dmmckinn 1200006SCS Visits (8411)
Have you seen the Rational Team Concert 6.0.2 videos? The following videos provide information about features available in version 6.0.2. They were posted a few months ago but we thought it would be good to bring them back in the spotlight.
The full playlist which include all of the following videos is available in Coll
For further information about other capabilities available in CLM version 6.02, you may want to checkout Highlights of 6.0.2.
dmmckinn 1200006SCS Visits (11046)
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
dmmckinn 1200006SCS Visits (1372)
There have been some exciting improvements in the latest v126.96.36.199 release of IBM Engineering Workflow Management (also known as IBM Rational Team Concert).
Key areas of focus for this release have been quality, enterprise agile and enhanced usability and scalability.
Here are some of the improvements you will see in this release:
Check out further details from Rolf Nelson, our Offering Manager for IBM Engineering Workflow Management (a.k.a. RTC), in What’s New in IBM Engineering Workflow Management v188.8.131.52 (RTC)
For a list of all the features in the release, see http
Migrate CCM application from one server machine to another with the same database server in Enterprise deployment topology using WAS
Arun K Sriramaiah 2700076GE8 Visits (1133)
How to migrate a CCM application from one server machine to another with the same database server in Enterprise deployment topology using WebSphere Application Server (WAS).
Example: A distributed environment where we have 5 server machines.
1st server machine for IHS,
2nd server machine for the database,
3rd server machine for DCC + RS,
4th server machine for JTS+RM+CCM and
5th server machine for LQE.
Expectation: CCM and RM are in the same server machine. How to move the CCM application to a new server machine?
Please find the procedure below referencing with the above scope of the requirement as an example.
1) Backup Conf
2) Install RTC in New Server
4) Restore the conf
5) Re-configure IHS for new RTC server.
6) Make sure you have the right JVM configured for the RTC applications.
Note: Two applications sharing the same JVM, needs more JVM to be set.
7) Set the new path to the indices folder in the team
Any feedback or suggestion based on specific scenario and your experience is appreciated.
Arun K Sriramaiah 2700076GE8 Visits (1293)
Is there an impact from Enabling automatic archiving of auditable links for RTC?
Before enabling automatic archiving of auditable links for RTC, you may want to know if it has the potential to cause any problems (such as performance issues)?
No known issues have been reported, so there is minimal impact.
But of course it all depends on how many links you have. If you would have millions of links, you could notice some impact but otherwise no.
The most effect seen is in history. If one item has many links, it might take some seconds to resolve all links. For one item, you should see no performance impact in general.
If you encounter any issues, please add a comment to this thread.
Good practice to verify the dependencies of the custom attribute with scripts/API's/Plugins and Operational Behavior before removing from the RTC editor presentations
Arun K Sriramaiah 2700076GE8 Visits (892)
Have you run into issues saving a workitem after removing custom mandatory attributes from an RTC editor presentation?
Note: A good practice is to verify the dependencies of the custom attribute with scri
Scenario: Below is one scenario that explains why even after removing the mandatory attribute the workitem save operation was still not successful.
The case below talks about Operational Behavior causing the issue while saving the workitem.
When you have a workitem mandatory attribute you want to remove from the editor presentation but still want it in another workitem type, check the attribute dependency with the Preconditions for a workitem before removing from the editor presentation.
In the case below, the customer is not able to save the workitem even after the attribute is removed from the editor presentation.
Check the below details:
Open RTC project Area>> Click on the >> process configuration tab >>navigate to Operation Behavior under Team Configuration >> Operations Window.
Navigate to Work Items>> Save Work Items (Server) >> Click on the role which should be affected by this configuration >>
The Preconditions for a work item will be displayed.
Click on "Required Attributes For Type and State"
In this use case that the 'Custom attribute ' still set mandatory in preconditions.
Note: Uncheck the 'Custom attribute' and save the project configuration.
*Required Attributes For Condition
Whichever custom attribute removed from the editor presentation should be unselected. Once finished, click OK and save the project area.
Arun K Sriramaiah 2700076GE8 Visits (2319)
Navigate to a repo workspace on a stream (where that old version was baselined), select component in a repository workspace or stream in the Team Artifacts window and click on "Replace with".
Arun K Sriramaiah 2700076GE8 Visits (2564)
Unidirectional & Bi Directional flow controls in IBM Rational Team Concert (RTC) Streams ( SIT \ UAT\ PROD) and Best Usage.
Below is one of the example for creating a RTC streams ( SIT \ UAT\ PROD) code delivery
Best usages & control of smooth code delivery between RTC streams (SIT, UAT and Prod)
Note: One of the best ways is to make sure SIT,UAT,Pre-PROD and PROD should be Unidirectional flows, so that it will not affect the existing codes.
The process is:
Below are a few things should be taken care of for smooth change flow.
1) The more frequently that you accept and deliver (assuming that your deliveries never break the product)
2) Merge in a small set of changes than a large set of changes.
3) The flow targets of a workspace have no effect on whether or not a change set shows up as ready to be accepted by other team members who share the same flow target. It is only when you have actually delivered
4) If you don't have any latest common changes, there shouldn't be any conflicts
5) A delivery of the code is made from the Module Streams to the Main Development stream.
Note: In case for the above situation if you find the conflict between streams. Please refer to the below blog.
Arun K Sriramaiah 2700076GE8 Visits (3546)
Enabling the RepoDebug service for Jazz Team Server (JTS) and Rational Team Concert (RTC) WebSphere Application Server (WAS) Liberty application server
The debug service is a general-purpose service that serves as the central location for finding various REST APIs that are useful for debugging. It was introduced into Jazz Foundation in v4.0.6 and is available for all JAF-based web applications.
Please refer the RepoDebug wiki for more details.
dmmckinn 1200006SCS Visits (4371)
If you are looking into server load issues on your Jazz application server, you may want to review the Known Resource-intensive Scenarios article. The article aims to capture user and system scenarios across the ALM portfolio that can potentially drive relatively higher load on a Jazz application. Such scenarios can lead to server debt (such as out-of-memory errors) if they are run during peak times on systems that don't have sufficient spare resources available. These scenarios are qualified or quantified to make them easier to understand. Where possible, best practices are provided that can minimize or avoid the issue altogether.
dmmckinn 1200006SCS Visits (4437)
This video will cover the creation, modification, and deletion of build engines from the RTC web client.