> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/4.0/administrator-guide/architecture-fundamentals.md).

# Architecture Fundamentals

Flopsar consists of three main components:

* Agent
* Server
* Workstation 

![Architecture](/files/-MUT51AaJkuylkA4Etpf)

The agent is a jar file that is installed on JVM running the user application. Every agent belongs to some application. The agent is attached to the JVM and produces data. The data are sent to the server, which collects and serves the data to the workstation clients. 

## Networking

There are two TCP servers exposed by the server. The default ports used by the servers are:

* **9000** - this server handles all the connections from agents.
* **9443** - this server handles connections from the workstation clients. The connections to this server are encrypted.

{% hint style="warning" %}
If you change the ports, make sure your clients connect to their corresponding servers otherwise, the environment will not work.
{% endhint %}

In this networking architecture the following connections must be allowed:

* outgoing connections from agents to the server,
* outgoing connections from workstations to the server.

##


---

# 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://docs.flopsar.com/4.0/administrator-guide/architecture-fundamentals.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.