Axway

Axway Amplify OUM CLIManage organizations, teams, and users.InstallationThis package is bundled with the Axway CLI and thus does not need to be directly installed.npm i -g axwayUsageOrganizationsList all organizations:$ axway org listView an organization:$ axway org view$ axway org view Rename an organization:$ axway org rename Organization UsersList all organization users:$ axway org user list Add a user to an org:$ axway org user add --role [...--role ]Update a user's roles:$ axway org user update --role [...--role ]Delete a user:$ axway org user remove Organization TeamsList all organization teams:$ axway team list [org]View a team's info:$ axway team view Add a team to an org:$ axway team add --desc [value] --tag [tag1] --tag [tag2] --defaultUpdate a team:$ axway team update # shows help$ axway team update # shows help$ axway team update --name [value] --desc [value] --tag [tag1] --tag [tag2] --defaultRemove a team from an org:$ axway team remove Organization Team UsersList all users in a team:$ axway team user list Add a user to a team:$ axway team user add --role [...--role ]Update a user's role within a team:$ axway team user update --role [...--role ]Remove a user from a team:$ axway team user remove Organization UsageView the usage:$ axway org usage --from [yyyy-mm-dd] --to [yyyy-mm-dd]Organization ActivityView the organization activity:$ axway org activity --from [yyyy-mm-dd] --to [yyyy-mm-dd]Organization IdPManage the organization identity provider settings:$ axway org idp Account ManagementView an account including organizations and roles:$ axway user viewUpdate your account information:$ axway user update --first-name --last-name View your user activity:$ axway user activity --from [yyyy-mm-dd] --to [yyyy-mm-dd]Change your log in credentials:$ axway user credentialsLegalThis project is open source under the Apache Public License v2 and is developed byAxway, Inc and the community. Please read the LICENSE file includedin this distribution for more information.

HomeAxway AMPLIFY Application Integration vs. Azure Data FactoryAxway and Microsoft are both solutions in the Data Integration category. Axway is ranked #42 with an average rating of 7.5, while Microsoft is ranked #1 with an average rating of 8.0. Axway holds a 0.3% mindshare in DI, compared to Microsoft’s 10.0% mindshare. Additionally, 100% of Axway users are willing to recommend the solution, compared to 92% of Microsoft users who would recommend it. Comparison Buyer's GuideExecutive SummaryUpdated on Dec 19, 2024Axway AMPLIFY Application Integration and Azure Data Factory compete in the integration and data transformation software market. Azure Data Factory takes the lead with its advanced feature set and scalability, appealing to large enterprises.Features: Axway AMPLIFY is noted for its extensive connectivity capabilities, seamless message integration, and robust file transfer features, making it suitable for complex workflows. Azure Data Factory provides a complete ETL solution, vast data transformation capabilities, and seamless integration with other Azure services, offering powerful real-time analytics.Room for Improvement: Axway AMPLIFY could enhance its cloud integration options to better compete with cloud-first competitors. It may also benefit from expanding its customer support channels and simplifying on-premise configurations. Azure Data Factory might improve by optimizing its monitoring features, expanding support documentation, and refining its cost predictability for complex projects.Ease of Deployment and Customer Service: Axway AMPLIFY offers a user-friendly setup, although its on-premise options can complicate deployment. Azure Data Factory benefits from straightforward cloud-based deployment, backed by extensive Microsoft Azure infrastructure. Azure's customer service is often praised for its responsiveness and comprehensive online resources, setting a higher support standard.Pricing and ROI: Axway AMPLIFY is priced accessibly for small to mid-sized organizations, yielding strong ROI for specific integration needs. Azure Data Factory, though potentially more costly, offers advanced features and scalability, making it a preferred choice for large enterprises seeking significant data operations, with scalability providing greater long-term value.Review summaries and opinionsCategories and RankingAxway AMPLIFY Application I...Ranking in Data Integration42ndRanking in other categoriesNo ranking in other categoriesRanking in Data Integration1stRanking in other categoriesCloud Data Warehouse (3rd)Mindshare comparisonAs of March 2025, in the Data Integration category, the mindshare of Axway AMPLIFY Application Integration is 0.3%, up from 0.3% compared to the previous year. The mindshare of Azure Data Factory is 10.0%, down from 12.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.Featured ReviewsQuotes from MembersProsConsPricing and Cost AdviceUse our free recommendation engine to learn which Data Integration solutions are best for your needs.842,194 professionals have used our research since 2012.Top IndustriesCompany SizeQuestions from the CommunityComparisonsProduct ReportsAlso Known AsOverviewSample Customers Find out what your peers are saying about Axway AMPLIFY Application Integration vs. Azure Data Factory and other solutions. Updated: March 2025.842,194 professionals have used our

