User Guide : Best Practices : Common Integration Techniques : Time Zone Considerations
Share this page             
Time Zone Considerations
You must plan for handling differences in the time zones. The end-points to which you are connecting can be in different time zones from each other. Additionally, the DataConnect Runtime Engine that is running the integration can be in a different time zone than one or more endpoints.
Business logic errors in the workflows or transformations caused by these inconsistencies are hard to detect and can even lead to missing data. Make sure that all components of the overall solution are in sync or use the scripting language to transform the date and time values accordingly.
Important Date Functions
Make sure that you align the time zone of the integration runtime environment with the integrated systems and use the appropriate functions to standardize them. Once you decide on the policy, you must conform to it.