IBM Sterling File Gateway Reviews

The solution was used for file transfer without any translation or transformation. We were pushing whatever files that were coming into the source. In the earlier project, we used the managed file transfer. It was a part of the process. The major part was translation using IBM map editor, the trained partner set up map creation. We had the MFT (Managed file transfer) as a minor part.

We did not encourage much customization. We had a standard role where the source would place a file in the mailbox, and we recommended using the destination mailbox prefix. Our business process was written in a way that when it finds the destination mailbox name fixed, it picks it up and sends it to the exact destination. We had IBM Sterling File Gateway in place for that.

One feature that we appreciate or use for multiple customers is the routing channel. We can provide particular instructions to the file gateway on routing the files. It was limited in the earlier project, and we had a defined custom web. However, not all projects would be on the same web. We can have different channels created or designed for each partner depending on their requests.

The tool would be new to a fresher who won't understand anything without experience. The solution should provide content or videos explaining to freshers how to configure it and what every field means.

When we have SFTP communication, where we need to link a communication channel with a protocol like SFTP, we first have to configure the SFTP connections in IBM's dashboard. Then, that would be listed in IBM Sterling File Gateway. We had to remember the exact name we had provided in the dashboard. Otherwise, we had to scroll and check everything, which was pretty difficult.

If a project had over 200 SFTP connections, we had to go through all the protocols and see where that exact SFTP name was located. This probably could be one area of improvement.

I have been using IBM Sterling File Gateway for five and a half years.

IBM Sterling File Gateway is a stable product, and we didn't encounter many bugs. It was also easy to track the issues. In case of a failure, we can check the logs and see where it exactly failed. We can also track at which protocol or step it was able to connect to the server and whether it failed during the write.

In my previous organization, around 20 projects used IBM Sterling File Gateway.

Deploying the solution in different environments, such as development, testing, and production, was pretty easy.

The solution's pricing is reasonable. IBM Sterling File Gateway is worth the money. The licensing cost is the only cost involved. Whenever customers ask for access, we do not provide them with read and write access. They would not have admin access. They would just have read access to see the file flow, which does not come under license.

I would recommend the solution to other users because it is a good tool for file transfer, where even customers can access or view the file flow.

If there is a communication we need to create between the source and destination, it's pretty easy to have it synced and created with the routing channel. The tool creates trouble when pointing out the SFTP connections. It is difficult for a beginner to understand the solution.

Overall, I rate the solution an eight out of ten.

I use Sterling File Gateway to check the routing status of files - if they're failed or successfully translated to the consumer. Mainly, we create trading partners using Sterling File Gateway, with different protocols and create routing channels to send files between partners. 

We need routes between these partners. So, using Sterling File Gateway, we create these routes using templates. We can also check the status of the file there. If a file fails, we can see where it failed and in which process it's getting stuck.

During my engineering studies, I had never heard of Sterling File Gateway. However, after joining my first company, I received training on Java and other technologies and was then assigned to work with Sterling File Gateway. The company provided a 15-day training session to help me understand the product. 

Once I started learning Sterling on my own, I began creating trading partners and establishing flows between them. It didn't take long to understand the system. Even someone without a technical background could easily learn Sterling File Gateway. It's a very helpful and user-friendly tool.

I like its ability to communicate in B2B scenarios. We can act as either the producer, sending files to the consumer, or as middleware between trading partners, collecting files from one and sending them to another. Sterling File Gateway enables us to create this communication and act as a middleware.

Sometimes, for example, when using the SFTP protocol, we need Sterling B2B Integrator to create the remote protocol. As you know, if you use SFTP, SDC is the binding agent, so we also need to check with the AS2 File Gateway and AS2 Integrator to create the SSH profile. If we could create the SSH profile directly in Sterling File Gateway, that would be an improvement.

Also, when creating a trading partner, we have the feature to create a producer as an initiating producer. But we don't have an option for a Sterling producer in the File Gateway. We need REST APIs or other tools to create that listening producer. If we could get that feature in Sterling File Gateway, that would be more helpful.

