7. Service Inventory & Glossary¶
This is the quick roster — topology is the source of truth
Use this page to learn the naming and find a service fast. For authoritative deployment status — which services are live, retiring, or nonprod-only, and how they wire together per environment — see Camel Topology.
The cm-* services, by layer¶
Experience (-exp) — face the callers:
| Service | Purpose |
|---|---|
cm-fulfill-exp |
Fulfillment REST API (experience layer) |
cm-int-service-exp |
Internal service experience layer |
cm-ext-service-exp |
External-facing experience layer (e.g. Cirro webhooks) |
Process (-prc) — own a domain, orchestrate:
| Service | Purpose |
|---|---|
cm-order-prc |
Orders → Cirro B2B/prepack, ship-confirmation routing; consumes the NAV order-release queue |
cm-edi-prc |
EDI 850/940/856/945 processing; SPS/PS SFTP polling |
cm-fulfill-prc |
Fulfillment processing, AES decryption, Cirro forwarding |
cm-product-prc |
Product data sync processing |
cm-batching-prc |
Batch processing |
cm-int-service-prc |
Internal service processing layer |
System (-sys) — thin adapters to one external system:
| Service | Talks to |
|---|---|
cm-cirro-sys |
Cirro (pure pass-through + Bearer auth) |
cm-osor-sys |
OMS (order sync / release acks) |
cm-int-service-sys |
Internal system layer — also carries the NAV SOAP / page calls |
cm-sfcc-sys |
Salesforce Commerce Cloud |
cm-product-sys |
Arena PLM |
cm-jackyun-sys |
Jackyun / KH China fulfillment |
cm-snowflake-sys |
Snowflake |
cm-printprod-sys |
Print production system |
cm-nav-sys is a legacy stub — don't start there for NAV
A cm-nav-sys module still exists in the repo, but it's a husk (no routes,
undeployed). NAV integration actually lives in two places today: outbound NAV
SOAP/page calls run through cm-int-service-sys, and the NAV → OMS
order-release path is consumed directly by cm-order-prc. See
Camel Topology and
NAV Order Release.
Infrastructure / utility:
| Service | Purpose |
|---|---|
cm-spring-cloud-config-server |
Serves per-environment config to every service |
cm-file-transfer |
File-transfer utilities |
Glossary¶
| Term | Meaning |
|---|---|
| EDI | Electronic Data Interchange — standardized documents exchanged with retail partners |
| X12 | The EDI standard whose transaction sets are numbered (850, 940, …) |
| 850 / 940 / 945 / 856 / 810 | PO / Warehouse Ship Order / Ship Advice / ASN / Invoice |
| ASN | Advance Ship Notice (the 856) — "here's what's shipping to you" |
| SSCC | Serial Shipping Container Code — barcode ID for a carton/pallet |
| SKU | Stock Keeping Unit — a specific sellable product |
| BOM | Bill of Materials — what a product is made of |
| OMS | Order Management System |
| ERP / NAV | Enterprise Resource Planning system; ours is Microsoft Dynamics NAV |
| 3PL | Third-Party Logistics — an outside warehouse (Cirro) |
| PLM | Product Lifecycle Management — ours is Arena |
| SFCC | Salesforce Commerce Cloud — the storefront |
| DTC | Direct-to-Consumer (vs. B2B/retail) |
| SB | Azure Service Bus — the async message backbone |
| DLQ | Dead-Letter Queue — where failed messages land |
| APIM | Azure API Management — the sync HTTP gateway |
| AKS | Azure Kubernetes Service — where services run |
| Config Server | Spring Cloud Config Server — central per-env configuration |
| Route | A Camel processing pipeline (from → … → to) |
| EIP | Enterprise Integration Patterns — the patterns Camel implements |
| DTO | Data Transfer Object — a plain data-shape class |
| Actuator | Spring Boot ops endpoints (health, route control, env) |
| ShedLock | Library ensuring a scheduled job runs on only one pod |
| exp / prc / sys | Experience / Process / System — the three service layers |