This article summarizes G-Map Server (GMS) run and security questions.
Where Can a GMS be Deployed and Run?
The GMS is a small set of Java byte code and is housed within the GenRocket Engine Jar. The GMS like other GenRocket servers (e.g., GMUS, G-Repository Server), have very small footprints and can be deployed and run on any computer be it a desktop, laptop, or rack machine. However, we only recommend and support the deployment and running of the GMS and our other servers on Linux and Mac operating systems.
Where Should a GMS be Deployed and Run?
A GMS should only be used for test engagements. Thus, a GMS should be run within your corporate on-prem environment behind your corporate firewall or within your corporate private cloud environments.
How Does a GMS communicate?
A GMS communicates over REST via a given port. This means multiple GMSs may be launched and run simultaneously, for complex testing workflows, as long as each GMS is running on a different port.
Where Does a GMS Store Its Persistent Cache?
A GMS stores data to persistent cache on the local computer it is launched with the .genrocket subdirectory. Within the .genrocket subdirectory, it will create several files:
- Configuration file - A modifiable configuration file name, GMapCache####.config, where #### defines the unique port number of the GMS (e.g., GMapCache8500.config).
- A Cache Subdirectory - This subdirectory has the name convention of, gmap_cache_####, where #### defines the unique port number of the GMS (e.g., gmap_cache_8500). Two files are created and managed within the directory that persist the cache data:
The below image shows three GMS configuration files and subdirectories within a .genrocket subdirectory. Each set of configurations is uniquely defined by its port number.