Troubleshooting the Integration

This page has not been liked. Updated 6/1/13, 12:21 PM by cfjohnstTags: None

This page contains additional information about troubleshooting the Rational Team Concert and Rational ClearQuest integration.

Troubleshooting SSL and Certificate Errors

If the Rational Team Concert or Rational ClearQuest server requires an SSL connection, you may see SSLHandshakeException or CertPathBuilderException errors when attempting to configure the OSLC integration.

To resolve this issue, the SSL certificate from Rational Team Concert or Rational ClearQuest must be imported into the SmartCloud Control Desk or Tivoli Service Request Manager server's trust store.

On Websphere Application Server:

  1. Login to the Websphere Application Server administrator console.
  2. Go to Security > SSL certificate and key management.
  3. Select Key stores and certificates.
  4. Select the trust store, usually CellDefaultTrustStore.
  5. Select Signer certificates.
  6. Select Retrieve from port.
  7. Enter the host, SSL port, and a name for the certificate entry for the Rational Team Concert or Rational ClearQuest server.
  8. Select Retrieve from port. The certificate information should appear if it was retrieved successfully.
  9. Select OK and choose to Save the configuration. Now you can continue with the OSLC integration configuration.

On Weblogic:

  1. Retrieve the certificate from the Rational Team Concert or Rational ClearQuest server, and save it on the admin workstation. Note the location of the certificate file for the next step.
  2. Run the following command on the Weblogic server: <weblogic_install_dir>\jdk160_18\jre\bin\keytool.exe -import -alias <alias> -file <certificate_file> -keystore <weblofic_install_dir>\jdk160_18\jre\lib\security\cacerts
  3. Enter the keystore password. The default password is changeit.
  4. When prompted, enter y to choose to add the certificate to the trust store.
  5. Restart the Weblogic server. Now you can continue with the OSLC integration configuration.

Troubleshooting OAuth Issues with Rational Team Concert

If the integration is configured with Rational Team Concert 3.0 or 3.0.1, the OAUTH_VERSION in the OSLC_DEFAULT_OAUTH End Point should be set to "1.0".

In later versions of Rational Team Concert, you may see a "parameter_rejected" error when configuring the OAuth Access Token. To fix this problem, set the OAUTH_VERSION in the OSLC_DEFAULT_OAUTH End Point to "1.0a".

 

Troubleshooting OAuth Issues with Rational Team Concert