Axway AMPLIFY Application Integration is a dynamic platform valued for its flexible API Gateway, integrating with multiple systems and enhancing data efficiency while ensuring robust security.
| Product | Mindshare (%) |
|---|---|
| Axway AMPLIFY Application Integration | 0.9% |
| Informatica Intelligent Data Management Cloud (IDMC) | 3.7% |
| SSIS | 3.6% |
| Other | 91.8% |
With its adaptive API Gateway, Axway AMPLIFY Application Integration facilitates seamless data movement across diverse computing environments. It connects to systems like Active Directory and provides detailed reports, enhancing data management and security. Its features in machine-to-machine communication, file transfer, and API usage contribute to its stable and efficient performance. Despite its strengths, it requires skilled personnel for optimal use and improvements in management and visibility, particularly for global enterprises.
What are the key features of Axway AMPLIFY Application Integration?Industries like automotive use Axway AMPLIFY Application Integration for projects involving application connectivity across regions. It supports dealer and logistics integrations, as well as bridging internal systems with platforms such as Salesforce, leveraging its policy engine to ensure secured data access and control, thereby enhancing transaction speed and security.
Axway AMPLIFY Application Integration was previously known as Integrator, Axway Integrator, AMPLIFY Application Integration.
BHF-BANK, BNP Paribas, Continental Corporation Automotive Group, Clearstream MFT, Federal Office of Information Technology, Systems and Telecommunication (FOITT), DHL, Union Nationale de Mutualit_s Socialistes, ZF Group, La Poste, Gassco, IdenTrust, Perugia Hospital, International Post Corporation, Bundesagentur fªr Arbeit (BA), IHC Health Solutions, Lenovo, Genzyme
| Author info | Rating | Review Summary |
|---|---|---|
| Principal Solution Architect at a comms service provider with 51-200 employees | 3.5 | We use Axway AMPLIFY Application Integration for dealer solutions and internal application integration. Its valuable features include file transfer and API robustness, but it needs better management, visibility, and scalability. We deploy it with Google as our cloud provider. |
| Client Executive at a tech services company with 51-200 employees | 4.5 | I find Axway API Gateway excellent for secure, high-speed data integration, replacing batch processes. Its flexibility provides great visibility and control. However, due to its depth, experienced personnel are crucial for quick and efficient implementation, despite easy setup. |
| Business Development Manager at TPIsfotware | 4.0 | I use Axway AMPLIFY Application Integration for logistics as it is a stable solution, although it is expensive. I haven't used or considered other solutions, and there is no specific cloud provider deployment mentioned in the review. |
| Principal Solution Architect at a comms service provider with 51-200 employees | 4.0 | I found Axway AMPLIFY easy to use and stable, but it lacks scalability for large, globally distributed enterprises due to deployment challenges across regions, making it unsuitable for my international company's needs. |
We use the solution for dealers. We also use it to integrate internal applications.
File transfer features are valuable for me. We also use API. The product is robust.
The management of the product must be improved. We have great pressure from our business to have visibility of integration. The product must improve its visibility and scalability.
I have been using the solution for ten years. I am using the latest version of the solution.
The tool is very stable. I rate the stability an eight out of ten.
I rate the tool’s scalability a five or six out of ten. Scalability is an issue. Our business increases day by day, and we are short of scalability. About 1000 employees use the solution in our organization. Almost all the dealers in the land use the product.
The initial setup is easy. It is very simple to start with. The last release from Axway provided many ways to simplify and speed up integration. The solution is deployed on the cloud and on-premises. We use Google, Amazon, and Azure as our cloud providers. The time taken for deployment is very short because the tool is robust.
The pricing is aligned with the competition. The product is not expensive.
We use Sentinel for monitoring. The product is good but needs to improve its scalability and visibility. Overall, I rate the product a seven out of ten.
One of the projects I'm working on is to use it to connect a web form where end-users will enter in data. This data will go from API Gateway to a mainframe, and then the mainframe will take that data, combine it with other data sets, massage it, and send the answer back in the form of a PDF.
We're looking to do a couple of things with API Gateway. The first one is that we're moving from a 24-hour batch process using Managed File Transfer to API Gateway where our transactions are in minutes or less, rather than every 24 hours.
The other thing is that by using API Gateway, we are now enabled to institute some very strong security modes, not only for authentication but also for authorization. We're going to use a single sign-on product for authentication, and once that's done, API Gateway is a policy manual that will securely regulate what data sets people are actually able to see or query, or send data to. For example, in today's situation, someone can query the mainframe for information, even though they have no business asking for that info. It is a 15-year-old setup, and security wasn't in everybody's mind at the time, and the tools were very hard.
Because API Gateway is a policy engine, I can apply policies that can say, "All right, you have to be from a certain company or a certain zip code, or certainly from the state of California before we will even accept your query." After that, we're going to inspect that query to say, "Okay, you are somebody who is working with this type of data, so we are going to allow you to send in your information and query the system for the information that we know you're authorized to see." We can also say, "Are you coming from an appropriate IP address at an appropriate day and time of day?" In other words, if your IP address is coming from a foreign country and it is Saturday morning at 1:00 AM, we know that's not normal. So, we would block that.
I'm working with the most recent version. It is a cloud solution.
The most valuable feature is that API Gateway is extremely flexible for any feature, such as connecting to Active Directory to pull the users and their authentication information. There are three ways to connect to Active Directory, and the reason for this is that the computing environments of our customers are very different. Every feature in API Gateway has got multiple methodologies for accomplishing those tasks, which is important because customers are constantly changing their security models, IT models, networks, etc. API Gateway is very flexible. It is not a one size fits all sort of situation where it is very rigid, and you can only use these pull-down menus, and that's all it ever does. It is much more open than that.
It can give you fabulous reports on your users, usage, security issues, and the data sets that are going through there. You'll suddenly have visibility on the movement of data within or between your organization and other organizations. The other thing is that you're connecting API to API, which is machine to machine. The things that were done manually in an Excel spreadsheet before exchanging data through email are now done machine to machine and server to server. It speeds up the velocity of your business.
Because it is so flexible, you really need someone who knows Axway Gateway or has been through the training and is certified. Just because you know APIs doesn't mean you're going to walk into that API Gateway and understand what to click on. If you're going to get something done quickly, you need to find an engineer from a company who has some experience with it. It is easy to learn, but if you're doing on-the-job training, it is going to take you longer to get your project accomplished.
I have been using this solution for just a couple of years.
It is extremely stable. It is a kind of fire-and-forget sort of scenario.
It is a very mature product. It is probably 15 or 20 years old at this point.
It scales extremely well.
Their technical support is good. They know what they're doing.
The setup is easy. To use API Gateway to connect to other applications, you need to understand the best practice for connecting. There could be three different ways to do that, and if you're trying to pick the best or the most efficient way, it typically needs experience.
API Gateway is priced on the number of transactions you run through it. API Gateway is free, and you can install as many API Gateways as you like or are necessary for your network. For example, if all of the data is inside your network or firewall, you may just need one API Gateway. If you have external customers trying to come into your organization through your firewall, you're going to need one API Gateway outside the firewall and one inside the firewall. If you have a lot of remote offices, you may want to put API Gateway in some of those offices as well. They only charge you for your usage of it. In other words, the number of transactions going through it. That's a good benefit.
I would advise others to get started now because what you're doing is you're enabling your business processes to operate at high speeds with a quality of service and reporting that is built-in. For example, a lot of people use the API for Amazon's web store. Imagine you're a manufacturer with thousands of part numbers, thousands of pictures that go with those parts, and thousands of descriptions of those products. You won't try to upload those one at a time to the Amazon web store. You need your content database to talk to the Amazon web store database so that when you update a part number, change a price, add more photos of a product, or make any other change, it automatically syncs with the Amazon web store, and it does it through APIs. So, it is machine to machine.
I would rate Axway AMPLIFY Application Integration a nine out of ten.
Axway AMPLIFY Application Integration is an expensive solution.
I have worked with Axway AMPLIFY Application Integration for six months.
We experienced a five-second loading delay with the solution.
I rate Axway AMPLIFY Application Integration a seven out of ten for stability.
Less than 20 people use the solution in our organization.
The solution's initial setup is quite complex.
The solution was deployed by an in-house team. The solution can be deployed in one and a half hours. The solution’s on-premise deployment takes about three hours, which could be because of our connection.
Five people, including myself, are required for the solution's deployment and maintenance.
Users need to pay an annual licensing fee for the solution.
I would recommend Axway AMPLIFY Application Integration to other users.
Overall, I rate Axway AMPLIFY Application Integration an eight out of ten.
I am working for an automotive company that has both Italian clients and American automotive clients. For example, the first project integrates with Salesforce, using API Gateway to decouple our internal applications and Salesforce Cloud applications.
I use the SQL Transport version 6, and for the Windows environment, I use the API Gateway, but this is only for testing and not used in production.
Axway AMPLIFY Application Integration is very easy to use.
The most important point to improve is the capability to deploy in large enterprises. We have some issues if the project is deployed around the world. We have offices in Europe, North America, Latin America, and the Asia Pacific, and we need to have control worldwide. We must have the correct right to autonomy to define any region, and in this case, the product is not very useful. If they improve this, it'll be a very good product.
I have been using Axway AMPLIFY Application Integration for about one and a half years.
Axway AMPLIFY Application Integration is a stable solution.
The scalability problem isn't scalability over the engine. Our company is located worldwide in different regions. The problem is the registry to configure the systems, and it's not really scalable for companies with offices worldwide.
We must have different regions with different IT specialists to configure this product, which is not very useful. The problem with scalability is deployment. To deploy when you define an IP, you must define and configure it, and this isn't very easy if you have different regions and users. This is why we decided to use the IBM product and not AMPLIFY.
Axway technical support is good. They also have a very good website.
The initial setup is straightforward and takes about three days to deploy.
It was implemented for us by our consultants.
I would recommend this product to new users if it's not a large global enterprise. It's a very good product for smaller deployments.
On a scale from one to ten, I would give Axway AMPLIFY Application Integration an eight.
