Deploying the Core Components
The core components include the Presto Server, Presto Hub and AppDepot (web-apps-home/presto), the Presto Repository, which is typically installed in a database other than the default Derby database, and the Presto Analytics In-Memory Stores and Presto caches.
Note: | In earlier releases, the Presto Hub and AppDepot were deployed in a separate web application from the Presto web application. Effective in 3.2, all the core components are deployed in the single web-apps-home/presto web application. |
For individual
Presto servers, you typically do a default installation (see
Installing Software AG Products). You may also move the
Presto Repository to a database of your choice. See
Move the
Presto
and
MashZone
Repositories to a Robust Database Solution for instructions.
You can leave the the
Presto Analytics In-Memory Stores and
Presto caches in local memory for a single
Presto server. This uses the default client installation of
BigMemory. If additional memory or reliability is required, you can also deploy
BigMemory as an add-on in a separate host or cluster.
See Working with
Presto Analytics In-Memory Stores for more information and links.To deploy multiple unclustered servers, see
Deploying Multiple
Presto Servers
in One Host. To deploy
Presto servers in clusters, see
Clustering
Presto Servers for requirements and links.
Contact Support
|
Community
|
Feedback