From do-not-reply at jboss.org Tue Jan 29 11:07:59 2013
Content-Type: multipart/mixed; boundary="===============2645166856613222378=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r9094 - in
 epp/docs/branches/6.0/Reference_Guide: en-US and 4 other directories.
Date: Tue, 29 Jan 2013 01:55:31 -0500
Message-ID: <201301290655.r0T6tVCu022989@svn01.web.mwc.hst.phx2.redhat.com>

--===============2645166856613222378==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: jaredmorgs
Date: 2013-01-29 01:55:31 -0500 (Tue, 29 Jan 2013)
New Revision: 9094

Modified:
   epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations=
/Configuring_Services.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIde=
ntity/AuthenticationAuthorizationOverview.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIde=
ntity/LDAP.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIde=
ntity/SAML2_Salesforce_and_Google_Integration.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIde=
ntity/SSO.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/De=
faultPortalConfiguration.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Ja=
vascriptInterApplicationCommunication.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Sk=
inning.xml
   epp/docs/branches/6.0/Reference_Guide/en-US/modules/ServerIntegration.xml
   epp/docs/branches/6.0/Reference_Guide/publican.cfg
Log:
Final version ready for Tech Field review

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml	2013-01-29 04:3=
1:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml	2013-01-29 06:5=
5:31 UTC (rev 9094)
@@ -5,88 +5,6 @@
 ]>
 <preface id=3D"pref-Reference_Guide-Preface">
   <title>Preface</title>
-  <section id=3D"sect-File_Name_Conventions">
-    <title>File Name Conventions</title>
-    <para>The following naming conventions are used in file paths to impro=
ve their readability. Each convention is styled so that it stands out from =
the rest of the text:
-  </para>
-    <variablelist id=3D"vari-Reference_Guide-Introduction-Devices">
-      <varlistentry>
-        <term>
-          <replaceable>CAS_DIR</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The installation root of the Central Authentication Service (CAS) si=
ngle sign-on framework. This directory is an arbitrary location chosen when=
 CAS is downloaded and installed.
-     </para>
-          <para>
-      This convention is mainly used in <xref linkend=3D"sect-SSO_Single_S=
ign_On_-Central_Authentication_Service"/>.
-     </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>
-          <replaceable>ID_HOME</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The <filename>JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/conf/o=
rganization/</filename> directory, which contains identity-related configur=
ation resources. =

-     </para>
-          <para>
-      This convention is mainly used in <xref linkend=3D"chap-LDAP_Integra=
tion"/>.
-     </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>
-          <replaceable>JPP_DIST</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The installation root of the JBoss Portal Platform instance. For exa=
mple, if the JBoss Portal Platform distribution archive is extracted to the=
 <filename>/opt/jboss/JPP/</filename> directory, the <replaceable>JPP_DIST<=
/replaceable> directory is <filename>/opt/jboss/JPP</filename>.    =

-        </para>
-          <para>
-      This directory contains the <filename>jboss-jpp-&VY;</filename>, <fi=
lename>gatein-management</filename> and <filename>gatein-sso</filename> dir=
ectories.
-        </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>
-          <replaceable>JPP_HOME</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The server root of the JBoss Portal Platform instance. For example, =
if the JBoss Portal Platform distribution archive is extracted to the <file=
name>/opt/jboss/JPP/</filename> directory, the <replaceable>JPP_DIST</repla=
ceable> directory is <filename>/opt/jboss/JPP/jboss-jpp-&VY;/</filename>.  =
  =

-        </para>
-          <para>
-      This directory contains the <filename>gatein</filename>, <filename>m=
odules</filename> and <filename>standalone</filename> directories.
-        </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>
-          <replaceable>JPP_SERVER</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The <filename>JPP_DIST/jboss-jpp-<replaceable>&lt;VERSION&gt;</repla=
ceable></filename> directory, which contains the application server and the=
 configuration files necessary to run JBoss Portal Platform.
-     </para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>
-          <replaceable>TOMCAT_HOME</replaceable>
-        </term>
-        <listitem>
-          <para>
-      The installation root of the Apache Tomcat server. Apache Tomcat is =
a simple Java-based web server that can host servlets or JSP applications. =
It is not a part of JBoss Portal Platform, however, it is used in various e=
xamples in this guide to host single sign-on authentication services.
-     </para>
-          <para>
-      This convention is mainly used in <xref linkend=3D"sect-Reference_Gu=
ide-SSO_Single_Sign_On"/>.
-     </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-  </section>
 <!--            FOR PUBLICAN              -->  <xi:include xmlns:xi=3D"htt=
p://www.w3.org/2001/XInclude" href=3D"Common_Content/Conventions.xml">
  <!--            FOR JDOCBOOK:            -->     <xi:fallback xmlns:xi=3D=
"http://www.w3.org/2001/XInclude">
        <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"fa=
llback_content/Conventions.xml"/>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml	2013-01=
-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml	2013-01=
-29 06:55:31 UTC (rev 9094)
@@ -30,9 +30,5 @@
   </part>
   <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"modules=
/Advanced.xml"/>
   <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"modules=
/eXoJCR.xml"/>
-  <part>
-    <title>Server Integration</title>
-    <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"modul=
es/ServerIntegration.xml"/>
-  </part>
   <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"Revisio=
n_History.xml"/>
 </book>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml	2013-0=
1-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml	2013-0=
1-29 06:55:31 UTC (rev 9094)
@@ -17,8 +17,10 @@
         </author>
         <revdescription>
           <simplelist>
+            <member>=3D=3DReady for Engineering Field Staff review=3D=3D</=
member>
             <member>Incorporated feedback for BZ#903884 &quot;Default Port=
al Configuration&quot;.</member>
             <member>Changed all references to $JBOSS_HOME to JPP_HOME, and=
 added this file path abbreviation to <xref linkend=3D"sect-File_Name_Conve=
ntions"/>.</member>
+            <member>Reviewed all file path abbreviations, and remove the J=
BOSS_SERVER abbreviation, which was basically the same as JPP_HOME.</member>
           </simplelist>
         </revdescription>
       </revision>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foun=
dations/Configuring_Services.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundation=
s/Configuring_Services.xml	2013-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundation=
s/Configuring_Services.xml	2013-01-29 06:55:31 UTC (rev 9094)
@@ -259,10 +259,9 @@
         <para>
                     As you have already learned the services are all singl=
