sales-boomi

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Boomi Platform Help

Boomi平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

references/learnings.md

exists, read it first for accumulated platform knowledge.

Ask the user:

What do you need help with?
- A) Integration development — connectors, data mapping, process building
- B) API management — design, publish, govern, secure APIs
- C) Data Hub — master data management, golden records, data quality
- D) Flow — low-code app/workflow building
- E) Event Streams — real-time event-driven integration
- F) B2B/EDI — partner data exchange, trading partners
- G) AI agents — AgentStudio, MCP, Platform Agents
- H) Deployment — Atoms, Molecules, Atom Clouds, runtime management
- I) Monitoring / troubleshooting — logs, errors, process execution
- J) Pricing / licensing — per-connection costs, editions, optimization
- K) Something else — describe it
What's your deployment model?
- A) Boomi Atom Cloud (Boomi-hosted)
- B) Local Atom (on-premises)
- C) Molecule (clustered, high availability)
- D) Not sure / evaluating
What's your role?
- A) Integration developer (builds processes)
- B) Architect (designs integration strategy)
- C) Admin (manages platform, environments, users)
- D) Business user (Flow / Task Automation)
- E) Evaluating Boomi

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask 1-2 critical clarifying questions.

若

references/learnings.md

文件存在，请先阅读以获取累积的平台知识。

向用户询问：

您需要哪方面的帮助？
- A) 集成开发——连接器、数据映射、流程构建
- B) API管理——API设计、发布、治理、安全
- C) Data Hub——主数据管理、黄金记录、数据质量
- D) Flow——低代码应用/工作流构建
- E) Event Streams——实时事件驱动集成
- F) B2B/EDI——合作伙伴数据交换、贸易伙伴管理
- G) AI代理——AgentStudio、MCP、平台代理
- H) 部署——Atom、Molecule、Atom Cloud、运行时管理
- I) 监控/故障排查——日志、错误、流程执行
- J) 定价/许可——按连接成本、版本、优化
- K) 其他——请描述
您的部署模式是什么？
- A) Boomi Atom Cloud（Boomi托管）
- B) 本地Atom（本地部署）
- C) Molecule（集群化、高可用）
- D) 不确定/正在评估
您的角色是什么？
- A) 集成开发者（构建流程）
- B) 架构师（设计集成策略）
- C) 管理员（管理平台、环境、用户）
- D) 业务用户（Flow/任务自动化）
- E) 正在评估Boomi

跳过规则：如果用户的提示已提供足够上下文，直接跳至步骤2。先基于合理假设（需明确说明）给出最佳答案，再询问1-2个关键澄清问题。

Step 2 — Route or answer directly

步骤2 — 转至对应服务或直接解答

Problem domain	Route to
Connecting Boomi to Salesforce/HubSpot/CRM	`/sales-integration {question}`
CRM comparison — Salesforce vs HubSpot vs others	`/sales-crm-selection {question}`
Salesforce-specific config (Flows, Apex, SOQL)	`/sales-salesforce {question}`
Simple no-code Zapier/Make automations	`/sales-integration {question}`
MuleSoft-specific questions	`/sales-mulesoft {question}`
SnapLogic-specific questions	`/sales-snaplogic {question}`
CRM data quality / deduplication	`/sales-data-hygiene {question}`
Integration architecture strategy	Answer directly — read platform guide
Connector setup or troubleshooting	Answer directly — read platform guide
API management and governance	Answer directly — read platform guide
Pricing optimization	Answer directly — read platform guide

When routing, provide the exact command.

问题领域	转至
Boomi与Salesforce/HubSpot/CRM连接	`/sales-integration {question}`
CRM对比——Salesforce vs HubSpot及其他	`/sales-crm-selection {question}`
Salesforce特定配置（Flows、Apex、SOQL）	`/sales-salesforce {question}`
简单无代码Zapier/Make自动化	`/sales-integration {question}`
MuleSoft特定问题	`/sales-mulesoft {question}`
SnapLogic特定问题	`/sales-snaplogic {question}`
CRM数据质量/去重	`/sales-data-hygiene {question}`
集成架构策略	直接解答——阅读平台指南
连接器设置或故障排查	直接解答——阅读平台指南
API管理与治理	直接解答——阅读平台指南
定价优化	直接解答——阅读平台指南

