> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup

> Learn how to set up and configure the PROSPER connector Windows service and connect to the PROSPER simulator.

## Before you start

<Steps>
  <Step title="Check the server requirements">
    Check the [server requirements](/cdf/integration/guides/simulators/connectors/prosper/prosper_server_requirements) for the connector.
  </Step>

  <Step title="Verify connector capabilities">
    Make sure the connector has [these capabilities](/cdf/access/guides/capabilities#simulator-connectors) in a Cognite Data Fusion (CDF) project.
  </Step>

  <Step title="Create configuration file">
    Create a configuration file according to the [configuration settings](/cdf/integration/guides/simulators/connectors/prosper/prosper_configuration) in the working directory of the folder where the connector is installed. The file must be in YAML format.
  </Step>
</Steps>

## Connect to PROSPER simulator

The connector uses COM to connect to the PETEX OpenServer protocol, which establishes the connection with the PROSPER simulator. In case of connection errors, it can retry. The retry parameters can be defined in the configuration file:

```yaml theme={"languages":{"custom":["/_languages/kuiper.json","../_languages/kuiper.json"]}}
 automation:
     simulator-retries:
         max-tries: 12
         max-delay: "60s"
```

This configuration enables retry attempts to the simulator for up to 5 minutes before failing. The retries follow an exponential backoff strategy, starting with shorter delays and gradually increasing to a maximum interval of one minute.

| Retry attempt | Delay duration before attempt        |
| ------------- | ------------------------------------ |
| 1             | ░░ (0.5s)                            |
| 2             | ░░░░ (1s)                            |
| 3             | ▓▓▓▓▓ (2s)                           |
| 4             | ██████ (4s)                          |
| 5             | ██████████ (8s)                      |
| 6             | ██████████████ (16s)                 |
| 7             | ██████████████████ (32s)             |
| 8             | ████████████████████████ (60s limit) |
| 9             | ████████████████████████ (60s limit) |
| 10            | ████████████████████████ (60s limit) |

## Run as a Windows service

<Steps>
  <Step title="Download the installer">
    Download the *prosper-setup-\{VERSION}.exe* file via the download links available from <span class="ui-element">Data fusion</span> > <span class="ui-element">Integrate</span> > **Extractors** in CDF.
  </Step>

  <Step title="Run the installer">
    Run the installer on a Windows operating system. A wizard guides you through the installation process.
  </Step>

  <Step title="Select installation folder">
    Select the destination folder where the connector will be installed. By default, this is **C:\Cognite\\**. Inside this folder, the **ProsperConnector** working directory is created. The connector expects a `config.yml` file as the configuration in the same directory.

    <Tip>
      You'll find templates for the configuration file in the `config` folder.
    </Tip>
  </Step>

  <Step title="Open Windows Services">
    Open the **Services** app in Windows and find the **Cognite PROSPER Connector** service.
  </Step>

  <Step title="Start the service">
    Right-click the service and select **Start**.
  </Step>
</Steps>

## Uninstall and update the connector

Run the same MSI installer to uninstall the connector. The installer deletes installed binaries, removes the service, and cleans the application registry. The installation is not deleted and still contains the configuration file, logs, and application data generated by the connector. If the connector is re-installed, it resumes the operation using the saved state.

When a new version of the PROSPER connector is available, run the MSI installer for the new version to upgrade the connector to the new version. After the upgrade, you must manually restart the service.