2020-03-03T08:47:42Z

What needs improvement with IBM DataPower Gateway?

7

Please share with the community what you think needs improvement with IBM DataPower Gateway.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
Guest
88 Answers

author avatar
Top 5LeaderboardReal User

Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on. It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity.

2021-06-03T09:57:22Z
author avatar
Top 5LeaderboardReal User

There is quite a lot that needs improvement. It's a very complex product and it takes time to get to control it and to know it. It's all about gaining knowledge in it. Also, the maintenance procedure of the physical machines and physical appliances is quite complicated, and there are some issues with it. Sometimes, when we deal with the maintenance process because the machine isn't booting, it comes down to working with support in the middle of the night. The two biggest issues of this solution are the complexity and the maintenance procedures. In the next release, I would like to see it easier to deeply, easier automated processes, easier maintenance, easier control, better monitoring, and I would like the information or knowledge documentation to be more accessible.

2021-03-06T07:29:37Z
author avatar
Top 5LeaderboardReal User

In the next release, I would like to see the product price reduced. It should be cheaper.

2021-02-10T16:36:27Z
author avatar
Top 5LeaderboardReal User

It would be great if the CI/CI and DevOps components were part of this offering. Having some pre-packaged proposals or integration solutions would be helpful, like many of the iPass providers are now supplying. Some pre-packaged connectors for integration with various applications, such as SaaS offerings, would be a useful addition.

2020-12-18T11:31:13Z
author avatar
Top 20LeaderboardReal User

New users just starting with this product find it a little complex or difficult to use, compared to other products such as AWS. Making it more user-friendly would be an improvement.

2020-09-30T08:03:27Z
author avatar
LeaderboardReal User

Scripting needs improvement. It's hard for our customers.

2020-04-20T07:27:00Z
author avatar
Top 20LeaderboardConsultant

Care needs to be taken when applying firmware upgrades, as they often fail. Also, the components that they include in the product that are, in fact, a WTX, really need to be removed from the product because they tend to fail. It's got some native capabilities and it's gotten some imported capabilities and you need to know the history of the product to understand the difference between the two. Most notable is the COBOL copybook handling, which is really straight out of WTX. It's poorly supported and often leads to failures.

2020-03-29T08:26:00Z
author avatar
LeaderboardReal User

The solution is quite expensive. They should work to help make it more affordable for more companies. Right now, I wouldn't consider the price point to be very competitive. The solution requires a lot of training manuals in order to get to know it better and to be able to use it effectively.

2020-03-03T08:47:42Z
Find out what your peers are saying about IBM, MuleSoft, Oracle and others in ESB. Updated: June 2021.
511,521 professionals have used our research since 2012.