Configure Rational Insight with an additional Jazz Team Server

Introduction

This document describes how to configure IBM Rational Insight to extract data from an additional Jazz Team Server (JTS) and related applications (CCM & QM). We will refer to the additional JTS that we will be working with as the “new JTS”.

Scenario

An organization would like to report on data captured across multiple teams, each with their own JTS (CLM) deployment. The organization is using Rational Insight, which is already configured to extract data from one of their teams’ JTS deployments. They now want to configure Insight to access a second JTS deployment.

Note: This document assumes you have already configured Rational Insight (version 1.1) to extract from one JTS server (version 3.0.1.3) and are attempting to configure a second JTS of version 3.0.1.x.

  1. Download the XML data configuration (XDC) files from the new JTS and respective Applications (as applicable)

    1. Download the relevant XDC files based on your deployment
    2. Add data source System DSN to your Windows box
      1. Use a suffix for the data source name to distinguish between Jazz Team Servers (e.g. Jazz Foundation Services 2)
    3. Verify the connections for the XML data configuration files
      1. Ensure that the CLM user credentials that are assigned the ‘Data Collection User’ license exist here

    See Integrating the Collaborative Lifecycle Management XML data configuration files with Rational Insight

  2. Modify the JTS connection in IBM Cognos Data Manager

    1. Launch IBM Cognos Data Manager
    2. Open your ETL catalog
    3. Navigate to the ‘Connections’ node
    4. Double-click on ‘Jazz Foundation Services’
    5. Navigate to the ‘Connection Details’ tab
    6. Change the relevant data source connection (‘Data Source Name’) to point to the new JTS connection (the new XDC file you configured in step 1)



    7. Save your catalog change

  3. Run the ETL jobs

    1. In Data Manager, navigate to ‘Jobs’ > ‘JFSJobs’ > ‘JFS3.0Jobs’ > ‘JFS_ODS3.0_Fullload’
    2. Right-click on this job and select ‘Execute’ to run it



    3. Once this completes successfully, repeat these steps for the remaining applications you are configuring (e.g. RTC, RQM)

      Note: Be sure to select the appropriate version of these jobs based on the version of your software. For example, if your CCM application is version 3.0.1.2, then you would select that version: ‘Jobs’ > ‘RTCJobs’ > ‘RTC3.0.1.2Jobs’ > ‘RTC_ODS3012_FullLoad’

      See Running the ETL jobs

  4. Create a master jobstream for this new JTS deployment

    1. Once you have successfully run the full load version of your JTS and relevant applications, you must create a master jobstream for this JTS deployment by using the ‘DeltaLoad’ version of the ODS jobs (JFS_ODS3012_DeltaLoad, RTC_ODS3012_DeltaLoad)
    2. Select a location for this new JTS deployment jobstream (in this example we have chosen to place it right under the ‘Jobs’ directory)
    3. Right-click on ‘Jobs’ and select ‘Insert Jobstream’



    4. Provide the new jobstream a name (e.g. ‘JTS2’) and click ‘Ok’
    5. Insert the JTS (JFS) job into the JobStream
      1. Right-click on your new ‘JTS2’ job, select ‘Insert Node’, and select ‘Insert Jobstream’



      2. Provide a Business name (e.g.’ JFS_ODS3.0_DeltaLoad’)
      3. Click on the ellipsis next to ‘Associated JobStream” and navigate to the relevant JTS (JFS) job that you would like to add



      4. Navigate to the ‘Predecessors’ tab and select the ‘Start’ node which will precede this JFS jobstream



      5. Click Ok and repeat step e for each relevant application

        Note: the jobstream flow should be in this order: ‘Start’, JFS, RTC, RRC, RQM.

  5. Publish this new jobstream as a Data Movement Task to the Report Server

    See Publishing a job as a data movement task

    Note: You must ensure that your ‘Build_Star’ job is the LAST job that runs. For example, your sequence should be running your first JTS jobstream (which includes JTS and relevant application), then your second JTS jobstream (e.g. JTS2), etc and finally, the ‘Build_Star’ job. Once these jobs are published, you can schedule them in IBM Cognos Connection to ensure the sequence of execution.

    For more information on scheduling jobs, see Schedule an Entry (Data Movement Task)

Summary

In this document, we demonstrated how to configure Rational Insight to extract data from a second (or multiple) JTS/CLM deployment(s). An organization will now be able to report on data captured across multiple teams, each with their own JTS/CLM deployment.


Feedback
Was this information helpful? Yes No 3 people rated this as helpful.