转至对应服务时，请提供准确命令。

Step 3 — Boomi platform reference

步骤3 — Boomi平台参考

Read
references/platform-guide.md
for the full platform reference — modules, pricing, connectors, deployment, Data Hub, API management, AI agents.

Answer the user's question using only the relevant section. Don't dump the full reference.

If the question involves the Boomi Platform APIs, also read
references/boomi-api-reference.md
for endpoints, authentication, and rate limits.

**阅读

references/platform-guide.md

**获取完整平台参考——模块、定价、连接器、部署、Data Hub、API管理、AI代理。

仅使用相关章节解答用户问题，不要直接输出完整参考内容。

若问题涉及Boomi Platform APIs，还需**阅读

references/boomi-api-reference.md

**获取端点、认证及速率限制信息。

Step 4 — Actionable guidance

步骤4 — 可落地指导

You no longer need the platform guide — focus on the user's specific situation.

Connector selection shortcut: Check Boomi Marketplace first for pre-built connectors. If no connector exists, use the HTTP Client connector for REST APIs or the Connector SDK to build custom. Technology connectors (Database, Disk, FTP, HTTP, SFTP) are always available.

Deployment decision shortcut: Atom Cloud for fastest start (Boomi-hosted, no infrastructure). Local Atom for on-prem data that can't leave the network. Molecule for high availability and load balancing. Start small, scale up.

Cost optimization shortcut: Audit active connections — each endpoint costs ~$300/mo. Consolidate processes where possible. Use the Professional tier if you need ≤5 connections. Negotiate multi-year for volume discounts. Consider the PAYG ($99/mo + usage) for testing.

If you discover a gotcha, workaround, or tip not covered in

references/learnings.md

, append it there.

无需再依赖平台指南——聚焦用户具体场景。

连接器选择捷径：先查看Boomi Marketplace获取预构建连接器。若无对应连接器，使用HTTP Client连接器调用REST API，或通过Connector SDK构建自定义连接器。技术连接器（数据库、磁盘、FTP、HTTP、SFTP）始终可用。

部署决策捷径：Atom Cloud启动最快（Boomi托管，无需基础设施）。本地Atom适用于无法离开内网的本地数据。Molecule适用于高可用和负载均衡。从小规模开始，逐步扩展。

成本优化捷径：审核活跃连接——每个端点每月约花费300美元。尽可能整合流程。若需要≤5个连接，选择专业版。协商多年合同获取批量折扣。测试阶段可考虑按使用付费模式（每月99美元+使用费用）。

若发现

references/learnings.md

未覆盖的陷阱、变通方案或技巧，请添加至该文件中。

Gotchas

注意事项

Best-effort from research — review these, especially pricing details and feature availability which change frequently.

Per-connection pricing adds up fast. Every endpoint (even basic local disk or HTTP) costs ~$300/mo additional. Map your connection count before signing. A 20-integration setup can easily exceed $6K/mo in connection fees alone.
Debugging is painful. Boomi's error messages are frequently vague ("process execution failed"). Enable detailed logging in process properties, use the Process Reporting tab, and check Atom logs directly for stack traces.
Single JVM per Atom — no auto-scaling. Each Atom runs as one JVM process. High-throughput workloads hit memory ceilings. Use Molecules (clustered Atoms) for horizontal scaling, but design processes to be stateless first.
3-7% annual contract escalation. Boomi contracts typically include automatic price increases at renewal. Negotiate a price cap or multi-year lock upfront.
Documentation is descriptive, not instructive. Boomi docs explain what features do but rarely show how to solve integration problems. Community forums (community.boomi.com) and Boomi training courses fill the gap.
Server restarts can lose in-flight transactions. Atom restarts (during updates or crashes) may drop transactions in progress. Implement idempotent processes and checkpoint/restart patterns for critical workflows.
Premium connector costs are hidden. SAP, Workday, and some ERP connectors carry separate licensing fees beyond the per-connection cost. Verify connector licensing before planning integrations.

基于研究的最佳实践——请重点关注这些内容，尤其是频繁变化的定价细节和功能可用性。

按连接计费成本增长迅速：每个端点（即使是基础本地磁盘或HTTP端点）每月额外花费约300美元。签约前统计连接数量。20个集成的设置仅连接费用就可能轻松超过每月6000美元。
调试难度大：Boomi的错误信息通常模糊（如“流程执行失败”）。在流程属性中启用详细日志，使用流程报告标签页，直接查看Atom日志获取堆栈跟踪。
单个Atom对应单个JVM——无自动扩缩容：每个Atom作为单个JVM进程运行。高吞吐量工作负载会遇到内存上限。使用Molecule（集群化Atom）进行水平扩展，但需先将流程设计为无状态。
年度合同自动涨价3-7%：Boomi合同通常包含续约时的自动涨价条款。提前协商价格上限或多年锁定价格。
文档侧重描述而非指导：Boomi文档仅解释功能用途，很少展示如何解决集成问题。社区论坛（community.boomi.com）和Boomi培训课程可填补这一空白。
服务器重启可能丢失正在处理的事务：Atom重启（更新或崩溃期间）可能丢失正在处理的事务。为关键工作流实现幂等流程和检查点/重启模式。
高级连接器成本隐藏：SAP、Workday及部分ERP连接器除按连接计费外，还需单独许可费用。规划集成前请确认连接器许可情况。

Related skills

Examples

示例

Example 1: Connector authentication failing

示例1：连接器认证失败

User says: "My Boomi Salesforce connector keeps failing with 'INVALID_SESSION_ID' after a few hours." Skill does: Reads platform guide for connector section. Explains that Salesforce OAuth tokens expire — configure the Salesforce connector to use OAuth 2.0 with refresh tokens instead of session ID. Walks through the connector configuration in AtomSphere: Connection tab → Auth Type → OAuth 2.0 → set Client ID, Client Secret, and Refresh Token. Notes that Connected App in Salesforce needs "Refresh token is valid until revoked" setting. Result: User has a persistent Salesforce connection that auto-refreshes.

用户提问：“我的Boomi Salesforce连接器几小时后持续显示‘INVALID_SESSION_ID’错误。” 技能处理：阅读平台指南中连接器章节。解释Salesforce OAuth令牌会过期——将Salesforce连接器配置为使用带刷新令牌的OAuth 2.0而非会话ID。引导用户在AtomSphere中配置连接器：连接标签页 → 认证类型 → OAuth 2.0 → 设置客户端ID、客户端密钥和刷新令牌。提醒用户Salesforce中的Connected App需设置“刷新令牌在撤销前始终有效”。结果：用户获得可自动刷新的持久Salesforce连接。

Example 2: Boomi vs MuleSoft for a mid-market company

示例2：中端市场企业选择Boomi vs MuleSoft

User says: "We're evaluating Boomi and MuleSoft for our integration needs — 15 applications, mostly cloud SaaS, team of 3." Skill does: Reads platform guide for pricing and positioning. Compares: Boomi is cloud-native with lower entry cost (~$550/mo Professional vs MuleSoft's $6K+/mo), faster learning curve (visual drag-and-drop vs DataWeave code), and 1000+ pre-built connectors. MuleSoft excels for API-led architecture and complex enterprise patterns. For 15 cloud apps with a small team, recommends Boomi for faster time-to-value. Notes Workato as another option for teams wanting automation-first ($1,500/mo). Result: User understands the trade-offs and has a recommendation matching their scale.

用户提问：“我们正在评估Boomi和MuleSoft以满足集成需求——15个应用，大多为云SaaS，团队共3人。” 技能处理：阅读平台指南中定价和定位章节。对比：Boomi是云原生平台，入门成本更低（专业版约每月550美元 vs MuleSoft每月6000美元以上），学习曲线更平缓（可视化拖拽 vs DataWeave代码），拥有1000+预构建连接器。MuleSoft在API优先架构和复杂企业模式方面表现更优。对于15个云应用和小型团队，推荐Boomi以更快实现价值。同时提到Workato是另一个自动化优先的选项（每月1500美元）。结果：用户了解各平台权衡点，获得匹配其规模的推荐。

Example 3: Process execution is slow under load

示例3：高负载下流程执行缓慢

User says: "Our Boomi process that syncs orders from Shopify to NetSuite takes 30 minutes during peak hours when we have 500+ orders queuing up." Skill does: Explains single-JVM bottleneck. Recommends: (1) enable parallel processing in the Process shape — set concurrent executions to match available CPU cores, (2) use batch processing with the Map shape to process orders in groups of 50, (3) if still slow, deploy a Molecule (clustered Atoms) for horizontal scaling. Also checks if the NetSuite connector is the bottleneck (NetSuite has concurrency limits — check SuiteCloud governance). Result: User has a scaling plan from process optimization to infrastructure upgrade.

用户提问：“我们将Shopify订单同步至NetSuite的Boomi流程在高峰时段（500+订单排队）需要30分钟才能完成。” 技能处理：解释单个JVM瓶颈问题。推荐：(1) 在流程形状中启用并行处理——设置并发执行数匹配可用CPU核心数；(2) 使用Map形状进行批量处理，每组处理50个订单；(3) 若仍缓慢，部署Molecule（集群化Atom）进行水平扩展。同时检查NetSuite连接器是否为瓶颈（NetSuite有并发限制——查看SuiteCloud治理规则）。结果：用户获得从流程优化到基础设施升级的扩展方案。

Troubleshooting

故障排查

"Process execution failed" with no useful error details

“流程执行失败”且无有效错误详情

Symptom: Process fails but the error message is generic — no stack trace, no field-level detail. Cause: Boomi's default logging level hides detailed errors. The Process Reporting view only shows high-level status. Solution: Enable "Document Logging" in the process properties (Process Options → Enable Document Logging). Check Atom logs directly (Setup → Atom Management → Properties → Logs). For connector errors, check the connector's operation log. Add Try/Catch shapes around error-prone steps to capture and log specific exception details.

症状：流程失败但错误信息通用——无堆栈跟踪、无字段级细节。原因：Boomi默认日志级别隐藏详细错误。流程报告视图仅显示高级状态。 解决方案：在流程属性中启用“文档日志记录”（流程选项 → 启用文档日志记录）。直接查看Atom日志（设置 → Atom管理 → 属性 → 日志）。对于连接器错误，查看连接器操作日志。在易出错步骤周围添加Try/Catch形状以捕获并记录具体异常细节。

Atom running out of memory during large data loads

大数据加载时Atom内存不足

Symptom: Process crashes or hangs when processing large files or high-volume batch operations. Cause: Single JVM heap exhausted — Boomi loads entire documents into memory by default. Solution: Increase Atom JVM heap in

atom.vmoptions

(set

-Xmx

to 4096m or higher). Use Flow Control shapes to batch large datasets (process 1000 records at a time). For very large files, use the Disk connector as intermediate storage instead of in-memory processing. Consider upgrading to a Molecule for distributed processing.

症状：处理大文件或高容量批量操作时流程崩溃或挂起。原因：单个JVM堆内存耗尽——Boomi默认将整个文档加载至内存。 解决方案：在

atom.vmoptions

中增加Atom JVM堆内存（将

-Xmx

设置为4096m或更高）。使用Flow Control形状将大数据集分批处理（每次处理1000条记录）。对于超大文件，使用磁盘连接器作为中间存储而非内存处理。考虑升级至Molecule进行分布式处理。

Connector working in test but failing in production

测试环境正常但生产环境连接器失败

Symptom: Integration works fine in development/test environment but fails after deployment to production Atom. Cause: Environment-specific configuration not deployed — connection credentials, environment extensions, or Atom properties differ between environments. Solution: Use Boomi Environment Extensions to manage environment-specific values (URLs, credentials, paths). Verify the production Atom has the correct extensions configured (Manage → Atom Management → Environment Extensions). Check that the production Atom's network can reach the target system (firewall rules, VPN, IP whitelisting).

症状：集成在开发/测试环境正常，但部署至生产Atom后失败。原因：未部署环境特定配置——连接凭据、环境扩展或Atom属性在不同环境间存在差异。 解决方案：使用Boomi环境扩展管理环境特定值（URL、凭据、路径）。验证生产Atom已配置正确的扩展（管理 → Atom管理 → 环境扩展）。检查生产Atom的网络是否可访问目标系统（防火墙规则、VPN、IP白名单）。