Production Access Server

The Production Access Server (PAS) manages user requests and orchestrates the rest of modules.

It is implemented using Java Tomcat Application Server and requires a standard MySQL database to store the required data to fulfil the requests. The implementation is a fully scalable, production-ready setup capable of serving hundreds of requests per second.

The functionalities covered by the PAS are to:

• Manage the configuration of the whole solution: define the engines and

optional modules available, their state and location.

• Implement the interface (API) between client applications and engines and

modules.

• Manage the ecosystem communicating the different engines and modules;

for instance to chain engines when the user requested process implies that several engines will concatenate.

• Access Control with usernames, password and APIKeys

• Grants management rights, who can access what.

• Store statistics about usage and performance.

• Access external engines (Pangeanic SaaS) to extend the customer installed

engines.

Installed, it is also mandatory when one of the provided client applications is to be used (PGB, PGWeb, CAT tools or the generic API).

When running an on-premises setup the PAS is the only component that is exposed to the rest of the network but is also the most-centered element, with direct access to the rest of components of the system