To change the server runtime environment, from the Runtime Environment list select a server runtime environment. Alternatively, to create and assign a new server runtime environment click Runtime Environment and follow the instructions.

To view or edit the server launch configuration, click Open launch configuration.

To specify that the server life cycle will be managed from outside the IDE, select the Server is externally managed check box.

To specify that the server should be launched to respond to requests on all hostnames, select the Listen on all interfaces to allow remote web connections check box. This option is most useful for remote servers and adds the -b 0.0.0.0 argument to the server launch command.

To enable management commands sent by the IDE to be successfully received by the server, select the Expose your management port as the server's hostname check box. This option is useful for remote servers and unnecessary for local servers.

To specify the location of the server, from the list select Local or Remote System Deployment. For remote systems, there are further details that must be specified: the host, the path of the remote application server, and the remote application server configuration file.

To customize which changes invoke application redeployment, select the Customize application reload behavior on changes to project resources check box. In the Force module restart on following regex pattern field, type a regex pattern indicating the changed resources that you want to trigger redeployment.

To disable application reload, select the Customize application reload behavior on changes to project resources check box and ensure the Force module restart on following regex pattern field is empty.

There are four methods from which to choose:

Note that server state detection options are disabled if the Server is externally managed check box under Server Behavior is selected.

Port offset is typically offered by newer application servers and it enables multiple servers to run on the same system without port conflicts. JBoss Server Tools uses information in the server configuration file, typically XPath values, to automatically detect the correct ports and port offset for communicating with the server but you can perform further customization.

To view the configuration file information used by JBoss Server Tools for automatic port detection, click Configure corresponding to the appropriate tool. The information used is displayed in the Current Value field. To change this value, click Edit XPath. Click OK to close the window.

To manually specify the server ports or port offset, clear the Detect from Local Runtime check box corresponding to the appropriate tool and edit the port value.

You can customize the deployment location and packaging type:

To filter the module list in the case that you have many modules, from the Filter by list select the criteria for the filter. If you select the By Module Name filter option, in the text field enter the part or whole name of the module.

To change the Deployment Location and Temporary Deploy Directory on a per module basis, in the table click the value to be changed and enter an alternative value. Ensure the values for these variables are specified use absolute paths or paths relative to the default deploy directory.