---
title: Step 3. Deploy AM
description: Deploying AM creates a default configuration you can access as AM's administrative user, amAdmin.
component: pingam
version: 8.1
page_id: pingam:evaluation:step-3-deploy-am
canonical_url: https://docs.pingidentity.com/pingam/8.1/evaluation/step-3-deploy-am.html
keywords: ["Evaluation", "Deployment"]
page_aliases: ["eval-guide:step-3-deploy-am.adoc"]
---

# Step 3. Deploy AM

Deploying AM creates a default configuration you can access as AM's administrative user, `amAdmin`.

Deploy AM into Apache Tomcat and configure it for use:

1. Copy the AM `.war` file to deploy in Apache Tomcat as `am.war` :

   ```bash
   $ cp AM-8.1.0.war /path/to/tomcat/webapps/am.war
   ```

   It can take Apache Tomcat several seconds to deploy AM.

2. Go to the deployed AM application. For example, `http://am.example.com:8080/am`.

3. On the initial configuration page, click Create New Configuration.

4. Review the software license agreement. If you agree to the license, click I accept the license agreement, and click Continue.

5. Set the Default User \[amAdmin] password to `changeit`, and click Next.

   |   |                                                                                                                                                                                                        |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
   |   | Don't use this password when configuring AM for real-world use. It is only to get started with AM. The `amAdmin` user is the default AM administrator, who has full control over the AM configuration. |

6. On the Server Settings page, enter the following details and click Next:

   * Server URL

     `http://am.example.com:8080`

   * Cookie Domain

     `am.example.com`

   * Platform Locale

     `en_US`

   * Configuration Directory

     `<$HOME>/am` making sure you replace `<$HOME>` with the full path to your `$HOME` directory.

7. On the Configuration Data Store Settings page, enter the following details and click Next:

   * SSL/TLS Enabled

     Select this option to use LDAPS to communicate with the configuration store. DS is configured for LDAPS by default.

   * Host Name

     `ds.example.com`

   * Port

     `1636`

   * Encryption Key

     Keep the randomly generated key.

   * Root Suffix

     `ou=am-config`

   * Login ID

     `uid=am-config,ou=admins,ou=am-config`

   * Password

     `5up35tr0ng`

   * Server configuration

     Leave the `New deployment` option selected.

8. On the User Data Store page, enter the following details and click Next:

   * User Data Store Type

     Leave the `ForgeRock Directory Services (DS)` option selected.

   * SSL/TLS Enabled

     Select this option to use a secure connection.

   * Directory Name

     `ds.example.com`

   * Port

     `1636`

   * Root Suffix

     `ou=identities`

   * Login ID

     `uid=am-identity-bind-account,ou=admins,ou=identities`

   * Password

     `5up35tr0ng`

9. On the Site Configuration page, leave the `No` option selected and click Next.

10. Check the details on the Configurator Summary page.

    * If anything needs changing, click Previous to return to earlier pages and update as needed.

    * If everything is correct, click Create Configuration to proceed. The configuration progress is shown in the browser and also output to the installation log.

    |   |                                                                                                                                        |
    | - | -------------------------------------------------------------------------------------------------------------------------------------- |
    |   | If your installation fails, find troubleshooting advice in [Troubleshoot installations](../installation/install-troubleshooting.html). |

11. When the configuration process completes, click Proceed to Login, and log in as the `amAdmin` administrator with the password you configured in a previous step,`changeit`.

    After logging in, the Realms page is displayed.

    AM stores its configuration in a directory named after the deployment URI. For example, if AM is deployed under `/am`, it saves its configuration under `$HOME/am/`.

    AM is now configured, and ready for use.

12. After successfully logging in to the AM admin UI, proceed to [Step 4. Configure AM](step-4-configure-am.html).