Server Components/Processes

Question 1

Gateway

Answer 1

Entry point for publishing and consuming a viz

Serves as a load balancer, routes requests to other components

Question 2

Application Server (Vizportal.exe)

Answer 2

Main interface for Server: Renders anything that’s not the viz

Login frame

Authentication –> goes to repository

Queries repository to see if user exists.

If Server is configured for AD, the App Server pings AD to make sure user exists inside AD.

Question 3

Repository

Answer 3

Stores metadata (user, groups, permissions, etc)

Content Brain of Server

1 active, 1 passive

Contains workbooks and associated files

Question 4

VizQL Server

Answer 4

Renders the and loads viz

Same functionality and user experience as VizQL in Desktop, but completely different context

Question 5

Data Server

Answer 5

Management of data sources (not actual data)

Tells system where to go to get the data

Central management of data connections and drivers

If Extract –> Data Engine

If Live –> Goes to data drivers

Published data sources

Question 6

Data Engine

Answer 6

Queries extracts (works with file store)

Multi-threaded

Active/Active: multiple concurrences

Question 7

File Store

Answer 7

Stores extracts

Question 8

Backgrounder

Answer 8

Handles tasks (extract refreshes, subscriptions, etc)

Communicates directly with data sources and Data engine

Single-threaded, so only does one extract at a time. To fix this, set up multiple backgrounders or set up different refresh times.

Question 9

Cache Server

Answer 9

Replicates returned results of a query (only data needed for view)

Uses Redis to synchronize duplicate services across nodes

Question 10

License Server

Answer 10

Checks internally (trusted Storage) to make sure users are still licensed

Question 11

Search and Browse

Answer 11

Powers all search and browse functionality (searching for workbooks/scrolling through workbook)

Question 12

Cluster Controller

Answer 12

Status Brain of system (health of system)

Decides when to fail over

Launches Repository process and coordinates active and passive repository

Tracks the current status of your distributed environment (actively used processes and their relationship to one another, across the cluster)

On all nodes

Question 13

Black Box Install

Answer 13

When your to download all of the components in one click. So when you put server on your local machine, it all comes in one executable file. Our competitors normally make you download each component of the server separately.

Question 14

Scalability

Answer 14

The ability of a machine to support multiple simultaneous actions, not just making one single action faster

Question 15

Availability

Answer 15

The ability to be resistant to component failures by increasing the availability of a solution (multiple machines)

Question 16

Scale Up

Answer 16

Adding more resources (RAM, CPU, etc.) to a single machine

Question 17

Scale Out

Answer 17

Adding more machines to a cluster

Question 18

Multi-process

Answer 18

Adding more throughput by running multiple instances of a process or service. These can be on a single server or can be distributed across multiple servers

Question 19

Multi-threaded

Answer 19

Within a process, being able to preform multiple tasks simultaneously across multiple CPUs

Question 20

Active/Active

Answer 20

When all instances of a multi-process service will process requests

Question 21

Active/Passive

Answer 21

When all instances of a multi-process service will process requests and other are only activated in the event of a component failure