Axway AMPLIFY B2B Integration Reviews

My main use case for Axway AMPLIFY B2B Integration is that it functions as an ETL tool. We receive XML format and convert it to corresponding output fields. For the business logic, we write it in mapping. We integrate the trigger component. Primarily, we use Axway AMPLIFY B2B Integration for managing business-to-business data exchange between parties. In my case, it involves multi-protocol connectivity. We use it as a gateway that speaks many different communication protocols: SFTP, AS2, AS4, OFTP, MQ, HTTPS, and others. Trading partners with different technical setups can all exchange files and messages without us building a custom connection for each one.

Another use case is file messaging, message translation, and mapping, converting between different data formats. For example, I translate a partner's flat file or XML into our internal format or vice versa. In my case, my bank is transforming SWIFT MT messages, ISO 20022, XML, or proprietary formats into something our core banking or payment system can consume.

The third use case is partner onboarding and community management, managing hundreds or thousands of external trading partners' profiles, their protocols, certificates, and routing rules in one place. Onboarding a new partner is configuration-driven, rather than custom coded each time.

The fourth use case is ensuring messages are delivered exactly once, tracking delivery status, retries, and providing non-repudiation, such as proof of sent and receipt. This is important for regulatory and financial transactions where I need an audit trail.

Regarding security, Axway AMPLIFY B2B Integration handles encryption, digital signatures, and certificate management for sensitive data in transit, which is critical in banking for SWIFT payment message exchange. In my experience, it typically sits between core banking, a payment processing system, and the outside world, routing payment instructions, SWIFT messages, and regulatory reports from correspondent banks, clearing systems, and corporate clients.

Axway AMPLIFY B2B Integration accelerates partner onboarding. The partner onboarding time was reduced with the effort to bring new trading partners online because protocol and mapping configuration replaced custom point-to-point code. There is reduced operational risk. Guaranteed delivery and audit trails cut down on manual reconciliation and missed or failed payment messages. Standardization, with the protocol-agnostic layer we built, means the bank can support diverse partners without proliferative one-off integration, cutting down on maintenance overhead. The performance is very good, touching the report generation flows tied to B2B message volumes, which is a concrete and quantifiable metric I can cite directly. I can share specific metrics that show how Axway AMPLIFY B2B Integration has helped my organization. The patching solution improved report generation performance by over 60 percent. Onboarding new partners used to take around 30 to 45 days, but now it takes nearly 10 days. Additionally, we reduced failed message retries by roughly 10 percent or less. This is very useful, significantly reducing the manual reconciliation effort and noticeably cutting partner onboarding time.

Axway AMPLIFY B2B Integration offers several best features, including broad protocol support. It has native support for AS2, AS4, SFTP, FTPS, and all kinds of communication channels. We can connect with virtually any trading partner regardless of their technical setup without custom code per protocol.

The partner management console is a major feature. A centralized UI allows us to manage trading partners' profiles, certificates, routing rules, protocol preferences, and SLAs, making partner onboarding largely configuration-driven rather than a coding exercise each time.

Another main advantage is the data transformation and mapping engine. It has built-in mapping tools to translate between formats such as EDMI, XML, flat files, SWIFT MT, and ISO. These tools are useful in converting between core banking formats and external payment messaging standards.

Axway AMPLIFY B2B Integration also guarantees delivery and non-repudiation, with message tracking with retry logic, delivery confirmation, and digital signature receipts, which are critical for audit trails in a regulated environment such as banking.

Security is important in every tool, so end-to-end encryption, certificate lifecycle management, and support for regulatory standards are important features for SWIFT and payment-related data.

Axway AMPLIFY B2B Integration provides visibility and monitoring dashboards, which are used for real-time tracking of message flows, failures, and SLA breaches. The ops team can spot and resolve issues before they cascade into missed payment cutoffs.

The system's high availability and scalability, clustering support, and load balancing are needed to handle high transaction volumes reliably, which is relevant for a bank processing large SWIFT payment message volumes daily.

