Communication
SIHOT supports two different ways of communication:
- ESB (Enterprise Service Bus): This is the preferred way to communicate with partners outside the local network. The messages are being sent over https with an API Key.
- Socket: This is preferred for vendors running the software in our local network, as this is the fastest way of communication
ESB (Enterprise Service Bus)
For details please refer to your local contact in GUBSE.
Socket
The communication between SIHOT and the interface is done over sockets. SIHOT provides by default two different TCP ports for the communication.
Ports
By default, SIHOT receives information from the interface on port 14774. On the other side, the information is sent to the interface on port 14773.
These ports could vary, depending on the installation and should therefore be configurable in the interface.
Asynchronous Data Handling
The complete handling of the data is done in an asynchronous manner. Asynchronous data handling means that while we wait for an acknowledgement of an operation 1, we can receive on a different socket (but same port) a second operation 2 and confirm this operation 2 with an acknowledge. The next step could be the confirmation of operation 1. The next example will clarify this data handling.
Example
| Socket | SIHOT | Interface |
|---|---|---|
1 -> |
Send a check-in to the interface to port 14773 using socket #1 | Start with the processing of the check-in |
2 <- |
Send a text to be displayed to SIHOT to port 14774 using a different socket #2 | |
2 -> |
Confirm the display of the text, information is sent on socket #2 | |
1 <- |
Send the confirmation of the check-in back on socket #1 |
So the acknowledge uses the same socket as the record but after receiving or sending it, the socket is closed. The next record will use a new socket.