When it comes to the tool's scalability, I cannot say that everything can be done in the best version. There is always a scope for improvement. The tool can try to make it a little bit more flexible so that we can easily invoke the APIs, and in such a way, it can be made a little bit better. In general, everything is fine with respect to the tool's scalability. My company has encountered some challenges. The tool does not allow the explicit port for some of the protocols, like FTP. We are still selling the tool to some of our clients. I feel they should allow us to do some testing for the SMB-related protocols or Windows path-related protocols, which we are not allowing, making it difficult for us to identify the issue with respect to those SMB protocols as well as Amazon S3's protocols. I believe it is an area that needs to be fixed so that it will help the end customer do those types of tests without the help of another external tool. As of now, I can remember only these two scenarios where improvements are needed.
It is complicated to manage multi-operations, particularly in handling file name changes within file transcripts. This particular area needs improvement. There could be an endpoint connection for multiple operations.
Director Of Operations at a outsourcing company with 10,001+ employees
Real User
Top 5
2023-07-19T05:55:10Z
Jul 19, 2023
Sometimes, the application's embedded databases couldn't perform well for a higher volume of data. Thus, legacy licensing for these databases needs improvement.
I am looking for a kind of feature in terms of high performance and high visibility in a system or solution. So right now, this is not the feature we are using now, but we are searching for this kind of a solution.
We are pretty happy with the solution. There haven’t been any shortcomings. We only hope that they continue to keep updating the solution and improving the offering. They could always do more updates and releases.
Application Development Senior Analyst at Accenture
Real User
2022-02-10T14:33:46Z
Feb 10, 2022
One area of improvement is troubleshooting. When a transfer fails, they provide little information about the login, which makes troubleshooting difficult. Also, file transfer scheduling is primitive. By that, I mean you can't define a complex schedule, like scheduling a job to run at particular hours multiple times in a day. Also, Axway Amplify doesn't have built-in analytics, so you need to use another product for that. It would be helpful if they could do some basic analytics, like statistics for a 24-hour period. I'd like to see something simple that shows how many file transfers came in and went out from the environment, and how many failed. I would also like to see Axway implement online patch management. We have to take the application completely offline to apply the patch and then restart. Other applications support online patch management, so I would appreciate it if they could do something similar. Of course, a restart would still be required, but online patch management could significantly reduce our downtime.
When it comes to the tool's scalability, I cannot say that everything can be done in the best version. There is always a scope for improvement. The tool can try to make it a little bit more flexible so that we can easily invoke the APIs, and in such a way, it can be made a little bit better. In general, everything is fine with respect to the tool's scalability. My company has encountered some challenges. The tool does not allow the explicit port for some of the protocols, like FTP. We are still selling the tool to some of our clients. I feel they should allow us to do some testing for the SMB-related protocols or Windows path-related protocols, which we are not allowing, making it difficult for us to identify the issue with respect to those SMB protocols as well as Amazon S3's protocols. I believe it is an area that needs to be fixed so that it will help the end customer do those types of tests without the help of another external tool. As of now, I can remember only these two scenarios where improvements are needed.
It is complicated to manage multi-operations, particularly in handling file name changes within file transcripts. This particular area needs improvement. There could be an endpoint connection for multiple operations.
Sometimes, the application's embedded databases couldn't perform well for a higher volume of data. Thus, legacy licensing for these databases needs improvement.
I am looking for a kind of feature in terms of high performance and high visibility in a system or solution. So right now, this is not the feature we are using now, but we are searching for this kind of a solution.
We are pretty happy with the solution. There haven’t been any shortcomings. We only hope that they continue to keep updating the solution and improving the offering. They could always do more updates and releases.
One area of improvement is troubleshooting. When a transfer fails, they provide little information about the login, which makes troubleshooting difficult. Also, file transfer scheduling is primitive. By that, I mean you can't define a complex schedule, like scheduling a job to run at particular hours multiple times in a day. Also, Axway Amplify doesn't have built-in analytics, so you need to use another product for that. It would be helpful if they could do some basic analytics, like statistics for a 24-hour period. I'd like to see something simple that shows how many file transfers came in and went out from the environment, and how many failed. I would also like to see Axway implement online patch management. We have to take the application completely offline to apply the patch and then restart. Other applications support online patch management, so I would appreciate it if they could do something similar. Of course, a restart would still be required, but online patch management could significantly reduce our downtime.