Getting Started with the Sandbox Project

The Sandbox project is provided by ActiveViam to customers to demonstrate how the Atoti Server API is used to build a project.

Not all the options it showcases are suitable for every production environment. Design decisions regarding operating systems, network configuration, encryption, DBMS's, cloud providers, etc. should be made with care and according to the industry standards and guidelines.

Embedded Servers versus Standalone Servers

The Sandbox project demonstrates two different setups :

• The "embedded servers" illustrates the deployment where all applications (Content service, Atoti Server, Atoti UI and optionally ActiveMonitor) are hosted on the same server. This configuration can be used in the following cases:

  - trying out features of the applications,
  - testing the implementation of a business project during the development phase

• The "standalone servers" illustrates the deployment where several servers are created and communicate. This configuration is generally used in Production phase of the project. The created servers in this configuration are:

  - an ActiveMonitor server,
  - a ContentServer with an embedded Atoti UI,
  - an Atoti server.

Project Organization

sandboxes
|
|----- activepivot
|----- common
|----- contentservice

Folder	Contents
sandboxes	Root folder of the sandbox project
activepivot	For a standalone Atoti application, or embedded servers, depending on the chosen profile
common	Common configuration classes for all the sandbox project
contentservice	For a standalone Content Server shipping a vanilla Atoti UI application

First Build and Launch

Running mvn clean install -DskipTests on the sandboxes folder will build the sandbox.

To launch Atoti, you can run the com.activeviam.sandbox.server.ActivePivotServer class directly from your IDE. A sample application is now running and can be interacted with using Atoti UI or an XMLA-enabled front end (for example Excel or Tableau).

To find out how to configure and use the sandbox, please read the README.md files at the root of each module of the sandbox.