How AppScan leverages Rational Team Concert

This article provides information about how Rational AppScan leverages Rational Team Concert (RTC) to provide a better understanding of the basic architecture.

Description of the architecture

1. The AppScan application runs on IIS (Internet Information Services) Microsoft Windows webserver
2. RTC runs on Apache Tomcat application server (if desired RTC can run on WebSphere)
3. AppScan uses RTC for SSO (single sign on)

Description of the integration

1. When users log into the AppScan application, they are first redirected to Jazz Team Server (JTS) for log in
2. Once the log in completes successfully, the user is redirected back to AppScan
3. AppScan will handle the licensing
4. No licenses are installed to RTC

Description of how AppScan configures Rational Team Concert

1. During an installation of RTC, AppScan will create a consumer key to allow communication between RTC and AppScan
2. AppScan will configure RTC to run as a service
3. AppScan Server runs a JTS Auto Setup script jtsautosetup.bat located in the install folder (typically: C:\Program Files (x86)\IBM\AppScan Enterprise\Tools\jtsautosetup) which does the following:
   
   1. During the installation of RTC, AppScan will create a consumer key to allow communication between RTC and AppScan
      b. Configures RTC to run as a service
      
4. Jazz configuration is accomplished by running the Jazz setup wizard /jts/setup

Related topics: Deployment web home, Deployment web home

External links:

• IBM

Additional contributors: None