Increase productivity by using Rational Application Developer with other Rational software

Rational Application Developer integrates with products across the Rational portfolio and provides third-party extension support. This two-part series gives an overview of integrating Rational Application Developer with IBM® Rational Team Concert™ and IBM® Jazz™ technology, IBM® Rational® Asset Manager, IBM® Rational® RequisitePro®, and IBM® Rational® ClearQuest®. The authors discuss installation, configuration, requirements, use cases, and limitations. You will learn how you can apply these integrations during software development in the Rational Application Developer environment, from requirements management and traceability, to implementation and maintainability, to governance with reusable assets.


Jarett Stein (, Software Engineer, IBM

Jarett SteinAs a member of the Rational Application Developer System Verification Test team, Jarett Stein focuses on integrations and Web tools. He designs and develops test applications to simulate environments in which customers use the software.

Kristine Heaton (, Software Engineer, IBM

Kristine Heaton is a technical lead tester for Rational Asset Manager on the Rational Asset Manager System Verification Test team.

18 May 2010

Also available in Chinese Russian Vietnamese Spanish

This article serves as an overview of selected integrations of IBM® Rational® Application Developer with these other Rational products:

  • IBM® Rational® Asset Manager
  • IBM® Rational® ClearQuest®
  • IBM® Rational® RequisitePro®
  • IBM® Rational Team Concert™

The authors explore features, functionality, and sample use cases to describe the ways that Rational Application Developer users can benefit from these integrations.

Overview of Rational Application Developer

Rational Application Developer offers users the ability to take advantage of features in other Rational products through its product integration support. Often a developer may be required to perform functions, report status, and update records using functionality that is not built in to their integrated developer environment (IDE). To perform these required actions they would have to leave their IDE, open another application, and perform the action there. The product integrations available from within Rational Application Developer enable developers to stay in their development environment while working with integrated products. The actions they take using the Rational Application Developer integration features will be available to other users of the integrated product within their own environment.

Rational Application Developer integration with Rational Asset Manager

Rational Asset Manager is for enterprises that are interested in asset management for virtually all types of assets so that people can work together to build and deliver software products. When installed and integrated with the Rational Application Developer development environment, Rational Asset Manager provides asset management functionality, such as asset review, approval, publication, traceability, utilization monitoring, and reuse. It also provides functionality such as storage, search, asset versioning and customizable processes, such as asset reviews. This collaborative tool can be used for strategic planning, as well as for governance. The repository can categorize and provide access control for any of your submitted assets. It provides statistics and reporting tools, too. By using Rational Asset Manager software, you can categorize assets according to your organization's defined classification, tag them with labels, and find them with full-text search or use search filters.

Additionally, Rational Asset Manager provides integration with other IBM products, such as IBM® Rational® ClearCase®, Rational ClearQuest, and IBM® WebSphere® Service Registry and Repository. Customizable Rational Asset Manager libraries can be preconfigured for specific Rational Application Developer asset types, constraints, attributes, or category schemas. Importing the library makes it available for use with Rational Application Developer artifacts.

Rational Asset Manager can work with various hardware and operating system platforms and offers two types of interfaces: Web and Eclipse-based clients.

Install third-party extensions similarly

The way that the Rational Asset Manager client is installed with Rational Application Developer, by using the Software Updater, is similar to how other extensions can be installed and integrated with Rational Application Developer.


The Eclipse-based Rational Asset Manager interface (the Eclipse client) can be integrated into Rational Application Developer with installation by using the Software Updater. The Software Updater is invoked from the Help menu.

  1. From the Help menu, select the Software Updater, and then select Add Site.
  2. In the Add Site window (see Figure 1), enter the URL address of an existing Rational Asset Manager server and select to install all features.
Figure 1. Software Update Add Site dialog window
Shows Rational Asset Manager update site URL

You can easily find the update site URL used by the Software Updater by opening the Asset Manager Web Client and selecting Help > Extensions, copying the update site URL, and pasting it into the Location field used in the Software Updater. The update URL site is provided on the Extensions page (Figure 2).

Figure 2. Rational Asset Manager Web client Help menu
Extensions link selected


The Rational Asset Manager Eclipse client can be installed into, or can extend, Eclipse IDEs (integrated development environments) or the IBM Rational Software Delivery Platform IDE (for example, Rational Application Developer or IBM® Rational® Software Architect).


You can use the Rational Asset Manager Eclipse client, such as that installed for Rational Application Developer, with a Rational Asset Manger server of the same release version and one release version earlier than that one. Release versions include the original release and fix packs. For example, you can use a Rational Asset Manager Eclipse client Version 7.2 with a Rational Asset Manager server Version 7.2 or 7.1.1.


After Rational Asset Manager integration is installed to an instance of Rational Application Developer, you will notice an Asset Manager perspective in the workspace (Figure 3). By using this perspective, you can connect to an existing asset manager repository. Views in the perspective include Asset Explorer, Asset Search, and Asset Repositories.

Figure 3. Rational Asset Manager perspective
Asset Management perspective in Rational Application Developer

You can use these and associated views to work with the repository assets. From the Asset Explorer view (Figure 4), you can connect to an existing repository by selecting the Create connections option. The New Asset Manager Repository Connection dialog window (Figure 5) is where you select the repository URL and log in by using a valid ID and password.

Figure 4. Asset Explorer view
Three tasks available in the Asset Explorer View
Figure 5. New Asset Manager Repository Connection view
New repository connection dialog fields

By selecting the connection, you can use the provided queries in the Asset Repositories view (Figure 6) to see your assets, recent submissions, and assets that are rated highest.

Figure 6. Asset Repositories tab view with default queries
Queries include the ones mentioned

By using Asset Search (Figure 7), you can search for assets and apply filters to your search.

Figure 7. Asset Search view with various filters
Asset Search view screen segment

You can easily submit assets by using the integrated Rational Asset Manager client in Rational Application Developer.

From the Asset Explorer view, select Create a new asset, or, if you want to find and import an existing asset, select the Find assets across repositories and use text search, tags, or filter searches.

You will se the dialog window for a new asset (Figure 8) when you select Create a new asset. Fill in the information there.

Figure 8. New Asset dialog window
General Details view

You submit new assets by providing information about the asset in the detail fields, adding files from your workspace or file system in the Content tab, and selecting Submit to submit the asset to the repository. Assets submitted from a Rational Application Developer integration with Rational Asset Manager might include common libraries, common projects, common templates, or other files that need to be shared, reviewed, or tracked through the Rational Asset Manager governance processes.

To import an asset:

  1. Enter a query in the Asset search view. Results of the search are shown in the Search results view.
  2. Select the asset. The asset displays in the asset editor.
  3. In the asset editor, select the Import button.
Figure 9. Asset search results and editor
Assets tab with table in lower part of screen
  1. After selecting the Import button, users will be prompted select a project for import. Alternatively, to import the asset into a new project, users can select the New Project icon New Project icon to invoke the New Project wizard (see Figure 10). This will load the contents of an asset to your Rational Application Developer workspace where you can use the asset in your development environment. For instance, you might import a Web page template to your Rational Application Developer Web project to begin developing the Web front end for a business application implementation.
Figure 10. Import an asset
Import asset dialog with target container

Rational Asset Manager can integrate with a Rational Application Developer environment that uses Rational ClearCase source control. If projects are being developed in Rational Application Developer under ClearCase source control, users can submit an asset and information about the source control system, which will save the artifact's source control location to the asset's metadata. Assets under source control are checked out when imported and checked back in under source control when the asset is resubmitted.

Rational Asset Manager is based on IBM Jazz technology. It provides a collaborative environment for creating and managing assets and artifacts. Its functionality allows for role-based asset reviews and software lifecycle management, among other capabilities. The Rational Asset Manager home page and the Help section within it provide tutorials and samples to demonstrate the functionality (see Resources).

Rational Application Developer integration with Rational ClearQuest

Rational ClearQuest offers change management capabilities, lifecycle traceability, reporting, and real-time visual metrics. Commonly, ClearQuest is used as a defect and change-tracking system for users to submit and manage change requests. You can take advantage of ClearQuest features within the Rational Application Developer environment to view, create, document, and manage change requests and issues without having to go outside of the IDE.


ClearQuest can be integrated with Rational Application Developer by using the Software Updater.

In a Microsoft® Windows® platform, using an installed Rational ClearQuest Version 7 (see Requirements, which follows), the Software Updater tool in Rational Application Developer is used to add the location of the Eclipse folder where the ClearQuest plug-in is located.

To install:

  1. Invoke the Software Updater from the Help menu in the Rational Application Developer workspace: Help > Software Updates > Available Software > Add site > Local
  2. Navigate to the folder where ClearQuest is installed on your hard drive and (ClearQuest V7.1 in this example), and select the cqecUpdateSite folder.
  3. Click OK.
Figure 11. Software Updates and Add-ons view, browsing for the ClearQuest plug-in
Browsing for the cqecUpdateSite folder
  1. Expand the added site, select the features, and click Install.
Figure 12. Software Update installation dialog window
CQ Update Site in software updater


Rational ClearQuest integration requires that ClearQuest be installed on your system or that you have access to a system where ClearQuest is installed. You need to have access to the ClearQuest plug-in. A cautionary note: different versions of the Rational ClearQuest and ClearCase software cannot co-exist on the same system. For example, you cannot install Rational ClearQuest V7.1 on a system where Rational ClearCase V7.0 is installed, because both products need to be at the same version sequence.

To access a ClearQuest database within Rational Application Developer environment, ClearQuest repositories must have been created, and they must be maintained with the site administration tool. Users must access repositories through a secured login that requires an ID and a password.


Within Rational Application Developer, you open the ClearQuest perspective and connect to a ClearQuest repository. After you are connected, you can create defects, manage existing defects, create new queries or use existing queries to search, and view work items in the ClearQuest repository.

  1. To access the ClearQuest perspective, as in many Rational software integrations, from the main menu, simply select Window > Open Perspective > Other, and choose ClearQuest from the drop-down menu.
  2. Connect to your repository by using a provided schema and login information. For example, from the ClearQuest menu (Figure 13), select Database > Connect > New to create a new connection.
Figure 13. ClearQuest database connection menu
Shows drop-down menu selections
  1. Select the schema for your ClearQuest database.
Figure 14. Schema Repository dialog view
New Connection window
  1. Select Next, and then enter your user ID to log in.

The ClearQuest perspective (Figure 15) contains a set of Eclipse views that you can use for various Rational ClearQuest actions. They consist of these views:

  • ClearQuest Navigator view
  • ClearQuest Query Results view
  • ClearQuest Record Details view
  • Console view
Figure 15. ClearQuest perspective
ClearQuest views in Rational Application Developer

The ClearQuest Navigator view displays queries, charts, reports and report formats. In this view, you can create new queries, edit existing queries, save, delete, or rename a query, or execute a query. The results are displayed in the ClearQuest Query Results view. You can select a record and check the record details by using the ClearQuest Record Details view. You can perform actions on the records from either the ClearQuest Query Results view or the ClearQuest Record Details view. The console view displays the success and failure messages.

A common function when using Rational Application Developer and the ClearQuest integration is to search for a ClearCase record to view or modify details of a defect report. To search for a record by ID, from the main menu select ClearQuest > Find Record.

Figure 16. Find Record is an option on the ClearQuest drop-down menu
ClearQuest menu expanded

The Find Record dialog window is where you can select the record type, such as ChangeRequest type (Figure 17), and the record ID.

Figure 17. Find Record dialog window
Type and ID fields

You can also use Rational Application Developer to submit a change request record:

  1. Select ClearQuest > New > Change Request to get to the Create Change Request window.
  2. Fill in the required fields, and click OK.
  3. To add attachments to the record, highlight the record, open the menu, and select Utilities > Add Attachment.

Attachments can also automatically be added to new records by right-clicking on development artifacts or items in the Problems view and selecting ClearQuest -> Create ClearQuest Record from Resource (Figure 18). The selected resource or problem will automatically appear in the attachments tab of a new record. This helps you avoid having to find a related resource or to copy and paste an error message from the Problems view to attach to a defect.

Figure 18. "Create a ClearQuest Record from Resource" menu option
ClearQuest menu expanded

When have completed your tasks, you can simply disconnect from the database:

  1. Select the connection in the ClearQuest Navigator view and then, from the menu, select Disconnect.

This outlines some of the integration functions that you can use from within Rational Application Developer to easily handle change management tasks without having to go outside of the Rational Application Developer environment.

Check the ClearQuest documentation for more information about additional functionality that is available.

Rational Application Developer integration with Rational RequisitePro

The remainder of this article focuses on integrations that are available in Rational Application Developer Version (the latest version available at time of publication) as part of the client installation from the IBM Installation Manager. Integrations that are available as part of the product installation include:

  • Rational RequisitePro
  • Rational ClearCase SCM Adapter (not discussed in this article)
  • Rational Team Concert Client (IBM Rational Jazz Server is required and available separately)
  • Rational Team Concert Client Debug Extension

Installation tool

This section covers integration with Rational RequisitePro or Rational Team Concert you use IBM Installation Manager to install the client.

Rational RequisitePro helps teams manage their requirements and use cases, improve traceability, reduce rework, and increase software quality. RequisitePro accomplishes this by providing a Web and desktop client that integrates with Microsoft® Word® and Eclipse IDEs to manage requirements, traceability, and relationships. By using a Rational RequisitePro project, Rational Application Developer can integrate the RequisitePro functionality within the development environment to provide traceability and the power of the requirement management solution, as well as specific Java™ Enterprise Edition (EE) support, to development artifacts inside Rational Application Developer.


Rational RequisitePro integration is available with the Rational Application Developer installation among the Rational lifecycle integration features (see Figure 19).

Figure 19. Integration options available in Rational Application Developer
Lifecycle integration check boxes

To install Rational RequisitePro as part of a new Rational Application Developer installation, simply select it during install. To install it to an existing Rational Application Developer installation:

  1. Open IBM Installation Manager, which you used to install Rational Application Developer.
  2. Click Modify.
  3. Select Rational Application Developer.
  4. Check the Rational RequisitePro Integration option.
  5. Click Modify.

Prerequisites and limitations

Using the Rational RequisitePro integration inside of Rational Application Developer requires that Rational RequisitePro Version 7.0 or 7.1 or later be installed on the same system.

Those versions cannot co-exist on systems that have inconsistent versions of Rational ClearCase or Rational ClearQuest installed. For instance, you will not be able to install Rational RequisitePro 7.1 on a system where Rational ClearQuest 7.0 is installed.


With the Rational RequisitePro integration feature installed for Rational Application Developer, you can access a Requirement perspective by selecting Window > Open Perspective > Other, and choose Requirement. The Requirement perspective provides access to RequisitePro projects and project artifacts (requirements, elements, traceability links, and so forth). It displays the following views by default:

  • Requirements Explorer
  • Requirement Editor
  • Requirement Trace
  • Link Clipboard
  • Requirement Query Results (after you run a query)

These views provide similar information and functionality as when they are opened in the RequisitePro Eclipse client, but they provide the added ability to associate requirement project elements with Rational Application Developer artifacts. Figure 20 shows an example of the Requirement perspective in Rational Application Developer.

Figure 20. Requirement perspective in Rational Application Developer
Requirements views showing menu

You can use the RequisitePro integration to open RequisitePro projects in the Requirements Explorer view by using the buttons at the top of the view. The RequisitePro project will display in a tree in the Requirements Explorer view. Double-click a requirement to see details about it in the Requirement Editor to the right of the Requirements Explorer view. The requirement editor also contains information about traceability and a requirement's history.

A developer will typically open a requirements project and review a project's requirement details to review what is required for a project or feature. After a developer implements a given requirement, artifacts exist in the workspace that meet the requirement, and connections between the two can be made to create navigability and show traceability.

Creating traceability links between requirements and development artifacts is easily accomplished. Selecting a development artifact and dragging it to the requirement will create a traceable link between the two. A linking indicator will appear on both the development artifact icon in the Project Explorer view and the requirement icon in the Requirement Explorer view. You can also view traceability links in the Requirement Editor's Traceability tab and in the Requirement Trace tab (Figure 21), which you will see after selecting either the development artifact or requirement and selecting from the Context Menu > Select Requirement In > Requirement Trace.

Figure 21. Requirement Trace view
Requirement Trace view showing traceability

One concept that the integration of RequisitePro with Rational Application Developer introduces is that of Eclipse Element Proxies. These proxies are stored in a folder by the same name inside of the Requirements project that appears in the Requirements Explorer. When you create links between Rational Application Developer development artifacts and requirements, an Eclipse element proxy is created as a representation of the development artifact and a traceability link is created between the requirement and the proxy element. The link between the development artifact and the requirement is, by default, created as an indirect link.

You have the option to change the way elements are linked or created in the project properties in the Requirements Explorer view (properties are available from the menu of the requirements project). There are predefined element types for Rational Application Developer artifacts listed as Enterprise Edition (J2EE) elements. For example, from the Link Policy page of the project properties, Link Policies can be created that specify whether or not a proxy element will be used when a certain requirement type and element kind are linked. On the Requirement Creation page, you can specify what kind of requirement to create, given a specific source element kind. Many kinds of J2EE elements are predefined in the RequisitePro and Rational Application Developer integration.

The Rational Application Developer and RequisitePro integration brings requirements management and the ability to define traceability into the developer's environment to help ensure better and more convenient linkability between requirements and development artifacts. The trace information stored in a RequisitePro requirements project allows this information to be visible in a RequisitePro Web client or in the RequisitePro desktop client by users in any role.

Rational Application Developer integration with Rational Team Concert

Rational Team Concert is built on IBM® Jazz® technology as the desktop client front-end for a collaborative development platform. Rational Team Concert allows project teams to define, automate, and govern software delivery projects. It includes tools for software development projects, such as iteration planning, project transparency, source control, work items, build support, and customizable process definition and enforcement. The integration of Rational Team Concert provides Rational Application Developer with a collaborative development environment by establishing a connection to a Rational Team Concert repository. See the Resources section for more information about Rational Team Concert.

The integration of Rational Team Concert with Rational Application Developer also provides a Collaborative Debug feature, which developers can use to transfer debug sessions to others and to save or retrieve debug sessions stored in the Rational Team Concert repository. For a demonstration of how to use the Collaborative Debug feature, see links in the Resources section.


Rational Team Concert integration is available during Rational Application Developer installation under the "Rational lifecycle integration" features, as shown in Figure 22.

Figure 22. Integrations available in Rational Application Developer installation
Rational Lifecycle features in installation

To install to a new Rational Application Developer installation, simply select the Rational Team Concert – Client integration feature as part of the initial installation process. To install to an existing Rational Application Developer installation:

  1. Open IBM Installation Manager which was used to install Rational Application Developer.
  2. Click Modify.
  3. Select Rational Application Developer.
  4. Check the Rational Team Concert – Client integration feature.
  5. Modify the installation.

Similarly, you can install the Debug Extension for Rational Team Concert Client, which provides Collaborative or Team debug functionality. The Debug Extension requires that the Rational Team Concert client also be installed. In order to use the Debug Extension, the Rational Debug Extension must be installed to the IBM Rational Team Concert Server. For information on how to install the Debug Extension to the Rational Team Concert Server, see the Technote titled IBM Rational Debug Extension for IBM Rational Team Concert Server, V7.5.3.

Rational Application Developer 7.5 includes Rational Team Concert Version 1.0. To install Rational Application Developer 7.5 and a Rational Team Concert Version 2.0 client, follow these steps (you need a valid ID, which entitles you to free Rational Team Concert downloads):

  1. Go to the Rational Team Concert download page.
  2. Select the version of Rational Team Concert you want to use with Rational Application Developer.
  3. Click the All Downloads tab.
  4. Download the edition of Rational Team Concert that you want, making sure to select a link under the edition's Installation Manager section that includes a client for the Eclipse IDE.
  5. After the download is finished, extract the contents locally, making a note of the extraction directory.
  6. Open the Installation Manager, which you used to install Rational Application Developer, and select File > Preferences.
  7. Navigate to the Repository page.
  8. Add the following repository:
    <Rational Team Concert extracted directory>\im-repo\repository.config
  9. Click OK.
  10. Click Install.
  11. Select IBM Rational Team Concert Version 2.0 (or later).
  12. Click Next until you arrive at the page where you can choose the option to install Rational Team Concert to use the existing package group where Rational Application Developer is installed.
  13. Continue through the installation wizard to finish the installation.

After you have finished the installation, Rational Team Concert Version 2.0 or later , a newer level and compatible with newer versions of a Rational Team Concert server, will be installed to the same shell as Rational Application Developer. It can be used in the same way as the Rational Team Concert feature bundled with the Rational Application Developer installation.


To use the Rational Team Concert integration with Rational Application Developer, you must be able to connect to a Rational Team Concert Server. This requires that you have a user who can access the Rational Team Concert Server with adequate permissions. Contact your Rational Team Concert Server administrator or see the Rational Team Concert documentation for more information.

The client version of Rational Team Concert must match the version of Rational Team Concert server that you connect to. For instance, a Rational Team Concert 1.0 or later client cannot connect to a Rational Team Concert 2.0 or later server, nor the reverse.



The integrated environment for Rational Team Concert and Rational Application Developer brings all of the functionality of Rational Team Concert to Rational Application Developer users. This includes the following functionality, which is described in this section:

  • Integrated Rational Team Concert client views in Rational Application Developer perspectives
  • Connections to Rational Team Concert Server repositories
  • Connections to and configuration of Rational Team Concert project areas
  • Work item access and links to source control actions
  • Interaction with Jazz Source Control, Repository Workspaces, and Streams
  • Collaborative Debug functionality

Integrated Rational Team Concert client views in Rational Application Developer perspectives

Rational Application Developer perspectives include, by default, views from Rational Team Concert that provide immediate access to Rational Team Concert integrated functionality. For example, the Java EE perspective includes the Team Artifacts view next to the Enterprise Explorer view, as well as the My Work view next to the Outline view. By using the Team Artifacts view, users can connect to repositories and projects on their Rational Team Concert server. The My Work view shows newly assigned work items, plus current and future work. It provides a dynamic view that helps keep developers aware of work items in their queues. The bottom status bar in Rational Application Developer (Figure 23) also includes Rational Team Concert integration.

Figure 23. Rational Team Concert work items in the Rational Application Developer status bar
Status bar search field and work item ID

From here, developers have access to work items by entering the work item ID or searching for text within a work item. The status bar also shows a work item ID and name if there is a work item in progress.

From the Team Artifacts view, developers can quickly connect to Rational Team Concert repositories and Team Project Areas. The first time that they access this view (Figure 24), developers will see the following options:

  • Accept Team Invitation
  • Connect to Project Area
  • Create a Project Area
  • Create a Repository Connection
  • Open First Steps welcome page for review
Figure 24. Team Artifacts default view
Team Artifacts options for connecting

The options provided by the Team Artifacts view assist the developer in quickly getting started in using the Rational Team Concert integration. After a Repository Connection is established, the Team Artifacts view (Figure 25) displays options to work with Rational Team Concert project areas and artifacts, including specific project area artifacts, debug artifacts, lists of favorites, feeds, repository workspaces, team areas, and a work item history.

Figure 25. Team Artifacts view after connected to repository
Team Artifacts view project artifacts

The context menu for each of the items in the Team Artifacts views provides deeper access to the Rational Team Concert integration. After first connecting to a Rational Team Concert repository, create a project area. You can do this by clicking the Connect to Project Area button at the top of the view: Project Area button. In the New Project Area wizard, there is a link to create a new project area, which will bring you to the Create Project Area wizard where you can name the project area and choose a development process template. The process template includes a process for your project that can be further customized later.

A developer works on projects in a Repository Workspace, which is each developer's own development area on the Rational Team Concert Repository. Projects in the Repository Workspace are not shared with the team until they are delivered by a developer to a stream. To create a new repository:

  1. In the Team Artifacts view, right-click My Repository Workspaces.
  2. Choose New > Repository Workspace.
  3. Choose your Rational Team Concert Repository, and click Next.
  4. You have the option to use the workspace to either back up your work or flow with a stream. Flowing with a stream will make it available to other developers working off the stream.
  5. If you chose to flow with a stream, then you can optionally select components to add to the repository workspace.
  6. Click Finish.

After the project area has been created, the project area editor will open. Additionally, the following Rational Team Concert views are available: Team Advisor, Team Organization, and Work Items. The project area editor allows for customizations to access control, membership, process configuration, work item categorization, and the release definition. The Team Advisor view provides feedback when a process violation occurs. For instance, you might get feedback in this view if you try to add development artifacts to source control for a project area where you are not a member. The Team Organization view shows a hierarchical view of members of project areas and underlying teams. The Work Items view (Figure 26) shows work items returned from a query. After you create the project area, it will show work items related to setting up your project area, based on the chosen process template.

Figure 26. Work Items view
Work items with search results listed

Work item access and linkage to source control actions

Work Item integration from Rational Team Concert in Rational Application Developer makes it easy to view, modify, and create tasks or defects, as well as to associate source check-ins with new or existing work items. Icons with indicators and stylized text on the work item in a view make it easy to see the status of a work item. As mentioned before, work items are quickly accessible from the Rational Application Developer status bar, which also indicates the work item currently in progress.

The source control and work item integration allows developers to work with development artifacts under source control while tracking changes back to work items for project transparency. Using the source control features in the Rational Team Concert integration is simple. Here's how to share a project:

  1. Right-click a project and select Team > Share Project.
  2. Choose the Jazz Source Control as the repository type.
  3. Choose or create a component to share the project. This will be adding the project to the component that you choose in the corresponding workspace and stream.
  4. Click Finish.

This will place your changes in an outgoing change set (in the Pending Changes view) and change the icons in your project and underlying files to indicate that they are under source control and contain outgoing changes. To deliver your project to source control:

More about In Progress work items

"In Progress" work items are automatically associated with source check-in actions. If a work item had already been marked as "In Progress" when using this integration, then the outgoing change set would automatically be associated with that work item.

  1. Switch to the Pending Changes view.
  2. Notice that your project and files are in an outgoing change set.
  3. Right-click the change set, and select Associate Work Item. Because a work item has not yet been associated to this outgoing change set, you must define one before delivering the changes.
  4. Choose an existing work item or create a new one to associate the changes with this work item.
  5. Notice that the work item now appears under the Outgoing folder in the change set.
  6. Right-click the change set, and select Deliver.
  7. The project will now be added to source control. It can be loaded into other developers' workspaces that are connected to the same stream.

Note about traceability to change sets:

Figure 27. Change sets section in work item
Change Sets link in work item

Projects already under source control can be loaded to a developer's Repository Workspace by following these steps:

  1. Right-click a Repository Workspace, and choose Load.
  2. Select Find and Load Eclipse Projects.
  3. Click Next.
  4. Projects under their associated component are visible.
  5. Selecting the project and clicking Next will load projects to your Rational Application Developer workspace.

Collaborative Debug functionality

Another feature of the Rational Application Developer and Rational Team Concert integration is Collaborative or "Team" debugging. This is available as an optional installation with Rational Application Developer that has a dependency on a Team Debug Extension that is also installed to the Rational Team Concert server. This topic is explored in more detail in two DeveloperWorks tutorials (see Resources), but a basic use case is outlined below.

Team Debug allows debug sessions to be stored, retrieved, suspended, and shared between developers using the Rational Team Concert repository connection as an intermediary. The Team Debug feature stores and shares breakpoints, source location set up, and console input/output streams for a debug session. The Team Debug feature supports debugging IBM® WebSphere® server applications (on V6.0, V6.1, and V7.0), Eclipse and Java applications, Java applets, JUnits, and remote Java applications using Java 1.5 or higher.

To save a debug session on the Rational Team Concert server:

  1. Set some breakpoints in an existing Java project.
  2. Right-click the Java project, select Debug As > Debug Configurations.
  3. In the Debug Configurations dialog window, double-click Java Application to create a new Java application configuration.
  4. Navigate to the Team tab in the Debug Configuration (Figure 28).
Figure 28. Team tab in new Debug Configuration wizard
Debug team tab checkbox and field
  1. Check Add debug session to team repository.
  2. Select your team repository.
  3. Click Debug.

Notice the "Add to Team Repository" process in the progress bar.

Figure 29. Team Debug process in progress bar
Add to Team Repository in progress bar
  1. You will be switched, or prompted to switch, to the Debug perspective.
  2. In the Debug view, notice that the application being debugged has a [Team] decorator on it, as Figure 30 shows.
Figure 30. Team decorator on debug session
Debug view with [Team] annotated thread
  1. Right-click the debug thread, and you'll notice these new options for Team Debug functionality:
    • Transfer to User
    • Park Debug Session
    • Remove from Team Repository
  2. To save the session to the Rational Team Concert repository, select Park Debug Session. This will disconnect your debug session.

To retrieve a debug session from the Rational Team Concert server:

  1. Open the Team Artifacts view.
  2. Expand the Debug artifact and Search Team Debug Sessions.
Figure 31. Team Artifacts view, Debug artifacts
Team debug built-in search queries
  1. The built in queries allow you to search for debug session on the repository.
  2. Double-click Started By Me to find the debug session that you just saved.

The Team Debug view (Figure 33) will open and display your search results.

Figure 32. Team Debug view search results
Debug session in search results

You can use the menu on a returned session to either Debug the session or Remove it from the Team Repository. Debugging the session will provide the option to import or overwrite breakpoints. If you have existing breakpoints, your breakpoints and the imported breakpoints will be grouped separately in the Breakpoint view.

To transfer a debug session to another user:

  1. Follow the steps above to save a debug session until you right click on the thread in the Debug view. Right clicking the thread will show the context menu seen in Figure 33.
  2. From the context menu or an active debug session, choose Transfer to User. A dialog will appear allowing you to search for another user.
Figure 33. Team Debug menu choices
'Transfer to User' option is first
  1. Search for a user, and click OK.
  2. The other user will be prompted that they have an incoming debug session, with the option to accept or decline. See Figure 34 for an example.
Figure 34. Incoming Debug Session dialog window
Import and Overwrite Breakpoint check boxes
  1. The other user will also have the option to import or overwrite breakpoints with yours.
  2. As the other user accepts the incoming debug sessions, your debug session will become suspended, and the other user will be able to debug where you left off.

This section has explained the integration between Rational Team Concert and Rational Application Developer that is part of the Rational Application Developer installation. This integration brings all of the features of Rational Team Concert (source control, work items, and process workflow) to the development environment. Additionally, the integration provides the opportunity for Rational Application Developer users to collaboratively debug applications by using the Rational Team Concert Server as an intermediary. For more information about Rational Team Concert functionality and the Team Debug feature, check the links in the Resources section.


The value of product integrations is in the productivity improvements that can be realized when developers can work with integrated products from within their development environments. Development artifacts created in Rational Application Developer can be used in conjunction with these integrations so that they are reusable, linkable, traceable, auditable, and automatically related to the tasks being performed.


The authors thank Tracey Brown Burton and Robert Taniwa for their technical and editorial contributions to this article.



Get products and technologies



developerWorks: Sign in

Required fields are indicated with an asterisk (*).

Need an IBM ID?
Forgot your IBM ID?

Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.


All information submitted is secure.

Dig deeper into Rational software on developerWorks

Zone=Rational, DevOps
ArticleTitle=Increase productivity by using Rational Application Developer with other Rational software