How to use Deployment Automation Manager

Go to <url_site>/suite/plugins/servlet/deploymentautomation. The documentation can be found here:
forum.appian.com/.../summary
and here:
community.appian.com/.../deployment-automation
Do you have a specific question?

Hi matts401, thanks for replying.

Yes. So basically I need to go my environment A, export the application in the Appian Designer, and then go to my environment B using this url: <myurl_site>/suite/plugins/servlet/deploymentautomation , use this tool to import the application. Is this so easy?

Yes. You also have the option of doing the import using the command line tool available on the Forum link I posted above. Remember it is a best practice to run an Inspect of your application in environment B before doing the Import, which you can also do with this tool

Can you explain me the difference between this, and simply export the application in the Appian Designer on my environment A, and go to my environment B and also import the application in the Appian Designer?

Deployment Automation Manager (DAM) is a bit more robust. Here are a few reasons why:
-Doing an Inspect or Import via /design throws 504 Gateway Timeout errors if the Inspect/Import takes longer than 5 minutes. DAM doesn't have this problem
-DAM allows you to trigger the deployments from an external CI/CD tool, ie Jenkins
-DAM also allows you to import Admin console settings and DDL, which is beyond the capabilities of an Import via /design

Deployment Automation Manager (DAM) is a bit more robust. Here are a few reasons why:
-Doing an Inspect or Import via /design throws 504 Gateway Timeout errors if the Inspect/Import takes longer than 5 minutes. DAM doesn't have this problem
-DAM allows you to trigger the deployments from an external CI/CD tool, ie Jenkins
-DAM also allows you to import Admin console settings and DDL, which is beyond the capabilities of an Import via /design