Retina Migration - SMDS CMD
In the current context, the SMDS CMD has successfully implemented C2G replication across all topics. The SMDS CMD initiates the publication of messages to the V3 topic, which are then ingested by both event cloud consumers and the on-premise CMD application. This setup ensures compatibility with the existing MQ broker, maintaining a seamless flow of information.
During the initial migration phase, the cloud topic will undergo replication onto RETINA, ensuring synchronization of offsets. As a result, cloud consumers will have the flexibility to access content through either the V3 topic or the RETINA topic. The CMD will exclusively channel data publication to the V3 topic, ensuring the ongoing stability of the current CMD arrangement remains unaffected.
In the subsequent migration phase, the transition will encompass the complete migration of C2G topics to the RETINA platform. SMDS CMD will exclusively dispatch messages to the RETINA topic, and consumers are required to exclusively subscribe to the RETINA topic for data consumption.
Topics in scope :
| MSK.commercial.customer.topic.internal.any.v3 |
|---|
| MSK.commercial.concern.topic.internal.any.v3 |
| MSK.commercial.customerFacility.topic.internal.any.v3 |
| MSK.commercial.notification.topic.internal.any.v3 |
| MSK.commercial.contact.topic.internal.any.v3 |
Important Links :
- Migration plan and Retina features: https://docs.retina.maersk.io/
- Tenant Guide for Producer : Producer Tenant :: RETinA Docs (http://maersk.io )
- Tenant Guide for Consumer: Consumer Tenant :: RETinA Docs (http://maersk.io )