The API-led extensibility, called Amplify Platform, is part of the broader Axway Amplify Platform. Axway AMPLIFY B2B Integration can integrate with API gateways and other Amplify components, allowing us to expose B2B flows as APIs for more modern integration patterns alongside traditional file-based exchange.

The feature I find myself relying on the most day-to-day is the protocol connectivity flexibility. Since I use Axway AMPLIFY B2B Integration to build something protocol-agnostic, it is quite good. This is probably the closest to my daily work. The other major things I rely on are guaranteed delivery and tracking. These are critical for my payment system. When dealing with payment messages, a lost or duplicate message is a big deal, so this is a very good feature.

The positive impact on my organization from Axway AMPLIFY B2B Integration is that it accelerates partner onboarding. The partner onboarding time was reduced with the effort to bring new trading partners online because protocol and mapping configuration replaced custom point-to-point code.

Another benefit is reduced operational risk. Guaranteed delivery and audit trails cut down on manual reconciliation and missed or failed payment messages.

Standardization is another advantage, with the protocol-agnostic layer we built, meaning the bank can support diverse partners without proliferative one-off integration, cutting down on maintenance overhead.

The performance is very good, touching the report generation flows tied to B2B message volumes, which is a concrete and quantifiable metric I can cite directly.

I can share specific metrics that show how Axway AMPLIFY B2B Integration has helped my organization. The patching solution improved report generation performance by over 60 percent. Onboarding new partners used to take around 30 to 45 days, but now it takes nearly 10 days. Additionally, we reduced failed message retries by roughly 10 percent or less. This is very useful, significantly reducing the manual reconciliation effort and noticeably cutting partner onboarding time.

Axway AMPLIFY B2B Integration can be improved in several areas. The architecture has legacy roots. Some people feel the platform has not fully caught up to cloud-native or container-first designs compared to newer iPaaS competitors such as MuleSoft, Boomi, or Azure Logic Apps. Faster progress on Kubernetes-native deployment and horizontal scaling would help.

UI/UX modernization is also required. The trading partner management console and mapping tools are often described as dated compared to more visual, drag-and-drop modern integration platforms. A refreshed, more intuitive UI would reduce the learning curve for new engineers.

Better observability and analytics are needed. While Axway AMPLIFY B2B Integration has monitoring dashboards, deeper real-time analytics would help ops teams get ahead of issues rather than just react to them.

Furthermore, the mapping engine can get complex for advanced transformation, especially around nested hierarchical formats such as ISO 20022 XML. A more visual, testable mapping designer would reduce development time.

Better first-class support for REST and GraphQL alongside traditional EDI and AS2 flows would help organizations blend modern API integration with legacy B2B protocols on one platform, rather than needing separate tools stitched together.

Axway AMPLIFY B2B Integration is stable. In my experience, it has been stable and reliable for core message delivery. I have not seen it silently lose a transaction, and the retry acknowledgment mechanism means failures are visible rather than hidden. The friction I have seen has stemmed less from platform stability and more from configuration complexity, such as mapping edge cases for nested ISO 20022 fields, which is more of a development and testing discipline issue than a platform reliability issue.

Axway AMPLIFY B2B Integration's scalability includes horizontal scaling via clustering and load balancing, along with database-backed state management, separation of processing tiers, and batch versus real-time handling.

The customer support for Axway AMPLIFY B2B Integration is great, and I rate it 10 out of 10.

My advice for others looking into using Axway AMPLIFY B2B Integration is to focus on mapping transformation testing. I do not want to underestimate certificate management, as expired certificates are one of the most common causes of mystery outages in B2B integration. Setting up proactive expired alerts well before renewal deadlines is essential; do not rely on manual tracking. Standardizing partner onboarding early and building monitoring and alerting beyond the platform defaults while planning for scale early and not reactively is critical. Keep the transformation logic modular and documented, and pair it with strong internal governance, not just platform features. These key elements will benefit others as well. I would rate my overall experience with Axway AMPLIFY B2B Integration an 8 out of 10.

