How to integrate IBM InfoSphere Data Architect and Rational Team Concert

Teams can collaborate yet customize these tools to increase productivity

IBM® Rational Team Concert™ is a collaborative environment that helps project teams simplify, automate, and govern software delivery. IBM® InfoSphere™ Data Architect (formerly IBM® Rational® Data Architect) is an enterprise data modeling and integration design tool and collaborative data design solution to discover, model, relate, and standardize diverse and distributed data assets. This article explains how to integrate the two so that teams can collaborate, yet each can customize the tools for their respective needs.

Share:

Prasobh Kallingal (prasobhkallingal@in.ibm.com), Database Administrator and Rational Subject Matter Expert, IBM

photo of Prasobh KallingalPrasobh Kallingal is a database administrator/modeler and Rational software subject matter expert for InfoSphere Data Architect. He works for IBM Global Business Services



27 April 2010

Also available in Chinese Portuguese Spanish

Prerequisites

  • A computer with IBM® Rational Team Concert™ and IBM® InfoSphere® Data Architect installed
  • Access to the IBM® Jazz™ source control and basic knowledge of how it works

Benefits of this integration

IBM® InfoSphere™ Data Architect (formerly IBM® Rational® Data Architect) is a collaborative enterprise data modeling and integration design tool to discover, model, relate, and standardize diverse and distributed data assets. IBM® Rational Team Concert™ is a collaborative software delivery environment that helps project teams simplify, automate, and govern software delivery. It extends the capabilities of the team by integrating work items, build updates, and software configuration management (SCM), all based on the collaborative infrastructure of the IBM® Rational® Jazz™ Team Server.

Integrating InfoSphere Data Architect and Rational Team Concert software can improve the productivity of teams and the quality of the work that they produce by allowing each team to customize the tools for their own best practices. Rational Team Concert uses this knowledge to automatically detect violations of the teams' process the moment that they happen. Integrated Work Item Management automatically creates and tracks progress of individual work items in accordance with the team process and project rules that you define. Additionally, it captures and maintains the relationships of work items to other artifacts, such as code change sets and builds. Integrated Source Control provides essential software version control, workspace management, and parallel development support to individuals and teams.


How to integrate these two applications

InfoSphere Data Architect and Rational Team Concert are integrated by using a shell-sharing technique. The concept of shell-sharing between Eclipse-based products means that you can share the core Eclipse components in each Eclipse-based product. Shell-sharing eliminates the need to install several Eclipse platforms for each product, thus it saves disk space and eliminates duplication of components.

Follow these steps to begin the integration:

  1. First, install Rational Team Concert Standard Edition on your machine by using the IBM® Installation Manager.
  2. Then install InfoSphere Data Architect, also by using the Installation Manager.
  3. When you reach the "Accept the license agreement" page, click Next.
  4. When you see the screen for creating a new package group, select the Use the existing package group radio button (see Figure 1), and it will automatically select a previous package of the Rational Team Concert and continue installation.

Note:
You can do these steps in reverse: First install InfoSphere Data Architect, and then install Rational Team Concert in the InfoSphere Data Architect package group (shared folder).

Figure 1. Selecting "Use the existing package group"
Shows default package under Installation Directory

How Jazz source control works

The source control component of the Jazz technology platform manages the source code, documents, and other artifacts that a team creates. It provides change-flow management to facilitate sharing of controlled artifacts, retains a history of changes made to these artifacts, and enables simultaneous development of multiple versions of shared artifacts so that teams can work on several development lines at the same time. Jazz source control includes these components:


Like many configuration management systems, Jazz source control uses a secure repository that is hosted on a server and accessed at a URL by clients who are using standard protocols. The repository stores objects such as streams, work items, and workspaces that help manage change flow. It also stores controlled artifacts that represent and can be retrieved as files or folders in a computer file system.

Workspaces
A workspace is an area where you can view or modify components. A repository workspace on the server stores components as versionable artifacts that can be loaded into a local workspace (such as an Eclipse workspace or an ordinary folder) on the client.

Streams and components
A stream is a repository object that includes one or more components. A component is a collection of related artifacts, such as an Eclipse plug-in or a group of documents that comprise Web site content.

Change sets
A change set is a repository object that collects a related group of file, folder, and component modifications so that they can be applied to a flow target (workspace or stream) in a single operation.

Change sets and change flow
Change sets flow between a repository workspace and its flow targets. Most workspaces have at least one flow target. Many have more than one. Flow targets can include streams or other workspaces.

Change flow, conflict detection, and conflict resolution
when two or more team members modify the same file or folder, conflicts result. These conflicts must be resolved when one team member accepts the other's changes into a workspace. Jazz source control detects potential conflicts and warns you about them before you accept them. It also provides a variety of tools and methods for resolving conflicts.


How to share your project to Jazz source control

  1. Open your InfoSphere Data Architect workbench, and select the Data Project Explorer tab.
  2. Right-click on Demo_Project and then select Team > Share Project (Figure 2).
Figure 2. Sharing a project through the IDA perspective
Shows menu selections as described
  1. Select the repository plug-in that you will use to share the selected project, and then click Next (Figure 3).
Figure 3. Sharing a project to a repository
Share Project view, Jazz Source Control selected
  1. Select the repository workspace and component where you want to share the project, and then click Next (see Figure 4).
Figure 4. Sharing a project in Jazz source control (selecting repository)
'Select Component' screen
  1. Under the existing stream called "Data Model Team Stream," create a new component called Demo_component, and then click Finish (see Figure 5).
Figure 5. Selecting a stream and creating a component
'Select a Stream' screen

Now you had created a component for sharing your model.


How to deliver projects into streams

Now that you have shared the project, the changes are finished in Pending Changes view.

Next, you need to deliver the changes from the Pending Changes view to the Team stream for you team to be able to see them, too.

  1. Follow one of these steps:
    • Either right-click on the Outgoing folder in the Pending Changes view and select Deliver to deliver the project into the stream (see Figure 6).
    • Or select the model from the Data Project Explorer and right-click Team > Deliver (see Figure 7).
Figure 6. Delivering project artifacts to the component
'Pending Changes' view
Figure 7. Delivering models to component through Data Project Explorer view
'Data Project Explorer' view

At this point, the developer or architect has shared the model under a new component that resides under an existing Team stream. That is, sharing the model/project into the component.


How to enable check-in policies

After you have shared the model, whenever you modify it hereafter, you can activate an option to automatically check it into the repository. This you have to do manually as shown below

  1. To enable this option, select Window > Preference > Team > Jazz source control > Check-in policies.
  2. Check the radio button for "Perform check-in whenever a resource is modified."
Figure 8. Enabling automatic check-in
'Check-in Policies' screen segment view

If you have made any changes, you need to deliver the changes into the stream again to reflect the changes to all.


How to view the history of the models

  1. To view the history of the models, right-click on the models Team > Show History, as shown in Figure 9.
Figure 9. Viewing the history of the model
'Screenshot showing Show History from dropdown menuHistory tab
  1. To view the comparison with previous models, right-click on the History comments, and select the Compare with Previous option.
Figure 10. Comparing the model with a previous model
'Compare with Previous' selected in drop-down menu

Now you can visualize the changes made to the model. The tabs at the bottom of the screen show more information on the changes to the model.

Figure 11. Viewing the changes to models
View changes of models

Larger view of Figure 11.

Resources

Learn

Get products and technologies

Discuss

Comments

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


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational, DevOps
ArticleID=483637
ArticleTitle=How to integrate IBM InfoSphere Data Architect and Rational Team Concert
publish-date=04272010