Publish historical data

Due to the synchronous nature of data in an event-oriented architecture, you can only keep data in sync after your application is integrated with ION.

You may need to consider how to share historical data with downstream systems that are interested to receive. This concerns the data which may not be amended in your system anymore. We recommend that you provide a facility to publish historical data when the application is ION-enabled. For example, driven by end users at time when required. This can happen more than once due to online offline deployment.

To keep the consistence of message ID and variation ID your system must publish BODs after historical data is published.