Arun K Sriramaiah 2700076GE8 Visits (777)
Here is a collection of some of the Basic Rational Team Concert Source code management links from IBM Rational Support. We hope you will find them as helpful as we have.
RTC Source Control Basics
Saurabh.Tyagi 270005CY2K Visits (1866)
IBM Rational Synergy is a task-based, software configuration management (SCM) solution that brings together global, distributed development teams on a unified platform. Rational Synergy provides capabilities that help software and systems development teams work and collaborate faster and easier.
Rational Synergy is licensed using IBM Rational Common Licensing. For information about Rational Common Licensing, see the Rational Common Licensing information center.
Rational Synergy supports the Floating, Named-User Floating, and Token license types. For a description of license types, see “License type definitions” in the Rational Common Licensing information center.
For Rational Synergy users, the login name is seen as the user of the token license. To reserve Named-User licenses for specific users, see “Setting up the options file” in the Rational Common Licensing information center. When configuring the options file for Rational Synergy and Rational Change, it is not necessary to put the default administrative users (ccm_root, ChangeAdmin, and csuser) in the INCLUDE list. The license file includes additional floating licenses for these users. Do not assign these licenses to other users because the products might fail.
How licensing works with Rational Synergy:
When you start Rational Synergy, it contacts the License Manager to request a license. Rational Synergy uses information that was provided during the server installation process to find the License Manager. The following example describes how licenses are configured during installation. The example assumes IBM Rational Common Licensing was installed before installing Rational Synergy.
-> When you install the Rational Synergy server, you are prompted for the host name and port number of the license manager. The information is recorded in the $CCM
-> When the Rational Synergy router process is started, it reads the license information from the $CCM
-> When a Rational Synergy session is started, the information about where to find the license manager is passed from the router to the Rational Synergy server. The Rational Synergy server also looks in the TELE
The Rational Synergy server contacts the license manager using the specified host and port, and requests a license on behalf of the user. The $CCM
Rational Synergy searches for license servers and license files in the following order:
If you move the license manager to a different system, you must edit the $CCM
Operations that consume Synergy license:
Starting a session does not consume a license. Only operations that update the underlying database consume a license, such as file check out, task creation, task completion, and so on.
Synergy license timeout
After a license is consumed by a user, that license is reserved for that user for 60 minutes after the last database update while the session is running. If the user exits the session, the license is released immediately.
License usage during integration:
Some Rational Synergy integrations hold a license for the duration of time the user is running the integration. Source-code related operations performed through the integration can then be updated in the database. In this case, the user can exit the visible session, but the integration is still running a session behind the scenes on behalf of the user
Rational Change supports the floating, named-user floating, and token license types.When you install Rational Change, the license server information (port@host) is requested and persisted to the file CHAN
There is a 30 minute minimum use time when Rational Change checks out a license. When a license is checked out, it stays checked out for at least 30 minutes, whether there is activity from the user. If the user exits or is inactive after that, the license is released.
Co-Authored by: Saurabh Tyagi and Pankaj Sharma
Sumant Renukarya 270002B42N Visits (1846)
Here is one of the requirements that was put across one of the users, using IBM Rational Team Concert (RTC) tool:
What you need to know about the CA Endevor "actions" used by the Rational Developer for System z CARMA Enhanced Edit feature
SteveSpirk 060001UESP Visits (2238)
Rational Developer for System z added the CARMA Enhanced Edit feature for CA Endevor SCM users in the 8.5.1 release. This CARMA Enhanced Edit feature is RDz's implementation of CA Endevor's Fast/Quick Edit. This feature allows RDz users to edit elements in the Endevor repository without having to retrieve/extract element out of repository into external file. When performing changes to a program, user will start by selecting the "version" of program/element within Endevor that they want to change. This usually is the "production" version of the program/element. When working with RDz CARMA, user would select (right-click on) element to be opened and select Edit/'Edit with' from the context menu.
When the CARMA Edit Element UI screen appears, user indicates to CARMA where they want element copied. This would typically be the "entry" environment/stage where they are allowed to edit element.
So what Endevor "actions" does CARMA use to copy "production" element into entry/editing environment/stage? That is a very important question because there are several different Endevor "actions" to do this, but not all RDz users are authorized to perform all Endevor "actions". The Endevor "actions" to handle this copy are generated from the RDz host Endevor RAM. These "actions" are run in foreground mode because of the unpredictable nature of running "action" as a batch job (CARMA has no idea when job will run/complete). Below I've listed how this "copy" of the element to "entry" environment/stage is handled in the available 8.5 releases and 9.0.
RDz 8.5.1 Endevor RAM: This was the initial implementation of the CARMA enhanced edit feature. In this release, the copy of the element to "entry" environment/stage is done using the Endevor GENERATE ELEMENT "action", with the "copyback" option. We have found that foreground GENERATEs are not allowed or are problematic in some customer environments.
RDz 126.96.36.199/9.0 Endevor RAM: In these releases, the copy to "entry" environment/stage was changed to use the Endevor TRANSFER ELEMENT "action". The element is opened in the RDz editor after the foreground Transfer has completed. In many cases, when the element is opened, some/all dependencies are not resolved until a GENERATE is done for the element being edited in this Environment/stage. We have also found that some customer sites do not allow RDz users to run Transfer "action".
RDz 188.8.131.52 Endevor RAM: In this release, the default way that CARMA handles this "copy" is still with the Endevor TRANSFER ELEMENT "action", however, we also allow you to configure RDz to use the RETRIEVE ELEMENT (from "prod") and ADD ELEMENT (to "test") "actions" to handle this "copy". To configure CARMA to use RETRIEVE-ADD "actions" for program/element "copy", you need to un-comment the 'ENT
To resolve dependencies when an element is opened using CARMA Enhanced Edit, a GENERATE ELEMENT request was added (184.108.40.206) following the TRAN
When you select this option, keep in mind there is good chance all dependencies will not be resolved by the RDz editor until a GENERATE is done on the element being opened, in the Endevor environment it is being opened from. This option should only be selected if you have trouble running foreground GENERATEs.
The current versions of RDz are 220.127.116.11 and 9.0 (Nov. 2013). The APAR mentioned in the previous paragraph will be delivered in the 8.5.1.next and 9.0.next RDz host PTFs. To verify what CA Endevor "actions" are being used in your environment, you can view the Endevor "actions" used in the MSG3FILE. The MSG3FILE is allocated in the user's CARMA server who performed the CARMA Enhanced Edit on element.
AcdntlPoet 2700019V2G Visits (2124)
Getting/setting properties of SCM artifacts using Rational Team Concert SCM CLI- This video demonstrates how to modify and list the properties of a workspace, stream, component, baseline, and a snapshot using the RTC SCM CLI client.