Secure internal file transfer solutions by Axway ensure safe and seamless data exchanges within organizations.Welcome to our comprehensive guide on AdHoc File Transfer with Axway SecureTransport! In this video, we'll explore how Axway SecureTransport simplifies and secures your file transfer processes, making it easier than ever to manage and monitor your data exchanges. Whether you're an IT professional, a business owner, or someone interested in secure file transfer solutions, this video provides valuable insights into the capabilities of Axway SecureTransport. Learn how to enhance your file transfer processes, ensure data security, and meet compliance requirements with the Out of the box AdHoc File transfer movement capability.What You'll Learn:Why you need AdHoc File transfer capability in your organization? Real-World Use Cases example Demonstration on how to use AdHoc data exchange as business user Demonstration on configuration of secure folder for partner collaboration Benefits of using this approach Don't Forget to Subscribe! If you found this video helpful, please like, share, and subscribe to our channel for more tutorials and updates on secure file transfer solutions. Hit the notification bell to stay updated on our latest content!Hello everyone, my name is Aniruddhya Baidya, and I serve as a Principal Solution Architect here at Axway. It’s my pleasure to welcome you to our current discussion on ad hoc file movement, a feature within Axway's managed file transfer solution called Secure Transport.For today, we have segmented the objectives into the following segments:Let’s start with a quick overview. Why might you need ad hoc file transfer? What makes it compelling or important to have this capability in your organization? To better understand this, let’s quickly touch base on the traditional MFT approach, which, in simple terms, refers to sending or receiving a file from defined sources or destinations over a secure channel. However, there are a few key challenges here. Imagine if you want to perform data exchange with a user who does not exist in your system, create one-time downloads, share files over email, or create shared folders for partner collaboration. All of these use cases make a compelling argument for why you need

How to upgrade systems with Account Retention or File Retention Add-on? In case account data import from SecureTransport 5.4 or 5.3.6 to a new SecureTransport 5.5 installation, File Retention and Account Retention properties will be recognized automatically. No additional actions are needed. In case of in-place upgrade from SecureTransport 5.4 or 5.3.6 to SecureTransport 5.5, the File Retention and/or Account Retention add-ons must be uninstalled completely BEFORE the upgrade is performed, following the steps below. After the upgrade the existing File Retention and Account Retention properties will be recognized automatically. No additional actions are needed.Remove File Retention Add-on filesBefore starting the upgrade to SecureTransport 5.5, perform the following:1. Stop ALL SecureTransport services2. Delete the following files under SecureTransport's home folder ():/brules/local/agents/inprocess/jars/fileretention-agents.jar/brules/local/wptdocuments/FileRetentionApp.xml/conf/mailer-templates/FileRetentionNotification.xhtml/lib/jars/fileretention-plugin.jar/lib/jars/fileretention-shared.jar/tomcat/admin/webapps/coreadmin/WEB-INF/classes/fileretention_account_errors.properties/tomcat/admin/webapps/coreadmin/WEB-INF/classes/fileretention_errors.properties/tomcat/admin/webapps/coreadmin/WEB-INF/classes/firetention_bu_errors.properties/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/applicationtypes/fileRetentionApp.jspx/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/fileRetentionAccount.jspx/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/fileRetentionAccountReadOnly.jspx/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/fileRetentionBusinessUnit.jspx3. Open /tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/plugin.xml file and delete the following:4. Open the /brules/local/agentlist.addin file and delete the following:com.axway.st.server.fileretentionapp.agents.FileRetentionAgent5. Open the /brules/local/wptdocuments/wptdocument.conf file and delete the following:FileRetentionApp=enabled6. Open the /conf/tm-log4j.xml file and delete the following blocks: appender with name FileRetentionLog /var/logs/fileretention-tm.log"/> /var/db/hist/logs/"/> logger with name com.axway.st.server.fileretentionapp.agents logger with name com.axway.st.server.fileretentionapp.shared 7. Open the /conf/admin-log4j.xml file and delete the following blocks: appender with name FileRetentionAdminLog /var/logs/admin/fileretention-admin.log"/> /var/db/hist/logs/admin"/> logger with name com.axway.st.server.fileretentionapp.admin 8. Open the /tomcat/admin/webapps/coreadmin/WEB-INF/plugin/applicationtypes/plugin.xml file and delete the following: Remove Account Retention Add-on filesBefore starting the upgrade to SecureTransport 5.5, perform the following:1. Stop ALL SecureTransport services2. Delete the following files under SecureTransport's home folder ():/lib/jars/Axway-AccountRetentionPolicy-psolicensemenu.jar/brules/local/agents/inprocess/jars/Axway-AccountRetentionPolicy-agents.jar/brules/local/wptdocuments/AccountTTLApp.xml/conf/mailer-templates/AccountTTLNotification.xhtml/conf/mailer-templates/AccountTTLNotificationAdmin.xhtml/lib/jars/Axway-AccountRetentionPolicy-admin.jar/lib/jars/Axway-AccountRetentionPolicy-license-tag.jar/lib/jars/Axway-AccountRetentionPolicy-license-tool.jar/lib/jars/Axway-AccountRetentionPolicy-utils.jar/tomcat/admin/webapps/coreadmin/WEB-INF/classes/cdg_errortext_accountretention.properties/tomcat/admin/webapps/coreadmin/WEB-INF/classes/cdg_errortext_accountretention_bu.properties/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/applicationtypes/AccountTTL.jspx/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/accountRetentionAccount.jspx/tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/accountRetentionBusinessUnit.jspx3. Open the /tomcat/admin/webapps/coreadmin/WEB-INF/plugin/pagecustomizations/plugin.xml file and delete the following:4. Open the /brules/local/agentlist.addin file and delete the following:com.axway.cdg.st.server.enhancedmaintenance.agents.AccountTTLAgent5. Open the /brules/local/wptdocuments/wptdocument.conf and delete the following:AccountTTLApp=enabled6. Open the /conf/tm-log4j.xml file and delete the following blocks: appender with name pso-rpa-accountTTL /var/logs/pso-rpa-accountTTL.log"/> /var/logs"/> logger with name com.axway.cdg.st.server.enhancedmaintenance.agents.AccountTTLAgent 7. Open the /conf/admin-log4j.xml file and delete the following: appender with name RetentionPolicyAdministrationAdmin /logs/admin/pso-rpa-admin.log"/> /var/db/hist/logs/admin"/> logger with name com.axway.cdg.st.server.enhancedmaintenance.admin 8. Open the /tomcat/admin/webapps/coreadmin/WEB-INF/plugin/applicationtypes/plugin.xml file and delete the following: Remove the Add-on Licenses menu from the Admin UI after the upgradeThe "Add-on Licenses" menu in the SecureTransport 5.5 Admin UI will still be available after in-place upgrade. The Account Maintenance application no-longer requires additional licensing and will be fully operational. The Add-on Licenses menu will not have functional impact. You can leave it there, or you

