Quantum Fabric Topology and Components

Quantum Fabric topology explains the logical arrangement of various components, such as, console, identity services, developer environment, and production environment.

In design time you configure apps with services, and publish them to a developer environment. After you confirm the changes in the apps, these apps will need to be published to a production environment. Authorized users can access apps on mobile devices from a production environment.

An overview of the Quantum Fabric architecture and components follows:

A typical Quantum Fabric topology:

An overview of the Quantum Fabric deployment architecture:

The following table describes the components of Quantum Fabric:

Convention	Description
Identity	This component validates user accounts and applications for authentication and authorization. Authentication identifies log-on credentials of a user. Authorization allows or denies access to resources based on a user's role. Identity is used to authenticate and authorize runtime and design-time users.
Accounts	The accounts component contains information about what a user can do, such as create other users, delete users, create environments, delete environments, and publish apps to an environment. This component uses auth service for authorizing requests based on user roles.
Workspace (WaaS)	Workspace configures MBaaS services (applications, identity, integration, orchestration, and engagement services). After these services are configured, these services must be published to respective clouds/environments so that the services are available for run-time use.
Console/Portal	The console/portal is the user interface for configuring services for an application.
API Developer Portal	Quantum Fabric Developer Portal feature lets you create a Portal for exposing APIs created using Quantum Fabric. Developers from internal and external partner teams can access the portal created to explore and test the APIs You can directly access your Quantum Developer Portal in Quantum Fabric Console.
Environments (Engagement Services, Integration Services)	This component adds runtime capabilities to apps, such as engagement services, and integration services.
Admin	Admin provides the capability to list down the set of services published and test the services shown in Admin Console. Also you can view list of published apps and provides the delete apps functionality. In Quantum Cloud, changing the log levels and checking the logs features are available as the cloud is managed by Quantum. You can also view reports if you are using metrics module. This is an optional component. For more details, refer to https://docs.kony.com/konylibrary/integration/kmf_integrationservice_admin_console_userguide/Default.htm
Middleware	This component exists between a mobile device and an endpoint server. It receives a request from a mobile device, sends it to an endpoint server, fetches the response from the backend and provides the required information to the device in the JSON format. IMPORTANT: For more information on Quantum Middleware layers and how it works, refer to Middleware Pipeline Overview.
Services	Services component is used only when Quantum Fabric is integrated. It has same runtime capabilities as the middleware. NOTE:  To use Quantum Server with Quantum Fabric integrated, you can ignore the middleware.war. Similarly when you use only standalone Quantum Server, you can ignore the services.war.

For frequently asked questions and troubleshooting, refer to FAQs and Troubleshooting.

Developer Environment

For development environment, a developer can preferably install Quantum Fabric components in a standalone mode (single node) on a local environment. For more details, refer to Single Node Installation.

Production Environment

For production environment, domain mode (multi-node) installation with HTTPs protocol is preferred. Multi-node installation helps to enable better performance, high availability, and load balancing. For more details, refer to Multinode Installation.