Author: mmcallis
Date: 2008-07-09 02:55:36 -0400 (Wed, 09 Jul 2008)
New Revision: 11362
Modified:
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/configuration.xml
Log:
code highlighting for configuration chapter. This
will break some examples...
Modified:
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/configuration.xml
===================================================================
---
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/configuration.xml 2008-07-09
06:24:42 UTC (rev 11361)
+++
docs/branches/JBoss_Portal_Branch_2_7/referenceGuide/en/modules/configuration.xml 2008-07-09
06:55:36 UTC (rev 11362)
@@ -19,12 +19,10 @@
<para>
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 <ulink
url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingPortForwardingWit...
forwarding</ulink>, it is recommended to change the port JBoss EAP or JBoss AS
listens on. 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; however, this
configuration only applies to Apache Tomcat:
</para>
- <para>
-<screen>
+<programlisting role="XML">
<Service name="jboss.web">
<Connector port="8088" address="${jboss.bind.address}"
-</screen>
- </para>
+</programlisting>
<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 take affect.
</para>
@@ -53,7 +51,8 @@
<orderedlist>
<listitem>
<para>Open the
<emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/jboss-web.xml</emphasis>
file. If this file does not exist, copy and save the following example:
-<programlisting><![CDATA[
+ </para>
+<programlisting role="XML"><![CDATA[
<?xml version="1.0"?>
<jboss-web>
<security-domain>java:jaas/portal</security-domain>
@@ -66,17 +65,14 @@
<jndi-name>java:PortalDS</jndi-name>
</resource-ref>
</jboss-web>]]></programlisting>
- </para>
</listitem>
<listitem>
<para>Edit the
<computeroutput><context-root></computeroutput> element with the
desired context path:
</para>
- <para>
-<programlisting>
+<programlisting role="XML">
<![CDATA[<context-root>/testing</context-root>]]>
</programlisting>
- </para>
<para>
Using this example, the main JBoss Portal page would be reached by navigating to
<emphasis>http://localhost:8080/testing</emphasis>.
</para>
@@ -97,12 +93,10 @@
<para>
Open the <filename>build/local.properties</filename> file and edit the
<computeroutput>portal.web.context-root</computeroutput> option with the
desired context path:
</para>
- <para>
<programlisting>
# Context root for the portal main servlet
portal.web.context-root=/testing
</programlisting>
- </para>
<para>
Using this example, the main JBoss Portal page would be reached by navigating to
<emphasis>http://localhost:8080/testing</emphasis>.
</para>
@@ -127,13 +121,11 @@
or add a <filename>jboss-web.xml</filename> file, which declares
another
context-root other than <emphasis>/</emphasis>, under the
<filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/</filename>
directory, for the above changes to take affect. The following is an example
<filename>jboss-web.xml</filename> file, which changes the Apache Tomcat
context path to <computeroutput>/tomcat-root</computeroutput>:
</para>
- <para>
-<programlisting><![CDATA[
+<programlisting role="XML"><![CDATA[
<?xml version="1.0"?>
<jboss-web>
<context-root>/tomcat-root</context-root>
</jboss-web>]]></programlisting>
- </para>
</sect2>
</sect1>
<sect1 id="configuration-hibdialect">
@@ -149,12 +141,10 @@
<para>
To modify these files to force the DB dialect, un-comment the following line from each
<filename>hibernate.cfg.xml</filename> file in each JBoss Portal module you
intend to use, so that it looks like the following:
</para>
- <para>
-<programlisting><![CDATA[
+<programlisting role="XML"><![CDATA[
<!-- Force the dialect instead of using autodetection -->
<property
name="dialect">org.hibernate.dialect.PostgreSQLDialect</property>
]]></programlisting>
- </para>
<para>
Note: this example is for a PostgreSQL database. If you use another database, you need
to modify
<computeroutput>org.hibernate.dialect.PostgreSQLDialect</computeroutput> to
reflect the correct database. For a list of supported dialects, refer to the <ulink
url="http://www.hibernate.org/hib_docs/v3/reference/en/html/session-...
list on the Hibernate website</ulink>.
</para>
@@ -175,12 +165,10 @@
<para>
Un-comment the following line, so that it looks like the following:
</para>
- <para>
-<programlisting><![CDATA[
+<programlisting role="XML"><![CDATA[
<!-- Force the dialect instead of using autodetection -->
<property
name="dialect">org.hibernate.dialect.PostgreSQLDialect</property>
]]></programlisting>
- </para>
</listitem>
</orderedlist>
</para>
@@ -220,8 +208,7 @@
<para>
A different SMTP server (other than localhost) can be configured, along with a SMTP
username and an SMTP password. The following is an example configuration that uses the
Gmail SMTP server:
</para>
- <para>
-<screen><![CDATA[
+<programlisting role="XML"><![CDATA[
<mbean
code="org.jboss.portal.core.impl.mail.MailModuleImpl"
name="portal:service=Module,type=Mail"
@@ -239,8 +226,7 @@
<attribute name="SMTPTimeout">10000</attribute>
<attribute name="JNDIName">java:portal/MailModule</attribute>
</mbean>]]>
-</screen>
- </para>
+</programlisting>
<para>
Using this example, replace
<computeroutput>username(a)gmail.com</computeroutput> and
<computeroutput>myPassword</computeroutput> with your correct Gmail username
and password.
</para>