Disaster Recovery Specialist at Carelon Global Solutions India
Aug 23, 2024
In IBM Sterling File Gateway, automation primarily involves schedulers, which significantly transfer daily generated claim files to the end user. We ensure that the directory and files are up to date, particularly those placed in specific directories by the source. Processing can stop if someonechanges the directory without updating it in the SFG partner profile.
On the destination side, after setting up a partner file, we provide the end user with an MFT link, user ID, password, and a guide on uploading, downloading, and viewing files. Initially, we set up a primary password for them, and they can later change it to a preferred one for viewing their files.
This process ensures smooth file handling, but miscommunication regarding directory changes can lead to issues.
What I like best is that the tool is very secure and reliable. We can send huge files, even up to hundreds of GB. The automation depends on the source - it can be through automated processes, manual transfers, shell scripting, or file scripting. Partners can schedule batches according to their needs.
IBM Sterling File Gateway depends on a database, which can be a drawback compared to platforms where system resources are entirely controlled internally.
Based on my experience, there's some room for improvement. We're currently using version 6.1.1, which has a limitation where files are purged after seven days. We have to restart the purge count manually through our standard procedure. This issue should be resolved in the latest version.
