12
MUnit tests
Back to projects
Enterprise integration
Cham Orders Mule Integration
MuleSoft integration that synchronizes confirmed orders from Cham Orders API into a canonical downstream JSON format.
Locally verified Release Candidate
Project overview
Context and approach
Overview
Cham Orders Mule Integration is a synchronous MuleSoft case study that retrieves every confirmed order page and converts the result into one canonical downstream JSON file.
Problem
A downstream consumer should not depend directly on the backend's authentication flow, pagination mechanics or internal response shape, and the integration must preserve traceability across every call.
Solution
An APIKit operation authenticates against Cham Orders API, traverses pagination sequentially, validates response metadata, maps historical order data with DataWeave and writes a canonical file with the same correlation context.
Key figures
66.28%
Application coverage
100%
order-sync coverage
2 pages
Real pagination proof
Architecture
- 01
API Client
POST /api/v1/order-sync with optional correlation ID.
- 02
APIKit
RAML routing and request validation.
- 03
Order sync
Authentication, orchestration and sequential pagination.
- 04
DataWeave
Canonical order transformation and validation.
- 05
JSON file
Local output simulating downstream ERP delivery.
Main capabilities
- POST /api/v1/order-sync through APIKit and RAML.
- Authentication against Cham Orders API with Bearer token propagation.
- Complete sequential pagination with configurable page size.
- DataWeave canonical transformation using historical item data.
- X-Correlation-ID propagation or generation.
- Centralized errors and externalized local credentials.
- Canonical JSON output generation.
Verification evidence
- Local Mule deployment passed.
- Real authentication and confirmed-order synchronization passed.
- Real two-page pagination passed with pageSize 1.
- Canonical JSON output was generated and reviewed.
- Authentication failure and unavailable backend scenarios passed.
- 12 of 12 MUnit tests passed.
- order-sync.xml coverage reached 100% and client coverage 95.65%.
Engineering decisions
- — Pagination is sequential and validated against backend metadata.
- — The complete result is transformed once into a canonical model.
- — Credentials remain external to source control.
- — Correlation IDs cross the inbound request, backend calls and output.
- — The implementation stays synchronous for a bounded local portfolio scope.
Scope limitations
- — No CloudHub or production deployment.
- — No real ERP integration; the JSON file is a simulator output.
- — No queues, persistent idempotency, scheduler or advanced retry policy.
- — No CI/CD execution or high-availability claim.
Review the implementation
Source code, documentation and reproducible local instructions are available on GitHub.