Inhaltsverzeichnis

Integration Scenario

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. Reguralely1)

Typical message flow between the host system and the trading partner

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

Host->eBiss:Message(INHOUSE-OUTBOUND) eBiss->eBiss:convert message eBiss->eGate:Message(EDIFACT-OUTBOUND) eGate->Trading Partner:Message(EDIFACT-OUTBOUND) Trading Partner->eGate:Message(EDIFACT-INBOUND) eGate->eBiss:Message(EDIFACT-INBOUND) eBiss->eBiss:convert message eBiss->Host:Message(INHOUSE-INBOUND)

Typical processing of inbound messages (INBOUND) from trading partner

Here, too, integration via file exchange2) is possible.

  1. An event occurs.
  2. The Job specified in automation 3) is triggered by the event and opens a defined Kommunikationskanal4) and receives the incoming messages via the channel INBOUND 5) messages.
  3. The incoming messages are created by the communication channel in the Nachrichtenkorb defined by the channel 6).
  4. A second job is initiated and receives the previously received messages.
  5. In this second job, the messages Analysiert 7) Selektoren 8) 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 9).
  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 12).
  10. In this third and mostly last job, the transferred messages are in turn stored with an outgoing communication channel 13).

Typical Processing of Outbound Messages (OUTBOUND) to Business Partners

Also here, an integration via file exchange14).

  1. An automated event occurs.
  2. The Job specified in the automation15) is triggered by the event and opens a defined Channel16) and receives the OUTBOUND17) transmitted over the channel. News.
  3. The outgoing messages are created by the communication channel in the Messageboxes18) 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 Analysed19) and loaded via EntitySelector20) 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 object21).
  8. Then the message is containerized with a EntityMessageCreator into the message basket22) specified by the same step)23).
  9. The messages generated in the job are passed on to a third job with the JobStep DelegatorJob 24).
  10. In this third and usually last job the transferred messages are again transmitted to the partner with an outgoing communication channel25).26)

Message flow in general

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

note right of eBiss: outbound message types eBiss-->eBiss:Event triggers outbound procedures HOST-->eBiss:Direktintegration/FILE transfer eBiss-->eBiss:transform eBiss->Partner:via SMTP,FTP,SFTP,HTTP,AS2,X400 note right of eBiss: inbound message types eBiss-->eBiss:Event triggers inbound procedures Partner->eBiss:via SMTP,FTP,SFTP,HTTP,AS2,X400 eBiss-->eBiss:transform eBiss-->HOST:Direktintegration/FILE transfer

inter-node communication

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

Topics

1)
Dies sind i.d.R. sog. *.ini Dateien.
2)
a widespread method. Alternatively,direct integration with local databases
3)
see also EventListener
4)
Usually an SMTP receive channel which retrieves messages from the eGate VAN account
5)
INBOUND is the direction of a message from the trading partner to the host system
6)
message header name is usually From.Partner
7)
normally partner recognition, document number via plugin definition and document type / subtype
8)
Here, the selection is usually defined by the target type, as different EDIFACT release standards are to be accepted for incoming Edifact messages.
9)
This is usually an object class defined in a custom plug-in.
10)
Message basket name is usually To. Host
11)
This is done depending on the containerizer stored in the repository for the entity type.
12)
Alternatively, the newly created messages can also be selected from the corresponding message basket and further delegated with aMessageSelector.
13)
Here this is usually a Harddisk send channel on a location defined in the channel in the local network.
14)
A widely used method. Alternatively, direct integration with local databases is possible.
15)
also EventListener
16)
Here usually a Dateisystem Empfangskanal, which sends messages from its own Host
17)
OUTBOUND is the direction of a message from the host system to the trading partner
18)
message basket name is usually From.Host
19)
Normally Partner recognition, document number via plugin definition and document type/subtype via Type repositories
20)
Usually a fixed source type is selected here, since only one specific format is to be expected from the host system per message type and direction.
21)
This is usually an object class which is defined in existing plugins.
22)
message basket name is usually To.Partner
23)
This depends on the containerizer stored in the repository for the entity type.
24)
Alternatively, the newly generated messages can be selected from the corresponding message basket with a MessageSelector and further delegated.
25)
Here this is usually a SMTP send channel
26)
Or normally via the partner's own eGate) VAN account.