So it’s been a busy week, it feels like Friday, but it’s only Wednesday. Weird, eh? It’s been very productive though. We managed to get integrator and gateway health assessments done for our production environment. I stayed up all night to work with support in France for the Synchrony Gateway 6.9.1 check, and then continued into the morning to work with PSO on our Synchrony Integrator 2.1.0 check. Between the tuning and optimization recommendations with reliability and scalability in mind, and the bug fixes we still need to implement, I think I’ll continue to be pretty busy!

I am in dire need of sleep, so this will be a short post, but I wanted to talk a bit about Synchrony Transfer, and how cool it is! We finally got an instance installed and configured on one of our composer boxes, and configured it to talk with our External gateway. The configuration was semi-complicated, but with a bit of explanation it becomes pretty simple. It’s got some really cool capabilities for adding/changing config stuff without having to bounce the process.

The coolest thing about Synchrony Transfer though, is that in the right environment it can be an incredibly powerful tool, and help provide a greater level of oversight on internal file transfer because sentinel can monitor the files as soon as transfer starts talking to gateway. As an example, take an environment where a mainframe system is generating files that are being sent in batches by a cronjob or other scheduler. What would typically happen is that the mainframe jobs would generate files, and then at the scheduled intervals the cronjob would send the files over to Gateway. If Transfer was set up to communicate with Gateway, the directory where the Mainframe system was generating the files could be mounted on the Transfer box, and transfer could monitor the directory in real time and send the files to Gateway with no delay, and increased visibility.

Can’t wait to dig further into it!

Tony