Author: jaredmorgs Date: 2012-03-08 20:49:31 -0500 (Thu, 08 Mar 2012) New Revision: 8553 Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Installation_Guide/en-US/SP_Installation.xml epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml Log: Removed section as part of https://bugzilla.redhat.com/show_bug.cgi?id=801248. Updated Clustering section to be task based as part of https://bugzilla.redhat.com/show_bug.cgi?id=801244. Also added cluster start-up instructions to the Test Your Installation section, and further improved the related task in this section. Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -9,10 +9,9 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.1</edition> - <pubsnumber>8</pubsnumber> + <pubsnumber>9</pubsnumber> <abstract> - <para> - This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform. It forms part of the complete document suite along with the <citetitle>User Guide</citetitle> and <citetitle>Reference Guide</citetitle> available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... type="http"/>. + <para>This book provides information about obtaining, installing and running JBoss Enterprise Portal Platform and its add-ons. It forms part of the complete document suite along with the <citetitle>User Guide</citetitle> and <citetitle>Reference Guide</citetitle> available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... type="http"/>. </para> </abstract> <corpauthor> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/ClusteringConfiguration.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -5,90 +5,98 @@ ]> <section id="sect-Reference_Guide-Clustering_Configuration"> <title>Clustering Configuration</title> - <section id="sect-Reference_Guide-Clustering_Configuration-Overview"> - <title>Overview</title> - <para>JBoss Enterprise Portal Platform has been developed to support high availability and high horizontal and vertical scalability. + <para>JBoss Enterprise Portal Platform supports high availability and high horizontal and vertical scalability. The setup instructions have been kept to a minimum, however, a good understanding of clustering services in - JBoss Enterprise Application Platform and JBoss Cache would be required in order to configure the optimal settings. + JBoss Enterprise Application Platform and JBoss Cache are required in order to configure the optimal settings. </para> - </section> - <section id="sect-Reference_Guide-Clustering_Configuration-Prerequisite"> - <title>Prerequisites</title> - <para>The clustering services are available only in the <literal>all</literal> + <para>The clustering services are available only in the <literal>all</literal> and <literal>production</literal> server configurations. Additionally the following prerequisites should be met: </para> - <itemizedlist> - <listitem> - <para> - A rapid shared file system is required such as a Storage Area Network (SAN). + <itemizedlist> + <listitem> + <para>A rapid shared file system is required such as a Storage Area Network (SAN). </para> - </listitem> - <listitem> - <para>Databases should be shared among the cluster nodes. - </para> - </listitem> - <listitem> - <para>All cluster nodes should be configured to point to the shared databases. </para> - </listitem> - </itemizedlist> - </section> + </listitem> + <listitem> + <para>All cluster nodes must be configured to point to the IDM and JCR shared databases. Refer to <xref linkend="sect-Reference_Guide-Database_Configuration"/> for detailed database set up procedures.</para> + </listitem> + </itemizedlist> <section id="sect-Reference_Guide-Clustering_Properties"> - <title>Configuration Properties</title> - <para>Edit the following entries in the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/configuration.properties</filename> file:</para> - <itemizedlist> - <listitem> - <para> - <literal>gatein.jcr.storage.data.dir;</literal> - <itemizedlist> - <listitem> - <para> - To specify the location of the &quot;value storage&quot;. This folder must not be deleted as it contains data required for the portal to run. For more details about &quot;value storage&quot; please refer to the JCR configuration in the JBoss Enterprise Portal Platform Reference Guide available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... type="http"/> - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para> - <literal>gatein.jcr.index.data.dir;</literal> - <itemizedlist> - <listitem> - <para> - To specify the location on a shared file system to store the JCR index. If the directory is deleted, the JCR will recreate the indexes on next start of the server. (This operation may take a very long time, depending on the size of the data stored in the JCR). - </para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para> - <literal>gatein.jcr.index.changefilterclass;</literal> - <itemizedlist> - <listitem> - <para> + <title>Configure</title> + <task> + <title>Task: Configure Clustering Properties</title> + <tasksummary> + <para>Complete this task to configure clustering properties required for </para> + </tasksummary> + <taskprerequisites> + <title>Prerequisites</title> + <itemizedlist> + <listitem> + <para>You understand clustering fundamentals as described in the JBoss Enterprise Application Platform core documentation.</para> + </listitem> + </itemizedlist> + <itemizedlist> + <listitem> + <para>You have read, and understand the information about <citetitle>The Java Content Repository</citetitle> (JCR) in the JBoss Enterprise Portal Platform <citetitle>Reference Guide</citetitle>.</para> + </listitem> + </itemizedlist> + </taskprerequisites> + <procedure> + <step> + <para>Open the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/configuration.properties</filename> file in a text editor:</para> + </step> + <step> + <para>Add the following properties to the file. An explanation is provided to assist you.</para> + <variablelist> + <varlistentry> + <term>gatein.jcr.storage.data.dir;</term> + <listitem> + <para>Specifies the location of the Java Content Repository (JCR) value storage. The location you specify contains critical data required to run the portal, and must not be deleted. Refer to the </para> + </listitem> + </varlistentry> + <varlistentry> + <term>gatein.jcr.index.data.dir;</term> + <listitem> + <para>Specifies the location on a shared file system to store the JCR index. </para> + <para>If the directory is deleted, the JCR will recreate the indexes on next start of the server. This operation may take a very long time, depending on the size of the data stored in the JCR.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>gatein.jcr.index.changefilterclass;</term> + <listitem> + <para>Specifies the filter class that should be used instead of the default filter class.</para> + <para> This must be changed to <literal>org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter</literal>. </para> - </listitem> - </itemizedlist> - </para> - </listitem> - <listitem> - <para> - <literal>gatein.jcr.config.type;</literal> - <itemizedlist> - <listitem> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term>gatein.jcr.config.type;</term> + <listitem> + <para>Specifies the type of configuration the server should use across all nodes. </para> + <para> This must be changed to <literal>cluster</literal>. </para> - </listitem> - </itemizedlist> - </para> - </listitem> - </itemizedlist> - <para> - The default property file would look like the following: -<programlisting># + </listitem> + </varlistentry> + </variablelist> + </step> + <step> + <formalpara> + <title>Result</title> + <para>You have provided the mandatory clustering configuration as it relates to the portal in the <filename>configuration.properties</filename> file.</para> + </formalpara> + </step> + </procedure> + </task> + <example> + <title>Default configuration.properties clustering directives</title> + <para> + The code sample depicts a <filename>configuration.properties</filename> directive file with the required clustering configuration set. + + </para> + <programlisting># gatein.conf.dir=${jboss.server.home.dir}/conf/gatein gatein.data.dir=${jboss.server.data.dir}/gatein @@ -111,24 +119,6 @@ gatein.jcr.workspace.default=collaboration gatein.jcr.workspace.system=system [...]</programlisting> - </para> + </example> </section> - <section id="sect-Reference_Guide-Clustering_Running"> - <title>Run the Cluster</title> - <para>To run the portal in high-availability mode, start all nodes with an extra profile configuration as follows:</para> - <formalpara> - <title>In Linux</title> - <para> -<programlisting><command>run.sh -c all -Dexo.profiles=cluster</command> -</programlisting> -</para> - </formalpara> - <formalpara> - <title>In Windows</title> - <para> -<programlisting><command>run.bat -c all -Dexo.profiles=cluster</command> -</programlisting> -</para> - </formalpara> - </section> </section> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -13,7 +13,8 @@ <itemizedlist> <listitem> <para>Java Content Repository (JCR) service, which depends on the native JDBC API. JCR has the capability to integrate with - any existing datasource implementation</para> + any existing datasource implementation. </para> + <para>Detailed information about JCR is located in the <citetitle>Reference Guide</citetitle>.</para> </listitem> <listitem> <para>Identity Management (IDM) service, which depends on JBoss Hibernate.</para> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -96,13 +96,16 @@ <step> <para>Restart the portal.</para> </step> + <step> + <formalpara> + <title>Result</title> + <para>You have configured the platform to communicate using a secure connection.</para> + </formalpara> + </step> </procedure> + <taskrelated> + <title>Related Information</title> + <para>Test clustering setup by following <xref linkend="Test_your_Installation"/>.</para> + </taskrelated> </task> - <formalpara> - <title>Result</title> - <para>You have configured the platform to communicate using a secure connection.</para> - </formalpara> - <para> - You can now access the portal from the address: <literal>https://<replaceable>&lt;ServerAddress&gt;</replaceable>:8443/portal</literal> - once you have completed the other configuration tasks in this guide.</para> </section> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Post_Installation.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -43,39 +43,40 @@ </para> </note> </section> - <section id="Set_JBOSS_HOME"> - <title> Set JBOSS_HOME Environment Variable </title> - <formalpara> - <title> On a Linux Platform </title> - <para> +<!--BZ#801248 Commented JBOSS_HOME section for EPP 5.2.1 because GSS confirmed it is not necessary to set this environment variable.--><!--<section id="Set_JBOSS_HOME"> + <title> Set JBOSS_HOME Environment Variable </title> + <formalpara> + <title> On a Linux Platform </title> + <para> Create an environment variable that points to the installation directory (<filename><replaceable>JBOSS_DIST</replaceable>/jboss-as</filename>) and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your <filename>/home</filename> directory. </para> - </formalpara> - <programlisting> + </formalpara> + <programlisting> #In this example /home/user/jboss-epp-<replaceable>VERSION</replaceable>/jboss-as is the installation directory. export JBOSS_HOME=/home/user/jboss-epp-<replaceable>VERSION</replaceable>/jboss-as export PATH=$PATH:$JBOSS_HOME/bin </programlisting> - <para> + <para> Set this variable for the user account(s) that will run the server. </para> - <formalpara> - <title> On Microsoft Windows </title> - <para> + <formalpara> + <title> On Microsoft Windows </title> + <para> Create an environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: <filename>C:\jboss-epp-<replaceable>VERSION</replaceable>\jboss-as\</filename>. </para> - </formalpara> - <para> + </formalpara> + <para> In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: <filename>C:\jboss-epp-<replaceable>VERSION</replaceable>\jboss-as\bin</filename>. </para> - <para> + <para> You may set these variables by going to the System Properties window then select the Advanced tab and finally click on the Environment Variables button. </para> - </section> - <section id="Adjust_Memory_Settings"> +</section>--> <section id="Adjust_Memory_Settings"> <title>Adjust Memory Settings</title> <para> - If the server is running out of memory, you may adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.conf</filename> on Linux or <filename><replaceable>JBOSS_HOME</replaceable>\jboss-as\bin\run.conf.bat</filename> on Windows. The default values do not take into account the memory requirements of your applications: + If the server is running out of memory, you can adjust the memory settings before deploying the applications. </para> + <para>You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.conf</filename> on Linux or <filename><replaceable>JBOSS_HOME</replaceable>\jboss-as\bin\run.conf.bat</filename> on Windows. </para> + <para>The default values do not take into account the memory requirements of your applications: <programlisting>-Xms1303m -Xmx1303m -XX:MaxPermSize=256m ....</programlisting> </para> </section> @@ -163,7 +164,7 @@ <step> <formalpara> <title>Result</title> - <para>The login links present on the front page of the portal main screen are not displayed, and the accounts are not available for use. + <para>The login links on the front page of the portal main screen are not displayed, and the accounts are not available for use. </para> </formalpara> </step> @@ -171,8 +172,8 @@ </task> </section> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="DatabaseConfiguration.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="EMailServiceConfiguration.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ClusteringConfiguration.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="HTTPSConfiguration.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="GadgetProxyConfig.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="EMailServiceConfiguration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="ClusteringConfiguration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="HTTPSConfiguration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="GadgetProxyConfig.xml"/> </chapter> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -9,6 +9,21 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.1-9</revnumber> + <date>Wed Mar 7 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>Removed $JBOSS_HOME section as part of https://bugzilla.redhat.com/show_bug.cgi?id=801248. </member> + <member>Updated Clustering section to be task based as part of https://bugzilla.redhat.com/show_bug.cgi?id=801244. Also added cluster start-up instructions to the Test Your Installation section, and further improved the related task in this section.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.1-8</revnumber> <date>Wed Mar 7 2012</date> <author> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/SP_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/SP_Installation.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/SP_Installation.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -165,19 +165,6 @@ </note> </step> --> </procedure> </task> - <para>Once you have completed all other configuration tasks in this guide, start the platform and navigate to <ulink url="http://localhost:8080/ecmdemo/public/classic" type="http">http://localhost:8080/ecmdemo/public/classic</ulink>. - </para> - <para> - If your installation has been successful, you will see the following sample homepage: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata width="444" scale="90" fileref="images/epp-sp-homepage.png" format="PNG"/> - </imageobject> - <imageobject role="fo"> - <imagedata width="444" contentwidth="150mm" fileref="images/epp-sp-homepage.png" format="PNG"/> - </imageobject> - </mediaobject> <!-- <para> If you did not include the <filename>gatein-ecmdemo-portal-&lt;version&gt;-GA.ear</filename> file, refer to the documentation available at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... /> for instructions on how to create a portal using Site Publisher's features. </para> --> </section> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Test_Your_Installation.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -4,20 +4,14 @@ %BOOK_ENTITIES; ]> <chapter id="Test_your_Installation"> - <title><remark>BZ#794687 </remark>Test your Installation</title> - <para>After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple start up test to validate that there are no major problems with your Java VM/operating system combination. Ensure you have set the <literal>JBOSS_HOME</literal> environment variables as explained in <xref linkend="Post_Installation_Configuration"/>. + <title><remark>BZ#794687 and BZ#801244</remark>Test your Installation</title> + <para>After you have installed JBoss Enterprise Portal Platform and completed the relevant post installation configuration steps, verify your configuration is correct by starting the platform. </para> + <remark>BZ#801244 - 20120309 - Refined task information to include note about sybase startup commands, cluster URL, portal screens dependent on add-ons. One task to cover all start up scenarios.</remark> <task> <title>Task: Test Your Installation</title> <tasksummary> - <para>Complete this task to verify your server starts, and navigate to the Portal management console.</para> - <warning> - <title>Warning: Sybase Requirements</title> - <para>Sybase requires a particular configuration of JBoss Enterprise Portal Platform, to switch on that configuration, it is - mandatory to run the portal with the extra <literal>sybase</literal> profile. This would - mean to run the application server with <literal>sh run.sh -Dexo.profiles=sybase</literal> in a single node - and <literal>sh run.sh -Dexo.profiles=sybase,cluster</literal> for a cluster node.</para> - </warning> + <para>Complete this task to verify the platform starts, and navigate to the Portal management console.</para> </tasksummary> <taskprerequisites> <title>Prerequisites</title> @@ -39,14 +33,52 @@ </para> </step> <step> - <para>Execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, with the name of the server profile you have configured as part of the tasks in this guide. + <para>Execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script. Substitute the name of the <replaceable>server profile</replaceable> you have configured as part of the tasks in this guide. </para> + <variablelist> + <varlistentry> + <term>Non-clustered Linux</term> + <listitem> + <programlisting>[bin]$ ./run.sh -c <replaceable>production</replaceable></programlisting> + </listitem> + </varlistentry> + <varlistentry> + <term>Non-clustered Linux, running Sybase</term> + <listitem> + <programlisting>[bin]$ ./run.sh -c <replaceable>production</replaceable> -Dexo.profiles=sybase</programlisting> + </listitem> + </varlistentry> + <varlistentry> + <term>Non-clustered Windows</term> + <listitem> + <programlisting>&gt; run.bat -c <replaceable>production</replaceable></programlisting> + </listitem> + </varlistentry> + <varlistentry> + <term>Clustered Linux</term> + <listitem> + <programlisting>[bin]$ ./run.sh -c <replaceable>production</replaceable> -Dexo.profiles=cluster</programlisting> + </listitem> + </varlistentry> + <varlistentry> + <term>Clustered Linux, running Sybase</term> + <listitem> + <programlisting>[bin]$ ./run.sh -c <replaceable>production</replaceable> -Dexo.profiles=sybase,cluster</programlisting> + </listitem> + </varlistentry> + <varlistentry> + <term>Clustered Windows</term> + <listitem> + <programlisting>&gt; run.sh -c <replaceable>production</replaceable> -Dexo.profiles=cluster</programlisting> + </listitem> + </varlistentry> + </variablelist> <example> <title>Sample Server Output using Production</title> - <para>The example uses the production configuration. Your output should look like the following (accounting for installation directory differences and version numbers) and should not contain any error or exception messages: + <para>The example uses the Linux non-clustered production configuration. The output should look similar to the following (accounting for installation directory differences and version numbers), and should not contain any error or exception messages: </para> - <programlisting>[user@localhost bin]$ ./run.sh -c production + <programlisting>[bin]$ ./run.sh -c production ========================================================================= JBoss Bootstrap Environment @@ -84,38 +116,65 @@ </note> </step> <step> - <para>Open <literal>http://localhost:8080/portal</literal> in your web browser. + <para>Open the portal in your web browser by selecting one of the following URLs. </para> - <para>If you have secured your portal for production use by following <xref linkend="sect-Installation_Guide-HTTPS_Configuration"/>, open <literal>https://localhost:8443/portal</literal><note> - <para>On some machines, the name <literal>localhost</literal> will not resolve correctly and you should use the local loopback address 127.0.0.1 instead. + <note> + <para>On some machines, the name <literal>localhost</literal> will not resolve correctly and you should use the local loopback address 127.0.0.1 instead. </para> - </note> - </para> + </note> + <variablelist> + <varlistentry> + <term>Standard Portal</term> + <listitem> + <para>Open <literal>http://localhost:8080/portal</literal> </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Standard Portal, with HTTPS configured</term> + <listitem> + <para>Open <literal>http://localhost:8443/portal</literal> </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Standard Portal, with HTTPS configured, and Site Publisher.</term> + <listitem> + <para>Open <literal>http://localhost:8443/ecmdemo/public/classic</literal> </para> + </listitem> + </varlistentry> + </variablelist> </step> <step> <formalpara> <title>Result</title> - <para>The contents of your page should look similar to <xref linkend="Test_your_Installation-Test_your_Installation"/>. - </para> + <para>The contents of your page should look similar to <xref linkend="fig-Standard_Portal_Home_Page"/>, or + <xref linkend="fig-Site_Publisher_Home_Page"/></para> </formalpara> <para> You are now ready to use JBoss Enterprise Portal Platform. Refer to the <citetitle>User Guide</citetitle> and <citetitle>Reference Guide</citetitle> for more information about the product&apos;s feature set and example applications showcasing JBoss Enterprise Portal Platform in action. </para> - <figure id="Test_your_Installation-Test_your_Installation"> - <title>Test your Installation</title> - <mediaobject> - <imageobject role="html"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100"/> - </imageobject> - <imageobject role="fo"> - <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px"/> - </imageobject> - </mediaobject> - </figure> </step> </procedure> </task> - <para> - - </para> + <figure id="fig-Standard_Portal_Home_Page"> + <title>Standard Portal Home Page</title> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" scale="100"/> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/test_install.png" format="PNG" align="center" contentwidth="444px"/> + </imageobject> + </mediaobject> + </figure> + <figure id="fig-Site_Publisher_Home_Page"> + <title>Site Publisher Home Page</title> + <mediaobject> + <imageobject role="html"> + <imagedata fileref="images/epp-sp-homepage.png" format="PNG" scale="90" width="444"/> + </imageobject> + <imageobject role="fo"> + <imagedata fileref="images/epp-sp-homepage.png" format="PNG" contentwidth="150mm" width="444"/> + </imageobject> + </mediaobject> + </figure> </chapter> Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml =================================================================== --- epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml 2012-03-08 16:51:51 UTC (rev 8552) +++ epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml 2012-03-09 01:49:31 UTC (rev 8553) @@ -3,41 +3,9 @@ ]> <chapter id="Uninstall_JBoss"> <title>Remove JBoss Enterprise Application Platform</title> -<!--Divide into GUI/CLI procedures. -<para> - There are several options for uninstalling JBoss Enterprise Application Platform. The options available to you depend on your installation method. -</para> - -<section> - <title>If you used the graphical installation</title> - <para> - There are two options for uninstalling if you installed using the graphical installer; you can uninstall with either the graphical uninstaller, or via the command line. - </para> - <procedure> - <title>Graphical uninstall</title> - <step> - <para> - - </para> - </step> - <step performance="optional"> - <para> - - </para> - </step> - - -</section> - -<section> - <title>If you used the ZIP installation</title> - - - - -</section> ---> <task> - <title>Remove Platform By Deleting Root Installation Directory </title> + <para>Read this section to learn how to remove JBoss Enterprise Portal Platform from a server.</para> + <task> + <title>Remove Platform by Deleting Root Installation Directory </title> <tasksummary> <para>Complete this task to remove the root installation directory, which removes the platform from your system. To verify the root installation directory, ensure the directory contains the <filename>/jboss-as</filename> directory.</para> </tasksummary>