Testing a connection
Test connection is safe to run at any time: it never sends or reads a message. It signs in where it can, lists or opens what it can, and stops. No HL7 is written to an MLLP socket (the other side would take it as a real message), and an HTTP endpoint only ever receives a GET.
How far did it get?
Every result says how much was actually proved:
| Result | Meaning |
|---|---|
| Verified | The engine signed in with the credential (or, for a folder, checked the access). |
| Reached | The system answered as the right kind of server, but the credential was not tried yet, because that needs a component that arrives with Stage 2. |
| Checked | There is nothing to reach (an inbound webhook, an inbound port), so the settings were checked on this engine instead. |
| Failed | Something is wrong. The message says what - see Troubleshooting. |
What each connector's test proves
| Connector | What the test proves |
|---|---|
| MLLP (HL7 over TCP) | Outbound: the host and port accept a connection. Inbound: the port is free on this engine. No message is sent. |
| Apache Kafka | Every broker in the list accepts a connection. Topic access is checked in Stage 2. |
| RabbitMQ | The host answers as an AMQP server. Signing in is checked in Stage 2. |
| Signs in to the mail server (IMAP LOGIN, or SMTP AUTH). No mail is read or sent. | |
| HTTP / REST API | The address answers and the credential is accepted, by a GET on the health path. Never a POST. |
| Inbound webhook | Nothing to reach - the partner calls us. The test checks the path is free and well-formed. |
| FHIR server | Signs in (OAuth client credentials, Basic or Bearer) and reads the server's CapabilityStatement. |
| SOAP web service | The WSDL can be read with the credential. |
| SFTP | The host answers as an SSH server. Signing in is checked once the SFTP component is installed (Stage 2). |
| FTP / FTPS | Signs in with the username and password and opens the folder. Nothing is read or written. |
| Shared folder | The folder exists and the engine can read it (inbound) or write to it (outbound). No file is created. |
| Database | PostgreSQL: signs in and runs SELECT 1. Others: the host and port answer (their drivers come in Stage 2). |
| Amazon S3 | The bucket exists and answers. The access key is checked in Stage 2. |
| Azure Blob Storage | With a SAS token: lists the container (proves the token). Without: the account answers. |
Worked examples that pass anywhere
These examples point at things on the engine itself, so Test passes on any machine:
- Demo HL7 listener (MLLP) - MLLP (HL7 over TCP)
- Demo REST endpoint (this engine) - HTTP / REST API
- Demo inbound webhook - Inbound webhook
- HAPI public FHIR (test) - FHIR server
- Demo order folder - Shared folder
All the others use placeholder hosts on example.com and need the partner's real address and credentials.