What is our primary use case?
Our business is, as far as corporate computing goes, is IBM i-centric. Because of that, some of the main use cases for the GoAnywhere product are for uploading data into the IBM i, from our finance department and other departments, and downloading data from the IBM i to a user or to our FTP server to be sent to a business partner. And when it comes to downloading data for users, it's typically in the form of Excel reports.
At this point, we are only accessing resources within our organization. We don't reach outside of our organization, even though the solution enables interaction with many things, such as Amazon and Google. The exceptions to that are one or two processes that do reach out to a business partner by way of SFTP.
How has it helped my organization?
One of the things GoAnywhere can do for us that our previous product could not is error handling. If something doesn't work properly, we can be alerted to that fact and act on it more quickly, versus the old product.
The workflow features eliminate the need for custom programs and scripts for file transfers. They simplify activities surrounding the movement of data. There is a concept within IBM i of normal tables and an aspect referred to as the integrated file system or IFS. Our older processes would typically create data in a table and run special commands that might make it troublesome to copy that data from the table to the IFS. From there, the old product would grab it from the IFS and send it to some other server. Now, we can eliminate that step of having to bother with the IFS, since GoAnywhere can reach directly into our tables. It's one more aspect of this product that helps simplify these sorts of tasks. When users say, "I'm building spreadsheets that I would like to be uploaded on a regular basis into the IBM i," we are able to accommodate that request within a matter of hours rather than the days it would take to create programs to do that. That is very useful. It has eliminated several dozens of scripts for us.
And when it comes to file uploads into the IBM i, this is only a guess, but it has saved us on the order of five hours per week.
We're able to craft solutions to little challenges faster, and that makes us more productive. One of the GoAnywhere projects that I was just helping a person with yesterday was updating an old program that produces a report for a user. I helped her create an SQL view and then make use of that view with GoAnywhere, which now emails a simple spreadsheet to the user. She was able to accomplish that in a fraction of the time it would have taken to modify the original program.
Additionally, the workflow features have helped to eliminate manual processes. One example is an upload process that is being done regularly by the payroll department. It typically involved a little more manual activity on the part of our payroll user to get us the data. Whereas now, with GoAnywhere, we are able to create something using what GoAnywhere calls a Secure Form. It enables us to present a very quick, very rudimentary webpage to the user where they do a few clicks and the file is provided to us. That is in contrast to their having to take the file from their desktop, find the network share that they're supposed to copy it to, followed by calling us to say they've copied it over there. It makes it easier for users to do things on their own, once we've created that ability for them.
What is most valuable?
One of the most valuable features is the ability to reach into our database tables on the IBM i, and other platforms, and extract data. That is most useful for us.
It's also easy to use. I was training somebody yesterday on some of the finer points of GoAnywhere, and she found it very easy to interact with and understand. We like the interface.
The workflow features are very comprehensive, from our point of view. GoAnywhere uses the term "project" for a job that we create within it. The projects can be run from our IBM i CL [command language] programs. They can be scheduled within the GoAnywhere Scheduler to run once an hour or whenever we need them to run. A process can also be triggered by a file showing up. It is robust in terms of how the GoAnywhere projects can be invoked.
What needs improvement?
It doesn't need much improvement, other than tiny idiosyncrasies. I've run into one or two things for which I've put in change requests to the software developers at GoAnywhere, but they are very minor things, the types of things that don't come up much. We've created in the neighborhood of 80 to 90 projects in GoAnywhere and, out of all of those, there have only been a couple where we've run into something and that made us say, "I wish they could improve this little thing here."
For example, when it comes to interacting with files, there is a function referred to as write CSV, to write a general text file. In this scenario of creating a simple text file, I ran into a situation where, if the product saw a quote or a double-quote in the data, it started wrapping all the text fields in double-quotes. The request I put in asks them to provide a feature that leaves my data alone and does not interpret anything. If I don't want double quotes, please don't put them in. It should have the option, on certain write CSV operations, of not inferring anything.
For how long have I used the solution?
We have been using HelpSystems GoAnywhere MFT for about a year.
What do I think about the stability of the solution?
It seems pretty stable. Like other Windows platform solutions, every once in a while the Windows platform needs to be rebooted, but otherwise it has been very stable.
What do I think about the scalability of the solution?
Scalability has been a non-issue for us. It seems like we could double or triple the number of projects we've got, which might happen over the next five or 10 years. We do not expect any issues with the scalability.
We don't have any plans, per se, to increase our usage of GoAnywhere, but something that we haven't talked about is another product we have that is going to have some competition from GoAnywhere. This other product, which I believe is owned by HelpSystems as well, is a reporting tool called Sequel Viewpoint. I've used it in a similar fashion to the way we use GoAnywhere: A user needs a report and I create an SQL view, go into Sequel Viewpoint, make use of that view and output a PDF or Excel document, and email it to the user. Doing the same thing in GoAnywhere is easier.
It's not so much that there are any specific plans for increased usage, but those types of tasks just come up from time to time. When a user in our finance, buyers, or our supply chain and planning department needs some data from our system, we have a solution for them very quickly using GoAnywhere to produce a simple Excel report.
How are customer service and support?
The technical support has been fine. It has been useful each time we've reached out to them, unless we find a little bug, like the one I mentioned where the product had decided on its own to put double quotes around all of the text fields. Short of little idiosyncrasies like that, they've been able to solve problems for us.
Which solution did I use previously and why did I switch?
We migrated off of a very rudimentary product that was little more than a file moving product. It was "garage software," meaning it was made by a very small organization. It was called Second Copy. It could move or copy a file from one server to another within the same file system, but it was very basic. There was no error handling, no ability to deal with FTP and IBM i, HTTP, databases, Amazon, and Azure. All those capabilities were nonexistent in Second Copy. GoAnywhere is like a Ferrari versus a Volkswagen Beetle. Our old product was a single-function tool, and GoAnywhere helped us to eliminate it.
How was the initial setup?
The initial setup was fairly straightforward except for one feature, which was an integration to the IBM i. As luck would have it, we've never actually ended up using that feature. It's what is called setting up an agent on the IBM i, and that took a bit of work with one of their tech support people. That allows for a little tighter integration with the IBM i when the product has been installed off of the IBM i. In our case, we installed the product on a Windows Server, as opposed to the IBM i itself. We figured that if we make use of the agent, it might give us a little better integration. Now, eight or nine months later, we've never made use of that IBM i agent. What made adding that agent complex was due to the nuance. The instructions were not clear enough and I was not able to do it by following instructions in the manual.
Not counting that agent, we had GoAnywhere up and running on the same day that we started installing it. The agent was just an add-on, and that dragged on for a few more days with interaction back and forth with their tech support.
We were replacing an existing product. Our implementation strategy was a matter of setting up GoAnywhere and doing a couple of pilot projects to see how easy it was and how it worked. We then started the process of converting 70 or 80 tasks out of the old product, slowly but surely, into the new product. That was doled out to half a dozen developers who looked at the existing tasks and implemented something similar, and/or better, in GoAnywhere.
Our user community for GoAnywhere is relatively small at the moment. We are a medium-size retail business. Our corporate headcount would be somewhere between 400 and 500 people, and the total headcount within the company is 1,100 to 1,200 people, including stores and warehouses. Out of all of them, there are just a handful of departments that we interact with a lot. Our finance and our planning/supply chain departments are two of our major users among our user community of about a dozen users.
As for maintenance of GoAnywhere, our IT department has three groups: web development, back office development, and technical support. This product can be used by, and of value to, all three IT groups. It is almost exclusively used by just the back office department, which I'm part of. Our focus is the IBM i, versus our customer-facing web pages which are handled by our web development folks. In our back office group, we've got about 20 developers and any one of them can do a project in GoAnywhere. We don't have anybody dedicated to maintaining the product. As a task comes up, somebody gets assigned to do it and takes care of it.
What about the implementation team?
We didn't use a third-party. It was a straightforward install for the most part.
What's my experience with pricing, setup cost, and licensing?
The cost of GoAnywhere versus the value it brings to our data transfer operations is reasonable. When I compare it to what we were using, that product called Second Copy, and how robust it is and how productive we can be with it, the cost is commensurate. The cost is relatively expensive but, back to the car analogy, that's to be expected with a Ferrari.
They provided a variety of options for pricing. "If you want just this basic feature, here's the price. Or you can have this add-on and that add-on." That variety of add-ons is useful because we are not using it to its fullest capabilities. Some of those other capabilities are licensed extra options.
One of the extra add-ons that came to our attention that we ended up purchasing, and that has provided value and will continue to provide value, is the Secure Forms. We use them to very quickly provide a web page interface for a user to make file transfers easier for them. It's also very useful when there's a report that they need but we need some input from them to produce it, like the date range of the data they want to see, or the particular stores they want a report for. Secure Forms are an extra cost and we went for that extra cost months after buying the initial product. We started with not much in the way of extras, and then added onto the product.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.