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

# Guides

Step-by-step guides for onboarding SAP systems to SeaLights with the ABAP Agent.

Onboarding is split into three parts, plus Fiori-specific support. Start with Part 1, then show value with Test Cycles; use Part 3 only for Tosca Cloud runner and TIA. If your network uses a proxy, see [Configure a proxy](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/configure-a-proxy.md).

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Setup and installation</strong></td><td>Part 1 — install through initial build map and search_testrepo for any supported test repository.</td><td><a href="/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md">Setup and installation</a></td></tr><tr><td><strong>Show the value with Test Cycles</strong></td><td>Part 2 — watcher transports, Test Cycle recommendations/gaps/coverage report, footprints, and running a test.</td><td><a href="/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md">Show the value with Test Cycles</a></td></tr><tr><td><strong>Tosca Cloud runner and TIA</strong></td><td>Part 3 — Tosca Cloud only: playlist runner integration and Test Impact Analysis beyond day-zero cycles.</td><td><a href="/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/tosca-cloud-runner-and-tia.md">Tosca Cloud runner and TIA</a></td></tr><tr><td><strong>Configure a proxy</strong></td><td>Route the agent through your corporate proxy — the connection to SeaLights and the connections to your test repositories.</td><td><a href="/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/configure-a-proxy.md">Configure a proxy</a></td></tr><tr><td><strong>Fiori support</strong></td><td>How Fiori/OData contexts, FLPCA titles, and SCMON interact for recommendations and coverage.</td><td><a href="/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/fiori-support.md">Fiori support</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.