IntroductionIntegration webhooks provide an “event” based means to monitor activity in Amplify Central in an external application that you create. Coupled with Amplify Central platform APIs, integration webhooks are a powerful tool for integrating Amplify Central into the rest of your API first toolchain.Integration webhooks are different than subscription webhooks, which are added to an environment and pertain to API subscription requests for catalog items from the environment. Integration webhooks can apply to one or more environments and pertain to many resources across those environments.For example, you can configure an integration webhook to trigger whenever an API Service is added to one or more environments or when an attribute is added to the environment. You use Amplify Central APIs or the Amplify CLI to configure integration webhooks. In this blog post, we’ll use APIs.Refer to the online docs: Set up integrations through Webhooks for all the technical details around integration webhooks.Let’s walk through an example of how to set up and test an integration webhook.Note: Refer to this blog post to learn how to make API calls to Amplify Central.Create an Integration WebhookIntegration Webhooks can be configured using the Axway CLI or via API calls. In this blog post series, I’ll be using APIs.In the following API calls, {{apiCentralUrl}} is the Amplify Central base address for API calls. By default, it is but could be different based on your region. Also, in all the API calls below, you need to pass in the following headers as described here:'Authorization': `Bearer `,'Content-Type': 'application/json'Create the IntegrationUse the following API call to create an integration called myintegration.POST {{apiCentralUrl}}/apis/management/v1alpha1/integrationsBody:{ "name": "myintegration", "title": "Integration", "tags": [ "cloud" ], "attributes": {}, "spec": { "description": "This is an integration." }}Create a SecretWe can use a secret so that the app that receives the webhook can be sure it is coming from a trusted source. The secret will be sent as an Authorization header.POST {{apiCentralUrl}}/apis/management/v1alpha1/integrations/myintegration/secretsBody:{ "name": "webhooksecret", "title": "API Key Secret for Webhook reference", "tags": [ "saas", "axway" ], "attributes": { }, "spec": { "data": { "apikey": "Password123" } }}Note that in this example, my Integration named myintegration is part of the API path (/apis/management/v1alpha1/integrations/{{IntegrationName}}/webhooks). This is the name given to the Integration in the prior API call.Note that you can see Password123 in the webhook Authorization header when triggered as follows:Host: en9c5wvi5vta4.x.pipedream.netX-Amzn-Trace-Id: Root=1-6065c447-3c5b35a840f6e43e078b9c79Content-Length: 1295Authorization: Password123X-Axway-Event-Id: 170d3081-9c48-459e-82e2-f37f5e3f1d74User-Agent: amplify-centralAccept: application/jsonContent-Type: application/jsonCreate a WebhookLet’s create a webhook in this integration. The