> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/install-the-abap-agent/install-the-abap-addon.md).

# Install the ABAP addon

{% hint style="danger" %}
**Not backwards compatible:** The ABAP Agent 2.0 add-on is a **new** add-on that does **not** support earlier ABAP Agent versions (1.x, including 1.3). It is required for 2.0, and earlier add-on versions are not compatible with the 2.0 agent. If you are upgrading, you must install this new add-on on your SAP landscape.
{% endhint %}

The ABAP add-on includes the SAP components required for the ABAP agent.

You must install the ABAP add-on on your SAP landscape's Quality Assurance (QAS) system — this applies to any non-PRD system you want to onboard. Your Production (PRD) system must be set up either with or without the add-on — see [Install the add-on on your Production system](#install-the-add-on-on-your-production-system). If you cannot connect the agent to PRD, export Production usage data using the ST03N transaction and import it into the QAS system using the SLABAPCLI program (see [Upload usage data to an RFC Destination](broken://pages/fw9npSbrE9ByW6ww8CGd)).

Download the add-on package: [abap\_addons.zip](https://agents.sealights.co/slabapaddon/latest/abap_addons.zip). The ZIP contains the `.PAT` and `.SAR` files used in the installation procedures below.

To install the ABAP add-on, carry out the steps in one of the following two sections. Use the `.SAR` file if you have SAPGUI front-end access to the target system; use the `.PAT` file if you can only reach the application server's file system directly (for example, via a remote shell).

{% content-ref url="/pages/nspG0n2penFIUe25GwFs" %}
[Broken mention](broken://pages/nspG0n2penFIUe25GwFs)
{% endcontent-ref %}

{% content-ref url="/pages/Gg9nK0y4RogXDjhBL9TE" %}
[Broken mention](broken://pages/Gg9nK0y4RogXDjhBL9TE)
{% endcontent-ref %}

## Install the add-on on your Production system <a href="#install-the-add-on-on-your-production-system" id="install-the-add-on-on-your-production-system"></a>

The agent reads production usage data (ST03) from your Production (PRD) system to decide which objects are actually used. You must set up each PRD system in **one** of the following two configurations:

| Configuration                    | On the PRD system                                                                | Pipeline setting             | How the agent reads usage data                               |
| -------------------------------- | -------------------------------------------------------------------------------- | ---------------------------- | ------------------------------------------------------------ |
| **Without the add-on** (default) | Nothing to install. If the add-on is installed, `useaddon = false` turns it off. | `useaddon = false` (default) | Standard SAP function module `SWNC_COLLECTOR_GET_AGGREGATES` |
| **With the add-on**              | Install the add-on with the same `.SAR` or `.PAT` procedure you used for QAS     | `useaddon = true`            | SeaLights function module `/TRICE/RFC_GET_ST03_DATA`         |

Using the add-on on PRD helps smooth the onboarding.

For either configuration:

1. Grant the RFC user of the PRD RFC Destination the authorizations for that configuration. See [Generate Authorization Profiles — Production system authorizations](broken://pages/JfFkO1xqq9huG22WXqhI#production-system-authorizations).
2. Set `useaddon` to match the configuration for every pipeline that uses this PRD system (`slabapcli pipeline set --use-addon true|false`). All pipelines that use the same PRD RFC Destination must use the same value. See [Configuration settings — Production usage data source](broken://pages/DZM4uWEu5r51kMDWCmDB#production-usage-data-source).