r6 - 2015-05-27 - 16:43:23 - Main.sbagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > IntegrationsTroubleshootingRTCandRationalAppScan > RationalTeamConcertAppScanIntegrationTroubleshooting

How do I troubleshoot issues that occur when using AppScan with RTC?

Authors: AbrahamSweiss
Build basis: IBM Rational Team Concert 4.0.x and later

This page provides information to help troubleshoot issues encountered when using IBM Rational AppScan with IBM Rational Team Concert (RTC).

INITIAL ASSESSMENT

Prerequisites

  • Ensure that the integration is configured correctly (see: RationalTeamConcertIntegrationsAppScan).
  • If the issue appears to be related to RTC, then you can take AppScan out of the picture by connecting directly to the jts/admin page. Doing this will help validate whether or not RTC is configured correctly.
  • If the issue is reproducible by connecting directly to RTC, then the issue would lie in RTC and may not be related to AppScan.
  • If the issue is not reproducible, then the issue will most likely lie in AppScan.

Recommended data gathering and subsequent analysis steps

The majority of issues reported with this integration have historically been related to the LDAP configuration, thus the investigation will primarily focus in that area.

Collect the log and trace output detailed in the AppScan section of MustGather: Integration issues when using Rational Team Concert

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r6 < r5 < r4 < r3 < r2 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.