Add an External Dynamic In-Memory Store Connection

Procedure

  1. Verify that the Terracotta Management Console (TMC) that manages the Big Memory Server hosting this dynamic store is running and that the store exists.
  2. You should also verify that the dynamic store meets minimum requirements for MashZone NextGen.
  3. Copy the JAR file containing the classes used as search attributes to extract data from the dataset in this store to <MashZone NextGen-installation/lib.

    See documentation for the external system that created this dynamic store to determine what JAR files are needed. For Apama, see documentation on the MemoryStore.

    The default location for the target folder in MashZone NextGen is <MashZone NextGen-installation>/apache-tomcat/mashzone/WEB-INF/lib. If MashZone NextGen is deployed in a cluster, however, this location may be a separate external folder. For more information, see Setting Up an External MashZone NextGen Configuration Folder.

  4. Restart the MashZone NextGen Server. For instructions, see Start and Stop the MashZone NextGen Server.
  5. Open the MashZone NextGen Admin Console.
  6. Click Server to expand this section of the Administration menu.
  7. Click Big Memory.
  8. Open the Terracotta Management Server tab.

    This tab lists connections to any existing external dynamic In-Memory Stores.

  9. Click Register a new Terracotta Management Server.
  10. Enter a unique Big Memory data source name for this connection to the dynamic external cache that will act as an In-Memory Store.
  11. Enter the domain and port, or IP address and port for the Terracotta Management Server. For example: localhost:9889.
  12. Enter the Terracotta Management Server connection name.

    Connection names cannot include periods (.), spaces or other common symbols or punctuation characters.

  13. Enter the name of the Cache Manager for this cache. This name is assigned by the external system that created the cache in Big Memory.

    Cache Manager names are a best practice for dynamic external stores. If the external system does not assign a cache manager name, Big Memory uses a default name which can lead to name collisions and errors.

  14. If the TMC requires SSL for connections, change the Security type to SSL.
  15. You can enter an user name and a password optionally.
  16. Click Add this external cache to save this connection.