You'll need to analyze the requirements and limitations and design an overall approach based on them.
For example, you need to decide which AIF services to use, whether you need a kind of middle-tier service allow the systems to communicate and/or transforming the data and so on.
I would start by looking at the data and deciding whether it's suitable for AIF document services or not.
Then I would think about triggers - which system decides that data should be sent and when (e.g. on a schedule or an event).
Another important thing is whether the systems can access each other and communicate directly, and even if so, whether you want it. Maybe you want to decouple them by letting both of them communicate just with a common storage or message queues instead of directly.
You also need to decide what should happen if the other system can't be reached (e.g. because it's down for maintenance or there is a network failure). Will it block the source system? Will the messages get lost? Will the source system resend them later? Or should there be a middle-tier service that the source system can send the message to and the middle-tier service will handle reliable delivery?
Most likely, the two system won't use the same format of data. Who will do the transformation? Maybe you can use transformations in AIF, maybe you need to do it outside, who knows.
This should give you an idea about the overall architecture and you'll be able to start thinking about details.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.