Sign in ☰Common Core / DREX-M
DREX-M (Data Remote EXchange for Messages) is the messaging backbone of the Common Core platform.
DREX-M lets your application (will be called Adapter going forward) publish and consume data across three deployment tiers:
Tier | Typical Location | Purpose
Site | Vessel, branch office | Collect local data; sync with a designated Central
Central | Customer-hosted or ABS-hosted hub | Source of truth; mediates all Site-to-Site and Site-to-Cloud traffic
Cloud | ABS Wavesight multitenant cloud | Company-wide SaaS and analytics services
Adapters interact with Drex exclusively through RabbitMQ - no special SDK is required, though we provide Service-Bus Libraries for .NET and Java to simplify header management and reconnect logic.
Why use Drex?
Unified API – One exchange (e.cc.drex.portal) for both direct and broadcast messages.
Per-adapter queues – Each adapter receives its own direct, broadcast, and (optional) feedback inbox.
End-to-end security – TLS by default between tiers; certificate handling automated by the installer.
Language-agnostic – Any AMQP-compatible client works.
Pluggable libraries – Official .NET and Java packages accelerate development.
Quick Links
First Steps | Reference | Operations
Getting Started – terminology & onboarding checklist | Message Headers Reference – required/optional headers | Installation Overview – what integrators need to install Central or Site
Developer Quick Start – code snippets & test docker-compose | Adapter Registration Files – JSON schemas & examples | Troubleshooting Guide – common issues & fixes
Messaging Patterns – Direct, Broadcast, Feedback | Cloud Adapter Registration – Cloud Adapter API | Release Notes & Changelog
Security & Certificates – TLS overview & rotation
Typical Flow at a Glance
!Site to central.png!Site or central internal.png
Additional Resources
API Documentation:
Service Bus Library:
Broadcast Examples: