Port configuration requirements (Core Services)
To use IIoT Core Services, you must provide access to the ports used by the system services and databases.
Message brokers, databases, and external-facing services
IIoT Core Services uses a combination of message brokers and RESTful services. Message brokers establish communication between applications and infrastructure for message queues and topics.
Check the following message brokers, databases, and other services to determine if the corresponding ports need to be open to run your IIoT Core Services. The needed ports must be open both on the load balancer and on each node.
| Service | Description | Default port | Optional install | Default login | Links |
| AMQP - RabbitMQ | Messaging over AMQP | 30671 | No | admin |
Documentation: https://www.rabbitmq.com/documentation.html |
| Service | Description | Default port | Optional install | Default login | Links |
| CouchDB | Unstructured data database access | 30084 | No | admin |
Documentation: http://docs.couchdb.org/en/stable/ UI: OR
OR
|
| MongoDB | Unstructured data database access | 30017 | Yes | admin |
Documentation: https://www.mongodb.com/docs/ |
| InfluxDB | Time-series data (historical data) database access | 30086 | No | admin |
Documentation: https://docs.influxdata.com/influxdb |
| MinIO | Object storage database access | 31000 | No | admin |
Documentation: https://docs.min.io/docs/ UI: OR
OR
|
| Service | Description | Default port | Optional install | Default login | Links |
| Hiota Ingress REST | HTTPS data ingestion to IIoT Core | 30443 | No | N/A |
N/A |
| Hiota Passport |
CouchDB Passport API access to Couch data | 30224 | No | N/A | N/A |
|
InfluxDB Time-series data (historical data) access | 30223 | No | N/A | N/A | |
|
PostgreSQL Structured data access | 30228 | No | N/A | N/A | |
| Hiota Product APIs | Access to management plane APIs | 30443 | No | N/A | Documentation: See Management plane REST API |
| OAuth-Helper | Simple OAuth handling | 30303 | No | N/A |
N/A |
Internal core services
Because the following ports are used by internal IIoT Core Services applications, verify that these ports are open to external access for the assigned IIoT Core Services to work properly.
| Service | Description | Default port | Links |
| Kafka | Kafka messaging support | 30091, 30092 |
Documentation: https://kafka.apache.org/intro |
| RabbitMQ (https-UI) | UI for troubleshooting | 31671 |
Documentation: https://www.rabbitmq.com/documentation.html |
| MQTT - RabbitMQ | Messaging over MQTT for gateway devices | 30884 |
Documentation: https://www.rabbitmq.com/documentation.html |
| Service | Description | Default port | Default login | Links |
| ArangoDB | ArangoDB multi-model database system | 30529 | admin |
Documentation: https://www.arangodb.com/documentation/ |
| CouchDB (https-UI) | UI for troubleshooting | 30984 | admin |
Documentation: http://docs.couchdb.org/en/stable/ UI: OR
OR
|
| Service | Description | Default port | Links |
| Docker Trusted Registry | Private Docker trusted registry that stores and manages Docker images for gateway services or user applications that run on gateways | 32500 |
Documentation: https://docs.docker.com/ee/dtr/ |
| Hiota Alert Manager | Enables alert management | 30443 | N/A |
| Hiota Asset | Enables asset and gateway management | 30443 | N/A |
| Hiota Kube Resource | Management wrapper API for Kubernetes resources for activities such as deploying software and configurations to gateways | 30443 | N/A |
| Hiota Manager (gRPC server) | gRCP server for internal connections | 30999 | N/A |
| Hiota Manager (REST server) | REST server for hiota-agent | 30998 | N/A |
| Hiota OI Manager | Open Image Manager enables upload of software on the user interface and provides statuses. | 30800 | N/A |
| OAuth-Helper | Simple OAuth handling | 30303 | N/A |
| Hiota Registry | Access to core and gateway route endpoints and statuses as well as core service configurations | 30443 | N/A |
| Hiota User Preferences | User preferences for notifications | 30231 | N/A |