9:37 p.m.
Author: jaredmorgs
Date: 2012-02-27 22:37:35 -0500 (Mon, 27 Feb 2012)
New Revision: 8474
Modified:
epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.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/Revision_History.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml
Log:
Incorporated feedback from theute in https://bugzilla.redhat.com/show_bug.cgi?id=794386.
New sections added to Database Configuration, specifically Multiple Portal JCR and IDM.
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-02-27 11:53:06 UTC
(rev 8473)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2012-02-28 03:37:35 UTC
(rev 8474)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.1</edition>
- <pubsnumber>3</pubsnumber>
+ <pubsnumber>4</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
<emphasis role="bold">User Guide</emphasis> and <emphasis
role="bold">Reference Guide</emphasis> available at <ulink
url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf...
type="http"/>.
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-02-27
11:53:06 UTC (rev 8473)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-02-28
03:37:35 UTC (rev 8474)
@@ -19,11 +19,12 @@
<para>Identity Management (IDM) service, which depends on JBoss
Hibernate.</para>
</listitem>
</itemizedlist>
+ <para>You must create a separate database for both the JCR and IDM services, for
<emphasis>each portal container</emphasis> required in your installation.
</para>
+ <para>The formula to apply when provisioning JCR and IDM databases
is:</para>
+ <programlisting>(1 IDM + 1 JCR Database) * (Number of Portal
Containers)</programlisting>
+ <para>For example, if you intend running Site Publisher with JBoss Enterprise
Portal Platform, you must create two separate JCR and IDM databases for the
<literal>portal</literal> container, and
<literal>ecmdemo</literal> container.</para>
+ <para>Refer to <xref linkend="task-Create_Production_Database"/>
to provision the required database based on the number of portal instances. After
completing this task, refer to <xref linkend="Single_Portal_JCR_IDM"/> and
<xref linkend="Multiple_Portal_JRC_IDM"/> for instructions relating to
configuring the JNDI names in the directive files.</para>
<warning>
- <title>Warning: Separate JCR and IDM Databases</title>
- <para>You must create a separate database for both the JCR and IDM services. If
you do not create a separate database for each service, database table conflicts will
occur and JBoss Enterprise Portal Platform will not start.</para>
- </warning>
- <warning>
<title>Warning: Do not delete
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/data</filename></title>
<para>
The JCR can store information both in a database and on the file system
depending on the configuration of the value storage. Refer to the JBoss Enterprise Portal
Platform Reference Guide for more information.
@@ -34,11 +35,11 @@
<para>
You can change this directory location by editing the
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/conf/gatein/configuration.properties</filename>
file, the name of the property being:
<literal>gatein.jcr.storage.data.dir</literal></para>
</warning>
- <para>In the case of HSQLDB, databases are created automatically. For production
databases, you must first install the database and create a default user so the platform
can create the correct database schema when it is first started.</para>
<task id="task-Create_Production_Database">
<title><remark>BZ#794386</remark>Task: Provision JCR and IDM
Production Databases</title>
<tasksummary>
- <para>Read and understand the guideline steps in this task to prepare a JCR
production database for JBoss Enterprise Portal Platform.</para>
+ <para>Read and understand the guideline steps in this task to prepare
production databases for JBoss Enterprise Portal Platform. </para>
+ <para/>
</tasksummary>
<taskprerequisites>
<title>Prerequisites</title>
@@ -52,6 +53,9 @@
<listitem>
<para>A JDBC connector, which is compatible with the selected
JDBC-compliant production database.</para>
</listitem>
+ <listitem>
+ <para>Understand the database provisioning formula discussed in <xref
linkend="sect-Reference_Guide-Database_Configuration"/>.</para>
+ </listitem>
</itemizedlist>
</taskprerequisites>
<procedure>
@@ -62,10 +66,10 @@
<para>Copy the JDBC driver file (the .jar file) to the
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/lib</filename>
directory. This adds the driver to the classpath.</para>
</step>
<step>
- <para>Create a database that the JCR service will use
exclusively.</para>
+ <para>Create a separate database for each portal container's JCR
service. </para>
</step>
<step>
- <para>Create a second database that the IDM service will use
exclusively.</para>
+ <para>Create a separate database for each portal container's
IDM service.</para>
</step>
<step>
<para>Create a database user that has access to all related databases,
with the following minimum permissions:</para>
@@ -83,120 +87,287 @@
</step>
</procedure>
</task>
- <para>Now you have installed the database and created a user, you can set the JCR
and IDM directives in the configuration files as described in <xref
linkend="task-Configure_JCR_Database_Datasource"/> and <xref
linkend="task-Configure_IDM_Database_Datasource"/>.</para>
- <task id="task-Configure_JCR_Database_Datasource">
- <title><remark>BZ#794386</remark>Task: Configure the JCR Database
Datasource</title>
- <tasksummary>
- <para>Complete this task to configure the JCR datasource
descriptor.</para>
- </tasksummary>
- <taskprerequisites>
- <title>Prerequisites</title>
- <itemizedlist>
- <listitem>
- <para>Complete <xref
linkend="task-Create_Production_Database"/></para>
- </listitem>
- </itemizedlist>
- </taskprerequisites>
- <procedure>
- <step>
- <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
- </step>
- <step>
- <para>Locate the
<jndi-name>gatein-jcr</jndi-name> directives that affect JCR
datasource descriptors: </para>
+ <para>More information about setting up specific datasources can be found in the
JBoss Enterprise Application Platform <citetitle>Getting Started
Guide</citetitle>, in the <citetitle>Using Other Databases</citetitle>
chapter. </para>
+ <section id="Single_Portal_JCR_IDM">
+ <title><remark>BZ#794386 </remark>Single Portal JCR and
IDM</title>
+ <para>For production instances that use a single portal container, you can
configure a single JCR and IDM database. If you run JBoss Enterprise Portal Platform with
the default configuration from a clean install, without Site Publisher, you meet this
requirement.</para>
+ <para>For customers installing Site Publisher, or customers that require
multiple portal containers in their JBoss Enterprise Portal Platform, follow the tasks in
<xref linkend="Multiple_Portal_JRC_IDM"/> to ensure you configure the JNDI
requirements for multiple platforms correctly.</para>
+ <task id="task-Configure_JCR_Database_Datasource">
+ <title><remark>BZ#794386</remark>Task: Configure the JCR Database
Datasource</title>
+ <tasksummary>
+ <para>Complete this task to configure the JCR datasource descriptor for
instances that have one portal container (the default when you install the platform for
the first time, without Site Publisher).</para>
+ </tasksummary>
+ <taskprerequisites>
+ <title>Prerequisites</title>
<itemizedlist>
<listitem>
- <para><connection-url></para>
+ <para>Complete <xref
linkend="task-Create_Production_Database"/></para>
</listitem>
+ </itemizedlist>
+ </taskprerequisites>
+ <procedure>
+ <step>
+ <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
+ </step>
+ <step>
+ <para>Locate the
<jndi-name>gatein-jcr</jndi-name> directives that affect JCR
datasource descriptors: </para>
+ <itemizedlist>
+ <listitem>
+ <para><connection-url></para>
+ </listitem>
+ <listitem>
+ <para><driver-class></para>
+ </listitem>
+ <listitem>
+ <para><user-name></para>
+ </listitem>
+ <listitem>
+ <para><password></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>Change the <connection-url> and
<driver-class> directive values to match those specified in the JDBC
documentation for your chosen production database.</para>
+ <important>
+ <para>Ensure you specify the JCR-specific database in the
<connection-url>.</para>
+ </important>
+ </step>
+ <step>
+ <para>Change the <user-name> and <password>
directive values to the default user created in <xref
linkend="task-Create_Production_Database"/>. </para>
+ <important>
+ <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password.</para>
+ </important>
+ </step>
+ <step>
+ <formalpara>
+ <title>Result</title>
+ <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the JCR datasource is
ready for production use.</para>
+ </formalpara>
+ </step>
+ </procedure>
+ </task>
+ <task id="task-Configure_IDM_Database_Datasource">
+ <title><remark>BZ#794386</remark>Task: Configure the IDM Database
Datasource</title>
+ <tasksummary>
+ <para>Complete this task to configure the IDM datasource
descriptor.</para>
+ </tasksummary>
+ <taskprerequisites>
+ <title>Prerequisites</title>
+ <itemizedlist>
<listitem>
- <para><driver-class></para>
+ <para>Complete <xref
linkend="task-Configure_JCR_Database_Datasource"/></para>
</listitem>
+ </itemizedlist>
+ </taskprerequisites>
+ <procedure>
+ <step>
+ <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
+ </step>
+ <step>
+ <para>Locate the
<jndi-name>gatein-idm</jndi-name> directives that affect JCR
datasource descriptors: </para>
+ <itemizedlist>
+ <listitem>
+ <para><connection-url></para>
+ </listitem>
+ <listitem>
+ <para><driver-class></para>
+ </listitem>
+ <listitem>
+ <para><user-name></para>
+ </listitem>
+ <listitem>
+ <para><password></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>Change the <connection-url> and
<driver-class> directive values to match those specified in the JDBC
documentation for your chosen production database.</para>
+ <important>
+ <para>Ensure you specify the IDM-specific database in the
<connection-url>.</para>
+ </important>
+ </step>
+ <step>
+ <para>Change the <user-name> and <password>
directive values to the default user created in <xref
linkend="task-Create_Production_Database"/>. </para>
+ <important>
+ <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password using a keypair.</para>
+ </important>
+ </step>
+ <step>
+ <formalpara>
+ <title>Result</title>
+ <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the IDM datasource is
ready for production use.</para>
+ </formalpara>
+ </step>
+ </procedure>
+ </task>
+ </section>
+ <section id="Multiple_Portal_JRC_IDM">
+ <title><remark>BZ#794386 </remark>Multiple Portal JCR and
IDM</title>
+ <para>If you run Site Publisher with JBoss Enterprise Portal Platform, or need
to configure multiple portal containers in your installation of JBoss Enterprise Portal
Platform, JNDI requires a separate JCR and IDM datasource definition for <emphasis
role="italic">each portal container</emphasis> in
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>.
</para>
+ <para>This requirement also means a separate JCR and IDM database is required
for <emphasis role="italic">each portal container</emphasis>.
</para>
+ <task id="task-Configure_Multiple_JCR_Database_Datasource">
+ <title><remark>BZ#794386</remark>Task: Configure Multiple JCR
Database Datasources</title>
+ <tasksummary>
+ <para>Complete this task to configure the JCR datasource descriptors for
two portal containers.</para>
+ <note>
+ <para>This task uses Site Publisher as the second database descriptor,
however if you are not running Site Publisher you can substitute the Site Publisher JNDI
name <literal>ecmdemo</literal> with the name of your second portal
container.</para>
+ </note>
+ </tasksummary>
+ <taskprerequisites>
+ <title>Prerequisites</title>
+ <itemizedlist>
<listitem>
- <para><user-name></para>
+ <para>Complete <xref
linkend="task-Create_Production_Database"/>, remembering to provision a JCR
and IDM database for each portal container.</para>
</listitem>
- <listitem>
- <para><password></para>
- </listitem>
</itemizedlist>
- </step>
- <step>
- <para>Change the <connection-url> and
<driver-class> directive values to match those specified in the JDBC
documentation for your chosen production database.</para>
- <important>
- <para>Ensure you specify the JCR-specific database in the
<connection-url>.</para>
- </important>
- </step>
- <step>
- <para>Change the <user-name> and <password>
directive values to the default user created in <xref
linkend="task-Create_Production_Database"/>. </para>
- <important>
- <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password.</para>
- </important>
- </step>
- <step>
- <formalpara>
- <title>Result</title>
- <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the JCR datasource is
ready for production use.</para>
- </formalpara>
- </step>
- </procedure>
- </task>
- <task id="task-Configure_IDM_Database_Datasource">
- <title><remark>BZ#794386</remark>Task: Configure the IDM Database
Datasource</title>
- <tasksummary>
- <para>Complete this task to configure the IDM datasource
descriptor.</para>
- </tasksummary>
- <taskprerequisites>
- <title>Prerequisites</title>
- <itemizedlist>
- <listitem>
- <para>Complete <xref
linkend="task-Configure_JCR_Database_Datasource"/></para>
- </listitem>
- </itemizedlist>
- </taskprerequisites>
- <procedure>
- <step>
- <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
- </step>
- <step>
- <para>Locate the
<jndi-name>gatein-idm</jndi-name> directives that affect JCR
datasource descriptors: </para>
+ </taskprerequisites>
+ <procedure>
+ <step>
+ <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
+ </step>
+ <step>
+ <para>Create two <local-tx-datasource> descriptors, with a
different <jndi-name> suffix. </para>
+ <para>You can copy the existing <local-tx-datasource>
blocks in the file and modify them to suit. For example:</para>
+ <itemizedlist>
+ <listitem>
+
<para><jndi-name>gatein-jcr_<replaceable>portal</replaceable></jndi-name></para>
+ </listitem>
+ <listitem>
+
<para><jndi-name>gatein-jcr_<replaceable>ecmdemo</replaceable></jndi-name></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>Each <local-tx-datasource> block has a set of common
directives that affect datasource descriptors: </para>
+ <itemizedlist>
+ <listitem>
+ <para><connection-url></para>
+ </listitem>
+ <listitem>
+ <para><driver-class></para>
+ </listitem>
+ <listitem>
+ <para><user-name></para>
+ </listitem>
+ <listitem>
+ <para><password></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>For
<jndi-name>gatein-jcr_<replaceable>portal</replaceable></jndi-name>,
change the <connection-url> and <driver-class> directive
values to match those specified in the JDBC documentation for your chosen production
database.</para>
+ <important>
+ <para>Ensure you specify the JCR-specific database created for the
<literal>portal</literal> portal container in the
<connection-url>. For example:</para>
+
<programlisting><connection-url>jdbc:mysql://mysql-hostname:3306/<replaceable>portal</replaceable></connection-url>
+<driver-class>com.mysql.jdbc.Driver</driver-class></programlisting>
+ </important>
+ </step>
+ <step>
+ <para>For
<jndi-name>gatein-jcr_<replaceable>ecmdemo</replaceable></jndi-name>,
change the <connection-url> and <driver-class> directive
values to match those specified in the JDBC documentation for your chosen production
database.</para>
+ <important>
+ <para>Ensure you specify the JCR-specific database created for the
<literal>ecmdemo</literal> portal container in the
<connection-url>. For example:</para>
+
<programlisting><connection-url>jdbc:mysql://mysql-hostname:3306/<replaceable>ecmdemo</replaceable></connection-url>
+<driver-class>com.mysql.jdbc.Driver</driver-class></programlisting>
+ </important>
+ </step>
+ <step>
+ <para>Change the <user-name> and <password>
directives in all <local-tx-datasource> blocks to the values for the
default user created in <xref linkend="task-Create_Production_Database"/>.
</para>
+ <important>
+ <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password.</para>
+ </important>
+ </step>
+ <step>
+ <formalpara>
+ <title>Result</title>
+ <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the JCR datasources for
both portal containers are ready for production use.</para>
+ </formalpara>
+ </step>
+ </procedure>
+ </task>
+ <task id="task-Configure_Multiple_IDM_Database_Datasource">
+ <title><remark>BZ#794386</remark>Task: Configure Multiple IDM
Database Datasource</title>
+ <tasksummary>
+ <para>Complete this task to configure multiple IDM datasource descriptors.
</para>
+ <note>
+ <para>This task uses Site Publisher as the second portal container,
however if you are not running Site Publisher you can replace the Site Publisher JNDI name
<literal>ecmdemo</literal> with the name of your second portal
container.</para>
+ </note>
+ </tasksummary>
+ <taskprerequisites>
+ <title>Prerequisites</title>
<itemizedlist>
<listitem>
- <para><connection-url></para>
+ <para>Complete <xref
linkend="task-Configure_JCR_Database_Datasource"/></para>
</listitem>
- <listitem>
- <para><driver-class></para>
- </listitem>
- <listitem>
- <para><user-name></para>
- </listitem>
- <listitem>
- <para><password></para>
- </listitem>
</itemizedlist>
- </step>
- <step>
- <para>Change the <connection-url> and
<driver-class> directive values to match those specified in the JDBC
documentation for your chosen production database.</para>
- <important>
- <para>Ensure you specify the IDM-specific database in the
<connection-url>.</para>
- </important>
- </step>
- <step>
- <para>Change the <user-name> and <password>
directive values to the default user created in <xref
linkend="task-Create_Production_Database"/>. </para>
- <important>
- <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password using a keypair.</para>
- </important>
- </step>
- <step>
- <formalpara>
- <title>Result</title>
- <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the IDM datasource is
ready for production use.</para>
- </formalpara>
- </step>
- </procedure>
- </task>
- <para>More information about setting up datasources can be found in the JBoss
Enterprise Application Platform <citetitle>Getting Started Guide</citetitle>,
in the <citetitle>Using Other Databases</citetitle> chapter. </para>
+ </taskprerequisites>
+ <procedure>
+ <step>
+ <para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
+ </step>
+ <step>
+ <para>Create two <no-tx-datasource> descriptors, with a
different <jndi-name> suffix. </para>
+ <para>You can copy the existing <no-tx-datasource> blocks
in the file and modify them to suit. For example:</para>
+ <itemizedlist>
+ <listitem>
+
<para><jndi-name>gatein-idm_<replaceable>portal</replaceable></jndi-name></para>
+ </listitem>
+ <listitem>
+
<para><jndi-name>gatein-idm_<replaceable>ecmdemo</replaceable></jndi-name></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>Each <no-tx-datasource> block has a set of common
directives that affect datasource descriptors: </para>
+ <itemizedlist>
+ <listitem>
+ <para><connection-url></para>
+ </listitem>
+ <listitem>
+ <para><driver-class></para>
+ </listitem>
+ <listitem>
+ <para><user-name></para>
+ </listitem>
+ <listitem>
+ <para><password></para>
+ </listitem>
+ </itemizedlist>
+ </step>
+ <step>
+ <para>For
<jndi-name>gatein-idm_<replaceable>portal</replaceable></jndi-name>,
change the <connection-url> and <driver-class> directive
values to match those specified in the JDBC documentation for your chosen production
database.</para>
+ <important>
+ <para>Ensure you specify the IDM-specific database created for the
<literal>portal</literal> portal container in the
<connection-url>. For example:</para>
+
<programlisting><connection-url>jdbc:mysql://mysql-hostname:3306/<replaceable>portal</replaceable></connection-url>
+<driver-class>com.mysql.jdbc.Driver</driver-class></programlisting>
+ </important>
+ </step>
+ <step>
+ <para>For
<jndi-name>gatein-idm_<replaceable>ecmdemo</replaceable></jndi-name>,
change the <connection-url> and <driver-class> directive
values to match those specified in the JDBC documentation for your chosen production
database.</para>
+ <important>
+ <para>Ensure you specify the IDM-specific database created for the
<literal>ecmdemo</literal> portal container in the
<connection-url>. For example:</para>
+
<programlisting><connection-url>jdbc:mysql://mysql-hostname:3306/<replaceable>ecmdemo</replaceable></connection-url>
+<driver-class>com.mysql.jdbc.Driver</driver-class></programlisting>
+ </important>
+ </step>
+ <step>
+ <para>Change the <user-name> and <password>
directives in all <no-tx-datasource> blocks to the values for the default
user created in <xref linkend="task-Create_Production_Database"/>.
</para>
+ <important>
+ <para>The password you specify in <password> is in plain
text, and anyone with access to the server can discover the password. Consider encrypting
this password.</para>
+ </important>
+ </step>
+ <step>
+ <formalpara>
+ <title>Result</title>
+ <para>You have provided the key information in the
<filename>gatein-ds.xml</filename> directives, and the IDM datasources for
both portal containers are ready for production use.</para>
+ </formalpara>
+ </step>
+ </procedure>
+ </task>
+ </section>
<section>
<title>First-run Database Schema Creation</title>
<para>When you start JBoss Enterprise Portal Platform for the first time,
- it will create the proper database schema based on the database configuration you
specified in <xref
linkend="sect-Reference_Guide-Database_Configuration"/>.</para>
+ it will create the proper database schema based on the database configuration you
specified in <xref linkend="Single_Portal_JCR_IDM"/> or <xref
linkend="Multiple_Portal_JRC_IDM"/>.</para>
<note>
<para>JBoss Enterprise Portal Platform assumes the default encoding for your
database is
<literal>latin1</literal>.</para>
@@ -204,18 +375,9 @@
<para>Before starting the server for the first time, continue to <xref
linkend="sect-Reference_Guide-EMail_Service_Configuration"/> for the next
mandatory configuration requirement.</para>
</section>
<section>
- <title>Example with MySQL Server 5.1</title>
- <indexterm>
- <primary>Configuration</primary>
- <secondary>MySQL</secondary>
- </indexterm>
- <indexterm>
- <primary>Database</primary>
- <secondary>MySQL</secondary>
- </indexterm>
- <indexterm>
- <primary>MySQL</primary>
- </indexterm>
+ <title><remark>BZ#794386 </remark>Example with MySQL Server
5.1</title>
+ <para>This section describes an example how to configure MySQL to work with a
single portal container. Refer to <xref
linkend="Multiple_Portal_JRC_IDM"/> if you need to configure multiple portal
containers in your installation, or intend to use Site Publisher. </para>
+ <para>More information about setting up other datasources can be found in the
JBoss Enterprise Application Platform <citetitle>Getting Started
Guide</citetitle>, in the <citetitle>Using Other Databases</citetitle>
chapter. </para>
<formalpara
id="form-Portal_EAP-Using_a_MySQL_Database-Installing_the_MySQL_RDBMS_JDBC_connector">
<title>Installing the MySQL JDBC connector</title>
<para>The MySQL JDBC connector is required for EPP to use a
<application>MySQL</application> database:</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-02-27
11:53:06 UTC (rev 8473)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml 2012-02-28
03:37:35 UTC (rev 8474)
@@ -6,7 +6,7 @@
<section id="sect-Installation_Guide-HTTPS_Configuration">
<title><remark>BZ#794440 </remark>HTTPS Configuration</title>
<remark>https://bugzilla.redhat.com/show_bug.cgi?id=794440 - 20120221 - Reworked
the entire section to cover keystore and truststore configuration specific to EPP.
</remark>
- <para>JBoss Enterprise Portal Platform runs by default in HTTP mode. For
security purposes, and to ensure portal gadgets run correctly, configure it to run in
HTTPS mode. </para>
+ <para>JBoss Enterprise Portal Platform runs by default in HTTP mode. For
security purposes, configure your production platform to run in HTTPS mode.
</para>
<important>
<para>Understanding the fundamentals of keystore and truststore configuration
is critical to the tasks in this section. </para>
<para>Refer to the JBoss Enterprise Application Platform
<citetitle>Security Guide</citetitle> <citetitle>"SSL
Encryption Overview"</citetitle> chapter for detailed encryption theory and
procedures relevant to all JBoss Middleware platforms. </para>
@@ -49,7 +49,7 @@
</taskprerequisites>
<procedure>
<step>
- <para>Navigate to<filename>
<replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/</filename></para>
+ <para>Navigate
to<filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/</filename></para>
</step>
<step>
<para>Generate the keystore by executing the following command. Ensure you
substitute the <replaceable>values</replaceable> with information relevant
to your organization, and record the information for later use:</para>
@@ -103,6 +103,6 @@
<para>You have configured the platform to communicate using a secure
connection.</para>
</formalpara>
<para>
- You can now access the portal via address:
<literal>https://<replaceable><ServerAddress></replaceable>:8443/portal</literal>
- </para>
+ You can now access the portal from the address:
<literal>https://<replaceable><ServerAddress></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/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-02-27
11:53:06 UTC (rev 8473)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-02-28
03:37:35 UTC (rev 8474)
@@ -9,6 +9,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.1-4</revnumber>
+ <date>Tue Feb 28 2012</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Incorporated feedback from theute in
https://bugzilla.redhat.com/show_bug.cgi?id=794386. New sections added to Database
Configuration, specifically Multiple Portal JCR and IDM. </member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.1-3</revnumber>
<date>Mon Feb 27 2012</date>
<author>
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-02-27 11:53:06
UTC (rev 8473)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Uninstall_JBoss.xml 2012-02-28 03:37:35
UTC (rev 8474)
@@ -1,13 +1,11 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
-
<chapter id="Uninstall_JBoss">
- <title>Uninstall JBoss Enterprise Portal Platform</title>
- <para>
- As JBoss Enterprise Portal Platform was installed from a zip file, you may uninstall it
by simply deleting the JBoss Enterprise Portal Platform directory installed on your
system.
- </para>
+ <title>Uninstall JBoss Enterprise Portal Platform</title>
+ <para>
+ As JBoss Enterprise Portal Platform is installed from a Zip file, you can remove it by
deleting the JBoss Enterprise Portal Platform directory installed on your system.
+ </para>
</chapter>
-