Share your experience using ibi iWay Service Manager

My main use case for this product is purely API management.

In my opinion, IBM DataPower Gateway's best features are the analytics as well as a developer portal.

IBM DataPower Gateway's multi-protocol transformation is important for my integration needs because all the API traffic is coming from this API data gateway.

IBM DataPower Gateway has positively impacted my organization by allowing me to implement rate limits on the different API usage, which is the benefit.

The developer portal should be an integrated part of IBM DataPower Gateway to improve it.

I think it is fine as is, and maybe no other additional features should be included in the next release.

My experience with the pricing of this product is that pricing is too high and should be reduced.

I have been using this product for around three years or more.

IBM DataPower Gateway is stable and it is running very smoothly, which is good in this product.

In my opinion, IBM DataPower Gateway's scalability is good and it is fine.

I would evaluate customer service and technical support as a little bit weak, so I give it a seven out of ten.

Positive

I evaluated WSO2 before choosing IBM DataPower Gateway, and I found it to be basically open source, so IBM DataPower Gateway is better than that.

The initial setup of IBM DataPower Gateway was done by the partner, which took a very long time to mature. Once it was done, it is working fine, but the partnership should be engaged and should be trained.

The initial setup of IBM DataPower Gateway was done by the partner.

I have seen ROI with this product.

I can provide some examples of return on investment by saying that we are running different APIs which we are using, and we are charging customers. We count the number of hits and can say we earn and actually get the benefit from it.

I have experience with API management and using API management tools effectively. We are using IBM DataPower Gateway, not just IBM DataPower. We do not use caching abilities. IBM DataPower Gateway's intelligent routing and load balancing features have not helped manage my workload since we are using a load balancer from another provider. I am using security features, but they are not from IBM.

I would rate IBM DataPower Gateway's traffic management as absolutely fine, a nine out of ten. Overall, I would scale IBM DataPower Gateway as eight out of ten. I do not give it a ten just because of the support team.

My company does not have any business relationship with IBM except being a customer. I would rate this product overall as eight out of ten.

We are currently using the latest version of the IBM DataPower Gateway, 10.0.6.0.

We are using the IBM DataPower Gateway for authentication purposes. We also developed a firewall for our purposes. When we develop a web application and require security for that particular web application, we can use the IBM DataPower Gateway. We also use SOAP services. If we want to deploy on the IBM DataPower Gateway, then we can utilize it. It's also used for authentication and authorization. It also has a rate limiting feature. If we handle multiple loads on this server, then using the rate limit function, we can handle the traffic load and API traffic load.

We are currently using the IBM DataPower Gateway only for API purposes. If we have a rate-limiting purpose and we deploy multiple APIs, then an issue will occur on the IBM DataPower Gateway. A rate-limiting issue will occur. For that type of feature, we also require some support from IBM.

We are using the IBM DataPower Gateway for security purposes. As per the development perspective, there are some limitations with IBM DataPower Gateway because it only supports XML and XSLT language, but it does not support the Java language. This is the only limitation of the IBM DataPower Gateway. For the authentication and authorization purpose, we can use the IBM DataPower Gateway. It's a very good product.

We are mostly using the IBM DataPower Gateway for security purposes and load balancing purposes. If we are handling the load for a particular server, then we can use the IBM DataPower Gateway.

The IBM DataPower Gateway is mostly used for security purposes. If we have some APIs and we are using some security for those APIs, then we can use it. It can also be used as a load balancer. It's also used for certificate management, user management purposes, authentication, and authorization.

For routing, the IBM DataPower Gateway has multiple URL-based routing and content-based routing capabilities. If we have multiple URLs, then we can use an XML script. Using the XSLT language, we can configure multiple URLs and implement URL-based routing. Content-based routing means if we have multiple requests, we can route the request to a particular URL. For this, we need to use the XSLT language only. We can't use XML, Java, or other scripting languages.

With IBM DataPower Gateway, we are using all the APIs. All APIs have been configured on the gateway. We have configured the particular TLS profile and some TLS client profiles as well. Using that TLS profile, we have configured the APIs and authentication. We have configured some tokens also, including JWT tokens and different types of auth tokens. There is also a rate limiting feature which we use for handling API loads.

I have significant experience with the IBM DataPower Gateway. As a security product, it is very good. However, from the development perspective, it has limitations because it only supports the XSLT language. It does not support multiple languages. We can't modify it because this is a custom OS. We can't customize the given product. Whatever feature is available on the IBM DataPower Gateway, that feature is the only one we can use. If we require additional features, we can't configure them on the IBM DataPower Gateway.

We do not utilize IBM DataPower Gateway's caching capabilities.

I have been working on the IBM DataPower Gateway for the last 5.8 years.

For the IBM DataPower Gateway, if we require a production environment or a development environment, for production, we definitely require three nodes in the cluster node. Because if there is multiple traffic on a single node, then it will definitely cause some damage or issues will occur. If we have multiple nodes for the IBM DataPower Gateway, then it will handle the multiple traffic. For a development environment, only a single node will be enough to handle the traffic.

If we have multiple servers and a multiple cluster for the IBM DataPower Gateway, then there will be no issue handling the traffic. However, if we have multiple traffic and only a single node, then issues will definitely occur. IBM DataPower Gateway does not handle all the traffic on a single node. If we have multiple nodes, then they can handle a large amount of traffic.

At the VM level, we can modify the RAM and the hard disk. However, it will impact the server. IBM does not recommend increasing the resources to increase the scalability once you install the product. It will be very risky. Once you install the product, we can't scale the resources on the IBM DataPower Gateway. This is also a limitation of this product.

Before IBM DataPower Gateway, we had used some .NET services. We had deployed them on the particular platform. Once IBM DataPower Gateway came into the picture, we started using it only for security purposes.

The installation process is very easy. We require 18 GB RAM and a four CPU processor and one particular server. Using that server, you can install it easily. There is also IBM documentation available on Google. Using that documentation, you can easily install the IBM DataPower Gateway.

The installation requires some large resources. However, the installation is easy. If we face any issue, then the IBM team will be available for our support.

This product is definitely expensive because if any issue occurs in the live environment or production environment, and our organization faces some issue with the IBM DataPower Gateway, then the IBM team will provide support. That's why the product is expensive.

Regarding pricing, I don't have much information because my management team manages the licensing. In my point of view, I think it costs around 5 Crore in Indian Rupees.

We can use Apigee, which is one of Google's gateways. However, as per the security purpose and implementation purposes, IBM DataPower Gateway is a very good product for implementation and configuration purposes. Some other organizations are also using the Apigee product.

In the previous version, there were some limitations, but in the upgraded versions, IBM has fixed some bugs. Currently, we don't have many limitations. It only supports the XSLT language from a development perspective. It does not support Java or Python. Other than XSLT, the IBM DataPower Gateway does not support other languages. On a scale of 1-10, I would rate this solution a 7.