# ONEWEB Server Configuration

ONEWEB is designed as a **modular and flexible platform**, allowing organizations to deploy platform capabilities in different server configurations based on business requirements, scale, and usage patterns.

Rather than enforcing a single deployment layout, ONEWEB enables customers to **select and combine server roles** that best fit their application architecture. Each server configuration represents a logical responsibility within the overall ONEWEB Platform Architecture.

***

### Server‑Based Architecture Model

From an architectural perspective, ONEWEB server configurations can be grouped into:

* **Runtime servers**, which execute applications, processes, and integrations
* **Design‑time servers**, which support application design and lifecycle management
* **Build services**, which generate deployable artifacts for specific platforms

These server roles can be deployed independently, co‑located, or distributed across environments depending on architecture choices such as Standalone, High Availability, or Cloud Architecture.

***

### Available ONEWEB Server Roles

The following table summarizes the primary ONEWEB server configurations and their architectural responsibilities.

| Server Role                  | Primary Responsibility                  | Architectural Purpose                                                                 |
| ---------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------- |
| **Process Server**           | Business process and workflow execution | Executes e‑Forms, human workflows, task allocation, and end‑to‑end process automation |
| **Microflow Server**         | Integration and microservices runtime   | Executes integration logic, APIs, and backend microservices                           |
| **User Experience Server**   | Web and mobile application runtime      | Hosts modern web and mobile user interfaces and interaction logic                     |
| **Designer Suite Server**    | Design‑time and management platform     | Provides AppSpace, App Designer, Process Designer, and related utilities              |
| **Mobile CI Server (Cloud)** | Mobile application build service        | Builds and packages iOS and Android mobile applications in a cloud environment        |

> Each server role may be deployed as a standalone service, combined with other roles, or containerized depending on the chosen architecture.

***

### How Server Configuration Fits into ONEWEB Architecture

Within **Design ONEWEB Architecture**, server configuration defines **what platform capabilities are deployed**, while other architectural dimensions define:

* **Deployment Architecture** – where servers are hosted (Standalone, HA, Cloud)
* **Container Structure** – how servers are packaged and orchestrated
* **Environment Strategy** – how servers are separated across Testing, Production, and DR

This separation allows ONEWEB to scale horizontally, evolve over time, and adapt to different enterprise environments.

***

### Architectural Considerations

When designing server configuration, consider:

* Which platform capabilities are required (UI, Process, Integration, Design)
* Expected workload and concurrency
* Availability and scalability requirements
* Security and environment separation policies

Smaller environments may consolidate multiple server roles, while enterprise or mission‑critical systems typically distribute roles across multiple servers or containers.


---

# 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.onewebstack.com/getting-started/installation-guide/plan-your-oneweb-installation/design-oneweb-architecture/oneweb-server-configuration.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.