I have been using it for three and a half years. For the first one and a half years, I worked on the cloud-based version. Now, I use it on on-premises.

I use the version 6.1.2.

Most of the time, I don't see any bugs in Sterling File Gateway. In Sterling File Gateway, you have the B2B console option. In B2B, we have different instances where we can see most of the things. 

Suppose we get notifications on the homepage; sometimes, if you don't clear those notifications, it can cause performance issues in the application. So, sometimes, I face issues accessing the dashboard.

As a developer, it's really scalable to use. In my company, I previously worked on some DGMSs. In that, I didn't see many large projects. I saw two or three projects related to IBM Sterling Integrator. 

Most clients now use EDI. In EDI, there are different tools, like Cyclone, GlobalScape, and Dell Boomi. Some use Sterling File Gateway or Sterling Integrator, while others use different tools for B2B communication using these kinds of protocols. So, out of ten people, only two to three use Sterling File Gateway or Sterling Integrator.

Most of the time, we face some issues. Sometimes there are errors that we don't understand, file-related, backend things. As a developer, I work on the frontend part. But sometimes, I see in the backend that there are issues if someone installs any JDK or SDK. Suppose there's a bug or something in that SDK; we need steps for proper installation. In those cases, we raise an IBM case and contact them for help.

It's not difficult. Even a non-technical person can learn Sterling File Gateway within two or three weeks. It won't take more than that. The GUI is really handy.

I've heard also that maintaining Sterling, whether it's cloud-based or on-premises, requires more resources compared to other tools.

I would give it a nine out of ten. I've been working with it for the past year, primarily on the development side. On-site teams often give me four to five days to create flows, but it's a very easy tool to use. It usually only takes me four to five hours to complete a task. Once you understand how to use Sterling File Gateway, it becomes even quicker to work on other tasks.

We use IBM Sterling File Gateway to transfer files from a source to a target. This involves creating producers, consumers, channels, and templates to facilitate the file transfer. In Sterling Integrator, we implement business processes to define how a particular file should be picked up, the file filter format, and the protocol to be used. These configurations can be set at the Unix level or within the Sterling Integrator business processes. The files are picked up from the source and transferred to the target. We manage external files by using IDs and other necessary details. We handle everything from gathering information from partners to onboarding and through the hypercare phase, ensuring complete management of the file transfer process.

It offers seamless file transfers. While other tools are available, Sterling File Gateway stands out for its security, sustainability, and visibility features. It supports partner integrations, enabling them to use mailboxes to log in and retrieve files. This process simplifies file management and enhances users' visibility.

We are currently manually creating routing templates. It automates creating routing templates, channels, and everything else.

IBM Sterling File Gateway is a secure file transfer solution designed to handle large volumes of data. It supports high-capacity transfers, such as sending files up to 2 gigabytes in size. The system uses robust security measures, including PGP encryption and AS2 protocols, to ensure secure file transmission.

The platform features a user-friendly desktop interface, which simplifies managing and executing file transfers. Additionally, IBM Sterling File Gateway can handle transformation and translation files, facilitating seamless data mapping and integration.

We conduct monthly maintenance. When the system becomes unstable, mainly when it receives a large volume of data simultaneously from the source, it can lead to issues. This instability might cause all devices to enter a routing state. In such cases, we need to manually verify and redeliver the files to ensure they are properly transferred. Alternatively, we can use the Fireflies mailbox to handle bulk file transfers. During instability, files might remain in the source and routing states. By checking the event details, we can confirm the delivery status of individual files. 

I have been using IBM Sterling File Gateway for six years.

Ten people are using this solution.

The product is expensive.

Some partners may not have the budget or other resources to use this product, but it’s important to highlight the security levels we offer with IBM Sterling File Gateway. We provide robust security features like password authentication, public key authentication, and, when using the AS2 protocol, certificate authentication. This ensures that we can securely transfer large volumes of data.

I highly recommend this product for its comprehensive visibility features. For instance, if a file gets stuck, we can quickly identify and resolve the issue. This visibility is crucial for monitoring and troubleshooting file transfers, ensuring a seamless process.

