Jazz Library Workarounds: Data Collection Component problems in Jazz Reporting Service 6.0
Author name

Workarounds: Data Collection Component problems in Jazz Reporting Service 6.0

The table of contents lists the known problems, workarounds, and limitations related to the Data Collection Component functionality in the Jazz Reporting Service (JRS) 6.0 release.

Workarounds

Problem Summary

The Data Collection Component does not yet support server rename.

Problem

The Data Collection Component does not yet support server rename. Before performing the rename, Data Collection Component must be unregistered from the application and re-registered after the rename with a empty new repository database. The resource groups must also be recreated. If you have other Jazz Reporting Service applications co-installed on the same server as the Data Collection Component, they must also be unregistered and re-registered after the rename.

Workaround

Complete the following steps if you have the Data Collection Component co-installed with other Jazz Reporting Service applications on the same server as Report Builder or Lifecycle Query Engine:

  1. For Report Builder, export your reports to a .zip file so that you can import them later to the renamed server.
  2. When you are preparing the mapping file for server rename, do not edit the URLs for the Data Collection Component, Report Builder, or Lifecycle Query Engine.
  3. Before you import the mapping files into the target server with the -importURLmappings command, unregister the Data Collection Component, Report Builder, and Lifecycle Query Engine from the Jazz Team Server.
  4. After you have performed the server rename, uninstall the Data Collection Component, Report Builder, and Lifecycle Query Engine.
  5. For WebSphere Application Server:
    1. Delete the dcc_war, rs_war, and lqe_war files from WebSphere Application Server. Remove the associated logs and temporary directories.
    2. Reinstall the Data Collection Component, Report Builder, and Lifecycle Query Engine on the renamed server.
    3. Deploy the dcc.war, rs.war, and lqe.war files to WebSphere Application Server.
    4. To start the applications, in WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications. Select the check box next to these applications, and then click Start:
      • dcc_war
      • rs_war
      • lqe_war
  6. For Apache Tomcat:
    1. Stop the Apache Tomcat servers for the Data Collection Component, Report Builder, and Lifecycle Query Engine.
    2. Back up the following files to another directory in case you need to revert the patch: .
      • [DCC_install_dir]/server/tomcat/webapps/dcc.war
      • [ReportBuilder_install_dir]/server/tomcat/webapps/rs.war
      • [LQE_install_dir]/server/tomcat/webapps/lqe.war
    3. Delete the following files:
      • [DCC_install_dir]/server/tomcat/webapps/dcc.war
      • [ReportBuilder_install_dir]/server/tomcat/webapps/rs.war
      • [LQE_install_dir]/server/tomcat/webapps/lqe.war
    4. Delete the following directories:
      • [DCC_install_dir]/server/tomcat/webapps/dcc
      • [DCC_install_dir]/server/tomcat/work/Catalina/localhost/dcc
      • [ReportBuilder_install_dir]/server/tomcat/webapps/rs
      • [ReportBuilder_install_dir]/server/tomcat/work/Catalina/localhost/rs
      • [LQE_install_dir]/server/tomcat/webapps/lqe
      • [LQE_install_dir]/server/tomcat/work/Catalina/localhost/lqe
    5. Reinstall the Data Collection Component, Report Builder, and Lifecycle Query Engine on the renamed server.
    6. Place the dcc.war file in the [DCC_install_dir]/server/tomcat/webapps/dcc directory.
    7. Place the rs.war file in the [ReportBuilder_install_dir]/server/tomcat/webapps/rs directory.
    8. Place the lqe.war file in the [LQE_install_dir]/server/tomcat/webapps/lqe directory.
    9. Start the server.
  7. Run the Jazz Team Server setup wizard and register the three applications. On the Data Collection Component page, add the database connection information. Ensure you have deleted the old databases (not the data warehouse) and created new empty ones for the Data Collection Component and Lifecycle Query Engine. If you are using Derby, this will happen automatically during the uninstall and reinstall process. If you are using DB2, Oracle, or SQL Server, you must manually delete and create the databases.
  8. After you have completed the setup wizard, log into the applications:
    • http://[dcc_server_name]:9443/dcc/web
    • http://[rs_server_name]:9443/rs/web
    • http://[lqe_server_name]:9443/lqe/web
    Note: For the Data Collection Component, initially you will see an error stating that the application is still initializing. Wait 20 to 30 minutes until you see a list of data collection jobs that can be run.
  9. In the Data Collection Component application:
    1. Open the Resource Group Configuration.
    2. Enter the information for the data warehouse and click Save.
    3. After the list of applications are added, enter the user name and password and click Save.
    4. Go back to the Data Collection Jobs page.
    5. Click Select All to select all the jobs to run.
    6. Click Run all data warehouse collection jobs.
  10. In Report Builder, import your reports from the *.zip file to the renamed server.

