How do the RadiantOne Synchronization Services work?
During the configuration of synchronization services, transformation scripts are customized to define how the data should be modified before the message is sent to the destination data store. Script templates are provided in RadiantOne. The transformation scripts will be executed inside the Synchronization Hub. You also have the ability to create Message Driven Beans (MDB) out of the transformation scripts and execute them inside of any J2EE-compliant Application Server (instead of using the Synchronization Hub). Executing the MDB inside of an Application Server provides better performance, security, and transactions. When there is a change in one of the data sources, the connector will be notified, format a message in XML and store it in the JMS message queue. The Synchronization Hub will receive the message, transform the data based on the Dynamic Java scripts, and store it in the message queue.
During the configuration of synchronization services, transformation scripts are customized to define how the data should be modified before the message is sent to the destination data store. Script templates are provided in RadiantOne. The transformation scripts will be executed inside the Synchronization Hub. You also have the ability to create Message Driven Beans (MDB) out of the transformation scripts and execute them inside of any J2EE-compliant Application Server (instead of using the Synchronization Hub). Executing the MDB inside of an Application Server provides better performance, security, and transactions. When there is a change in one of the data sources, the connector will be notified, format a message in XML and store it in the JMS message queue. The Synchronization Hub will receive the message, transform the data based on the Dynamic Java scripts, and store it in the message queue. The destination connector will be notified of the change, receive the message and apply t
