> 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/phased-onboarding/java-onboarding-guide/getting-started.md).

# Getting Started

### Overview

This guide walks you through the process of integrating **SeaLights** with applications that include **Java components**. It explains the onboarding and setup steps required to integrate SeaLights with each Java-based component of your application.

{% hint style="info" %}
If your application includes components built with other technologies, refer to the corresponding onboarding guides for those technologies. All technology-specific guides can be found in the ["SeaLights Agents & Plugins" section of "Setup & Configuration".](https://docs.sealights.io/knowledgebase/setup-and-configuration/)
{% endhint %}

Repeat the process described in this guide for each Java component in your application.

### Using This Guide

SeaLights recommends a [**phased onboarding approach**](/knowledgebase/phased-onboarding/readme.md#what-youll-achieve-in-each-phase). Each phase builds upon previous phases—gradually increasing the value you gain from SeaLights while adding configuration layers step by step.


---

# 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/phased-onboarding/java-onboarding-guide/getting-started.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.