G-MapServer allows Domain Attributes to put key/value data into mapped memory and disk cache and allows other Domain Attributes to get value data from cache with a key. When its mapped memory cache is full, it uses a Least Recently Used (LRU) algorithm to retrieve values from its disk cache to place into mapped memory.
The G-MapServer communicates over REST via a given port. Thus, multiple G-MapServers can operate simultaneously within a single test server or on multiple testing servers within a closed testing environment.
Since G-Map communicates via REST services, it benefits the testing of complex workflows by allowing the management of referential integrity across different components during the workflow testing process.
Learn All About G-Map Security, Benefits & Components
To learn more about G-Map Features, please select from the following topics:
|G-Map Server - Workflow & Referential Integrity Benefits||Learn why G-Map Server is so beneficial when testing complex workflows and maintaining referential integrity across components|
|G-Map Components||Learn about G-Map Generator, Receiver, and Server Components|
|G-Map Server - Internal Components||Learn about G-Map Server's Internal Components|
|G-Map Server - Run|
|G-Map Server - Command-Line Options|
|G-Map Server - Customize Configuration File||Learn how to customize a G-Map Server configuration file|
|G-Map Unknown Parent/Child Insert Example||The child data being generated and inserted into a database table, by a GenRocket Scenario, does not know the value of the parent key-value, because it was not Generated by the GenRocket parent Scenario during insertion.|