> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-bolt-database.md).

# Install Cortex XSOAR with Bolt Database

{% hint style="info" %}

### Note

* If you deploy a signed installer, import the public key to the operating system. The public key is valid for six months.
* If you are installing on an Oracle Linux operating system, you need to manually [Install Docker](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/docker/docker-installation.md).
  {% endhint %}

**Installation File Structure**

The following is the file and folder structure in a standard Cortex XSOAR installation.

By default, Cortex XSOAR is installed in the `/root` folder, but you can [Move Data Folders to Another Location on the Server](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/manage-data/move-data-folders-to-another-location-on-the-server.md), if necessary.

| Asset         | Path                                                                               |
| ------------- | ---------------------------------------------------------------------------------- |
| Binaries      | **`/usr/local/demisto`**                                                           |
| Data          | **`/var/lib/demisto`**                                                             |
| Logs          | **`/var/log/demisto`**                                                             |
| Configuration | **`/etc/demisto.conf`** (not created if defaults are selected during installation) |
| Reports       | **`/tmp/demisto_install.log`**                                                     |
| Install Log   | **`/tmp/demisto_install.log`**                                                     |

If you want to create different mounts for the **`/var/lib/demisto`**, **`/var/lib/docker`**, and **`/tmp`** partitions, it is recommended to allocate the following space to each partition (dependent on the expected amount of data, and the size of your incidents and indicators).

* **`/var/lib/demisto`**: 200 GB (development) 1000 GB (production)

  If using Elasticsearch, see [Elasticsearch System Requirements](/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/system-requirements/elasticsearch-system-requirements.md).
* If using Docker - **`/var/lib/docker`**: 70 GB (development) 150 GB (production)
* If using Podman - **`/home`**: 70 GB (development) 150 GB (production)
* **`/tmp`**: 10 GB (development and production)

**Prerequisites**

Verify the following information and requirements before you install Cortex XSOAR.

* Your installation meets the [system requirements](/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/system-requirements/cortex-xsoar-system-requirements.md).
* You have root access.

How to install Cortex XSOAR with Bolt Database

1. Log in to [Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts).
2. In the **Available for Activation** section, use the serial number to locate the tenant to download.

   By default, the **Production-Standalone** license is selected. You can also select **Dev**.

   If you want to use a production and a development tenant with a private remote repository, select **Dev**. If you don't select it now, you can install a development tenant later.
3. Select **Download On Prem**.
4. Click **Next**.
5. Under **Choose Download Option**, select **Installer**.
6. Select the checkbox to agree to the terms and conditions of the license and click **Download**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Tip</h3><p>In Google Chrome, to download the image and license files together, you may need to set the browser <strong>Settings</strong> → <strong>Privacy and security</strong> → <strong>Site settings</strong> → <strong>Additional permissions</strong> → <strong>Automatic downloads</strong> to the default behavior <strong>Sites can ask to automatically download multiple files</strong>.</p></div>

   Two files download: the `demistoserver-xxxxx.sh` installer file and a zipped JSON license file.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>You can copy the download link button from the Downloads section in your browser to get the token needed for offline installation.</p></div>
7. (Optional) If you are deploying Cortex XSOAR using a signed installer (GPG), you need to import the GPG public key that was provided with the signed installer.

   For example, you can use the **`rpm --import public.key`** command to import the public key into the local GPG keyring. Note that each operating system has specific requirements.
8. (Optional) If you are deploying Cortex XSOAR using a signed installer (GPG) you might need to manually install the `makeself` package by running the **`yum install makeself`** command.
9. Run the **`chmod +x demisto.sh`** command to convert the **`.sh`** file to an executable file.
10. Execute the **`.sh`** file, by running the following command.

    **`sudo ./demisto.sh`**

    Add [Installer Flags](/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-bolt-database/installer-flags.md) as required.
11. Accept the EULA and add the information when prompted.
    1. The Server HTTPS port (default is 443)
    2. Type **`No`** when asked if you are connecting to an Elasticsearch database.
    3. Type the name of the Admin user (default is admin).
    4. Type the password (default is admin).
12. (Optional) After the installation has completed, do the following:
    1. Confirm that the Cortex XSOAR server status is active, by running the **`systemctl status demisto`** command.

       If the server is not active, run the **`systemctl start demisto`** command to start the server.
    2. Confirm that the Docker service status is active, by running the **`systemctl status docker`** command.
    3. In a web browser, go to the **`https://serverURL:port`** to verify that Cortex XSOAR was successfully installed.

       When you open Cortex XSOAR for the first time, you need to add the license.

### Troubleshooting

In some cases, due to moving previous installation files, the installation can fail and the following error message is displayed:

```screen
mv: cannot stat '/var/lib/dpkg/info/demistoserver.postrm': No such file or directory
Failed to execute: 'mv': exit status 1
            
```

There are two options to resolve this issue:

* Make a note of the path to the **`demistoserver.postrm`** file. Rerun the installation using this path for the -- **`-prev-uninstall-script`** flag. Example: **`-- -prev-uninstall-script="/path/to/demistoserver.postrm"`**
* Rerun the installation with the flag **`-- -use-prev-uninstall-script=true`**. Note that if you use this flag and have previously created a special ID & group for demisto users, the demisto user and group are deleted and recreated during installation.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-bolt-database.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.
