CC Platform provides an automated framework that configures RabbitMQ (RMQ) for you.

Integration requires one simple registration step (for receiving) and a standard send format (for sending).

Receive Messages (Direct or Broadcast)

To receive messages from CC Platform, you must register your adapter (application).

Step

Call the Adapter Registration API Adapter Registration Files - Overview

https://apim-abs-cc-[env].azure-api.net/drexadapters/apps

What you define in the request body

• Message type: broadcast, direct, or both

• Topics you want to receive (for broadcast)

• Adapter name and version

Adapter naming (IMPORTANT)

• Format: namespace:appName

• Allowed symbols: a-z 0-9 - . _

• Must be globally unique

• Recommended:

• namespace = client name (adv, cdp, erp)

• appName = adapter or microservice name

• Max length: 150 characters

What happens under the hood

After successful registration, CC Platform automatically creates and binds a queue:

q.cc.drex.inbox.[broadcast|direct].adapter.<adapter_name>

Example:

q.cc.drex.inbox.broadcast.adapter.test:testApp

Messages are routed to your queue based on topic and type(direct or broadcast).

Send Messages

To send messages, no registration is required.

Requirements

• The receiver must already be registered

• Send messages to the static exchange:

e.cc.drex.portal

You must set correctly

• Topic(broadcast only)

• Headers details

Make sure that you provided one of the 2 options:

• common-core tenant id

• GUID assigned by Common Core when tenant is created

• client_id and clienttenantid

• client_id

• GUID assigned by Common Core to client apps (adv, cdp, erp)

• clienttenantid

• Tenant identifier used in the client system

• Examples: guid.wcn, wcn, etc.

If these headers are correct, the message will be routed automatically.

Summary

Register once to receive, send anytime via e.cc.drex.portal to publish — routing and queues are handled automatically.