Teamscale Docs

Appearance

Prerequisites for the SAP® Integration ​

Before Teamscale can analyze ABAP® code, three things must be in place: the SAP Java Connector library on the Teamscale server, the Teamscale Connector add-on in the SAP system, and a technical SAP user for Teamscale to log on with. This article covers the first of these and introduces the other two, which are described in detail in Installation Steps in the SAP System.

Installation of the SAP Java Connector ​

A prerequisite for Teamscale to communicate with SAP systems is the SAP Java Connector (SAP JCo) library. SAP's licensing restrictions do not permit redistribution of this library with Teamscale. However, SAP JCo is licensed without additional fees as part of a licensed SAP solution or component license.

SAP Java Connector (SAP JCo) for Cloud-Hosted Instances

For instances hosted on our cloud platform, the SAP Java Connector (JCo) is automatically included for customers with SAP integrations.

  1. Download the SAP Java Connector (SAP JCo). SAP JCo is available through the SAP Service Marketplace for registered SAP customers. Download the most recent version (>= 3.1) for the platform running Teamscale. When SAP JCo is needed for deploying our docker container, use the version for Linux for Intel compatible processors.

  2. Uncompress the contained library files into a temporary directory.

  3. Copy the Java library sapjco3.jar and the native library file for the specific platform (sapjco3.dll for Windows, libsapjco3.so for Linux, or libsapjco3.dylib for macOS) to a directory named lib-ext.

    • For Teamscale zip distributions, the lib-ext directory must be inside the Teamscale installation directory.
    • For Teamscale Docker distributions, the lib-ext directory must be mounted directly in the volumes section of the docker-compose.yml file to the directory /opt/teamscale/lib-ext, see below. Please consider setting the appropriate access rights (see How to install Teamscale with Docker).
    yaml
        volumes:
      - /path-on-host/lib-ext:/opt/teamscale/lib-ext

  4. On Windows systems, please make sure the prerequisite Microsoft Visual Studio C/C++ Runtime is installed. The architecture (x86 or x64) must match your JVM's architecture. If in doubt, consult the System > System Information view. For details, see SAP Note 2786882.

  5. (Re-)start Teamscale to load the SAP JCo library. You can confirm that the JCo library has been successfully loaded on the System > System Information view.

Teamscale Connector for SAP NetWeaver® AS ABAP® ​

The Teamscale Connector for SAP NetWeaver® AS ABAP® provides the connection between Teamscale and SAP NetWeaver AS ABAP based systems. The connector has to be transported to the SAP NetWeaver system and provides the following main functions:

  • An RFC-based interface, which is used by Teamscale to poll the SAP system for custom code changes, so they can be analyzed within Teamscale

  • Execution of SAP Code Inspector (SCI) and export of the inspection results to Teamscale

  • Extraction of test coverage and usage data for Teamscale to support Test Gap analysis and usage analysis

  • A plug-in for the ABAP Workbench and the Change and Transport System to access Teamscale results from the SAP system. This is realized by a custom SAP Code Inspector test case which shows messages for findings identified in Teamscale.

The Teamscale Connector for SAP NetWeaver® AS ABAP® is compatible with SAP NetWeaver AS ABAP 7.40 EHP8 and later versions.

How to obtain and transport it is described in Installation Steps in the SAP System.

User and Role for RFC Access ​

Teamscale connects to the SAP application server via RFC (remote function call) to retrieve the source code, which should be analyzed as well as some metadata (for example test coverage). The called functions are in function group /CQSE/TEAMSCALE_CONNCT_RFC . Additional functions reside in /CQSE/TEAMSCALE_TIA_RFC . Hence, a (technical) SAP user is required, which will be used by Teamscale to connect to the SAP system. Also, if SAP Unified Connectivity (UCON) is used to secure communications, access to these RFC functions must be granted in the UCON configuration.

The required authorizations and how to create the user are described in Installation Steps in the SAP System.

Git-Based ABAP Development ​

If your organization develops ABAP in a Git-based workflow rather than with the Teamscale Connector, see Creating an ABAP Project in Teamscale instead.