This article describes the port configuration of a G-Map Server.
G-Map Server Port Configuration
A G-Map Server requires one port to receive and respond to REST requests.
- requestPort - 8050 (default) - Receives client requests.
- The port number may be changed at DevOps's discretion.
- The user enters the port number (configured by DevOps) when launching a G-Map Server.
Detailed Port Deployment Example of a G-Map Server (GMS)
The diagram below shows a detailed deployment of a G-Map Server (GMS), a GMUS, and a G-Repository Server (GRS) within a Test Environment. In this example, all three servers are installed and run on the same Linux machine.
Here are key points to observe from the diagram:
- GMS, GMUS, and GRS are installed on a machine whose IP address is 192.168.100.10.
- GMS has its port configured to 8050
- GMUS has its port configured to 9010
- GRS has its cloudPort configured to port 443.
- GRS has its mainPort configured to port 8020.
- GRS has its downloadPort configured to port 8021.
- GRS is communicating directly to GenRocket Cloud over HTTPS via port 443.
- Each GenRocket Cloud component has its own unique URL
- Each GenRocket Cloud component only allows access over HTTPS via port 443.
- Clients directly request the GMUS via IP address 192.168.100.10 and port 9010.
- GMUS loads a Scenario.
- GMUS uses the GenRocket Engine (GE) to run the Scenario.
- Specific GenRocket Generators send data to and receive data from the GMS via port 8050.
- Specific GenRocket Receivers send data to and receiver data from the GMS via port 8050.
- The GMS, GMUS, and GRS can only access ports your DevOps team makes available.
- Configuring your machines' internal protocols is your DevOps team's responsibility.
- Selecting and opening port numbers is left to the discretion of your DevOps team.