Sidebar
en:howtos:multiknotenkommunikation
Table of Contents
Multi node communication via HTTP
A communication (or inter-node communication) between different eBiss systems or eBiss nodes can be displayed via HTTP. This looks like this in a flow chart:
eBiss\nKnoten A->URL&Port: HttpSendChannel
URL&Port-->eBiss\nKnoten B: PortEventListener
eBiss\nKnoten B->eBiss\nKnoten B:Job\nmit\nChannelReceiver
URL&Port->eBiss\nKnoten B: HTTPReceiveChannel
For the multicode communication, therefore, a distinction is made between a sending system and a receiving system / node. The receiving system needs a HttpReceiveChannel which is to receive a specified URL and port. In order for this communication channel to be opened, it also needs a Port Eventlistener which listens on the same URL (and port) and triggers a job that opens the previously defined communication channel in the event. In the sending system it is only necessary to send a channel HttpSendChannel to the URL set up in the target node.
Necessary settings in the receiving System
| Components | Description |
|---|---|
| HttpReceiveChannel | There you need to activate the option MultiMessages by placing a check mark in the box. This allows the HttpChannelSender to send more than one (all existing) messages that go to the exact same URL over a connection. This is especially useful with localhost transfers. This optimization runs only one thread for all messages. |
| Port Eventlistener | URL and dedicated port |
| ChannelReceiver | In a job that is triggered by the Port Eventlistener and opens theHttpReceiveChannel. |
Necessary settings in the sending System
| Components | Description |
|---|---|
| HttpSendChannel | There you need to activate the option UsePlainHttpSender by placing a check mark in the box. This causes that the System.Net.HttpClient is no longer used, but uses an own and faster one, which supports MultiMessages (s.u.). However, it does not support proxy settings and the like. Furthermore, the MultiMessages option has to be activated by ticking the checkbox. This setting is used to set the counterpart to the settings of the ChannelReceiver (the receiving system / node). Only if these two options are set together with the UsePlainHttpSender, will this MultiMessage Feature work. |
| ChannelSender | SortMessageyByRecipientAddressshould be set to true. This will sort the messages accordingly. |
en/howtos/multiknotenkommunikation.txt · Last modified: 2024/02/20 08:15 by 127.0.0.1