{{indexmenu_n>3}}
==== Integration Scenario ====


For a fast integration of eBiss into a new environment, the use eGate is recommended. [[wpde>Mehrwertnetz]] This offers the advantage of a fast connection to the network participants. All eGate participants can also be found by the TNR-Searcg [[http://www.pranke.com/de/service-center/teilnehmer-suche|Teilnehmersuche]] ini files maybe downloaded and implemented in eBiss. Reguralely((Dies sind i.d.R. sog. ***.ini** Dateien.)) 

==== 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**:

<sequencediagram>
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)
</sequencediagram>

==== Typical processing of inbound messages (INBOUND) from trading partner ====

Here, too, integration via file exchange((a widespread method. Alternatively,direct integration with local databases)) is possible.

  - An [[en:prozessdefinition:automatisierungen:automatisierungen|event]] occurs.
  - The [[en:prozessdefinition:jobs:start|Job]] specified in automation ((see also [[en:prozessdefinition:automatisierungen:automatisierungen|EventListener]])) is triggered by the event and opens a defined [[en:kommunikation:kanal:start|Kommunikationskanal]]((Usually an SMTP receive channel which retrieves messages from the [[http://egate.pranke.com|eGate]] [[wpde>Mehrwertnetz|VAN]] account)) and receives the incoming messages via the channel INBOUND ((INBOUND is the direction of a message from the trading partner to the host system)) messages.
  - The incoming messages are created by the communication channel in the [[kommunikation:nachrichtenkoerbe:start|Nachrichtenkorb]] defined by the channel ((message header name is usually ** From.Partner **)).
  - A second job is initiated and receives the previously received messages.
  - In this second job, the messages [[en:prozessdefinition:repositorien:analysator:start|Analysiert]] ((normally partner recognition, document number via plugin definition and document type / subtype)) [[en:prozessdefinition:jobs:jobsteps:allgemein:EntitySelector|Selektoren]] ((Here, the selection is usually defined by the target type, as different EDIFACT release standards are to be accepted for incoming Edifact messages.)) Object loaded.
  - Then the first[[en:prozessdefinition:jobs:jobsteps:allgemein:EntityTransformer|Transformation]] converts from the source object with a suitable [[en:transformation:mappings:standardmappings|MiddleWare]]- mapping into the appropriate target object.
  - Another second transformation necessarily converts the MiddleWare object into the[[en:transformation:mappings:objektdefinition:start|INHOUSE Ziel-Objekt]] associated with the document type ((This is usually an object class defined in a custom plug-in.)). 
  -The message is then containerized with a[[en:prozessdefinition:jobs:jobsteps:allgemein:EntityMessageCreator|]] in the message basket specified at the same job step ((Message basket name is usually **To. Host**)) ((This is done depending on the containerizer stored in the repository for the entity type.)).
  -With the JobStep[[en:prozessdefinition:jobs:jobsteps:allgemein:delegatorjob|]] the messages generated in the job are passed on to a third job ((Alternatively, the newly created messages can also be selected from the corresponding message basket and further delegated with a[[prozessdefinition:jobs:jobsteps:allgemein:MessageSelector]].)).
  -In this third and mostly last job, the transferred messages are in turn stored with an outgoing communication channel ((Here this is usually a [[en:kommunikation:kanal:harddisksend]] on a location defined in the channel in the local network.)).

==== Typical Processing of Outbound Messages (OUTBOUND) to Business Partners ====


Also here, an integration via file exchange((A widely used method. Alternatively, direct integration with local databases is possible.)).
  - An [[en:prozessdefinition:automatisierungen:automatisierungen|automated event]] occurs.
  - The [[en:prozessdefinition:jobs:start|Job]] specified in the automation((also [[prozessdefinition:automatisierungen:automatisierungen|EventListener]])) is triggered by the event and opens a defined [[en:kommunikation:kanal:start|Channel]]((Here usually a [[kommunikation:kanal:harddiskReceive]], which sends messages from its own [[wpde>Host]] )) and receives the OUTBOUND((OUTBOUND is the direction of a message from the host system to the trading partner)) transmitted over the channel. News.
  - The outgoing messages are created by the communication channel in the [[en:kommunikation:nachrichtenkoerbe:start|]]((message basket name is usually **From.Host**)) defined for the channel.
  - A second job is triggered and receives the previously received messages.
  - In this second job the messages are also [[en:prozessdefinition:repositorien:analysator:start|Analysed]]((Normally Partner recognition, document number via plugin definition and document type/subtype via [[en:prozessdefinition:repositorien:start]])) and loaded via [[en:prozessdefinition:jobs:jobsteps:allgemein:EntitySelector]]((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.)) into your corresponding [[transformation:mappings:objektdefinition:start|INHOUSE Source Object]]. 
  - Then in a first [[prozessdefinition:jobs:jobsteps:allgemein:EntityTransformer|Transformation]] the [[transformation:mappings:objektdefinition:start|INHOUSE Source Object]] is converted to the appropriate middleware target object with suitable custom mapping.
  - Another second transformation necessarily converts the MiddleWare object into the EDIFACT target object((This is usually an object class which is defined in existing plugins.)). 
  - Then the message is containerized with a [[prozessdefinition:jobs:jobsteps:allgemein:EntityMessageCreator|]] into the message basket((message basket name is usually **To.Partner**)) specified by the same step)((This depends on the containerizer stored in the repository for the entity type.)).
  - The messages generated in the job are passed on to a third job with the JobStep [[prozessdefinition:jobs:jobsteps:allgemein:delegatorjob|]] ((Alternatively, the newly generated messages can be selected from the corresponding message basket with a [[prozessdefinition:jobs:jobsteps:allgemein:MessageSelector]] and further delegated.)).
  - In this third and usually last job the transferred messages are again transmitted to the partner with an outgoing communication channel((Here this is usually a [[en:kommunikation:kanal:smtpsend]])).((Or normally via the partner's own [[http://egate.pranke.com|eGate]]) [[wpde>Value Added Network|VAN]] account.))


==== Message flow in general ====


Eventlistener->Job->ReceiveChannel->Messagebox->Analyzer->Selector->Transformierung->Transformierung->Containerisierung->MessageSelector->Job->SendChannel

<sequencediagram>
    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
</sequencediagram>



==== inter-node communication =====

Data exchange between several eBiss systems via HTTP is explained in[[howtos:multiknotenkommunikation]].


===== Topics =====

{{indexmenu>:ueberblick:integration:integrationsszenario|navbar}}