Author: mmcallis
Date: 2008-02-07 23:18:03 -0500 (Thu, 07 Feb 2008)
New Revision: 9859
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml
Log:
adding example about specifying a configuration
eg run.bat/sh -c default
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-08
04:01:19 UTC (rev 9858)
+++
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-02-08
04:18:03 UTC (rev 9859)
@@ -25,7 +25,7 @@
</listitem>
<listitem>
<para>
- <emphasis role="bold">Start the server:</emphasis> change
into the <filename>JBOSS_PORTAL_INSTALLATION_DIRECTORY/bin/</filename>
directory. On Microsoft Windows, execute <command>run.bat</command>. On Linux,
run the <command>./run.sh</command> command.
+ <emphasis role="bold">Start the server:</emphasis> change
into the <filename>JBOSS_PORTAL_INSTALLATION_DIRECTORY/bin/</filename>
directory. On Microsoft Windows, execute <command>run.bat</command>. On Linux,
run the <command>./run.sh</command> command. To specify a configuration to
use, for example, the default configuration, append the <command> -c
default</command> option to the <command>run.bat</command> or
<command>./run.sh</command> commands.
</para>
</listitem>
<listitem>
@@ -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 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.
+ 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. The production configuration only exists on JBoss EAP, and
not JBoss AS. 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:
@@ -161,7 +161,7 @@
</listitem>
<listitem>
<para>
- <emphasis role="bold">Start the server:</emphasis> change into
the <filename>$JBOSS_HOME/bin/</filename> directory. On Microsoft Windows,
execute <command>run.bat</command>. On Linux, run the
<command>./run.sh</command> command.
+ <emphasis role="bold">Start the server:</emphasis> change into
the <filename>$JBOSS_HOME/bin/</filename> directory. On Microsoft Windows,
execute <command>run.bat</command>. On Linux, run the
<command>./run.sh</command> command. To specify a configuration to use, for
example, the default configuration, append the <command> -c default</command>
option to the <command>run.bat</command> or
<command>./run.sh</command> commands.
</para>
</listitem>
<listitem>
@@ -348,7 +348,7 @@
<para>
Replace <replaceable>proxy-hostname</replaceable> with the proxy
server's hostname, and <replaceable>proxy-port</replaceable> with the
correct proxy server port number.
</para>
- <para>To build and deploy JBoss Portal from the sources, change into the
<filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory, where
<filename>JBOSS_PORTAL_SOURCE_DIRECTORY</filename> directory is the directory
where the JBoss Portal source code was downloaded to. Then, Microsoft Windows users need
to run the <command>build.bat deploy</command> command, and Linux users need
to run the <command>./build.sh deploy</command> command.
+ <para>To build and deploy JBoss Portal from the sources, change into the
<filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory, where
<filename>JBOSS_PORTAL_SOURCE_DIRECTORY</filename> is the directory where the
JBoss Portal source code was downloaded to. Then, Microsoft Windows users need to run the
<command>build.bat deploy</command> command, and Linux users need to run the
<command>./build.sh deploy</command> command.
</para>
<para>
At the end of the build process, the <filename>jboss-portal.sar</filename>
file is copied into the
<filename>$JBOSS_HOME/server/default/deploy/</filename> directory:
@@ -441,7 +441,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, 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. The
production configuration only exists on JBoss EAP installations, and not JBoss AS.
</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: