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:

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.
Environments (Engagement Services, Integration Service) 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 Temenos. You can also view reports if you are using metrics module. This is an optional component.

For more details, refer to Integration Service - App Services User Guide
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.

 

NOTE:  The Quantum Fabric components can be configured on one node or separate nodes - for example, you can use one of the following choices:
  • Install All Components on one node.
  • Install Quantum Fabric Console, Quantum Identity Service, and  Quantum Integration Service on separate nodes.

Temenos recommends using the Quantum Fabric Installer for deploying Quantum Fabric V9.0 onwards.
If you want to install Quantum Fabric manually due to your business rules and policies, please contact support@kony.com for approval and to obtain access to the Quantum Fabric manual install artifacts.
Manual installs not approved by Temenos will not be supported.

Close