Arun K Sriramaiah 2700076GE8 Visits (492)
Scenario and advantages of Baseline auto creation in IBM Rational Team Concert (RTC) SCM.
Baselines: A baseline represents a configuration of a component at any particular point in time. Baselines serve as fixed points of reference, and are useful both for initializing streams and workspaces that pick up from a given point of a set of components, and for sharing the changes to components at a granularity coarser than that of their individual change sets. Read more at Component baselines in the CLM Knowledge Center.
Baseline size is negligible and is an expected behavior of the SCM concepts. You shouldn't worry about having more baselines.
What are the 'backup before drop' and "backup before replace" baselines in RTC source control? What does this mean and why is it appearing?
Note: Baselines which are automatically created in RTC and includes the change sets, when it replaces the baseline or drops the baseline.
Arun K Sriramaiah 2700076GE8 Visits (710)
This article is regarding Rational CLM integration with JIRA, able to get the information that JIRA can be integrated with CLM containers (RRC, RTC and RQM) with Rational Adapter for JIRA.
Advantages of RTC and JIRA Integration
Following are some of the benefits that an organization will get by integrating RTC with JIRA:
As per the topology, JIRA application is installed on a single application server and the CLM applications are also installed on a single application server.
For example: Standard Topology
The JIRA application server communicates with the CLM application server through server friend relationships. The adapter resolves links from CLM work items back to the JIRA server.
As long as the JIRA application can connect or ping to the repository you may install it on the same machine or another server
dmmckinn 1200006SCS Visits (671)
Looking for some of those special little tidbits to help with your use of Rational Integration Tester? Check out the following most recently published content which may offer some assistance.
This document will be helpful to users who have constructed a Custom Function previously for RIT and may wish to repeat the process without working through all the instructions in the manual again. The document may also assist users reviewing the process undertaken when troubleshooting.
Provides details about how you can pretty print XML from IBM Rational Integration Tester that may be desirable in cases such as logging.
Arun K Sriramaiah 2700076GE8 Visits (730)
This article explains how to reduce the number of Rational Team Concert component flow displays in the pending changes window.
By default, all components in a Repository workspace (RWS) use the current flow target. You can use the Repository workspace editor to add flow targets or change their scope so that not all components use them. Refer to Flow targets for further details.
For example, you can specify in flow targets for some of the components in a Repository workspace (RWS) display, or decide that a specific component must display in pending changes window.
Note: You can use the Flow Only components checked below option in RWS\Stream Flow Target to make the Pending Changes view more manageable. This helps more when streams or workspace have 10++ and which might not be all needed in the pending changes window.
You can use the above scenario where in you can avoid unwanted components display in the pending changes.
Arun K Sriramaiah 2700076GE8 Visits (787)
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