Check Autoform DM Deployment Status and Troubleshoot Startup Issues

If users cannot access Autoform DM or if its REST API does not respond, check Autoform DM’s deployment status. This article describes how to check this and how to troubleshoot some common startup issues.

Note

The instructions on this page apply to standalone installations of Autoform DM only.

Check Autoform DM Deployment Status

Autoform DM is Java software running on a bundled Wildfly application server. After Wildfly starts, it completes the following deployment process, which creates a running instance of Autoform DM:

1. Wildfly loads an EAR file that contains the Autoform DM software.

2. Wildfly runs the software in that EAR file.

If Autoform DM is running, it has been successfully deployed. However, if Wildfly cannot deploy Autoform DM, the application will not run.

If you think that Autoform DM is not running, check its deployment status. To do this, follow these steps:

1. On the Autoform DM server, navigate to <installation directory>\Wildfly-<version>\standalone\deployments. Appropriately substitute <installation directory> and <version>.

2. Locate pdm_app_module.ear. This file contains the main Autoform DM components.

3. The extension of an accompanying file describes Autoform DM’s deployment status. Locate this file and check the current deployment status. For example, pdm_app_module.ear.deployed.

   • .deployed: Autoform DM was successfully deployed and is running.

   • .deploying: Wildfly is currently deploying Autoform DM. If it succeeds, the file’s extension will change to .deployed. If it fails, the extension will change to one of the other extensions.

   • .undeployed: Wildfly has not deployed Autoform DM. Before trying to restart Autoform DM, you must complete further configuration steps. Check the Autoform DM logs for messages that identify the cause of the problem. Often, licensing issues cause this problem. If you require further assistance, contact Formpipe Support.

   • .failed: Wildfly failed to deploy Autoform DM. See the information below about how to resolve common startup problems.

Troubleshoot Startup Issues

The following sections of this article describe some common startup issues and provide resolution steps.

If none of these issues are the cause of the Autoform DM deployment failure, check the Autoform DM logs for messages that identify the cause of the problem.

If the logs do not help you to identify the cause, contact Formpipe Support.

Autoform DM Starts Before One or More of the Components That It Depends On

If an external software component that Autoform DM depends on has not yet started when Autoform DM tries to start, Wildfly will fail to deploy Autoform DM. This can happen when the server is restarted.

As this is a temporary issue, try manually restarting Autoform DM.

Autoform DM Port Conflict

A port conflict can prevent Autoform DM from starting.

Use your preferred tools and approach to investigate the current port allocation for Autoform DM and other software. If a conflict is found, take appropriate steps.

Autoform DM Startup is Affected by a Firewall or Local Security Policy

Firewall configuration or local security policy can prevent Autoform DM from binding its configured port. This will prevent Autoform DM from starting.

To resolve this issue, follow these steps:

1. Locate the Autoform DM standalone.xml file. It is in  <installation directory>\Wildfly-<version>\standalone\configuration file (appropriately substitute <installation directory> and <version>). The standalone.xml file is in the same directory as node.properties .

2. Locate the following lines in the file:

   <server name="default-server">
      <http-listener name="default" socket-binding="http" max-post-size="${max.post.size}" max-parameters="15000" ...
      <https-listener name="default-https" socket-binding="https" max-post-size="${max.post.size}" max-parameters="15000" ...
        <host name="default-host" alias="localhost">
          <location name="/" handler="welcome-content"/>
            ...

3. In the <host name="default-host" alias="localhost"> line, change localhost to the server’s host name.

4. Save standalone.xml.

5. Restart Autoform DM.

Manually Restart Autoform DM

After you take steps to try and resolve a startup issue, restart Autoform DM.

If Autoform DM is running as a Windows service, follow these steps to restart it:

1. Open the Windows Services window.

2. Locate the Autoform DM service. For example, Autoform DM Server 10.5 - Standalone [Production]. The service name contains the Autoform DM version number, and also includes the corresponding Autoform DM node name in square brackets.  An appropriate node name is entered when Autoform DM is installed, so it is likely that the name of the relevant service will differ from the example provided.

3. Click Restart Service.

Note

The restart can take up to 10 minutes.