> 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/getting-started/steps-for-successful-onboarding/onboarding-pre-requisites.md).

# Onboarding Pre-Requisites

## General <a href="#general" id="general"></a>

* The application to integrate with SeaLights is identified and ready.
* Test stages that can be run against the application are ready to integrate SeaLights with
* Relevant project members with proper permission set are identified and allocated

## Technical and Application Checklist <a href="#technical-and-application-checklist" id="technical-and-application-checklist"></a>

<table data-header-hidden><thead><tr><th width="216.69921875">Item</th><th width="360.1171875">Description</th><th>Relevant Approach(es)</th></tr></thead><tbody><tr><td>Testing frameworks</td><td>Frameworks used across all test stages (e.g., JUnit, NUnit, Pytest)</td><td>All</td></tr><tr><td>Build tool</td><td>Build system used (e.g., Maven, Gradle, MSBuild), if applicable</td><td>All</td></tr><tr><td>Application servers</td><td>Runtime environments (e.g., Tomcat, IIS)</td><td>All</td></tr><tr><td>Containers</td><td>Containers (e.g., Docker, Kubernetes) and their purpose</td><td>All</td></tr><tr><td>Package names/namespaces</td><td>Application-specific packages or namespaces for mapping coverage</td><td>All</td></tr><tr><td>Map files (if transpiled)</td><td>Location of source maps (e.g., from TypeScript, Babel)</td><td>All</td></tr><tr><td>Network/security configuration</td><td>Proxy/firewall details: allow outbound HTTPS access to SeaLights</td><td>All</td></tr><tr><td>Source Control System (SCM)</td><td>e.g., GitHub, Bitbucket, GitLab</td><td>All</td></tr><tr><td>Build &#x26; test trigger type</td><td>CI-only: auto/manual triggers or job chaining</td><td>CI/CD only</td></tr><tr><td>Runtime arguments</td><td>App runtime options or parameters</td><td>All</td></tr><tr><td>Agent compatibility</td><td>Match SeaLights agent types to tech stack (Java, .NET, etc.)</td><td>All</td></tr><tr><td>Deployment Script / Runtime System Access</td><td>For CD/Standalone: ability to run the agent where the app is deployed</td><td>CD-only &#x26; Standalone</td></tr></tbody></table>

## Agents compatibility <a href="#agents-compatibility" id="agents-compatibility"></a>

### Java <a href="#java" id="java"></a>

* Ability to download one or more of the following, according to the setup:
  * SeaLights Java agent from [Downloading The Java Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/default-usage-cli/downloading-the-java-agent.md)
  * SeaLights Maven plugin from Maven Central or local Maven repo
  * SeaLights Gradle plugin from Maven Central or local Maven repo
* Knowledge and ability to configure the JVM arguments of the application servers

### NodeJS and Client-Side JS <a href="#nodejs-and-client-side-js" id="nodejs-and-client-side-js"></a>

* Npm & Node installed on any machine that will be running the sealights agent: [Downloading the Node.js Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/downloading-the-node.js-agent.md)
* Sealights node agent installed on any machine that will be running the sealights agent: [Downloading the Node.js Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/downloading-the-node.js-agent.md)
* For unit tests coverage - The ability to generate the `coverage-final.json` (NYC JSON coverage report)
* For Client-Side JS, Ability to generate Source maps of ‘original source’ quality: [Javascript & Node.js Source Map Files](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/legacy-commands-deprecated/javascript-and-node.js-source-map-files.md)

### .Net <a href="#dotnet" id="dotnet"></a>

* Knowledge of architecture (32 or 64 bits) that which the process coverage will be captured
* (If needed) Ability to download and run the Microsoft Process Explorer on machines that report coverage for debugging purposes.
  * See the Official documentation page: <https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer>

### Python <a href="#python" id="python"></a>

TBC

### Golang <a href="#golang" id="golang"></a>

TBC

### ABAP <a href="#golang" id="golang"></a>

TBC


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/getting-started/steps-for-successful-onboarding/onboarding-pre-requisites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.