AcdntlPoet 2700019V2G Visits (9633)
paulellis 270001KTVW Visits (11067)
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 (4403)
Update on changes: Rhapsody Design Manager and Rhapsody Model Manager
As our teams are busy working on the second release of Rhapsody Model Manager, we wanted to provide you with an update on changes that are being made with regard to Rhapsody Design Manager.
The following blog provides further details about the changes: Update on Rhapsody Design Manager and Rhapsody Model Manager
Arun K Sriramaiah 2700076GE8 Visits (3243)
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.
dmmckinn 1200006SCS Visits (2237)
We've been busy wrapping up 2018 and preparing for the start of the new year. As we look back over the last year, we thought we’d share some of our top blog posts from 2018 in case you missed them.
dmmckinn 1200006SCS Visits (788)
AE91_SHINJI_KANAI 110000AE91 Visits (7319)
AE91_SHINJI_KANAI 110000AE91 Visits (8063)
dmmckinn 1200006SCS Visits (10555)
What were some of the most used technotes in 2016?
We've compiled a list of the top 20 troubleshooting technotes for our Maximo, TRIRIGA and Continuous Engineering products that were most accessed on the web in 2016. We hope that highlighting these technotes here will help with your troubleshooting efforts.
AcdntlPoet 2700019V2G Visits (10160)
What’s new in Team Concert Jenkins plug-in 184.108.40.206 - We are pleased to announce that Team Concert Jenkins plug-in 220.127.116.11 is here! The Team Concert Jenkins plug-in integrates Jenkins with Rational Team Concert’s (RTC) SCM and Build capabilities using the richer features of the build toolkit. It provides options to configure Jenkins jobs to use RTC source control. Jenkins jobs can also be configured to use the source control options specified in an RTC build definition, facilitating Jenkins builds to be managed from RTC and take advantage of the traceability provided across RTC work items, builds, and change sets. The plug-in also publishes the changelog information in the Jenkins builds and supports polling....
An overview of the different build configurations supported by the Team Concert Jenkins plug-in - Using the Team Concert Jenkins plug-in, you can configure your Jenkins jobs to use Rational Team Concert (RTC) source control and, optionally, report information back to Rational Team Concert builds. The plug-in integrates Jenkins with RTC using the richer features of the build toolkit. This plug-in is different from the other Rational Team Concert plug-in for Jenkins which uses SCM CLI to integrate with RTC. This article provides an overview of the different build configurations supported by the Team Concert Jenkins plug-in 18.104.22.168. For instructions on how to setup and configure the plug-in, refer to Team Concert Jenkins plug-in wiki....
Loading symbolic links correctly when using the Rational Team Concert/Jenkins integration - When using the Jenkins plugin to load files from Jazz SCM it is possible that the symbolic links in the Jazz streams will not be loaded correctly. The problem is that the default Java runtime for Jenkins will not know how to deal with the symbolic links. It is necessary to manually include the .dll/.so files into the Jenkins library path so the symbolic links will load correctly. This article will detail how to setup Jenkins to get the symbolic links to load correctly....
Note: This post and related articles describes a usage or software configuration that is not supported by IBM.