Please share with the community what you think needs improvement with BMC Control-M Managed File Transfer.
What are its weaknesses? What would you like to see changed in a future version?
At this time, you can receive file transfers but it is not possible to send them. Ideally, we also want to be able to send files using this solution. Scalability is something that needs to be improved.
The structure between the Control-M/Server and Control-M/Agent could possibly be improved. It would also be helpful if the deployment of Control-M/Agent could be simplified. Sometimes you can spend a lot of your day just doing the maintenance work to keep the system running. So that's something that could be improved. I think they could also improve the basic engineering of the server. The product has been around for a long time now, it's 30 years old, so most of the big issues were fixed a long time ago. Any issues now are not serious. The API that they recently introduced is very good and lots of people are using that. It's really about development for the future, which means improving the API. I would go back to the API in terms of additional features, in that they should expand the possibilities of the API. Not everything is possible with the API, and you've got utilities in all the controlling systems that are very powerful, but they're not all opened up to the API yet. I think they should really just expand the API to catch up with the rest of the system.
What do you like most about BMC Control-M Managed File Transfer?
Thanks for sharing your thoughts with the community!