On occasion, Windows dynamically assigns the required port to another service which can result in a DM deployment failure.
It's best practice to find out which port is being used by Autoform DM. To do this, open Command Prompt and type 'netstat -ano'.
This will display a list of all ports in use and may able give you enough information to find what is using the required port.
If the port is not listed using the Netstat command or you are still unable to find what is using the port, the next step is to use a tool like CurrPorts. CurrPorts lists all open TCP/IP and UDP ports as well as information about what is using them. This should allow you to find the required port.
Change the alias - standalone.xml
When the port shows up as not being in use and DM is unable to bind to it due to a Firewall or Local Security Policy, follow these steps:
- Open the standalone.xml file (that is used to change the logging level here) and find the following lines of XML:Standalone.xml file
<subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost"/> </virtual-server> </subsystem>
- Change the alias name to the server name rather than localhost and restart Autoform DM for the changes to take effect.