Anaplan Data Orchestrator (ADO) - AMQP Connector

Pierre.

We have implemented a event driven architecture in order to interface our application (including Anaplan) in "close to real time".

However, the Advanced Message Queuing Protocol (AMQP) is not supported for the time being by ADO, which forces us to use an additionnal middleware.

This would allow us to implement a seemless integration of Anaplan with our event messaging backbone and to significantly reduce the Total Cost of Ownership of Anaplan solution.

brownmack

It sounds like you're looking to integrate Anaplan into mcdvoice your event-driven architecture but are facing limitations with AMQP support in ADO. Using additional middleware could streamline this integration and reduce the Total Cost of Ownership for your Anaplan solution.

Guillaume.Auger

Hello Brownmack,

You are right we could use an additional middleware to transfer EDA messages to ADO, but it would add complexity in the integration with additional cost, compared to a direct integration from our Message Brooker (SOLACE: Advanced Event Broker. An event mesh for connected enterprises | Solace) to ADO.

That's why we would prefer an AMQP connector directly available in ADO.

FrankPau

Hello, everyone, from what i know and ot's written here: https://community.anaplan.com/discussion/33552/oeg-best-practice-imports-and-exports-and-their-effects-on-model-performance historically in Anaplan Imports are blocking operations.

How this issue work with ADO? Still the same case? Thank in advance for your help!

@Pierre. @Guillaume.Auger

Guillaume.Auger

Hi @FrankPau,

My understanding is that ADO is not based on Hyperblock technology, data are not stored in an Anaplan Model but in the ADO database. So you can replace existing Anaplan Data Hub by ADO to integrate data and transform them, without blocking operations. However, once the data are ready in ADO, you will still need to transfer them from ADO to the Anaplan spoke models, then it will still block the operations during this transfer.