Additionally, I can educate partners using FastTrack on how to leverage these benefits effectively. I will guide them through the process, emphasizing the advantages of using IBM Sterling File Gateway, particularly the ease of handling major issues. Once implemented, the system operates smoothly and will only be impacted if there are changes.

It is easy to understand, though it might present some complications that could be challenging for beginners. Even newcomers can grasp it with some time and effort. The self-help tools and visibility features enhance the learning experience, making it easier for users to navigate and utilize the system efficiently.

IBM Sterling File Gateway involves multiple levels of encryption. We employ various encryption methods to ensure data security. This provides a robust security level.

It is an excellent product used by many companies and clients. We have been using it for a long time, and it provides a seamless process that is easy for users to understand.

Overall, I rate the solution a ten out of ten.

It's a very good, stable, and organized tool, as it is from IBM. It has great support. 

It's supported all available file transfer protocols to automate our transfers.

The file transfer automation is organized and monitored and gave us a solution with all protocols.

It is very easy to manage and implement a transfer solution with the multi-platform conversion of characters without issue.

The validation and monitoring of the file transfer are helpful.

It offers easy utilization of resources for smooth transfers.

It has supported all available file transfer protocols to automate our transfers and is helpful in giving virtuality to utilize the DMZ via a secure proxy. It is an organized and stable way to utilize the infra.

The file transfer automation and the way it is organized and monitored is great.

It is very easy to manage and implement a transfer solution multi-platform conversion of characters without issue.

The validation and monitoring of a file transfer is easy. It offers smooth transfers.

It's very good, stable, and organized. 

It has supported all available file transfer protocols to automate transfers.

The file transfer automation is great.

It is very easy to manage and implement transfer solutions via a multi-platform conversion of characters without issue.

The validation and monitoring of file transfer are easy.

The admin console needs some work. There are old buttons and limitations when looking for logs. 

required the reason why has so old way of buttons and limitations for looking at logs.

I've been using this product for seven years.

The solution is very stable. 

The solution is very scalable. 

We did use something else for vendor support.

It is easy to organize.

It's the best solution and is easy to utilize.

We did not evaluate other options. 

We use this solution for financial management. For example, transactions between the bank and credit card and cheque printing that need to be given to the printing service industries for transfer. There are APIs that are exposed for the corporate customers for their salary posting and other transaction settlements.

I have found almost all the features valuable. 

IBM is advising not to use the IT translate anymore but this is going to be an extra cost to the customer to use the alternative. 

Additionally, the solution can improve the REST API protocols. If you look at the REST API client services available, you can do an API call to any other API exposed, but the way the API comes it is not treated right.

I have been using this solution for approximately 15 years.

The solution is stable and reliable.

The solution does not have any issue with scalability.

The technical support is very responsive and as soon as you raise a ticket you are connected to someone that is able to help you at all levels, whether it is at the product level or any technical level.

The initial setup is straightforward.

There are two types of customer licenses, an annual preview license, and an ELA-based license. I have found the solution is priced well. However, they need to review the pricing model because if you look at any other competitors, such as GlobalSCAPE, they do pricing based on the components and what you select. With this solution you have a monolithic application which you need to buy, there is no component level price discount.

I have evaluated GlobalSCAPE.

I would recommend this solution to others.

I rate IBM Sterling File Gateway a nine out of ten.

I work as a consultant to one of our clients who use SFG.

The functionality of this solution is very high and it has many features. The one feature, which is good is that you are able to plug in your own code. For example, if you want to process files, you can write your own code to parse the file the way you like. You can interpret it, so feature wise, it is rich.

One of the issues with this solution is that it has so many features which is in itself the problem. It should be just a simple file transfer solution. It's very frustrating  because it's a very rich tool but it has so many problems. The UI is essentially not good, the interaction with the control center and report runs are not good. The usability, performance, and reliability, are absolutely no good. There is a newer version, perhaps it's better. 

I've been using this solution for six months. 

This solution is not at all scalable. 

