Skip to main content

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:

ResultMeaning
VerifiedThe engine signed in with the credential (or, for a folder, checked the access).
ReachedThe 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.
CheckedThere is nothing to reach (an inbound webhook, an inbound port), so the settings were checked on this engine instead.
FailedSomething is wrong. The message says what - see Troubleshooting.

What each connector's test proves​

ConnectorWhat 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 KafkaEvery broker in the list accepts a connection. Topic access is checked in Stage 2.
RabbitMQThe host answers as an AMQP server. Signing in is checked in Stage 2.
EmailSigns in to the mail server (IMAP LOGIN, or SMTP AUTH). No mail is read or sent.
HTTP / REST APIThe address answers and the credential is accepted, by a GET on the health path. Never a POST.
Inbound webhookNothing to reach - the partner calls us. The test checks the path is free and well-formed.
FHIR serverSigns in (OAuth client credentials, Basic or Bearer) and reads the server's CapabilityStatement.
SOAP web serviceThe WSDL can be read with the credential.
SFTPThe host answers as an SSH server. Signing in is checked once the SFTP component is installed (Stage 2).
FTP / FTPSSigns in with the username and password and opens the folder. Nothing is read or written.
Shared folderThe folder exists and the engine can read it (inbound) or write to it (outbound). No file is created.
DatabasePostgreSQL: signs in and runs SELECT 1. Others: the host and port answer (their drivers come in Stage 2).
Amazon S3The bucket exists and answers. The access key is checked in Stage 2.
Azure Blob StorageWith 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:

All the others use placeholder hosts on example.com and need the partner's real address and credentials.