This approach doesn’t need to use the ATG Integration Framework. In this case, we periodically dump data from the remote system into the relational database used by the ATG application. The data is accessed by the SQL repository. Since this approach doesn’t need to issue commands against the remote system in real time, there doesn’t need to be an Integration Repository.
Advantages:
ATG’s performance is as fast as possible.
The only interaction with the remote system is a periodic batch data transfer, which probably can be scheduled to place a minimal burden on the remote system.
Disadvantages:
The local repository is not updated in real time, so any changes in the remote system are reflected in the local repository and therefore in your Web application only after the scheduled data transfer.
