> 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/chinese/gai-shu-yu-ji-chu/architecture.md).
# 架构
## **DocBits 云端客户**
## DocBits 本地部署
Doc**Bits** 通过 ION API、ION Desk 和 Infor 标准 BOD 与 Infor LN/M3 无缝集成。通过 API 集成，我们可以将数据导出到 Infor，并在 Doc**Bits** 中执行主数据验证。
## **DocBits Operator 架构**
组件之间的所有连接均使用行业标准加密协议进行保护。SSH、HTTPS 和其他安全通道可确保整个系统中的数据完整性和机密性。
**本地部署：**
{% content-ref url="/pages/8SqgP3eZPk4m6qDmRMdn" %}
[Prefect 本地设置要求](/chinese/gai-shu-yu-ji-chu/architecture/prefect-local-setup-requirements.md)
{% endcontent-ref %}
**云端**：
## 将数据导出到 Infor
我们使用 ION API 将带有属性的 PDF 发送到 IDM，并将 BOD Sync.CaptureDocument 发送到 ION Desk。在 ION Desk 中，我们根据正在处理的文档类型，将 [Sync.CaptureDocument](/chinese/infor-ji-cheng-yu-pei-zhi/exporting-in-docbits.md) 转换为所需的目标 BOD。随后，这些转换后的 Infor BOD 会自动导入 LN 或 M3。
{% hint style="info" %}
导出到 [Infor](/chinese/infor-ji-cheng-yu-pei-zhi/exporting-to-infor.md)
{% endhint %}
## 在 DocBits 中验证主数据
为识别供应商或比较/匹配采购订单行，我们会在 LN/M3 中激活一个触发器，将 Sync.RemitToPartyMaster、Sync.SupplierPartyMaster 和 Sync.PurchaseOrder BOD 发送到 Doc**Bits**。我们在 ION Desk 中配置此流程，将数据流定义到 Doc**Bits** 的特定连接点。
{% hint style="info" %}
[主数据验证](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data.md)
{% endhint %}
## 电子邮件导入 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/chinese/gai-shu-yu-ji-chu/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)
