MashZone NextGen 10.2 | Appendix | Administration | MashZone NextGen Server Administration | Deploying MashZone NextGen Instances, Clusters or Artifacts | Deploying the Core Components
 
Deploying the Core Components
The core components include the MashZone NextGen Server, MashZone NextGen Hub and AppDepot (web-apps-home/presto), the MashZone NextGen Repository, which is typically installed in a database other than the default Derby database, and the MashZone NextGen Analytics In-Memory Stores and MashZone NextGen caches.
Note: In earlier releases, the MashZone NextGen Hub and AppDepot were deployed in a separate web application from the MashZone NextGen web application. Effective in 3.2, all the core components are deployed in the single web-apps-home/presto web application.
For individual MashZone NextGen servers, you typically do a default installation (see Installing Software AG Products). You may also move the MashZone NextGen Repository to a database of your choice. See Move the MashZone NextGen repository to a robust database solution for instructions.
You can leave the the MashZone NextGen Analytics In-Memory Stores and MashZone NextGen caches in local memory for a single MashZone NextGen 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 MashZone NextGen Analytics In-Memory Stores for more information and links.
To deploy multiple unclustered servers, see Deploying Multiple MashZone NextGen Servers in One Host. To deploy MashZone NextGen servers in clusters, see Clustering MashZone NextGen Servers for requirements and links.
Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release