Complete the following steps if you only have the Data Collection Component installed on the server without any other Jazz Reporting Service applications:

  1. When you are preparing the mapping file for server rename, do not edit the URLs for the Data Collection Component.
  2. Before you import the mapping files into the target server with the -importURLmappings command, unregister the Data Collection Component from the Jazz Team Server.
  3. After you have performed the server rename, uninstall the Data Collection Component.
  4. For WebSphere Application Server:
    1. Delete the dcc_war file from WebSphere Application Server. Remove the associated logs and temporary directory.
    2. Reinstall the Data Collection Component on the renamed server.
    3. Deploy the dcc_war to WebSphere Application Server.
    4. Start the .war file.
  5. For Apache Tomcat:
    1. Stop the Apache Tomcat server for the Data Collection Component.
    2. Back up the following file in case you need to revert the patch: [DCC_install_dir]/server/tomcat/webapps/dcc.war.
    3. Delete the following file: [DCC_install_dir]/server/tomcat/webapps/dcc.war.
    4. Delete the following directories:
      • [DCC_install_dir]/server/tomcat/webapps/dcc
      • [DCC_install_dir]/server/tomcat/work/Catalina/localhost/dcc
    5. Reinstall the Data Collection Component on the renamed server.
    6. Place the dcc.war file in the [DCC_install_dir]/server/tomcat/webapps/dcc directory.
    7. Start the server.
  6. Run the Jazz Team Server setup wizard. On the Register Applications page, add the Data Collection Component. On the Data Collection Component page, add the database connection information. Ensure you have deleted the old database and created a new empty one for the Data Collection Component. If you are using Derby, this will happen automatically during the uninstall and reinstall process. If you are using DB2, Oracle, or SQL Server, you must manually delete and create the databases.
  7. After you have completed the setup wizard, log into the Data Collection Component application at http://[dcc_server_name]:9443/dcc/web.

    Note: Initially you will see an error stating that the application is still initializing. Wait 20 to 30 minutes until you see a list of data collection jobs that can be run.
  8. Open the Resource Group Configuration.
  9. Enter the information for the data warehouse and click Save.
  10. After the list of applications are added, enter the user name and password and click Save.
  11. Go back to the Data Collection Jobs page.
  12. Click Select All to select all the jobs to run.
  13. Click Run all data warehouse collection jobs.

Related Information

The following links point to related information:

Problem Summary

Data Collection Component does not initialize after setup.

Problem

Data Collection Component does not initialize after setup.

Workaround

If the Data Collection Component page displays errors after initial setup, restart the Data Collection Component application. For example, the error may look like the following:

CRRCD1500E An exception java.lang.NullPointerException was caught in the class com.ibm.team.repository.service.internal.oauth.OAuthServiceProvider from calling the function getKeyAndSecret.

Related Information

The following links point to related information:

Return to the top of the page


Limitations

Use the links below to learn more about the limitations (an issue, without a workaround) in this release:

Limitation Summary

The Data Collection Component does not support loading of requirement data originating from non-CLM systems like Rational RequisitePro and exposed through the RQM Reportable REST API.

Problem

Rational Quality Manager (RQM) 6.0 dropped certain forms of integration with non-CLM requirement tools like Rational RequisitePro. The Data Collection Component (DCC) will not load requirement data that originates from those systems and is exposed through the RQM Reportable REST API. The above limitation also applies to mixed environments that have both deployments of RQM 6.0 and RQM 5.X. The only requirement data that DCC can load is the one originating from Rational Doors Next Generation (RDNG). Clients upgrading to CLM 6.0 should consider the above limitation before going ahead with the upgrade.

Related Information

The following links point to related information:

 
 

Return to the top of the page

 

Fri, 26 Jun 2015