> 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/build-and-test-execution/integration-build/integration-build-explicit-components-and-versions/component-file.md).
# Component File
The following steps describe the requirements to report an integration build using the Java or NodeJS build scanner.
{% hint style="warning" %}
As a **pre-requisite**, each component needs to be built, scanned, and reported to SeaLights before reporting the integration build itself.
{% endhint %}
## Create an Integration Build Session ID
Each integration build gets reported as a new build to Sealights, and therefore needs a new session ID of its own.
#### **Java Agent**
{% code overflow="wrap" lineNumbers="true" %}
```
java -jar sl-build-scanner.jar -config -tokenfile /path/to/sltoken.txt -appname "IntegrationBuildName" -branchname "master" -buildname "1" -pi "*integration.build*" -buildsessionidfile integrationBSID.txt
```
{% endcode %}
#### **Nodejs Agent**
{% tabs %}
{% tab title="Unix" %}
{% code overflow="wrap" lineNumbers="true" %}
```
./node_modules/.bin/slnodejs config --tokenfile /path/to/sltoken.txt --appname "IntegrationBuildName" --branch "master" --build "1"
mv buildSessionId integrationBSID.txt
```
{% endcode %}
{% endtab %}
{% tab title="Windows" %}
{% code overflow="wrap" lineNumbers="true" %}
```
call .\node_modules.bin\slnodejs config --tokenfile \path\to\sltoken.txt --appname "IntegrationBuildName" --branch "master" --build "1"
ren buildSessionId integrationBSID.txt
```
{% endcode %}
{% endtab %}
{% endtabs %}
{% hint style="info" %}
Please notice that for clarity, we have changed the default file name of the Build Session ID to `integrationBSID.txt` (instead of default `buildSessionId.txt` in Java or `buildSessionId` in slnodejs)
{% endhint %}
## Create a Components JSON File
Create a dependencies file using one of the formats available below. You can name this file `sl-integration-components.json` for example.
{% tabs %}
{% tab title="Using app/branch/build format for every component" %}
{% code overflow="wrap" lineNumbers="true" %}
```json
[
{
"appName": "sl-sample-backend",
"branch": "master",
"build": "1.0.1_233"
},
{
"appName": "sl-sample-frontend",
"branch": "master",
"build": "1.2.2_44"
}
]
```
{% endcode %}
{% endtab %}
{% tab title="Using buildSessionId format for every component" %}
{% code overflow="wrap" lineNumbers="true" %}
```json
[
{
"buildSessionId": "123456789"
},
{
"buildSessionId": "abcdefghi"
}
]
```
{% endcode %}
{% endtab %}
{% endtabs %}
{% hint style="warning" %}
The components listed in the dependencies file must be referring to builds already reported to Sealights (including the Build Scan step) using exact same appName/branchName/buildName parameters reported.
{% endhint %}
#### Adding comments to the JSON file with components' BSID only
The JSON file format does not currently support comments.\
In order to assist CI job troubleshooting, when reporting a large number of components using the BSID only method, an arbitrary field can be added which serves as a component name comment e.g.
{% code overflow="wrap" lineNumbers="true" %}
```json
[
{
"component_name": "sample-frontend",
"buildSessionId": "123456789"
},
{
"component_name": "sample-backend",
"buildSessionId": "abcdefghi"
}
]
```
{% endcode %}
{% hint style="info" %}
Note that the **keywords "appName", "branch" and "build" are reserved** and cannot be used as the additional field name.
{% endhint %}
## Report the Integration Build to the Dashboard via the Build Scanner
Run the build scanner referencing the dependencies file created in the previous step and that we have named `sl-integration-components.json`
#### **Java Agent**
{% code overflow="wrap" lineNumbers="true" %}
```
java -jar sl-build-scanner.jar -scan -tokenfile sltoken.txt -buildsessionidfile integrationBSID.txt -componentfile sl-integration-components.json
```
{% endcode %}
#### **Nodejs Agent**
{% tabs %}
{% tab title="Unix" %}
{% code overflow="wrap" lineNumbers="true" %}
```
./node_modules/.bin/slnodejs scan --tokenfile sltoken.txt --buildsessionidfile integrationBSID.txt --dependenciesFile sl-integration-components.json
```
{% endcode %}
{% endtab %}
{% tab title="Windows" %}
{% code overflow="wrap" lineNumbers="true" %}
```
call .\node_modules\.bin\slnodejs scan --tokenfile sltoken.txt --buildsessionidfile integrationBSID.txt --dependenciesFile sl-integration-components.json
```
{% endcode %}
{% endtab %}
{% endtabs %}
Once this has run, all components listed in the dependencies file will be added to the newly created integration build.
{% hint style="info" %}
Once the integration build has been created, it is possible to run cross-component integration tests, referencing the same session ID created in step #1.
{% endhint %}
---
# 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/build-and-test-execution/integration-build/integration-build-explicit-components-and-versions/component-file.md?ask=&goal=
```
`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.