> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/deutsch/overview-and-basics/architecture.md).
# Architektur
## **DocBits Cloud-Kunde**
## DocBits On-Premise
Doc**Bits** integriert sich nahtlos in Infor LN/M3 über die ION API, ION Desk und die Infor-Standard-BODs. Unsere API-Integration ermöglicht es uns, Daten nach Infor zu exportieren und die Stammdatenvalidierung in Doc**Bits** durchzuführen.
## **DocBits Operator-Architektur**
Alle Verbindungen zwischen den Komponenten werden mit branchenüblichen Verschlüsselungsprotokollen gesichert. SSH, HTTPS und andere sichere Kanäle gewährleisten die Datenintegrität und Vertraulichkeit im gesamten System.
**On-Premise:**
{% content-ref url="/pages/SEzclVOsoBO3pmKtBsyx" %}
[Anforderungen an die lokale Prefect-Einrichtung](/deutsch/overview-and-basics/architecture/prefect-local-setup-requirements.md)
{% endcontent-ref %}
**Cloud**:
## Daten nach Infor exportieren
Wir verwenden die ION API, um das PDF mit Attributen an IDM und die BOD Sync.CaptureDocument an ION Desk zu senden. In ION Desk transformieren wir die [Sync.CaptureDocument](/deutsch/infor-integration-and-configuration/exporting-in-docbits.md) je nach verarbeitetem Dokumenttyp in die gewünschten Ziel-BODs. Diese transformierten Infor-BODs werden anschließend automatisch in LN oder M3 importiert.
{% hint style="info" %}
Export nach [Infor](/deutsch/infor-integration-and-configuration/exporting-to-infor.md)
{% endhint %}
## Stammdatenvalidierung in DocBits
Um den Lieferanten zu identifizieren oder Bestellpositionen zu vergleichen/abzugleichen, aktivieren wir in LN/M3 einen Trigger, der die BODs Sync.RemitToPartyMaster, Sync.SupplierPartyMaster und Sync.PurchaseOrder an Doc**Bits** sendet. Wir konfigurieren diesen Prozess in ION Desk, indem wir den Datenfluss zu einem bestimmten Verbindungspunkt zu Doc**Bits** definieren.
{% hint style="info" %}
[Stammdatenvalidierung](/deutsch/infor-integration-and-configuration/importing-customer-master-data.md)
{% endhint %}
## E-Mail-Import OAuth Office365
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docbits.com/deutsch/overview-and-basics/architecture.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
