> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/get-started/faq/add-license-1.md).

# Adding a License to WebViewer Server

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

## Adding a license when using Docker Compose

The Apryse key you were provided is passed to WebViewer Server through environment variables in docker. In your `docker-compose.yml` file you can do this by placing the key in the `TRN_PDFNET_KEY` variable under environment:

<pre class="language-yaml" data-line-numbers><code class="lang-yaml">pdfd-tomcat:
    image: "pdftron/webviewer-server:latest"
    environment:
      TRN_PDFNET_KEY: '<code class="expression">visitor.claims.wvKey || "YOUR_LICENSE_KEY"</code>'
</code></pre>

## Adding a license when using Docker directly

When using Docker directly through other systems or command line you would declare `TRN_PDFNET_KEY` as an `-e` (environment) argument.

<pre class="language-bash" data-line-numbers><code class="lang-bash">docker run -p 8090:8090 -e TRN_PDFNET_KEY="<code class="expression">visitor.claims.wvKey || "YOUR_LICENSE_KEY"</code>" pdftron/webviewer-server:latest
</code></pre>

## Adding a license when using the Windows installer

If you installed WebViewer Server through our Windows installer you can add the key by modifying `wvs_config.json` - you will find this under your program data directory `ProgramData/Apryse/wvs_config.json`

<pre class="language-json" data-line-numbers><code class="lang-json">"TRN_PDFNET_KEY":"<code class="expression">visitor.claims.wvKey || "YOUR_LICENSE_KEY"</code>"
</code></pre>


---

# 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.apryse.com/web/get-started/faq/add-license-1.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.