ABAP Agent

Introduction

The SeaLights ABAP Agent continuously monitors changes made to an SAP application, and identifies whether tests you’ve run in Tosca exercise these changes. This allows you to see the test coverage for new or changed ABAP components in SeaLights, and identify ABAP components that don’t yet have any tests.

The agent has a command-line interface which allows you to do the following:

• Install the agent and connect it to SeaLights.

• Create RFC Destinations to connect to your QAS and Production systems.

• Create Pipelines to identify QAS and Production systems in your SAP landscape.

The SeaLights ABAP lets you create the following:

Initial Build Map

The agent uses a watcher program which you run once for each Pipeline to create an Initial Build Map. The agent creates an Initial Build Map as follows:

• It retrieves usage data for standard and custom objects from the Pipeline’s Production System and finds the Development Class or Package associated with each used object. By default, the agent retrieves the last 13 months’ of usage data.

• It accesses the Pipeline’s QAS system to retrieve all the objects that belong to each Development Class or Package.

• It sends the objects to SeaLights.

The agent stores the Initial Build Map in a SeaLights app named after the Pipeline. You can add each app to the SeaLights Coverage Dashboard.

The agent stores the following code objects in the Initial Build Map:

• Programs

• Functions

• Function Groups

• Classes

• Methods

• Enhancement Objects

Build Modifications

The agent uses a watcher program which runs every five minutes and checks for code changes made to a Pipeline by transports imported into its QAS system. The agent stores the changes in Build Modifications, and adds these to the Pipeline’s app that you can add to the SeaLights Coverage Dashboard.

Footprints

If you have connected Tosca to SeaLights, you can configure the watcher program to check for test executions in Tosca and report these to SeaLights. When you run a test in Tosca, the agent matches the ABAP components that you ran in the test against objects in the latest Build Modification. It then sends this data to SeaLights as a Footprint.

SeaLights processes the Footprint data and updates the test coverage for the ABAP objects in the latest Build Modification. You can see the test coverage in your SeaLights app’s Coverage Report.

Software components

We deliver the SeaLights ABAP agent in a ZIP file that includes the following components:

• ABAP addon: An SAP addon that includes the ABAP agent’s SAP components.

• WATCHER: A program that watches for ABAP changes and reports them to SeaLights.

• SLABAPCLI: A command-line interface program that lets you configure the ABAP Agent and connect it to SeaLights.