IBM DataPower Gateway is quite big for smaller organizations, looking at different types of clients who are virtually assisted in this, I would say it's not really a good product for smaller firms.

One area that could be improved is the integration with Postgres and SQL databases. Currently, IBM DataPower Gateway only integrates with Oracle databases.

So it doesn't integrate with Postgres.

An area for improvement in IBM DataPower Gateway is its price point because it's a relatively expensive product. Sometimes, when the customer use case is just a very small subset of what's being offered in IBM DataPower Gateway, then the product can be expensive, making my company lose some of the opportunities because of the expensive pricing.

A lower price point for IBM DataPower Gateway, even if that results in a less feature-rich version, would be appreciated.

In terms of additional features that I'd like to see in the next release of IBM DataPower Gateway, nothing specific comes to mind because IBM constantly improves its standards and provides quarterly updates to the product, so it's quite fine.

Additional documentation needs to be provided for complex automations.

The product's cost for data appliances or hardware is quite high. It needs improvement.

I would like the tool to improve its training. 

Right now, the programming language is only supported in XSLT and Gateway script. Offering another programming language like Python would be better for all. We had one difficulty with signing and encryption, which it doesn't support in the data pool but does in Java programming language. It wasn't contained in the latest algorithm, so that's an issue we faced with one customer. 

It is challenging to understand the solution's design and support skills. We have to keep importing skills all the time. It requires a technical person to understand multiple operating systems environments. They should make it more accessible for entry-level developers. Also, they should add features to manage API integrations.

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

It is a costly product. So, it is not an open-source solution, making it costly.

In the future, I would like to see an open-source version.

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.

The user interface or the application development perspective and customization of the tool could be a little better.

They should improve the solution's clustering features. Also, they should include algorithms for correct load balancing. In addition, they should provide integration with MQ logs. We require proper documentation to understand the solution's parameters as well.

For the workloads that are not too high, appliance is a little bit expensive. This is especially true in the development test and UAT environment, in which we can use the virtual version of the product. For live environments, we can continue to use the appliances. 

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.

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.

The IBM community does not have much engagement from the IT community in Saudi Arabia and developers for this solution are difficult to find. 

They have to enable the location subscribe using Message Queue which could be improved.

We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option.

We use it from a maintenance point of view and therefore do not necessarily need extra features. 

The solution could be more user-friendly.

The customization of the solution isn't as straightforward as we would like it to be. There should be more integration capabilities and it should be much easier to integrate other products.

The product should be more adapted to the DevOps process.

The product was very sensitive to heat. The hardware had a hard time if it wasn't cool enough.

The initial setup is quite difficult. You need to be well-trained in the solution in order to understand the process.

The admin and user interfaces could be improved.

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

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.

It is challenging to find the right resources while dealing with system errors for the solution. Thus, its support could be better. Also, its UI could be more feasible.

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.

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.