Infrastructure Tech Lead at a financial services firm with 10,001+ employees
Real User
Top 10
2022-10-03T03:37:00Z
Oct 3, 2022
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.
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.
Performance and Reliability Consultant at a computer software company with 201-500 employees
Real User
2020-11-10T13:05:55Z
Nov 10, 2020
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.
Senior Manager - Architecture and Standards at a financial services firm with 201-500 employees
Real User
2020-09-01T05:25:11Z
Sep 1, 2020
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.
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.
Find out what your peers are saying about IBM, Amazon Web Services (AWS), Progress Software and others in Managed File Transfer (MFT). Updated: March 2024.
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.
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.
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 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.
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.