eBiss 3

For a fast integration of eBiss into a new environment, the use eGate is recommended. Mehrwertnetz This offers the advantage of a fast connection to the network participants. All eGate participants can also be found by the TNR-Searcg Teilnehmersuche ini files maybe downloaded and implemented in eBiss. Reguralely¹⁾

The following figure shows the typical message flow between the host system and a trading partner with the converter eBiss and the Gateway eGate:

Here, too, integration via file exchange²⁾ is possible.

1. An event occurs.
2. The Job specified in automation ³⁾ is triggered by the event and opens a defined Kommunikationskanal⁴⁾ and receives the incoming messages via the channel INBOUND ⁵⁾ messages.
3. The incoming messages are created by the communication channel in the Nachrichtenkorb defined by the channel ⁶⁾.
4. A second job is initiated and receives the previously received messages.
5. In this second job, the messages Analysiert ⁷⁾ Selektoren ⁸⁾ Object loaded.
6. Then the firstTransformation converts from the source object with a suitable MiddleWare- mapping into the appropriate target object.
7. Another second transformation necessarily converts the MiddleWare object into theINHOUSE Ziel-Objekt associated with the document type ⁹⁾.
8. The message is then containerized with aEntityMessageCreator in the message basket specified at the same job step ^{10) 11)}.
9. With the JobStepDelegatorJob the messages generated in the job are passed on to a third job ¹²⁾.
10. In this third and mostly last job, the transferred messages are in turn stored with an outgoing communication channel ¹³⁾.

Also here, an integration via file exchange¹⁴⁾.

1. An automated event occurs.
2. The Job specified in the automation¹⁵⁾ is triggered by the event and opens a defined Channel¹⁶⁾ and receives the OUTBOUND¹⁷⁾ transmitted over the channel. News.
3. The outgoing messages are created by the communication channel in the Messageboxes¹⁸⁾ defined for the channel.
4. A second job is triggered and receives the previously received messages.
5. In this second job the messages are also Analysed¹⁹⁾ and loaded via EntitySelector²⁰⁾ into your corresponding INHOUSE Source Object.
6. Then in a first Transformation the INHOUSE Source Object is converted to the appropriate middleware target object with suitable custom mapping.
7. Another second transformation necessarily converts the MiddleWare object into the EDIFACT target object²¹⁾.
8. Then the message is containerized with a EntityMessageCreator into the message basket²²⁾ specified by the same step)²³⁾.
9. The messages generated in the job are passed on to a third job with the JobStep DelegatorJob ²⁴⁾.
10. In this third and usually last job the transferred messages are again transmitted to the partner with an outgoing communication channel²⁵⁾.²⁶⁾

Eventlistener→Job→ReceiveChannel→Messagebox→Analyzer→Selector→Transformierung→Transformierung→Containerisierung→MessageSelector→Job→SendChannel

Data exchange between several eBiss systems via HTTP is explained inMultiknotenkommunikation via HTTP.