# Server Configuration #### Overview **ONEWEB Server Configuration** defines how platform capabilities are deployed and combined based on customer requirements. Rather than forcing a single fixed setup, ONEWEB allows organizations to select and deploy specific platform services that best align with their business use cases and scale. Each server configuration represents a logical grouping of runtime or design‑time capabilities within the ONEWEB Platform. These configurations can be deployed independently or together as part of a broader platform architecture. *** #### Modular Server‑Based Architecture ONEWEB follows a **modular server architecture**, where each server focuses on a specific responsibility, such as user experience delivery, process execution, system integration, or application design. This modular approach enables: * Flexible deployment across environments * Independent scaling of platform capabilities * Clear separation of concerns * Easier alignment with business and operational needs *** #### Available Server Configurations The following table outlines the primary server configurations supported by the ONEWEB Platform. | # | Server Configuration | Primary Purpose | Architectural Role | | - | ---------------------------- | --------------------------------------- | -------------------------------------------------------------------------- | | 1 | **Process Server** | Business process and workflow execution | Executes human workflows, task orchestration, and process automation logic | | 2 | **Microflow Server** | System integration and microservices | Executes integration flows, APIs, and backend service orchestration | | 3 | **User Experience Server** | Web and mobile application runtime | Hosts user‑facing applications, pages, and interaction logic | | 4 | **Designer Suite Server** | Application design and management | Provides AppSpace, Designer Studios, and development utilities | | 5 | **Mobile CI Server (Cloud)** | Mobile application build services | Builds and packages iOS and Android applications in a cloud environment | *** #### How Server Configurations Fit into Platform Architecture From a platform architecture perspective: * **Runtime‑focused servers** (Process, Microflow, UX) are responsible for executing applications and logic * **Design‑time servers** (Designer Suite) support application creation and lifecycle management * **Build services** (Mobile CI) enable automated generation of deployable mobile artifacts These server configurations can be deployed: * On a single node for simpler environments * Across multiple nodes for high availability * As containerized services in cloud environments This flexibility allows ONEWEB to adapt to different architectural patterns such as Standalone, High Availability, and Cloud Architectures. *** #### Relationship to Other Architecture Layers Within the overall **Platform Architecture**: * **Deployment Architecture** defines *where* servers run * **Container Architecture** defines *how* servers are packaged and orchestrated * **Server Configuration** defines *what platform capabilities are deployed* Together, these layers provide a complete and composable architecture model. --- # 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/overview/platform-architecture/server-configuration.md?ask= ``` 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.