Presto Administration : Presto Server Administration : Deploying Presto Instances, Clusters or Artifacts : Sharing the Presto Repository in Clustered Environments : Create and Share a New Presto Repository
Create and Share a New Presto Repository
To create a new shared repository
1. Create a new Presto Repository in the appropriate database for your environment.
Using the SQL tool for the database that will be host, add Presto Repository tables with the scripts shown below from the corresponding folder in presto-install/prestorepository:
Database
Folder
SQL Scripts
Microsoft SQL Server
mssqldb
*createDBTables.txt for MetaData and the default User Repository
*createSnapsTables.txt for Snapshots
*createSchedulerTables.txt for Scheduler
MySQL
mysqldb
Oracle
oracledb
PostgreSQL
postgresdb
There are also scripts to drop the corresponding Presto Repository tables in these folders, if needed.
2. Copy the JAR file for the JDBC driver for your database to the presto-config folder for JAR files.
If you are using a shared external configuration folder, you can copy the JAR to that single folder. For example, you might copy this to G:\PrestoConfig\lib on a Windows system or /mountA/home/PrestoConfig/lib on Linux, Mac OS X or UNIX systems.
If you are not sharing a configuration folder across the cluster, you must copy the JAR to web-apps-home/presto/WEB-INF/lib for each Presto Server that uses this Presto Repository. See Setting Up an External Presto Configuration Folder for more information.
3. If this is a new cluster, update configuration information for the MetaData, User and Snapshot repositories for one Presto Server in the cluster. See steps 3 onward in Move the Presto and MashZone Repositories to a Robust Database Solution for instructions.
4. Copy the rdsJdbc.properties file to the presto-config folder for the entire cluster or to each Presto Server in the cluster.
If you are using a shared external Presto configuration folder, both of these files are already in the list of property files that you place in this folder. See Setting Up an External Presto Configuration Folder for more information.
5. Enable distributed caching for artifacts (required) and optionally distributed caching for mashable/mashup responses. See Configure BigMemory Servers for Presto Caching and In-Memory Stores for more information and instructions.
6. If the Presto Repository is hosted in Microsoft SQL Server, MySQL or Oracle, change the repository JAR in the Presto Server. See Upgrade the Presto 3.5 Repository JAR for MSSQL, MySQL or Oracle for instructions.
7. Restart each Presto Server in the cluster.
Copyright © 2013-2015 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback