Tuoling 驼铃 · the camel bell — powered by the LightESB engine

Runnable integration delivery package

Make existing systems work together — without starting over.

LightESB connects old applications, factory equipment, robots, and AI tools. It translates data, checks access, records every step, and delivers it where the business needs it.

  • Keep the systems that already work
  • Start with one small integration
  • Run privately or at the edge

Brand film

Tuoling in three minutes

Five real pain points, one platform. See how Tuoling connects legacy systems, industrial devices, robots, and AI tools into one governed flow.

Keep what worksConnect existing software instead of forcing a full rewrite.
Bridge the fieldBring APIs, databases, industrial protocols, and robot workflows together.
Stay in controlValidate access, trace activity, diagnose issues, and manage delivery.
Start smallUse a working example for one integration, then reuse the pattern.

Why it exists

Modernize integration without rewriting core systems

LightESB-Camel helps teams wrap existing systems with route services, protocol adapters, validation, logging, and operational controls. It is small enough for private or edge deployment and structured enough for repeatable POC and delivery work.

Legacy systems

Connect what already runs

Expose or consume HTTP APIs, databases, message flows, ERP interfaces, and internal services through Camel XML routes and configuration.

Industrial protocols

Bridge field systems

Use examples and documentation for OPC UA, MQTT 5, Modbus/PLC paths, AVEVA Plant SCADA, SAP NetWeaver, and ExternalDB access.

Robotics and AI

Govern high-level orchestration

Coordinate task intake, telemetry normalization, command validation, audit events, and AI Agent + Tools workflows outside hard real-time control loops.

Delivery model

A public repository that can be read, copied, and validated

The delivery context contains runtime files, documentation, examples, skills, and this static website. The source repository remains the editing authority; the public delivery repository is generated by sync scripts.

1

Pick an example

Start from example/routes and choose the closest integration pattern.

2

Adapt config

Set service properties, endpoints, protocol targets, and validation rules.

3

Load route

Deploy the service package and use hot loading where the runtime boundary allows it.

4

Verify behavior

Use curl, CLI commands, diagnostics, and service logs to prove the route works.

5

Operate safely

Use deployment APIs, audit patterns, and rollback guidance for controlled delivery.