> For the complete documentation index, see [llms.txt](https://help.connected.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.connected.illumina.com/dragen-stratamap/dragen-spatial-transcriptome/getting-started/dragen-app-manager-local/prerequisites.md).

# Prerequisites

### System & Software Requirements

* DRAGEN v4 Server is fully operational and network-connected.
* DRAGEN software v4.4.4 or later.
  * If using v4.4.4, the Spatial License must be installed manually.
    * `sudo dragen_lic -i auto -f Spatial`
  * If using v4.5+, the Spatial License is included automatically.
* DRAGEN Spatial License
  * License includes the "Spatial Transcriptome" feature.
  * License is not expired.
  * To verify your license, run either one of the following commands:

    ```bash
    sudo dragen_lic -j
    or
    sudo dragen_lic status
    ```

    Look for the "Spatial" section with "Active" status.
* Docker 26 or later.
* Oracle Linux 8 operating system image.
  * If needed, upgrade instructions (CentOS 7 → OL8) are available on MyIllumina.
* DRAGEN Application Manager v1.1.7 successfully installed on the DRAGEN server.
  * The run script for the application manager is provided within the installation package.
  * On the first installation of the local application, the installer will detect whether DRAGEN Application Manager is installed. If it is missing or outdated, it will prompt you to install the required version using the provided DRAGEN Application Manager run script.
    * Refer to "Step 2: Install the Application" found on the[ Installation Page](/dragen-stratamap/dragen-spatial-transcriptome/getting-started/dragen-app-manager-local/installation.md#step-2-install-the-application) for more information

### Permissions

* `sudo` permissions are required to install the software.
* Elevated permissions are recommended to avoid read/write issues during analysis.

### Input & Output Data Access

* You must have a method to transfer input and output files to and from the DRAGEN server.
  * Examples include a mounted network share or a USB drive.
    * Inputs to the pipeline must reside locally on the server.
    * Outputs from the pipeline should also be written locally to prevent transfer issues caused by network connection disruptions.
    * Instructions for configuring file transfers are not provided here. Work with your internal IT team to set this up prior to installation.

{% hint style="warning" %}
Docker does not allow inputs from a mounted network share. Copy all analysis inputs to the server prior to pipeline execution.
{% endhint %}

### Storage & Performance Requirements

* Ensure sufficient storage and memory are available to run a single analysis.
  * It is recommended to keep only one set of input and output files on the server at a given time.
    * Maintain efficient and careful data transfer and removal practices to ensure smooth performance.
  * **Input and output data should not be stored on the DRAGEN server long-term.**


---

# 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://help.connected.illumina.com/dragen-stratamap/dragen-spatial-transcriptome/getting-started/dragen-app-manager-local/prerequisites.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.