Network Requirements
When deploying Germain to monitor your business applications and infrastructure, it is important to open specific network ports to facilitate communication and data collection. The exact ports that need to be opened can vary based on the users, processes, and technologies involved in your monitoring setup. Here is a general guideline for network ports that may need to be opened:
Source Ports
Web Browsers
Typically, outbound connections from web browsers use commonly used HTTP(S) ports such as 80 and 443 for accessing web applications.Servers or Agents
Outbound connections from the servers or agents running Germain components may require specific ports depending on the technologies and protocols they interact with.
Destination Ports
Application Servers
Inbound connections to the application servers hosting the business applications you want to monitor. The required ports can vary based on the specific application protocols used (e.g., HTTP, HTTPS, RDP, SSH, database-specific ports, etc.).Infrastructure Components
Inbound connections to network devices, servers, databases, and other infrastructure components that Germain needs to monitor or automate transactions against. The ports required will depend on the technologies and protocols employed by these components.
It is crucial to understand that the specific ports you need to open will be determined by your unique environment and the technologies you utilize. Consult the documentation provided by Germain or reach out to their support team for detailed information on the specific network ports required for your setup.
Additionally, adhere to your organization's security policies and best practices when opening network ports, ensuring that only the necessary ports are exposed, and appropriate security measures are implemented.
On-Premise
Port | Protocol/Usage | Source | Destination |
|---|---|---|---|
61616 | Active MQ OpenWire/JMS | Germain Engines | Germain Enterprise |
8080 | HTTP/S | Germain Users | Germain Enterprise |
8005 | HTTP/S | Germain Users | Germain Enterprise |
8009 | HTTP/S | Germain Users | Germain Enterprise |
443 | Chat button on Germain Workspace (so you can talk to any technical support engineers right the way clicking on that chat button) | Germain Users | https://api-iam.intercom.io/* |
443 | Geo Mapping | Germain Users | https://www.google.com/* |
database port (for oracle 1521, etc) | Application Database (oracle, sqlsrvr, db2, hadoop, etc) | Germain Enterprise | Germain Database |
database port (for oracle 1521, etc) | Application Database (oracle, sqlsrvr, db2, hadoop, etc) | Germain Enterprise | Application Database (DEVELOPMENT database that Germain CRT is going to connect to, to perform a review of application repository) |
database port (for oracle 1521, etc) | Application Database (oracle, sqlsrvr, db2, hadoop, etc) | Germain Engines | Application Database (environment is going to be monitored by Germain) |
application url port (80, 443) | Application URL (virtual and physical) | Germain Engines | Web server(s) (virtual and physical) |
application administration console ports (e.g. for siebel 2320, 2321, etc) | Application Administration Console | Germain Engines | Application Server where administration console runs on (e.g. Siebel, it is |
135 | TCP | Germain Engines | Windows server/desktop to be monitored by Germain |
137 | UDP | Germain Engines | Windows server/desktop to be monitored by Germain |
138 | UDP | Germain Engines | Windows server/desktop to be monitored by Germain |
139 | TCP | Germain Engines | Windows server/desktop to be monitored by Germain |
445 | TCP | Germain Engines | Windows server/desktop to be monitored by Germain |
SSH port | SSH | Germain Engines | Unix server/desktop to be monitored by Germain |
port range TBD | WMI | Germain Engines | Windows server to be monitored |
1099 | JMX - TCP | Germain Engines | Java Application Server/JVM to be monitored |
Cloud
Port | Protocol/Usage | Source | Destination |
|---|---|---|---|
443 | HTTP/S | Germain Agents | Germain Enterprise Cloud get URL/IP after your sign up on your cloud instance |
database port (for oracle 1521, etc) | Application Database (Oracle, SQL Server, DB2, hadoop, etc) | Germain Agents | Application Database (DEVELOPMENT database that Germain CRT is going to connect to, to perform a review of application repository) |
database port (for oracle 1521, etc) | Application Database (Oracle, SQL Server, DB2, hadoop, etc) | Germain Agents | Application Database (environment is going to be monitored by Germain) |
application url port (80, 443) | Application URL (virtual and physical) | Germain Agents | Web server(s) (virtual and physical) |
application administration console ports | Application Administration Console | Germain Agents | Application Server where administration console runs on (e.g. siebel, it is /siebsrvr/bin/srvrmgr.exe) |
135 | TCP | Germain Agents | Windows server/desktop to be monitored by Germain |
137 | UDP | Germain Agents | Windows server/desktop to be monitored by Germain |
138 | UDP | Germain Agents | Windows server/desktop to be monitored by Germain |
| TCP | Germain Agents | Windows server/desktop to be monitored by Germain |
445 | TCP | Germain Agents | Windows server/desktop to be monitored by Germain |
SSH port | SSH | Germain Agents | Unix server/desktop to be monitored by Germain |
port range TBD | WMI | Germain Engines | Windows server/desktop to be monitored by Germain |
5985 = HTTP | Powershell | Germain Engines | Windows server/desktop to be monitored by Germain |
1099 | JMX - TCP | Germain Agents | Java Application Server/JVM to be monitored |
443 | HTTP/S | Germain Users | Germain Enterprise Cloud (get URL/IP after your sign up on your cloud instance) |
443 | Chat button on Germain Workspace (so you can talk to any technical support engineers right the way clicking on that chat button) | Germain Users | https://api-iam.intercom.io/* |
443 | Geo Mapping | Germain Users | https://www.google.com/* |