Integrate Software AG Products Using Digital Event Services : MashZone NextGen Help : Appendix : Administration : MashZone NextGen Server Administration : Deploying MashZone NextGen Instances, Clusters or Artifacts : Sharing the MashZone NextGen Repository in Clustered Environments : Share an Existing MashZone NextGen Repository
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 MashZoneNG-install/apache-tomcat/lib folder for the new MashZone NextGen Server cluster member.
b. Copy the rdsJdbc.properties file from the web-apps/mashzone/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. 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.
3. If the MashZone NextGen Repository is hosted in Microsoft SQL Server, MySQL or Oracle, change the repository JAR in the MashZone NextGen Server.
4. Restart the new MashZone NextGen Server for this cluster.
Copyright © 2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback