Spectrus JS: Overview and Architecture

Installation Overview

A typical Spectrus JS installation includes five servers, including the License Server. Understanding how these components interact can help you identify where a startup or login issue is occurring.

How Request Routing Works

Example request:

The request path determines which internal service handles the request.

Requests that begin with /auth/* are forwarded by the Spectrus JS Web Server to the Authentication Server.

Requests that begin with /api/* are forwarded by the Spectrus JS Web Server to the Processing Server.

Example: http://myserver.com/api/getmydata

All other requests are handled directly by the Web Server.

Startup and Login Sequence

1. Browser downloads Spectrus JS (SJS) application code and configuration files from the SJS Web Server
2. Browser requests configuration from Authentication server
3. According to configuration, the browser is redirected to Authentication application (login page)
4. After successful login, the browser is redirected back to SJS application along with user session information
5. The SJS application send requests to Processing Server, providing user session information, asking for user settings and list of datasets
6. The Processing Server contacts Authentication Server to confirm validity of user session and retrieve user information (username, etc)
7. The Processing Server contacts License Server to confirm the user has access to functionality
8. The Processing Server contacts the Database Server to retrieve requested info and sends it back to the browser
9. The browser displays home page