> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/installation-and-configuration/understanding-the-console-deployment-structure.md).

# Understanding the Console Deployment Structure

Since <code class="expression">space.vars.X\_Product\_Name</code> has the ability to dynamically apply software updates without requiring a restart of the application server, and with different users using different versions of the same application; there are some unusual considerations with regards to the console’s deployment structure.

Firstly, the web application installed under the application server path is purely an application loader. The application loader in turn finds all of the required files and executable code under a folder designated as the file location in the **web.xml** file for the console application.

The file location referenced is typically under the <code class="expression">space.vars.X\_Product\_Name</code> console home folder in an **Applications** sub-folder. Below that folder in turn, you can find multiple builds *(as they are installed by the update server)*. Those builds largely conform to a typical web application structure.


---

# 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.tomorrowx.com/cap/product-reference/installation-and-configuration/understanding-the-console-deployment-structure.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.