> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/getting-started/requirements.md).

# Requirements

These requirements are for all operating systems.

* [Software/Hardware requirements](#software-hardware-requirements)
* [Network requirements/domain name](#networking-requirements)
* [Security](https://docs.infotopics.com/getting-started/requirements/security.md)
* [Database credentials](#database-credentials)
* [SSL Certificate](#ssl-certificates)
* [License](#license-requirement)
* [Installation files](#installation-files)
* [Database drivers](#database-drivers-and-odbc)

Each operating system can have different requirements:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Windows requirements</td><td><a href="https://docs.infotopics.com/getting-started/requirements/windows.md">Windows</a></td></tr><tr><td>Linux requirements</td><td><a href="https://docs.infotopics.com/getting-started/requirements/linux.md">Linux</a></td></tr></tbody></table>

### **Software/Hardware requirements**

WriteBackExtreme ships with everything it needs to run, including its own web server and its own PHP runtime. You do not install PHP, a web server or a database engine yourself.

* Minimum system requirements:
  * 4 (v)CPU, processing power
  * 8Gb RAM
  * 50Gb application disk space
  * 100Mbps or 1Gbps network-interface
* 64-bit **x86\_64/AMD64** only. ARM is not supported on any platform.
* Temporary internet access while installing, so the installer can fetch any missing system component.

### Network requirements

Firewall rules allow access to the port where the application will run. This applies to both internal and external networks, as well as server firewalls.

Ensure a valid web domain is available for the WritebackExtreme application to serve and distribute its content. When selecting a domain, it's important to consider how the application will be made available:

* Only within the internal/company network. This could be the machine/server name. The network DNS server will handle the request internally.
* Customers/users can use the WritebackExtreme application outside of the network. A web domain, for example, `<https://extension.company.com>` (create a DNS entry) which points to the host of WriteBackExtreme.
* Ensure the server is accessible solely via a VPN or within the company's internal network.
* Read the security page and make sure you are compliant: [here](https://docs.infotopics.com/getting-started/requirements/security.md)

When using a network/internal domain, the traffic of WritebackExtreme is available exclusively within the network (e.g., via VPN). Users outside the network cannot access the WritebackExtreme application.

### **Repository database r**equirements

WriteBackExtreme requires a repository database to store its internal data. This is **not** the same as the [database](https://docs.infotopics.com/prologue/architecture/supported-databases.md) you write back to from Tableau.

You can use any of the supported databases below as your repository database. If you don’t have access to MySQL, PostgreSQL, or SQL Server, you can use the built-in SQLite option.

**Supported repository databases**

| Database   | Supported versions         | Notes                                                                                                                                    |
| ---------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| SQL Server | 2016 or later              | Connects through ODBC Driver 18 for SQL Server. A SQL Server account is required; Windows-authenticated (AD) accounts are not supported. |
| MySQL      | 5.7, 8.0 or later          |                                                                                                                                          |
| PostgreSQL | Current supported releases | No minimum version is enforced.                                                                                                          |
| SQLite     | Built in                   | Local flat-file database. Fine for a trial or a test install, not for production.                                                        |

{% hint style="warning" %}
The repository database engine cannot be changed after setup. Pick the engine you want to keep before you run the wizard.
{% endhint %}

### **SSL Certificates**

SSL certificates are **required** if the system **is not behind a proxy/load-balancer**. When the system is behind a load balancer, the SSL certificate needs to be configured in the Load balancer.

We support the following SSL certificates:

* Using a `.key` and `.cer` certificate via the public keys method. (The key needs to be unencrypted!)
* Using a `.pfx` Windows-style certificate.

{% hint style="info" %}
Please note that Tableau requires extensions to be running on HTTPS/SSL connection and therefore required!
{% endhint %}

### **License requirement**

A valid License for WritebackExtreme. The license can be found in our [portal](https://my-appsfortableau.infotopics.com/login).

### **Installation files**

One-Click Executable files for easy installation. These files can be downloaded via our [portal](https://my-appsfortableau.infotopics.com/login).

### Database drivers

To use a database that connects through ODBC — Snowflake, Databricks, Teradata or IBM DB2 — you install and configure the driver yourself on the machine that runs WriteBackExtreme, using ODBC Data Source Administrator on Windows or `/etc/odbc.ini` and `/etc/odbcinst.ini` on Linux. See the page for your database under [Database connections](https://docs.infotopics.com/features/database-connections.md).

The Docker image already includes the ODBC drivers for Snowflake, Databricks and SQL Server. Drivers for Teradata and IBM DB2 are not included, so those need a custom image.

<table data-card-size="large" data-view="cards" data-full-width="true"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Next</strong></td><td>Getting started</td><td><a href="https://docs.infotopics.com/getting-started/getting-started.md">Install WriteBackExtreme</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/getting-started/requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
