Application Servers

Application Server nodes are responsible for providing shared resource templates to primary nodes (so that they become replicated resources) and login servers (so that they become session resources) . Another function is execution of autonomous operations (i.e. operations that are not initiated by specific users via login servers) over various sets of primary nodes.

An application running in a horizontal cluster is, indeed, a set of resources created, debugged, tested and operated all together. An application is initially imported to an application server node from a Git repository or an Iotellect store.

Deployment of an application in a horizontal cluster starts with importing an application on an application server node. Once an app is imported, a Register Application action can be called on a cluster coordinator to create replicated resources on primary nodes based on resource templates of that particular app.

Hosting of replicated resource templates: Application servers then interact with the cluster coordinator and primary nodes in order to distribute replicated resources across the application tenants' realm. Replicated resources deployed on primary nodes are based on (and stay in sync with) resource templates stored on the application server.

Hosting and operation of session resources: Session resource are not distributed to primary nodes but rather directly mapped into a login server’s virtual context tree when a user logs in. These resources reside only on the application server and are mainly used for data visualization, as well as “broadcasting” requests to multiple primary nodes.

Was this page helpful?

Tell us more

Send

Thank you!