I am currently working on new partner onboarding for Axway AMPLIFY B2B Integration, and we handle day-to-day activities. When there is an integration issue, we work on it and find the root cause. We also deploy new partners, set up new flows according to partner requirements, and establish connectivity with new partners. Additionally, we maintain our certificates and ensure connectivity for our existing partners.

I have worked with OpenText for a small project for three months. In comparison to Axway AMPLIFY B2B Integration, I think Axway is superior in terms of UI and adaptability.

In Axway AMPLIFY B2B Integration, the best aspect is that it supports almost every protocol for every connection type. You can connect Axway AMPLIFY B2B Integration to MQ, TradeXpress, and any other tool, which I consider the best feature. The UI is very user-friendly, allowing you to easily set up a partner and configure the flow.

Axway AMPLIFY B2B Integration has advanced mapping features connected through AI. There is no need to write any complex logic; you can simply provide the condition, and it creates the map for you. The multi-output mapping capability is useful for some partners, and you can also implement conditional mapping such as if-else conditions and switch cases. Additionally, you can use looping for repetitive segments in mapping.

The advanced mapping features in Axway AMPLIFY B2B Integration are very flexible for data validation and include user-defined functions for data conversion and string formatting. The product also provides string functions such as trim, uppercase, lowercase, and replace, which can be very helpful.

Axway AMPLIFY B2B Integration comes with a product called Sentinel, which allows us to track each and every transaction and see how many transactions occur per day. Based on that record, we can assist the vendor in identifying how they might modify their system according to that bandwidth.

Real-time analytics and monitoring through Axway AMPLIFY B2B Integration have enhanced my decision-making processes because it has its own monitoring tool called Fusion, through which we can monitor all the systems. We can check all nodes and the product and see if there are any failures.

Axway AMPLIFY B2B Integration has strong security features, as my application architecture includes an Axway AMPLIFY B2B Integration node with a DMZ server in front. External traffic cannot hit Axway AMPLIFY B2B Integration directly; it first goes to the DMZ node, which acts as a firewall. After identifying the partner and the specific file, only then does it enter the server and go into the main application, so they employ a very robust security mechanism.

The main benefit I see from using Axway AMPLIFY B2B Integration is its adaptability. If I have a partner that can only connect through the OFTP2 protocol, it is easy for me because Axway AMPLIFY B2B Integration is adaptable for every protocol. You can deploy that partner in your system without facing any challenges.

For improvements in Axway AMPLIFY B2B Integration, I noticed that we are currently using version 2.6 from the July 2024 release, along with one latest version. There are some limitations in the old version that could be enhanced. Specifically, they should increase the support time for the older versions since many companies still use them. If there is an issue with the product, they sometimes say it is out of support, and this can be challenging. Moreover, not every organization agrees to upgrade to the latest version due to dependencies on older tools, such as an older version of the MQ tool.

In Axway AMPLIFY B2B Integration, an area for improvement is connectivity, especially in the latest versions that primarily support the most recent database versions. For instance, they do not support Oracle 12c, only 19c or 17c. They need to work on compatibility with all database versions, as upgrading Axway AMPLIFY B2B Integration often necessitates upgrading the database, which may not be feasible in some cases.

The key differences I see between Axway AMPLIFY B2B Integration and OpenText include, on the positive side, Axway AMPLIFY B2B Integration's database compatibility and adaptability. However, on the negative side, there is performance with large files when mapping can sometimes be slow, as well as significant memory consumption, requiring a server with high memory. Additionally, the initial setup can be complex, requiring an experienced administrator to manage it effectively.

I am currently using Axway AMPLIFY B2B Integration for new partner onboarding and day-to-day activities, and I have also worked with the product across multiple versions.

I find Axway AMPLIFY B2B Integration stable. In my project, we are using a cluster with Node 0 and Node 1, along with a load balancer, which ensures we do not face significant product issues or instability.

I can confidently say that Axway AMPLIFY B2B Integration is scalable and easy to scale up or out.

I would evaluate Axway AMPLIFY B2B Integration's tech support at 4.5 out of 5 since whenever we need assistance, calling them to raise a P1 gets them on the line within 10 minutes.

I have worked with OpenText for a small project for three months. In comparison to Axway AMPLIFY B2B Integration, I think Axway is superior in terms of UI and adaptability.

The key differences I see between Axway AMPLIFY B2B Integration and OpenText include, on the positive side, Axway AMPLIFY B2B Integration's database compatibility and adaptability. However, on the negative side, there is performance with large files when mapping can sometimes be slow, as well as significant memory consumption, requiring a server with high memory. Additionally, the initial setup can be complex, requiring an experienced administrator to manage it effectively.

In terms of Axway AMPLIFY B2B Integration's setup process, I did not face any major challenges, but you do need an admin for specific tasks. If you are using a cluster and it goes down, you need that admin to investigate and find the root cause of the issue.

I can confidently say that Axway AMPLIFY B2B Integration is cost-effective and brings good ROI. While there are many tools in the market, none offer the compatibility that Axway AMPLIFY B2B Integration provides. You can connect with any protocol, partner, or even directly to an API through Axway AMPLIFY B2B Integration, so this feature makes it a reasonable choice depending on your specific requirements.

Regarding the pricing aspect of Axway AMPLIFY B2B Integration, I do not know the exact cost, but as I mentioned earlier, there is a tool called Sentinel that allows them to charge per message. If you have a traffic of 1,000 messages, they will charge you for those 1,000 messages only.

I find the pricing reasonable because if I have a small organization and I am working with a few partners, I can take that subscription according to my bandwidth and traffic needs.

If you are considering transitioning to Axway AMPLIFY B2B Integration from another tool, my advice would be to assess your requirements first—how much traffic and load you anticipate. Based on that load, you can select an appropriate subscription. Axway AMPLIFY B2B Integration offers different packages, including a premium package that provides everything you need while managing daily transactions and gives you support if you encounter any issues. I would rate this solution an 8.5 out of 10 overall.

My main use case for Axway AMPLIFY B2B Integration is essentially as a gateway for any two ERPs, or any two system platforms, who cannot interact with each other directly, allowing them to exchange data.

Specific cases for Axway AMPLIFY B2B Integration include all the EDI transactions, as it accepts all the EDI file types and everything. The transmission is secured, encrypted, and signed, making it a seamless, easy, automated process.

The process of using Axway AMPLIFY B2B Integration helps my team day to day significantly. For a recent example, it is widely used for all health authorities for their overall data collection, mainly in pharmacovigilance, where I have worked extensively. Different CROs or Clinical Research Organizations perform clinical research on drugs, and it is mandatory for all health authorities, including pharma companies, to transmit their clinical trial cases and data to health authorities using Axway AMPLIFY B2B Integration. This automation process causes data that could take around three to six months to reach a health authority manually to instead take at most two or three minutes; it is all digitized. They use the internet and various methods to send data, with Axway AMPLIFY B2B Integration utilizing multiple means, the most common being data transmission via REST API URLs, enabling easy interaction with health authority URLs on the same platform.

Axway AMPLIFY B2B Integration offers outstanding features, including the latest signing and encryption algorithms, allowing users to create their own certificates. It possesses a very easy user interface where users can easily create a community and configure partners, manage partner certificates, and ensure that messages exchanged with health authorities or the community are integrated, signed, and secured effortlessly on a day-to-day level.

The easy-to-use interface and straightforward certificate management within Axway AMPLIFY B2B Integration have made my work much easier and more efficient. For instance, creating a certificate in Axway AMPLIFY B2B Integration takes hardly two to three minutes. It has its own encryption mechanism and a method for creating self-signed certificates, which saves me from the hassle of using multiple unreliable tools or reaching out to costly certificate authorities like Symantec or GoDaddy. This in-house option is cost-effective and incorporates the latest encryption mechanisms like SHA-256 or SHA-1, standard practices in data encryption and exchange.

Axway AMPLIFY B2B Integration positively impacts my organization as it acts as an easy gateway; we need not set up various inbound bridges or coding mechanisms for exchanging data with different partners. With this one-stop shop, we can create different partner profiles and seamlessly exchange data using secure measures.

Time savings are evident; if individual data channels are created with different partners, it would consume substantial time and cost, but Axway AMPLIFY B2B Integration provides an easy method for managing multiple partners efficiently and simultaneously. The add-ons, including certificates and encryption algorithms, can also be swiftly managed through Axway AMPLIFY B2B Integration.

Axway AMPLIFY B2B Integration can be improved in ways such as incorporating AI to create inbound ERP or system access to collect data and create dignified or EDI files for transmission. If Axway AMPLIFY B2B Integration could implement an AI module to interact seamlessly with downstream applications using its logic and allowing users to input their own business logic for file transmission, that would elevate user experience.

The accuracy and reliability of output from Axway AMPLIFY B2B Integration are still areas needing improvement.

I have been using Axway AMPLIFY B2B Integration for approximately eight years.

Axway AMPLIFY B2B Integration is stable.

The scalability of Axway AMPLIFY B2B Integration is straightforward, providing functionality for having multiple nodes to manage heavy inbound traffic, allowing efficient routing of that traffic across different nodes and handling network complexity smoothly.

Customer support for Axway AMPLIFY B2B Integration is efficient.

Previously, we used Seeburger, which was a good tool in its time, but considering the current era, Axway AMPLIFY B2B Integration is much better than Seeburger.

I can say that it is efficient, but specific metrics regarding return on investment are confidential, so I am not at liberty to disclose them.

The setup cost for Axway AMPLIFY B2B Integration is an area that should definitely be addressed.

We also evaluated other options, such as IBM Sterling Integrator and Seeburger, but Axway AMPLIFY B2B Integration was the most user-friendly choice.

I have not encountered a system that cannot directly integrate with Axway AMPLIFY B2B Integration; it seems to work well for me. They just need to keep updated with new upcoming platforms.

My advice for others considering Axway AMPLIFY B2B Integration is to review the training material provided by Axway and engage in hands-on training; once completed, it becomes much easier to use. I would rate this product an eight out of ten.

For the B2B gateway, we are exposing a few APIs and those are exposed as APIs, and the messaging format that we use is ebXMLs. Basically, we have a lot of our consumers coming onto the B2B gateway, posting orders.

For my integration, I am very new to the product, so I'm not aware of other scenarios, but for my use case, we use ebXMLs. ebXMLs are not normal XML or SOAP XML messages. They are signed XMLs in which you also have a few certificate details and other things. That messaging standard is currently supported by Axway AMPLIFY B2B Integration and also by Oracle SOA Suite. We do not have enough products in the market, so Axway is one of them which is supporting ebXMLs. That's the reason why we are working on it.

Since we use it more for business-to-business communications, we use it to onboard a lot of our communication providers onto our platform so that we will check various functionalities. For example, if you consider your internet connection at home, we use it to check faults in the line, check the availability of whether your area is serviceable or not. All of that information we check. We provide services to a lot of our communication partners like Vodafone, TalkTalk, and Sky. They connect to our B2B gateway and we call them dialogue services. They connect to our dialogue services as ebXML APIs and then they do the further checks, whatever if they need any serviceability, whether that area is serviceable or not, do we have enough connectivity, what is the bandwidth that we can provide in that area. All these checks we do. Generally, all business-to-business calls occur. There is no individual intervention here.

Axway AMPLIFY B2B Integration is good. We have used various functionalities of a forwarder. We terminate the SSL connections at the entry point of the gateway. We use it as an SSL termination product as well, basically for mutual TLS because we exchange certificates and consumers come and connect to us over mutual TLS with the certificate exchange. We use it as an SSL termination tool as well. So that's how we have been using it.

It is very useful. We use the inbuilt functionalities of Axway AMPLIFY B2B Integration for our analysis and to identify the point of failures. Additionally, we also dump our logs into Splunk and we also rely on external kinds of monitoring tools.

Basically, what happens is that during the initial boot-up of the product upon installation, we do face some hiccups because of the DB connectivity. That is a major issue in which initially the console doesn't load properly. This is the initial part. Although during transactions, we have not faced any issues. But here and there, those internal DBs which will be storing all those configurations are impacted sometimes.

It is the process of integration with the DB and the loading up of the console, which is something we found difficult. That is one thing. Another thing which we found is that we were running a migration project from Oracle onto Axway AMPLIFY B2B Integration. In that migration project, we found that we wanted to modify a few headers. That is something which is not available out-of-the-box. We had to write some custom coding. That's the reason why we had to take help from Axway Professional Services. Configurations or customizations is something which is not very easy. We have to go through a lot of assistance from Axway support team, their product support team, to get those custom logics implemented here. These were header conversions, basically upper case to lower case header conversions.

It is a little complex because as I said, we do certificate installations. Axway AMPLIFY B2B Integration doesn't have a trust store or certificate store which will hold all the certificates. This is not the same, because as I said, we were migrating from Oracle. Oracle was having a trust store. Axway AMPLIFY B2B Integration was not having a trust store. Somehow mapping that was kind of difficult for us to set it up initially.

We are satisfied with the functionality part. Performance is also not an issue. Sometimes we do face some issues loading up and with customizations.

For the last one year, I have been working with Axway AMPLIFY B2B Integration.

Although we are not using them, the feature is very helpful. What we do is that we just pass on those requests into our downstream ESB systems, Enterprise Service Buses for integration. They pass the request from meaningful XMLs and give acknowledgements and other things, and integrate to various other downstream systems. But we have not integrated it into any ERP system.

The model, since we are using other products of Axway as well, it's not a pay-per-use, it's a per-transaction model which we are using. It's per transaction that Axway is billing us. Ours is a different pricing model where, as I said, it's per transaction, and that model is clubbed along with our Axway API Gateway as well. That way, we are getting a few leeways.

Currently, we were using Oracle SOA Suite, and Axway AMPLIFY B2B Integration also satisfies the product. It has almost 95% plus, I think 95 to 100% of the features of the products offered in the market are available with Axway AMPLIFY B2B Integration. Basically, whatever Axway AMPLIFY B2B Integration is offering is up to the market standards and up to the requirements of the customers.

We do work on Axway AMPLIFY B2B Integration as well, as I mentioned, I already left a review three months ago about Axway API Management.

We have a separate product called Axway API Gateway, which we use for API Management. An interesting fact is that we are also running a program to migrate all those legacy ebXMLs onto our Axway API Management gateway because as I said, ebXMLs is not a very popular messaging standard. We are going to expose these, basically APIs on Axway AMPLIFY B2B Integration as REST APIs on Axway. That migration will also undergo. It is in progress, but not fully live.

We are the users of the product and we are using a per-transaction based model. My overall rating for this product is 9 out of 10.

My main use case for Axway AMPLIFY B2B Integration involves mapping and troubleshooting, as well as reviewing data flows. I use Axway AMPLIFY B2B Integration day-to-day primarily for partner onboarding, mapping, and monitoring B2B EDI flows.

Axway AMPLIFY B2B Integration offers several best features, including being a central hub for managing all B2B EDI traffic between payer, provider, and vendor onboarding. I appreciate how it handles X12, UN/EDIFACT, XML, JSON, and flat files. The mapping transformation feature stands out for me because it allows me to build reusable mapping templates between X12 and internal formats, validate segments, loops, and elements, and handle all different versions such as 4010, 5010, and custom guides. I can also apply business rules within the mapping transformation.

Axway AMPLIFY B2B Integration has positively impacted my organization by making processes smoother and quicker than our previous solution. It accomplishes this by supporting automated partner onboarding, automated routing logic, automated error handling, and organized workflows.

I cannot think of any improvements for Axway AMPLIFY B2B Integration at this time.

I have been using Axway AMPLIFY B2B Integration for approximately five years.

Axway AMPLIFY B2B Integration is stable in my experience.

Axway AMPLIFY B2B Integration's scalability is good.

Axway AMPLIFY B2B Integration's customer support is quite good.

Before Axway AMPLIFY B2B Integration, we used a proprietary solution. We switched because Axway seemed to be a better option that was faster, and we valued the AI capabilities.

I have not seen a return on investment. I have not noticed fewer employees needed, money saved, or time saved.

Regarding Axway AMPLIFY B2B Integration's AI capabilities, I believe its governance and security are solid. Axway AMPLIFY B2B Integration uses machine learning to detect recurring transaction failures, identify abnormal partner behavior, and flag unusual payload patterns, highlighting anomalies in X12, XML, JSON, or flat files. I would advise others looking into using Axway AMPLIFY B2B Integration to research it and other products to determine which one they believe is best. I give this product an overall rating of 8 out of 10.

We use the solution for transmission purposes, where we send files from our system to the customer's system.

Axway AMPLIFY B2B Integration has a great user interface that is easy to understand. The solution can easily find errors, update the certificate, and retransmit the batch files.

The solution's performance could be improved and made similar to that of IBM Sterling B2B Integrator.

I have been using Axway AMPLIFY B2B Integration for three years.

I rate the solution an eight or nine out of ten for stability.

We do not have any issue with the solution's scalability. We added new partners, and we already have more than 1,000 partners.

The solution's technical support team is very good and responds very quickly.

I also work with IBM Sterling B2B Integrator. Unlike Axway AMPLIFY B2B Integration, IBM Sterling B2B Integrator doesn't have a UI-based platform to monitor all incoming and outgoing transactions.

We use IBM Sterling B2B Integrator for everything, including transmission. We use Axway AMPLIFY B2B Integration only for transmission purposes. We use Axway AMPLIFY B2B Integration because it has a great user interface, which makes it very easy to monitor everything.

IBM Sterling B2B Integrator is better than Axway AMPLIFY B2B Integration because it is a very robust solution. Unlike cloud-based systems, IBM Sterling B2B Integrator can handle very complex logic. It can easily process files with 5 GB to 10 GB sizes. Once you take the license, you won't have to pay anything extra for computing power.

The solution's initial setup is very simple. You just have to give a list of commands, and it will install any update.

Compared to other SaaS platforms, the solution's pricing is less.

The solution is deployed on the cloud. I would recommend the solution to other users.

Overall, I rate Axway AMPLIFY B2B Integration a seven or eight out of ten.

We are using it for data transfers. It's a data transfer tool. It provides a lot of management and makes everything very simple. 

Everything used to be done with home-grown scripts. This kind of information is taken care of by this solution that brings in its own database. Manual scripting has been removed from the process.

The automation of all the data transfers is great. It removes manual scripting needs and home-grown scripting. It makes it easier to manage. You can see what data was transferred to the customer and vice versa.

It can transfer data in one format, and we can use various formats and centralizes everything without issue.

They are moving into the cloud. We're happy this is happening. Moving into the cloud will take care of all the day-to-day maintenance we have traditionally had to deal with. Updates and backups will be simpler. 

The initial setup can be a bit tricky. It's technical, and it's important to go through all documentation first.

We are happy with the features so far. 

The company has used the solution for the past 20 years. I've personally used it for four years. 

The solution is stable. I'd rate it seven out of ten. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable. 

The solution is scalable. I'd rate it eight out of ten. 

Technical support is very helpful. We are happy with the level of service we receive.

The initial setup was a bit tricky. You need to know what you are doing. It's important to go through the requirements and documentation first. If you don't follow, you will face hiccups. It's not exactly intuitive. 

I don't deal with pricing. I can't speak to the exact cost.

I'm using the latest version. 

I'd recommend the solution to others. 

I'd rate it eight out of ten.