etons, so that the container creates only one single instance of each conta=
iner. The services are created by calling the constructors (called <emphasi=
s>constructor injection</emphasis>). If there are only zero-arguments const=
ructors (<code>Foo public Foo(){}</code>) there are no problems to be expec=
ted. That&apos;s easy.
                 </para>
-        <para>
+<!--<para>
                     But now look at <ulink url=3D"https://anonsvn.jboss.or=
g/repos/exo-jcr/core/trunk/exo.core.component.organization.jdbc/src/main/ja=
va/org/exoplatform/services/organization/jdbc/OrganizationServiceImpl.java"=
>https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.component.orga=
nization.jdbc/src/main/java/org/exoplatform/services/organization/jdbc/Orga=
nizationServiceImpl.java</ulink>
-                </para>
-        <para>
+                </para>-->        <para>
                     This JDBC implementation of BaseOrganizationService in=
terface has only one constructor:
                 </para>
         <programlisting language=3D"Java" role=3D"Java">public Organizatio=
nServiceImpl(ListenerService listenerService, DatabaseService dbService);</=
programlisting>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Authenticatio=
nAndIdentity/AuthenticationAuthorizationOverview.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/AuthenticationAuthorizationOverview.xml	2013-01-29 04:31:05 UTC (rev=
 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/AuthenticationAuthorizationOverview.xml	2013-01-29 06:55:31 UTC (rev=
 9094)
@@ -110,7 +110,7 @@
   <section id=3D"sect-Authentication_Authorization_Intro-Login_Modules">
     <title>Login modules</title>
     <para>
-From the WCI servlet API login, the user is redirected to JAAS authenticat=
ion. JBoss Portal Platform uses its own security domain (<emphasis role=3D"=
bold">gatein-domain</emphasis>) with a set of predefined login modules. Log=
in module configuration for <emphasis>gatein-domain</emphasis> is contained=
 in the <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/MET=
A-INF/gatein-jboss-beans.xml</filename> file.
+From the WCI servlet API login, the user is redirected to JAAS authenticat=
ion. JBoss Portal Platform uses its own security domain (<emphasis role=3D"=
bold">gatein-domain</emphasis>) with a set of predefined login modules. Log=
in module configuration for <emphasis>gatein-domain</emphasis> is contained=
 in the <filename>JPP_HOME/gatein/gatein.ear/META-INF/gatein-jboss-beans.xm=
l</filename> file.
         </para>
     <para>
             Below is the default login modules stack:

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Authenticatio=
nAndIdentity/LDAP.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/LDAP.xml	2013-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/LDAP.xml	2013-01-29 06:55:31 UTC (rev 9094)
@@ -8,7 +8,7 @@
     <title>Notational Device</title>
     <remark>Docs Note - jmorgan - The file path relating to ID_HOME has ch=
anged in JPP6. I&apos;ve made this change based on Marek&apos;s feedback. I=
&apos;ve also added this to the File Name Conventions section in the Prefac=
e.</remark>
     <para>
-            For ease of readability the following section uses the notatio=
nal device <replaceable>ID_HOME</replaceable> to represent the file path <f=
ilename>JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/<=
/filename>, as this directory is the root of all JBoss Portal Platform&apos=
;s  identity-related configuration.
+            For ease of readability the following section uses the notatio=
nal device <replaceable>ID_HOME</replaceable> to represent the file path <f=
ilename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/</f=
ilename>, as this directory is the root of all JBoss Portal Platform&apos;s=
  identity-related configuration.
             </para>
   </note>
   <para>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Authenticatio=
nAndIdentity/SAML2_Salesforce_and_Google_Integration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Authenticatio=
nAndIdentity/SSO.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/SSO.xml	2013-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndId=
entity/SSO.xml	2013-01-29 06:55:31 UTC (rev 9094)
@@ -384,10 +384,10 @@
       <section id=3D"sect-CAS_Portal_SSO_Primary_Configuration_File">
         <title>Portal SSO Primary Configuration File</title>
         <para>
-                  The main portal configuration file for SSO integration i=
s <code>JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/conf/sso/security-s=
so-configuration.xml</code> . All required SSO components such as agents an=
d SSO interceptors (servlet filters in v5.x of the product) are configured =
in this file.
+                  The main portal configuration file for SSO integration i=
s <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/sso/security-sso=
-configuration.xml</code> . All required SSO components such as agents and =
SSO interceptors (servlet filters in v5.x of the product) are configured in=
 this file.
                </para>
         <para>
-                  In most cases, it will never be necessary to edit <filen=
ame>security-sso-configuration.xml</filename> directly when using JBoss Por=
tal Platform. The portal architecture allows users to override the base con=
figuration described in this file using name/value pairs configured in one =
place: <filename>JPP_SERVER/standalone/configuration/gatein/configuration.p=
roperties</filename>
+                  In most cases, it will never be necessary to edit <filen=
ame>security-sso-configuration.xml</filename> directly when using JBoss Por=
tal Platform. The portal architecture allows users to override the base con=
figuration described in this file using name/value pairs configured in one =
place: <filename>JPP_HOME/standalone/configuration/gatein/configuration.pro=
perties</filename>
                </para>
         <para>
                   The exception to this rule is where configuration presen=
t in <filename>security-sso-configuration.xml</filename> is fundamentally u=
nsuitable for the production environment the server will be deployed to, or=
 when additional underlying functionality is required (for example, another=
 custom interceptor).
@@ -403,7 +403,7 @@
           <title>Configuring SSO configuration.properties for CAS</title>
           <step>
             <para>
-                        Open <filename>JPP_SERVER/standalone/configuration=
/gatein/configuration.properties</filename> and locate the SSO sections in =
the file.
+                        Open <filename>JPP_HOME/standalone/configuration/g=
atein/configuration.properties</filename> and locate the SSO sections in th=
e file.
                      </para>
           </step>
           <step>
@@ -449,7 +449,7 @@
             <term>gatein.sso.login.module.enabled</term>
             <listitem>
               <para>
-                           Specifies whether a pre-defined SSO login modul=
e declared in <filename> JPP_SERVER/standalone/configuration/standalone.xml=
</filename> is used for authentication. When the property is set to &quot;t=
rue&quot;, the SSODelegateLoginModule delegates work to another login modul=
e, as specified using the <property>gatein.sso.login.module.class</property=
> property. SSODelegateLoginModule will also resend all its options to its =
delegate.
+                           Specifies whether a pre-defined SSO login modul=
e declared in <filename> JPP_HOME/standalone/configuration/standalone.xml</=
filename> is used for authentication. When the property is set to &quot;tru=
e&quot;, the SSODelegateLoginModule delegates work to another login module,=
 as specified using the <property>gatein.sso.login.module.class</property> =
property. SSODelegateLoginModule will also resend all its options to its de=
legate.
                         </para>
               <para>
                            This parameter removes the need to manually cha=
nge any login module configuration in the standalone.xml file, which simpli=
fies platform configuration.
@@ -1227,7 +1227,7 @@
     <section id=3D"sect-Reference_Guide-SSO_Single_Sign_On_-OpenAM-Setupth=
eOpenAMclient">
       <title>JBoss Portal Platform Setup as OpenAM Client</title>
       <para>
-   On the JBoss Portal Platform server, you need to ensure proper configur=
ation of single sign-on properties in the <code>JPP_SERVER/standalone/confi=
guration/gatein/configuration.properties</code> file. Locate the SSO sectio=
n in this file and change/add properties in the section as follows:
+   On the JBoss Portal Platform server, you need to ensure proper configur=
ation of single sign-on properties in the <code>JPP_HOME/standalone/configu=
ration/gatein/configuration.properties</code> file. Locate the SSO section =
in this file and change/add properties in the section as follows:
     </para>
       <programlisting># SSO
 gatein.sso.enabled=3Dtrue
@@ -1659,7 +1659,7 @@
         <title>Configuring SPNEGO Integration with JBoss Portal Platform</=
title>
         <step>
           <para>
-                     Modify the <literal># SSO</literal> section of the <f=
ilename><replaceable>JPP_SERVER</replaceable>/standalone/configuration/gate=
in/configuration.properties</filename> file, replacing the original content=
 with the following properties:
+                     Modify the <literal># SSO</literal> section of the <f=
ilename><replaceable>JPP_HOME</replaceable>/standalone/configuration/gatein=
/configuration.properties</filename> file, replacing the original content w=
ith the following properties:
                   </para>
           <programlisting>
 <xi:include xmlns:xi=3D"http://www.w3.org/2001/XInclude" href=3D"../../ext=
ras/Authentication_Identity_SSO/default124.xml" parse=3D"text"/>
@@ -1703,7 +1703,7 @@
                 <term>gatein.sso.filter.login.sso.url</term>
                 <listitem>
                   <para>
-                         This value ensures that clicking the <guibutton>S=
ign in</guibutton> link will redirect users to the <literal>/portal/dologin=
</literal> URL, which is a secured URL declared in the <filename>security-c=
onstraint section of JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/web.xm=
l</filename> file, allowing the <systemitem>GateInNegotiationAuthenticator<=
/systemitem> valve to intercept the HTTP request.
+                         This value ensures that clicking the <guibutton>S=
ign in</guibutton> link will redirect users to the <literal>/portal/dologin=
</literal> URL, which is a secured URL declared in the <filename>security-c=
onstraint section of JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/web.xml<=
/filename> file, allowing the <systemitem>GateInNegotiationAuthenticator</s=
ystemitem> valve to intercept the HTTP request.
                         </para>
                 </listitem>
               </varlistentry>
@@ -1720,7 +1720,7 @@
                 <term>gatein.sso.valve.enabled</term>
                 <listitem>
                   <para>
-                         SPNEGO integration requires a custom Tomcat valve=
 to intercept HTTP requests for secured URLs. The <systemitem>SSODelegateVa=
lve</systemitem> is defined in the <filename>JPP_SERVER/gatein/gatein.ear/p=
ortal.war/WEB-INF/jboss-web.xml</filename> file and is used only if this op=
tion is set to <literal>true</literal>. The purpose of the valve is to dele=
gate the real work to another valve declared in the <literal>gatein.sso.val=
ve.class</literal> property. This eliminates the need to edit configuration=
 in the <filename>jboss-web.xml</filename> file.
+                         SPNEGO integration requires a custom Tomcat valve=
 to intercept HTTP requests for secured URLs. The <systemitem>SSODelegateVa=
lve</systemitem> is defined in the <filename>JPP_HOME/gatein/gatein.ear/por=
tal.war/WEB-INF/jboss-web.xml</filename> file and is used only if this opti=
on is set to <literal>true</literal>. The purpose of the valve is to delega=
te the real work to another valve declared in the <literal>gatein.sso.valve=
.class</literal> property. This eliminates the need to edit configuration i=
n the <filename>jboss-web.xml</filename> file.
                         </para>
                 </listitem>
               </varlistentry>
@@ -1737,7 +1737,7 @@
         </step>
         <step>
           <para>
-                     Modify configuration of the <systemitem>security</sys=
temitem> subsystem in the <filename><replaceable>JPP_SERVER</replaceable>/s=
tandalone/configuration/standalone.xml</filename> file:
+                     Modify configuration of the <systemitem>security</sys=
temitem> subsystem in the <filename><replaceable>JPP_HOME</replaceable>/sta=
ndalone/configuration/standalone.xml</filename> file:
                   </para>
           <substeps>
             <step>
@@ -1844,7 +1844,7 @@
          As demonstrated in <xref linkend=3D"proc-Reference_Guide-JBoss_En=
terprise_Portal_Platform_Configuration-SPNEGO_Testing"/>, users trying to s=
ign in without a valid Kerberos ticket are automatically redirected to the =
JBoss Portal Platform logon page. There, they can perform standard FORM aut=
hentication using their user name and password. =

         </para>
         <para>
-         If you want to disable FORM authentication to allow only users wi=
th a valid Kerberos ticket to sign in, you need to comment out the <paramet=
er>usernamePasswordDomain</parameter> option in the <literal>SPNEGOLoginMod=
ule</literal> configuration in the <filename><replaceable>JPP_SERVER</repla=
ceable>/standalone/configuration/standalone.xml</filename> file.
+         If you want to disable FORM authentication to allow only users wi=
th a valid Kerberos ticket to sign in, you need to comment out the <paramet=
er>usernamePasswordDomain</parameter> option in the <literal>SPNEGOLoginMod=
ule</literal> configuration in the <filename><replaceable>JPP_HOME</replace=
able>/standalone/configuration/standalone.xml</filename> file.
         </para>
         <programlisting language=3D"XML"><![CDATA[<login-module
     code=3D"org.gatein.sso.spnego.SPNEGOLoginModule" flag=3D"requisite">
@@ -1858,7 +1858,7 @@
       <section>
         <title>Enabling Logging</title>
         <para>
-         To enable logging of events related to SPNEGO authentication, you=
 can add the following entries to the <systemitem>logging</systemitem> subs=
ystem in the <filename><replaceable>JPP_SERVER</replaceable>/standalone/con=
figuration/standalone.xml</filename> file:
+         To enable logging of events related to SPNEGO authentication, you=
 can add the following entries to the <systemitem>logging</systemitem> subs=
ystem in the <filename><replaceable>JPP_HOME</replaceable>/standalone/confi=
guration/standalone.xml</filename> file:
         </para>
         <programlisting language=3D"XML"><![CDATA[<logger category=3D"org.=
gatein.sso">
     <level name=3D"TRACE"/>
@@ -1893,7 +1893,7 @@
     <section id=3D"sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_V=
alve-Default_Config">
       <title>Default Configuration</title>
       <para>
-               The JBoss SSO valve is enabled by default. The enablement i=
s ensured by the following JBoss Web subsystem configuration entry in the <=
filename>JPP_SERVER/standalone/configuration/standalon-ha.xml</filename> fi=
le:
+               The JBoss SSO valve is enabled by default. The enablement i=
s ensured by the following JBoss Web subsystem configuration entry in the <=
filename>JPP_HOME/standalone/configuration/standalon-ha.xml</filename> file:
             </para>
       <programlisting language=3D"XML"><![CDATA[
 <sso cache-container=3D"web" cache-name=3D"sso" reauthenticate=3D"false" />
@@ -1929,7 +1929,7 @@
         </step>
         <step>
           <para>
-                     On both servers, open the <filename><replaceable>JPP_=
SERVER</replaceable>/standalone/configuration/standalone-ha.xml</filename> =
file. Add the <parameter>domain</parameter> parameter to the <parameter>sso=
</parameter> entry and specify the name of the shared DNS domain in its val=
ue.
+                     On both servers, open the <filename><replaceable>JPP_=
HOME</replaceable>/standalone/configuration/standalone-ha.xml</filename> fi=
le. Add the <parameter>domain</parameter> parameter to the <parameter>sso</=
parameter> entry and specify the name of the shared DNS domain in its value.
                   </para>
           <programlisting language=3D"XML"><![CDATA[
 <sso cache-container=3D"web" cache-name=3D"sso" reauthenticate=3D"false" d=
omain=3D"yourdomain.com"/>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.=
xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml	20=
13-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml	20=
13-01-29 06:55:31 UTC (rev 9094)
@@ -1,27 +1,96 @@
 <?xml version=3D'1.0' encoding=3D'UTF-8'?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.=
oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY VY '6.0'>
 <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent">
 %BOOK_ENTITIES;
 ]>
 <chapter id=3D"chap-Reference_Guide-Introduction">
   <title>Introduction</title>
   <para>
-JBoss Portal Platform is based on the GateIn project, which is the merge o=
f two mature Java projects: JBoss Portal and eXo Portal. This new community=
 project takes the best of both offerings and incorporates them into a sing=
le portal framework. The aim is to provide an intuitive user-friendly porta=
l, and a framework to address the needs of today&apos;s Web 2.0 application=
s.
+JBoss Portal Platform is based on the GateIn Portal project. The aim is to=
 provide an intuitive user-friendly portal, and a framework to address the =
needs of today&apos;s Web 2.0 applications.
  </para>
-<figure>
-<title id=3D"Frontpage">Front Page</title>
-  <mediaobject>
-    <imageobject role=3D"html">
-      <imagedata width=3D"444" align=3D"center" scale=3D"100" fileref=3D"i=
mages/Common/Frontpage.png" format=3D"PNG"/>
-    </imageobject>
-    <imageobject role=3D"fo">
-      <imagedata width=3D"444" contentwidth=3D"150mm" align=3D"center" fil=
eref=3D"images/Common/Frontpage.png" format=3D"PNG"/>
-    </imageobject>
-  </mediaobject>
-</figure>
+  <figure>
+    <title id=3D"Frontpage">Front Page</title>
+    <mediaobject>
+      <imageobject role=3D"html">
+        <imagedata width=3D"666" fileref=3D"images/Common/JPP_Front_Page.p=
ng" format=3D"PNG"/>
+      </imageobject>
+    </mediaobject>
+  </figure>
   <para>
-  This book provides a deep-dive information about installation and config=
uration of the services provided by JBoss Portal Platform.
+  This book provides  deep-dive information about installation and configu=
ration of the services provided by JBoss Portal Platform.
  </para>
+  <section id=3D"sect-File_Name_Conventions">
+    <title>File Name Conventions</title>
+    <para>The following naming conventions are used in file paths to impro=
ve their readability. Each convention is styled so that it stands out from =
the rest of the text:
+  </para>
+    <variablelist id=3D"vari-Reference_Guide-Introduction-Devices">
+      <varlistentry>
+        <term>
+          <replaceable>CAS_DIR</replaceable>
+        </term>
+        <listitem>
+          <para>
+      The installation root of the Central Authentication Service (CAS) si=
ngle sign-on framework. This directory is an arbitrary location chosen when=
 CAS is downloaded and installed.
+     </para>
+          <para>
+      This convention is mainly used in <xref linkend=3D"sect-SSO_Single_S=
ign_On_-Central_Authentication_Service"/>.
+     </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <replaceable>ID_HOME</replaceable>
+        </term>
+        <listitem>
+          <para>
+      The <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/org=
anization/</filename> directory, which contains identity-related configurat=
ion resources. =

+     </para>
+          <para>
+      This convention is mainly used in <xref linkend=3D"chap-LDAP_Integra=
tion"/>.
+     </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <replaceable>JPP_DIST</replaceable>
+        </term>
+        <listitem>
+          <para>
+      The installation root of the JBoss Portal Platform instance. For exa=
mple, if the JBoss Portal Platform distribution archive is extracted to the=
 <filename>/opt/jboss/JPP/</filename> directory, the <replaceable>JPP_DIST<=
/replaceable> directory is <filename>/opt/jboss/JPP</filename>.    =

+        </para>
+          <para>
+      This directory contains the <filename>jboss-jpp-&VY;</filename>, <fi=
lename>gatein-management</filename> and <filename>gatein-sso</filename> dir=
ectories, and is used extensively in sections that contain configuration st=
ored in these directories.        </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <replaceable>JPP_HOME</replaceable>
+        </term>
+        <listitem>
+          <para>
+      The <filename>JPP_DIST/jboss-jpp-&VY;</filename> directory, which co=
ntains the application server and the configuration files necessary to run =
JBoss Portal Platform.
+     </para>
+          <para>
+      This directory contains the <filename>gatein</filename>, <filename>m=
odules</filename> and <filename>standalone</filename> directories.
+        </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <replaceable>TOMCAT_HOME</replaceable>
+        </term>
+        <listitem>
+          <para>
+      The installation root of the Apache Tomcat server. Apache Tomcat is =
a simple Java-based web server that can host servlets or JSP applications. =
It is not a part of JBoss Portal Platform, however, it is used in various e=
xamples in this guide to host single sign-on authentication services.
+     </para>
+          <para>
+      This convention is mainly used in <xref linkend=3D"sect-Reference_Gu=
ide-SSO_Single_Sign_On"/>.
+     </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+  </section>
   <section id=3D"sect-Reference_Guide-Introduction-Related_Links">
     <title>Related Links</title>
     <variablelist>
@@ -29,7 +98,7 @@
         <term>Technical documentation</term>
         <listitem>
           <para>
-      Other technical documentation, including an <emphasis role=3D"bold">=
Installation Guide</emphasis>, and a <emphasis role=3D"bold">User Guide</em=
phasis> can be found at <ulink url=3D"http://www.redhat.com/docs/en-US/JBos=
s_Enterprise_Portal_Platform" type=3D"http">www.redhat.com/docs</ulink>
+Technical documentation, including an <emphasis role=3D"bold">Installation=
 Guide</emphasis>, and a <emphasis role=3D"bold">User Guide</emphasis> can =
be found at <ulink url=3D"https://access.redhat.com/knowledge/docs/JBoss_Po=
rtal_Platform/" type=3D"http"/>
      </para>
         </listitem>
       </varlistentry>
@@ -37,38 +106,15 @@
         <term>Non-technical documentation</term>
         <listitem>
           <para>
-      Links to non-technical documents are included on the front page of t=
he portal:
-     </para>
-<figure>
-<title id=3D"nontechdocs">Non-technical documentation</title>
-          <mediaobject>
-            <imageobject role=3D"html">
-              <imagedata width=3D"444" align=3D"center" scale=3D"90" filer=
ef=3D"images/Common/Non-tech-docs.png" format=3D"PNG"/>
-            </imageobject>
-            <imageobject role=3D"fo">
-              <imagedata width=3D"444" contentwidth=3D"130mm" align=3D"cen=
ter" fileref=3D"images/Common/Non-tech-docs.png" format=3D"PNG"/>
-            </imageobject>
-          </mediaobject>
-</figure>
+      Links to non-technical documents are available by clicking &quot;Por=
tals the Red Hat way&quot;,  or &quot;Launch fast with Maven Quick Starts&q=
uot;.     </para>
         </listitem>
       </varlistentry>
       <varlistentry>
         <term>Videos</term>
         <listitem>
           <para>
-      A link to <ulink url=3D"http://vimeo.com/channels/gatein" type=3D"ht=
tp">videos</ulink> related to the JBoss Portal Platform is also included on=
 the front page:
-     </para>
-<figure>
-<title id=3D"videos">Videos</title>
-          <mediaobject>
-            <imageobject role=3D"html">
-              <imagedata width=3D"444" align=3D"center" scale=3D"90" filer=
ef=3D"images/Common/Videos.png" format=3D"PNG"/>
-            </imageobject>
-            <imageobject role=3D"fo">
-              <imagedata width=3D"444" contentwidth=3D"130mm" align=3D"cen=
ter" fileref=3D"images/Common/Videos.png" format=3D"PNG"/>
-            </imageobject>
-          </mediaobject>
-</figure>
+      A link to <ulink url=3D"http://vimeo.com/channels/gatein" type=3D"ht=
tp">videos</ulink> related to the JBoss Portal Platform is also included on=
 the front page from the Videos tab. </para>
+          <para>These videos are prepared by GateIn Portal development tea=
m members using development versions of JBoss Portal Platform, and therefor=
e should be used only as reference examples when configuring your productio=
n system.     </para>
         </listitem>
       </varlistentry>
     </variablelist>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelop=
ment/DefaultPortalConfiguration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/D=
efaultPortalConfiguration.xml	2013-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/D=
efaultPortalConfiguration.xml	2013-01-29 06:55:31 UTC (rev 9094)
@@ -93,76 +93,76 @@
 <!--Disabling a Portal Container =

        This content is mirrored in the JPP 5.2 Reference Guide.
        Any changes here should be reflected there as well.
-       --><!--<section id=3D"sect-Reference_Guide-Default_Portal_Configura=
tion-Disabling_a_Portal_Container">
-  <title><remark>BZ#794416</remark>Disabling a Portal Container</title>
-  <para>
+       -->  <section id=3D"sect-Reference_Guide-Default_Portal_Configurati=
on-Disabling_a_Portal_Container">
+    <title><remark>BZ#794416</remark>Disabling a Portal Container</title>
+    <para>
              Once you have created a custom portal container that suits yo=
ur needs, you may wish to disable a portal container   that is no longer re=
quired.
           </para>
-  <task>
-    <title>Task: Disable a portal in JBoss Portal Platform 5</title>
-    <tasksummary>
-      <para>Disable an unused portal container in a JBoss Portal Platform =
instance. =

+    <task>
+      <title>Task: Disable a portal in JBoss Portal Platform 5</title>
+      <tasksummary>
+        <para>Disable an unused portal container in a JBoss Portal Platfor=
m instance. =

                    </para>
-    </tasksummary>
-    <taskprerequisites>
-      <title>Prerequisites: </title>
-      <itemizedlist>
-        <listitem>
-          <para>
+      </tasksummary>
+      <taskprerequisites>
+        <title>Prerequisites: </title>
+        <itemizedlist>
+          <listitem>
+            <para>
 A new portal container is created,                                =

                             </para>
-        </listitem>
-      </itemizedlist>
-    </taskprerequisites>
-    <procedure>
-      <title/>
-      <step>
-        <para>
+          </listitem>
+        </itemizedlist>
+      </taskprerequisites>
+      <procedure>
+        <title/>
+        <step>
+          <para>
                          Add the following configuration to the <filename>=
configuration.xml</filename> of the custom extension in order to disable a =
portal container:
                       </para>
-        <programlisting language=3D"XML" role=3D"XML"><![CDATA[<?xml versi=
on=3D"1.0" encoding=3D"UTF-8"?>
-<configuration xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
-    xsi:schemaLocation=3D"http://www.exoplaform.org/xml/ns/kernel_1_0.xsd =
http://www.exoplaform.org/xml/ns/kernel_1_1.xsd"
-    xmlns=3D"http://www.exoplaform.org/xml/ns/kernel_1_1.xsd">
-    <external-component-plugins>
-        <!-- The full qualified name of the PortalContainerConfig -->
-        <target-component>org.exoplatform.container.definition.PortalConta=
inerConfig
-        </target-component>
-        <component-plugin>
-            <!-- The name of the plugin -->
-            <name>Add PortalContainer Definitions</name>
-            <!-- (existing configuration for new portal container) -->
-        </component-plugin>
-        <component-plugin>
-            <!-- The name of the plugin -->
-            <name>Disable a PortalContainer</name>
-            <!-- The name of the method to call on the PortalContainerConf=
ig in order to register the changes on the PortalContainerDefinitions -->
-            <set-method>registerDisablePlugin</set-method>
-            <!-- The full qualified name of the PortalContainerDefinitionD=
isablePlugin -->
-            <type>org.exoplatform.container.definition.PortalContainerDefi=
nitionDisablePlugin</type>
-            <init-params>
-                <!-- The list of the name of the portal containers to disa=
ble -->
-                <values-param>
-                    <name>names</name>
-                    <value>$PORTAL_NAME</value>
-                </values-param>
-            </init-params>
-        </component-plugin>                =

-    </external-component-plugins>
-</configuration>
-]]></programlisting>
-      </step>
-      <step>
-        <para>The portal name declared in the &lt;values-param&gt; directi=
ve will no longer be available at http://{hostname}:{port}/portal</para>
-      </step>
-    </procedure>
-    <taskrelated>
-      <note>
-        <title/>
-        <para>
+          <programlisting language=3D"XML">&lt;!-- Comment 1 --&gt;
+&lt;?xml version=3D&quot;1.0&quot; encoding=3D&quot;UTF-8&quot;?&gt;
+&lt;configuration xmlns:xsi=3D&quot;http://www.w3.org/2001/XMLSchema-insta=
nce&quot;
+    xsi:schemaLocation=3D&quot;http://www.exoplaform.org/xml/ns/kernel_1_0=
.xsd http://www.exoplaform.org/xml/ns/kernel_1_1.xsd&quot;
+    xmlns=3D&quot;http://www.exoplaform.org/xml/ns/kernel_1_1.xsd&quot;&gt;
+    &lt;external-component-plugins&gt;
+        &lt;!-- The full qualified name of the PortalContainerConfig --&gt;
+        &lt;target-component&gt;org.exoplatform.container.definition.Porta=
lContainerConfig
+        &lt;/target-component&gt;
+        &lt;component-plugin&gt;
+            &lt;!-- The name of the plugin --&gt;
+            &lt;name&gt;Add PortalContainer Definitions&lt;/name&gt;
+            &lt;!-- (existing configuration for new portal container) --&g=
t;
+        &lt;/component-plugin&gt;
+        &lt;component-plugin&gt;
+            &lt;!-- The name of the plugin --&gt;
+            &lt;name&gt;Disable a PortalContainer&lt;/name&gt;
+            &lt;!-- The name of the method to call on the PortalContainerC=
onfig in order to register the changes on the PortalContainerDefinitions --=
&gt;
+            &lt;set-method&gt;registerDisablePlugin&lt;/set-method&gt;
+            &lt;!-- The full qualified name of the PortalContainerDefiniti=
onDisablePlugin --&gt;
+            &lt;type&gt;org.exoplatform.container.definition.PortalContain=
erDefinitionDisablePlugin&lt;/type&gt;
+            &lt;init-params&gt;
+                &lt;!-- The list of the name of the portal containers to d=
isable --&gt;
+                &lt;values-param&gt;
+                    &lt;name&gt;names&lt;/name&gt;
+                    &lt;value&gt;$PORTAL_NAME&lt;/value&gt;
+                &lt;/values-param&gt;
+            &lt;/init-params&gt;
+        &lt;/component-plugin&gt;                =

+    &lt;/external-component-plugins&gt;
+&lt;/configuration&gt;</programlisting>
+        </step>
+        <step>
+          <para>The portal name declared in the &lt;values-param&gt; direc=
tive will no longer be available at <literal>http://{hostname}:{port}/porta=
l</literal>.</para>
+        </step>
+      </procedure>
+      <taskrelated>
+        <note>
+          <para>
                           Disabling the default <emphasis>portal</emphasis=
> container is possible as well, but some functions, such as WSRP, or Servi=
ces Management, depend on the default portal container to be deployed, and =
will no longer work if this is disabled.
                       </para>
-      </note>
-    </taskrelated>
-  </task>
-</section>--></chapter>
+        </note>
+      </taskrelated>
+    </task>
+  </section>
+</chapter>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelop=
ment/JavascriptInterApplicationCommunication.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/J=
avascriptInterApplicationCommunication.xml	2013-01-29 04:31:05 UTC (rev 909=
3)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/J=
avascriptInterApplicationCommunication.xml	2013-01-29 06:55:31 UTC (rev 909=
4)
@@ -56,7 +56,7 @@
   <section id=3D"sect-Reference_Guide-JavaScript_Inter_Application_Communi=
cation-Library">
     <title>Library</title>
     <para>
-   The Inter Application Communication library is found in <filename>01eXo=
Resources.war:/javascript/eXo/core/Topic.js</filename>
+   The Inter Application Communication library is found in <filename>JPP_H=
OME/gatein/gatein.ear/eXoResources.war/javascript/eXo/core/Topic.js</filena=
me>
   </para>
     <programlisting language=3D"Java" role=3D"Java"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_JavascriptInterApplicationCommunication/default155.java" parse=3D"text"/><=
/programlisting>
   </section>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelop=
ment/Skinning.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/S=
kinning.xml	2013-01-29 04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/S=
kinning.xml	2013-01-29 06:55:31 UTC (rev 9094)
@@ -153,7 +153,7 @@
     <section id=3D"sect-Reference_Guide-The_Skin_Service-Resource_Request_=
Filter">
       <title>Resource Request Filter</title>
       <para>
-               Because of JBoss Portal Platform&apos;s Right-To-Left suppo=
rt, all CSS files need to be retrieved through a Servlet filter and the web=
 application needs to be configured to activate this filter. This is alread=
y done for <literal>01eXoResources.war</literal> web application which cont=
ains the default skin.
+               Because of JBoss Portal Platform&apos;s Right-To-Left suppo=
rt, all CSS files need to be retrieved through a Servlet filter and the web=
 application needs to be configured to activate this filter. This is alread=
y done for the<literal>JPP_HOME/gatein/gatein.ear/eXoResources.war</literal=
> web application which contains the default skin.
             </para>
       <para>
                Any new web applications containing skinning CSS files will=
 need to have the following added to their <filename>web.xml</filename> :
@@ -170,7 +170,7 @@
   <section id=3D"sect-Reference_Guide-Skinning_the_Portal-The_Default_Skin=
">
     <title>The Default Skin</title>
     <para>
-            The default skin for JBoss Portal Platform is located as part =
of the <literal>01eXoResources.war</literal>. The main files associated wit=
h the skin are:
+            The default skin for JBoss Portal Platform is located as part =
of the <literal>JPP_HOME/gatein/gatein.ear/eXoResources.war</literal>. The =
main files associated with the skin are:
          </para>
     <variablelist>
       <varlistentry>
@@ -227,7 +227,7 @@
                </para>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default186.xml" parse=3D"text"/></programlisting>
         <para>
-                  The default portal skin and window styles are defined in=
 <filename>01eXoResources.war/WEB-INF/gatein-resources.xml</filename>.
+                  The default portal skin and window styles are defined in=
 <filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/WEB-INF/gatein-resou=
rces.xml</filename>.
                </para>
         <note>
           <title>CSS</title>
@@ -244,18 +244,17 @@
         <para>
                   It is recommended that preview icons of any other skins =
are included when creating a new portal skin and that the other skins are u=
pdated with your new portal skin preview.
                </para>
-
-<figure>
-<title id=3D"portal-change-skin">Portal_Skin_Change</title>
-        <mediaobject>
-          <imageobject role=3D"html">
-            <imagedata width=3D"444" align=3D"center" scale=3D"100" filere=
f=3D"images/PortalDevelopment/Skinning/portal-change-skin.png" format=3D"PN=
G"/>
-          </imageobject>
-          <imageobject role=3D"fo">
-            <imagedata width=3D"444" contentwidth=3D"150mm" align=3D"cente=
r" fileref=3D"images/PortalDevelopment/Skinning/portal-change-skin.png" for=
mat=3D"PNG"/>
-          </imageobject>
-        </mediaobject>
-</figure>
+        <figure>
+          <title id=3D"portal-change-skin">Portal_Skin_Change</title>
+          <mediaobject>
+            <imageobject role=3D"html">
+              <imagedata width=3D"444" align=3D"center" scale=3D"100" file=
ref=3D"images/PortalDevelopment/Skinning/portal-change-skin.png" format=3D"=
PNG"/>
+            </imageobject>
+            <imageobject role=3D"fo">
+              <imagedata width=3D"444" contentwidth=3D"150mm" align=3D"cen=
ter" fileref=3D"images/PortalDevelopment/Skinning/portal-change-skin.png" f=
ormat=3D"PNG"/>
+            </imageobject>
+          </mediaobject>
+        </figure>
         <para>
                   The portal skin preview icon is specified through the CS=
S of the portal skin. In order for the current portal skin to be able to di=
splay the preview it must specify a specific CSS class and set the icon as =
the background.
                </para>
@@ -264,10 +263,10 @@
                </para>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default187.xml" parse=3D"text"/></programlisting>
         <para>
-                  In order for the default skin to display the skin icon f=
or a new portal skin, the preview screen shot needs to be placed in: <filen=
ame>01eXoResources.war:/skin/DefaultSkin/portal/webui/component/customizati=
on/UIChangeSkinForm/background</filename>.
+                  In order for the default skin to display the skin icon f=
or a new portal skin, the preview screen shot needs to be placed in: <filen=
ame>JPP_HOME/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/portal/web=
ui/component/customization/UIChangeSkinForm/background</filename>.
                </para>
         <para>
-                  The CSS stylesheet for the default portal needs to have =
the following updated with the preview icon CSS class. For a skin named <li=
teral>MySkin</literal>, the following needs to be updated: <filename>01eXoR=
esources.war:/skin/DefaultSkin/portal/webui/component/customization/UIChang=
eSkinForm/Stylesheet.css</filename>.
+                  The CSS stylesheet for the default portal needs to have =
the following updated with the preview icon CSS class. For a skin named <li=
teral>MySkin</literal>, the following needs to be updated: <filename>JPP_HO=
ME/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/portal/webui/compone=
nt/customization/UIChangeSkinForm/Stylesheet.css</filename>.
                </para>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default188.xml" parse=3D"text"/></programlisting>
       </section>
@@ -277,17 +276,17 @@
       <para>
                Window styles are the CSS applied to window decorations. An=
 administrator can decide which style of decoration should go around the wi=
ndow when they add a new application or gadget to a page.
             </para>
-<figure>
-<title id=3D"windowStyles">Window Styles</title>
-      <mediaobject>
-        <imageobject role=3D"html">
-          <imagedata width=3D"444" align=3D"center" scale=3D"100" fileref=
=3D"images/PortalDevelopment/Skinning/windowStyles.png" format=3D"PNG"/>
-        </imageobject>
-        <imageobject role=3D"fo">
-          <imagedata width=3D"444" contentwidth=3D"150mm" align=3D"center"=
 fileref=3D"images/PortalDevelopment/Skinning/windowStyles.png" format=3D"P=
NG"/>
-        </imageobject>
-      </mediaobject>
-</figure>
+      <figure>
+        <title id=3D"windowStyles">Window Styles</title>
+        <mediaobject>
+          <imageobject role=3D"html">
+            <imagedata width=3D"444" align=3D"center" scale=3D"100" filere=
f=3D"images/PortalDevelopment/Skinning/windowStyles.png" format=3D"PNG"/>
+          </imageobject>
+          <imageobject role=3D"fo">
+            <imagedata width=3D"444" contentwidth=3D"150mm" align=3D"cente=
r" fileref=3D"images/PortalDevelopment/Skinning/windowStyles.png" format=3D=
"PNG"/>
+          </imageobject>
+        </mediaobject>
+      </figure>
       <section id=3D"sect-Reference_Guide-Creating_a_New_Window_Style-Wind=
ow_Style_Configuration">
         <title>Window Style Configuration</title>
         <para>
@@ -298,7 +297,7 @@
                </para>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default189.xml" parse=3D"text"/></programlisting>
         <para>
-                  The windows style configuration for the default skin is =
configured in: <filename>01eXoResources.war/WEB-INF/gatein-resources.xml</f=
ilename>.
+                  The windows style configuration for the default skin is =
configured in: <filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/WEB-IN=
F/gatein-resources.xml</filename>.
                </para>
         <note>
           <title>Window Styles and Portal Skins</title>
@@ -316,7 +315,7 @@
                   In order for the skin service to display the window deco=
rators, it must have CSS classes specifically named in relation to the wind=
ow style name. The service will try and display CSS based on this naming co=
nvention. The CSS class must be included as part of the current portal skin=
 for the window decorators to be displayed.
                </para>
         <para>
-                  The location of the window decorator CSS classes for the=
 default portal theme is located at: <filename>01eXoResources.war/skin/Port=
letThemes/Stylesheet.css</filename>.
+                  The location of the window decorator CSS classes for the=
 default portal theme is located at: <filename>JPP_HOME/gatein/gatein.ear/e=
XoResources.war/skin/PortletThemes/Stylesheet.css</filename>.
                </para>
         <para/>
         <para>
@@ -521,7 +520,7 @@
                The portlet specification defines a set of default CSS clas=
ses that should be available for portlets. These classes are included as pa=
rt of the portal skin. Please see the portlet specification for a list of t=
he default classes that should be available.
             </para>
       <para>
-               For the default portal skin, the portlet specification CSS =
classes are defined in: <filename>01eXoResources.war/skin/Portlet/Styleshee=
t.css</filename>.
+               For the default portal skin, the portlet specification CSS =
classes are defined in: <filename>JPP_HOME/gatein/gatein.ear/eXoResources.w=
ar/skin/Portlet/Stylesheet.css</filename>.
             </para>
     </section>
   </section>
@@ -561,14 +560,14 @@
         <para>
                   The decorator is a pattern to create a contour or a curv=
e around an area. In order to achieve this effect you need to create nine c=
ells. The <literal>BODY</literal> is the central area that you want to deco=
rate. The other eight cells are distributed around the <literal>BODY</liter=
al> cell. You can use the width, height and background image properties to =
achieve any decoration effect that you want.
                </para>
-<figure>
-<title id=3D"decoratorPattern">Decorator Pattern</title>
-        <mediaobject>
-          <imageobject>
-            <imagedata width=3D"418" fileref=3D"images/PortalDevelopment/S=
kinning/decoratorPattern.png" format=3D"PNG"/>
-          </imageobject>
-        </mediaobject>
-</figure>
+        <figure>
+          <title id=3D"decoratorPattern">Decorator Pattern</title>
+          <mediaobject>
+            <imageobject>
+              <imagedata width=3D"418" fileref=3D"images/PortalDevelopment=
/Skinning/decoratorPattern.png" format=3D"PNG"/>
+            </imageobject>
+          </mediaobject>
+        </figure>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default193.xml" parse=3D"text"/></programlisting>
       </section>
       <section id=3D"sect-Reference_Guide-Some_CSS_Techniques-Left_Margin_=
Left_Pattern">
@@ -576,17 +575,17 @@
         <para>
                   Left margin left pattern is a technique to create two bl=
ocks side by side. The left block will have a fixed size and the right bloc=
k will take the rest of the available space. When the user resizes the brow=
ser the added or removed space will be taken from the right block.
                </para>
-<figure>
-<title id=3D"leftMarginPattern">Left Margin Pattern</title>
-        <mediaobject>
-          <imageobject role=3D"html">
-            <imagedata align=3D"center" fileref=3D"images/PortalDevelopmen=
t/Skinning/leftMarginPattern.png" format=3D"PNG"/>
-          </imageobject>
-          <imageobject role=3D"fo">
-            <imagedata width=3D"100mm" align=3D"center" fileref=3D"images/=
PortalDevelopment/Skinning/leftMarginPattern.png" format=3D"PNG"/>
-          </imageobject>
-        </mediaobject>
-</figure>
+        <figure>
+          <title id=3D"leftMarginPattern">Left Margin Pattern</title>
+          <mediaobject>
+            <imageobject role=3D"html">
+              <imagedata align=3D"center" fileref=3D"images/PortalDevelopm=
ent/Skinning/leftMarginPattern.png" format=3D"PNG"/>
+            </imageobject>
+            <imageobject role=3D"fo">
+              <imagedata width=3D"100mm" align=3D"center" fileref=3D"image=
s/PortalDevelopment/Skinning/leftMarginPattern.png" format=3D"PNG"/>
+            </imageobject>
+          </mediaobject>
+        </figure>
         <programlisting language=3D"XML" role=3D"XML"><xi:include xmlns:xi=
=3D"http://www.w3.org/2001/XInclude" href=3D"../../extras/PortalDevelopment=
_Skinning/default194.xml" parse=3D"text"/></programlisting>
       </section>
     </section>

Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/ServerIntegra=
tion.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(Binary files differ)

Modified: epp/docs/branches/6.0/Reference_Guide/publican.cfg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/6.0/Reference_Guide/publican.cfg	2013-01-29 04:31:05 =
UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/publican.cfg	2013-01-29 06:55:31 =
UTC (rev 9094)
@@ -3,4 +3,4 @@
 debug: 1
 type: Book
 git_branch: docs-rhel-6
-show_remarks: 1
+#show_remarks: 1


--===============2645166856613222378==--