Chapter 3. Customizing your Installation

This chapter describes how to customize the default installation. This includes the JBoss EAP listening port, email and proxy settings, and database dialect settings. For further configuration details, refer to Section 6.3, “JBoss Portal Descriptors” and Chapter 27, Troubleshooting and FAQ.

Choosing server Configuration

In rest of the document, you will see several references of $JBOSS_HOME/server/production/. This also applies to $JBOSS_HOME/server/default/ as well as $JBOSS_HOME/server/all/

3.1. Changing the Port

It is common for web services to run on port 80. By default, JBoss EAP and JBoss AS use port 8080. If you can not use port forwarding, it is recommended to change the port JBoss EAP or JBoss AS listens on. To change the default port, open the $JBOSS_HOME/server/production/deploy/jboss-web.deployer/server.xml file, and edit the Connector port value for the jboss.web service; however, this configuration only applies to Apache Tomcat:
<Service name="jboss.web">
<Connector port="8088" address="${jboss.bind.address}"
This example changes the default port to port 8088. The JBoss EAP or JBoss AS server must be restarted before the new port settings take affect.
The default SSL port is 8843. To enable HTTPS support, refer to the JBoss AS Guide. For further information, refer to the Apache Tomcat SSL configuration how-to.

Changing/Adding a connector

When adding or changing a JBoss Web connector make sure to keep emptySessionPath="true" which is required for the portal to work correctly
Please refer to Section 15.3.1, “Considerations to use WSRP when running Portal on a non-default port or hostname” to update the WSRP service after having changed the port.

Root User Privileges

Linux operating systems require root user privileges to run a service on a port less than 1024. Starting JBoss EAP on port 80 as a non-privileged user will not work. Running JBoss EAP as the root user could lead to security breaches.