Author: mmcallis Date: 2008-02-04 23:28:33 -0500 (Mon, 04 Feb 2008) New Revision: 9763 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml Log: revising content for 3.1. Changing the Port Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-05 03:19:46 UTC (rev 9762) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-05 04:28:33 UTC (rev 9763) @@ -12,41 +12,38 @@ <email>roy at jboss dot org</email> </author> </chapterinfo> - <title>Customizing your installation</title> - <para>This section is intended to describe some customization features available in JBoss - Portal. If it is not covered here, please view the FAQ chapter at the end of this document or the descriptor - chapter ( - <xref linkend="portaldescriptors"/> - ) for further documentation on configuration and tuning JBoss Portal. + <title>Customizing your Installation</title> + <para> + This chapter describes how to customize a default installation of JBoss Portal. This includes the listening port, email and proxy settings, and database dialect settings. For further configuration details, please see <xref linkend="portaldescriptors"/> and <xref linkend="troubleshooting"/>. </para> <sect1> - <title>Changing the port</title> - <para>It is common to have a server running on the port 80 instead of the default port 8080.</para> - <para>It might be easier to use - <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOnPort80">... forwarding</ulink> - than to change the - port manually. Since port forwarding is not always possible, below are the instructions to change the port - number manually. + <title>Changing the Port</title> + <para> + It is common for web services to run on port 80, instead of the JBoss EAP and JBoss AS default port of 8080. If you can not use <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingPortForwardingWit... forwarding</ulink>, it is recommended to change the default port in <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</filename>. To change the default port, open the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</filename> file, and edit the <computeroutput>Connector port</computeroutput> value for the <computeroutput>jboss.web</computeroutput> service: </para> - <para>To change it, you need to edit the file <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</literal> - and change the port value of the HTTP Connector. + <para> +<screen> +&lt;Service name="jboss.web"&gt; +&lt;Connector port="8088" address="${jboss.bind.address}" +</screen> + </para> + <para> + This example changes the default port to port 8088. The JBoss EAP or JBoss AS server must be restarted before the new port settings will take affect. + </para> + <para> + The default SSL port is 8843. To enable HTTPS support, refer to <ulink url="ttp://docs.jboss.org/jbossas/jboss4guide/r4/html/ch9.chapt.html... AS Guide</ulink>. For further information, please see the <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html">... SSL configuration how-to</ulink>. </para> <para> - You can also change the value of the SSL port, by default it is set to 8443. To activate support for HTTPS, - please refer to the appropriate - <ulink url="http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch9.chapt.htm... of the - JBoss AS guide. You might also want to refer to - <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html">... SSL configuration how-to</ulink> - for more details. + <warning> + <title>root user priviliges</title> + <para> + Linux systems require root user privileges to run a server on a port less than 1024. Starting JBoss EAP or JBoss AS on port 80 as a non-privileged user will not work. Running JBoss EAP or JBoss AS as the root user could lead to security breaches. + </para> + </warning> </para> <para> Please refer to <xref linkend="wsrp-ports"/> to update the WSRP service after having changed the port. </para> - <para>Now you can restart JBoss and use the new port that you defined. On systems like Linux, - you need privileges to be able to run a server on a port lower than 1000, starting JBoss on - the port 80 as a regular user will not work. For testing purposes, you can start JBoss AS as root but this - setup is not recommended if the server is public as it could lead to security breaches of your system. - </para> </sect1> <sect1 id="configuration-contextroot"> <title>Changing the context path</title> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-02-05 03:19:46 UTC (rev 9762) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-02-05 04:28:33 UTC (rev 9763) @@ -125,7 +125,7 @@ </imageobject> </mediaobject> <para> - Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default, minimal, or production. For example, if you are using the production configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/production/deploy/</filename> directory. + Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default or minimal. For example, if you are using the all configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/all/deploy/</filename> directory. </para> <para> After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the username, password, connection-url, and driver-class are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: