Business Analyst at a manufacturing company with 10,001+ employees
Real User
Top 5
Jul 15, 2026
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.
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.
Learn what your peers think about Axway AMPLIFY B2B Integration. Get advice and tips from experienced pros sharing their opinions. Updated: August 2026.
Axway AMPLIFY B2B Integration provides a seamless approach for businesses to integrate their B2B processes. It enables efficient data exchange, ensuring reliable and compliant B2B interactions.
Axway AMPLIFY B2B Integration supports enterprises in connecting with partners, enhancing collaboration, and streamlining supply chain operations. Its architecture ensures secure and scalable data exchanges, simplifying complex integrations. This solution supports digital business initiatives,...
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.
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.
We use the solution for transmission purposes, where we send files from our system to the customer's system.
We are using it for data transfers. It's a data transfer tool. It provides a lot of management and makes everything very simple.