# Server Installation

A prerequisite for working with the Composable Agentic Platform <code class="expression">space.vars.X\_Agent\_Name\_Single</code> is an instance of a Composable Agentic Platform console server.

To perform the installation, un-zip the Composable Agentic Platform Server distribution somewhere within the local file system and start it using the Tomorrow\.bat file *(or the Tomorrow\.sh file if using Linux, Solaris, or the Tomorrow\.command file if using macOS).*

The installation uses the open source Jetty application server. If you need to change ports or use of SSL, you can configure the application server using the `http.ini` configuration file found in the subfolder **server/start.d/**.

Please note that the server installation does not lay down a proper database. We strongly recommend that you use a production level database such as DB2, Oracle or MySQL.

Now open a browser and point it to <http://localhost/console>.

<figure><img src="/files/R3ihV2m1wwHF3fWrjyMe" alt=""><figcaption><p>Login interface</p></figcaption></figure>

You will see the main page and the console is ready to use. However, we suggest that you first review and complete additional configuration by following the steps in the relevant sections below, and also refer to the earlier section “Getting Started”.

## Installing as a Windows Service

### Composable Agentic Platform Console service wrapper

The CAP Console can be installed as a Microsoft Windows service. This provides a convenient way to manage the Console as part of standard Windows administration (auto-start on boot, automatic restart on failure, management via `services.msc`).

The wrapper used is [**WinSW**](https://github.com/winsw/winsw) (Windows Service Wrapper, MIT licensed). It is shipped in the `WinService` subdirectory of the distribution and requires no additional download or installation.

**Prerequisites**

* Windows 10 / Windows Server 2016 or later (.NET Framework 4.6.1+ is pre-installed on these versions).
* A **Command Prompt running as Administrator** — installing or removing a Windows service requires admin rights.

**Install the Console service**

```powershell
cd <distribution-root>\WinService
install-console.bat
```

This registers the service `CAPConsole`, configures it to start automatically on boot, and starts it immediately. Behind the scenes the service runs the existing `Tomorrow.bat` launcher in the distribution root, so all JVM arguments and Jetty configuration stay in one place.

The service will appear in `services.msc` as **CAP Console**.

**Stop, start, restart**

Use standard Windows commands from any administrator command prompt:

```powershell
net stop  CAPConsole
net start CAPConsole
```

**Uninstall the Console service**

```powershell
cd <distribution-root>\WinService
uninstall-console.bat
```

Further WinSW documentation is available at <https://github.com/winsw/winsw>.

### CAP Multi-Protocol Agent (PDA) service wrapper

Multi-Protocol agents (and other Programmable Data Agents) live in subdirectories of the distribution root, each containing its own `tomorrow.bat` launcher. The default agent subdirectory is `Multi-Protocol`; load testing uses `Stress`.

To install a PDA as a Windows service, take note of the agent subdirectory name (e.g. `Multi-Protocol`) and run:

```powershell
cd <distribution-root>\WinService
install-agent.bat Multi-Protocol
```

For example:

```powershell
C:\Users\Administrator>cd \
C:\>cd CAP-Console-12.0
C:\CAP-Console-12.0>cd WinService
C:\CAP-Console-12.0\WinService>install-agent.bat Multi-Protocol
CAP Agent service installed and started.
  Service name: CAPAgent_Multi-Protocol
  Manage with:  services.msc
```

The service appears in `services.msc` as **CAP Agent - Multi-Protocol**. Repeat for additional agents (e.g. `install-agent.bat Stress`).

Uninstall the PDA service with:

```powershell
uninstall-agent.bat Multi-Protocol
```

For full details on the WinService folder layout, log file locations, antivirus considerations, and troubleshooting, see `WinService\README.md` in your CAP Console distribution.

## Installing as a Linux Service

Please refer to the full Linux setup instructions found in the section [**Creating a stand-alone built in forwarding proxy**](/cap/product-reference/creating-a-stand-alone-built-in-forwarding-proxy.md) or [**Installing on Red Hat Enterprise Linux**](/cap/product-reference/installation-and-configuration/installing-on-red-hat-enterprise-linux.md).


---

# Agent Instructions: 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:

```
GET https://docs.tomorrowx.com/cap/product-reference/installation-and-configuration/server-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.