What is our primary use case?
We have a lot of different files that we need to move from in-house to a vendor. While our online banking configuration is real-time, we upload files every morning to cover some aspects of that online banking. Customers also send us files and we pull them off of our secure servers and push them on to our core application vendor. In summary, our use case is almost entirely secure file movement: making sure a file gets from here to there.
We're running this as a cluster with four Linux platforms, two at our on-site and two at our co-location site. Always live.
How has it helped my organization?
Our web development team wants to do source code management for change control of our executables. They are working right now on setting that up. GoAnywhere is the resource that handles movements from test to acceptance, and from acceptance into production. The reason we do that with GoAnywhere is that its logging capabilities, of all of the actions that have been taken, are exquisite, in my opinion, and I've been working in core for 40 years. If anybody wants to know if something did or didn't happen, I can point at a specific line in a job log that says yes or no.
It has also centralized the exchange of data. We used to use an iSeries to run our core operations. There was a job scheduler on it, and we used that to invoke certain GoAnywhere jobs to do motion. Since then, we've converted off of the iSeries, and because GoAnywhere can run on Linux or Windows platforms, we didn't need to do away with it. We could just move it. And we could also move some of the scheduling that we still had to do off of the Series and have GoAnywhere's job scheduler handle it for us. And that's what we did.
We used to use two or three other scripted FTP processes in Robo-FTP, where the operator would double-click on an icon on a desktop to do something. Those all got moved into GoAnywhere.
And its workflow features have very much helped us to eliminate manual processes. That has made our operations a lot smoother. We've had some staff changes. One of those staff changes necessitated our automating a bunch of functions and we're doing so and continuing to improve that automation. In addition, the automation of file transfers has helped to reduce workload by about one-third to one-half of an FTE.
In terms of handling more documents, we set up a lot of file transfers to the core application server of documents created in our bank's branch system. GoAnywhere supported all of that.
All of our internal, as well as external file transfers, are secured now, and GoAnywhere is what was used. We used GoAnywhere when we created the external servers to go from FTP to secure FTP and GoAnywhere supported that transition really easily. We were able to get rid of one internal FTP server after we did that.
What is most valuable?
The workflow features eliminate the need for custom programs and scripts for file transfers. It handles a lot of different things. We have gone into database programming, to some extent, with a few of our transfers that require a bit of translation between how they are when we pick them up and what they need to look like for where we send them. I'm looking forward to using that ability a little bit more.
Another nice feature is that you can invoke a native program from GoAnywhere. That helps you because you don't have to get fancy with agents. If a native program runs on the server that GoAnywhere is running on, like sed or perl, you can use it,
The intuitiveness of GoAnywhere's user interface is pretty good. The nature of job scheduling is that it can sometimes be really intricate, and difficult to see and understand. We've had learning on it, but the main person who supports it for us digs in and finds documentation that explains how to go about things. We'll then run some test jobs to make sure it works the way we think it's going to, and then we'll use it. In general, it's very intuitive.
What needs improvement?
When it comes to GoAnywhere's workflow features, there are a couple of areas where I'd like to get a little more consistency. The two aspects of scheduling that we use are scheduled jobs and monitors. And there's cross-capability between the two. We've done some philosophical thinking about when a function should be handled by a monitor and when it should be handled by a scheduled job. When a monitor invokes a project to accomplish something, that gets logged as a job. I've had a little difficulty figuring out where to look to see the monitor's activities itself, to see if the monitor is having a problem.
For instance, if an account on a secure FTP server has expired, the monitor that uses that account doesn't announce to us that it's having a problem. I want to work with them on this to get it fixed.
Another aspect would be greater visibility into exactly what's happening. But part of that is because we haven't learned how to look at it. I still need to establish some training for my people who support this. We've learned a lot and done a lot with the documentation, which is pretty good, but some formal training would really help tie together a lot of the little tidbits of knowledge in our heads.
For how long have I used the solution?
We have been using HelpSystems GoAnywhere MFT for eight to 10 years.
What do I think about the stability of the solution?
I don't believe it was any fault of HelpSystems, but the service did stop working for a couple of hours one time. I need to check with them and see if there's a way to restart that says, "Go back and pick up the stuff that didn't run." In this particular instance, the number of things that didn't run was small enough that I could manually look at the schedule screen and figure out what needed to be run. Still, I'm wondering if there's a button I could have pushed that would have taken care of all of that automatically. If that's not a feature they have, that might be something they should implement.
What do I think about the scalability of the solution?
Aside from supporting the occasional new needs, we don't have plans to increase our use of GoAnywhere.
How are customer service and support?
Their tech support is pretty good in responding to us and in helping us to work through any issues that might crop up.
At times we've had some difficulty getting a point across, but I won't assign 100 percent of the responsibility for that to them. Sometimes we won't phrase things correctly. But they don't run away from us. They stick to it and figure out what's going on.
How would you rate customer service and support?
How was the initial setup?
I didn't do the original deployment. It was done by some engineers who reported to me, and then our web developer did the current implementation of four Linux servers. But the original setup was pretty straightforward.
I have one guy who supports the servers but he rarely has to do anything on them. I also have one web developer who manages all of the jobs. It works out to 1.25 FTEs and that's because they're always looking at ways they can make these projects work better.
What was our ROI?
GoAnywhere pays for itself easily. It has saved us work and enables us to sleep through the night.
What's my experience with pricing, setup cost, and licensing?
They were open-minded and they did what they could for us, in terms of cost, when we made the transition to GoAnywhere.
And when we migrated from the iSeries to Linux servers, HelpSystems carried forward the startup money that we spent when we originally installed GoAnywhere on the iSeries. We did not have to pay startup fees on the Linux servers. We got credit and that was nice of them.
Which other solutions did I evaluate?
GoAnywhere was on our radar before we got it. We knew of other options, but after seeing the demo for GoAnywhere, we saw that it does what we needed. I did do a small business case for it that included an examination of other options, but that was a long time ago.
What other advice do I have?
I'm fond of this tool. I don't know how much of an opportunity I'll get to explore other aspects of GoAnywhere's services, but I like what it's doing for us.
I would 100 percent recommend GoAnywhere to someone else who is looking for solutions in this area.
Which deployment model are you using for this solution?
On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.