PingAM 8.0.0

Deploy AM

After you have downloaded AM software, deploy it to your installed application container.

Deploying AM only extracts the files into the application container, prior to installation and configuration. Deploying AM also makes LDIF files available, which can be used to prepare datastores for use with AM.

After deploying AM, but before installation, your application container serves AM’s installer (or upgrader, if performing an upgrade) user interfaces.

We recommend that any external network access to the application container is suspended until the install, or upgrade, is complete. When complete, AM prevents access to the installer, or upgrader UI itself.

The AM-8.0.0.war file contains the AM server. How you deploy the .war file depends on your web application container.

  1. Deploy the .war file on your container.

    For example, copy the file to deploy on Apache Tomcat.

    $ cp AM-8.0.0.war /path/to/tomcat/webapps/am.war

    In development or demonstration deployments, change the .war file name to am.war when deploying in Tomcat, so that the deployment URI is /am.

    • Change the file name to something other than am.war when deploying to a production environment so the deployment URI isn’t /am. Your deployment URI in production shouldn’t disclose the kind of software it is hosting.

    • AM requires a deployment URI with a non-empty string after /. Don’t deploy AM in the root context. For example, don’t rename the .war file to ROOT.war before deploying on Tomcat.

    It can take several seconds for AM to be deployed in your container.

  2. Go to the initial configuration page. For example, https://am.example.com:8443/am.

    The initial configuration page lets you start configuring AM.

    AM is now ready for installation.

  3. You can now configure datastores using the files created during deployment. Learn more in Prepare datastores.