Share an Existing MashZone NextGen Repository

If you are creating a cluster using an existing MashZone NextGen Repository or simply adding members to an existing cluster, you simply update each new MashZone NextGen Server in the cluster to use the existing repository.

1. If the cluster does not have a shared JDBC driver folder and a shared external configuration folder:

a. Copy the JAR file for the JDBC driver for your database to the web-apps-home/presto/WEB-INF/lib folder for the new MashZone NextGen Server cluster member.

b. Copy the rdsJdbc.properties file from the web-apps/presto/WEB-INF/classes folder of an existing MashZone NextGen Server in the cluster, to the same folder for the new cluster member.

See Setting Up an External MashZone NextGen Configuration Folder for more information on shared configuration for clusters.

2. If the cluster does have a shared JDBC driver folder and a shared external configuration folder, update the application server’s classpath for the new cluster member to include all three folders.

Depending on your application server, you may update the classpath in the administration console, in configuration files or in the startup script for the application server. See documentation for your application server for more information.

For Tomcat on Windows, for example, you can edit the tomcat-install/bin/catalina.bat file and add the path to this folder to the classpath environmental variable to be something like this:

set "CLASSPATH=%CLASSPATH%;C:\PrestoConfig;C:\PrestoConfig\classes;C:\PrestoConfig\lib;C:\PrestoConfig\db\jdbc"

On Linux, Mac OS X or UNIX systems, you would update tomcat-install/bin/catalina.sh to something like this:

CLASSPATH="$CLASSPATH":/users/PrestoConfig:/users/PrestoConfig/classes:/users/PrestoConfig/lib:users/PrestoConfig/db/jdbc

3. Enable distributed caching for artifacts (required) and optionally distributed caching for mashable/mashup responses. See Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores for more information and instructions.

4. If the MashZone NextGen Repository is hosted in Microsoft SQL Server, MySQL or Oracle, change the repository JAR in the MashZone NextGen Server.

5. Restart the new MashZone NextGen Server for this cluster.