I know there are some pretty good people who know how to deal with the tool and fix problems. We had to engage with the support a lot of times which indirectly means that the product is not good. Again, I hear the latest version is an improved product. 

The initial setup is fairly easy, it's not that tough.

There are solutions like GoAnywhere or Axway where the usability and flexibility is so easy. SFG has a legacy we have to deal with. I know they have pretty big clients and are one of the prime vendors. I'm not talking about the latest version of SFG, I haven't had a chance to look at it. If what they promise is correct, it might be a big improvement. 

I would rate this product a two out of 10. 

We exchange many files with our partners. So our primary use case for this product is for our partners to securely send us files for processing.  

The most valuable feature is really the same as our main use case: secure file transfer. I would need to consult with my operation team for any other valuable features.  

I think it would be good if IBM continues to focus on the primary use of Sterling File Gateway which is file transfer. They can continue to expand those capabilities. We can already get the files securely and we can work with the partner on some of the schedule. But the solution might also cover working with different aspects of the workflow. We have quite a big spectrum of customers in our portfolio, and having more options could help us to better work with them. The workflow capabilities are some of the key features as to why I believe IBM Sterling has been picked as a solution for this type of product in the past.  

I have been exploring whether we can expand API capabilities. I am studying what they have to offer now, but I would like it if the solution could offer even more support of API usage. It would be good to be able to make API calls yourself to do more with integration. With a more open API trend, we could place more focus on this area. That would be something I would really be looking for in future releases.  

The version that we are using will be going through some changes in support from IBM. I want to start the long term roadmap to look at how that affects our usage.  

I just joined the company, but I think they have been using the product for more than 10 years. I have been using it personally for more than five years.  

IBM Sterling is quite scalable per my experience. We cover the whole sector of a broad industry and that is a lot of users. I think it is hard to say exactly how many end-users there are. But entity-wise, we are working with more than 200 companies through our instance.  

I have had the opportunity to contact technical support and I think that the technical team is okay. We just want to be sure that the product will be good for our long term roadmap.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution as a ten-out-of-ten. In the past, it seems the whole industry adopted this solution because it was the leader in the field. Whether their whole architecture will be adaptable enough for the cloud is something that needs to be studied further.  

We are using this solution for file management within our organization, and in different outlets as well.

It's highly configurable and there is no need for standalone scripting. It's adaptive, functional, and it's quick and easy to set up interfaces. It's similar to the Oracle product switch and Fusion Huawei.

The areas that need improvement are user management, user interface, and the segregation of users. These are the areas that I am battling with at the moment. It's not geared towards your user community. If you're an administrator of the system, it's fairly easy, but then to segregate the configuration and give the availability to it, it's a bit of a nightmare.

In the next release, I would like to see upgraded user segregation, user management, and looking into auto-deploys. Once you need to deploy a new bundle of software, you need some service downtime. I would like to see auto-deployment without service disruptions. That is what this industry is always looking at. 

When you deploy something, you want your service to always be on, and with this solution that is not the case.

I have been using this solution for ten years.

It's fairly stable. 

Over the years, we have only encountered one or two bugs, which were introduced through new software releases.

This solution is scalable, but there are always licensing cost implications. 

You can scale it, but it depends on how you scale it. If you scale it horizontally, there will be license implications.

It's an enterprise solution and we have just under 2,800 interfaces on the system. Every interface would count as a user.

The initial setup is straightforward. It takes approximately three months to deploy.

Within our company, we have a team of four, plus two integrators to deploy this solution. 

To maintain this solution we have our team of four.

We used an integrator to deploy this solution.

It is now something that is an off-the-shelf solution. It's not something that we custom develop. When it comes to a roll-out, it's fairly easy.

It's reasonably priced at $800,000. That's the annual maintenance cost.

You have to pay to expand your additional platform.

The only limitation of this solution is that you have to pay to expand it, other than that it's stable and flexible.

Plan your upgrades very carefully, and go through the documentation.

It's a fairly stable product, but there are always other products on the market.

I would rate this solution a six out of ten.