Connectivity

An adapter’s purpose is to communicate with an external system, so network connectivity between theItential Platform server and that system is a prerequisite. If a firewall or network policy blocks the path, the adapter cannot function. Firewall rules must allow traffic from theItential Platform server to the external system on the required host and port.

Verify connectivity

Run these checks from theItential Platform server itself — not your local machine. Connectivity must be verified from the machine where the adapter runs.

• ping — confirms theItential Platform server can reach the external server.
• telnet — tests the specific host and port the external system listens on.
• traceroute — if connectivity appears blocked, identifies where the path breaks. This gives the relevant network team the information they need to open access.
• curl — sends an actual HTTP request from theItential Platform server to the external system, confirming the full request path is open.

Required adapter properties

If the service instance configuration has incorrect connectivity values, the adapter will load, but the health check (if configured) will fail on restart, and all adapter calls will fail — usually with a 400 or 404 error. Verify the following properties:

• host
• port
• protocol
• ssl sub-properties, if the external system uses SSL/TLS:
  • Set ssl.enabled to true.
  • For development and lab environments, ssl.accept_invalid_cert can be set to true to bypass certificate validation. This is not appropriate for production.
  • For production, set ssl.ca_file to the path of a CA file. Obtain the CA from the administrator of the external system.