12:55 a.m.
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/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2_Salesforce_and_Google_Integration.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/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/DefaultPortalConfiguration.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.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
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml 2013-01-29 04:31:05 UTC (rev
9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Preface.xml 2013-01-29 06:55:31 UTC (rev
9094)
@@ -5,88 +5,6 @@
]>
<preface id="pref-Reference_Guide-Preface">
<title>Preface</title>
- <section id="sect-File_Name_Conventions">
- <title>File Name Conventions</title>
- <para>The following naming conventions are used in file paths to improve their
readability. Each convention is styled so that it stands out from the rest of the text:
- </para>
- <variablelist id="vari-Reference_Guide-Introduction-Devices">
- <varlistentry>
- <term>
- <replaceable>CAS_DIR</replaceable>
- </term>
- <listitem>
- <para>
- The installation root of the Central Authentication Service (CAS) single 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="sect-SSO_Single_Sign_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/organization/</filename>
directory, which contains identity-related configuration resources.
- </para>
- <para>
- This convention is mainly used in <xref
linkend="chap-LDAP_Integration"/>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>
- <replaceable>JPP_DIST</replaceable>
- </term>
- <listitem>
- <para>
- The installation root of the JBoss Portal Platform instance. For example, 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>,
<filename>gatein-management</filename> and
<filename>gatein-sso</filename> directories.
- </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
<filename>/opt/jboss/JPP/</filename> directory, the
<replaceable>JPP_DIST</replaceable> directory is
<filename>/opt/jboss/JPP/jboss-jpp-&VY;/</filename>.
- </para>
- <para>
- This directory contains the <filename>gatein</filename>,
<filename>modules</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><VERSION></replaceable></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 examples in this guide to host
single sign-on authentication services.
- </para>
- <para>
- This convention is mainly used in <xref
linkend="sect-Reference_Guide-SSO_Single_Sign_On"/>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
<!-- FOR PUBLICAN --> <xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="Common_Content/Conventions.xml">
<!-- FOR JDOCBOOK: --> <xi:fallback
xmlns:xi="http://www.w3.org/2001/XInclude">
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="fallback_content/Conventions.xml"/>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml
===================================================================
--- 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="http://www.w3.org/2001/XInclude"
href="modules/Advanced.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="modules/eXoJCR.xml"/>
- <part>
- <title>Server Integration</title>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="modules/ServerIntegration.xml"/>
- </part>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="Revision_History.xml"/>
</book>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-29 04:31:05
UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-29 06:55:31
UTC (rev 9094)
@@ -17,8 +17,10 @@
</author>
<revdescription>
<simplelist>
+ <member>==Ready for Engineering Field Staff review==</member>
<member>Incorporated feedback for BZ#903884 "Default Portal
Configuration".</member>
<member>Changed all references to $JBOSS_HOME to JPP_HOME, and added
this file path abbreviation to <xref
linkend="sect-File_Name_Conventions"/>.</member>
+ <member>Reviewed all file path abbreviations, and remove the
JBOSS_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/Foundations/Configuring_Services.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/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 singletons, so that
the container creates only one single instance of each container. The services are created
by calling the constructors (called <emphasis>constructor
injection</emphasis>). If there are only zero-arguments constructors
(<code>Foo public Foo(){}</code>) there are no problems to be expected.
That's easy.
</para>
- <para>
+<!--<para>
But now look at <ulink
url="https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.com...
- </para>
- <para>
+ </para>--> <para>
This JDBC implementation of BaseOrganizationService interface has
only one constructor:
</para>
<programlisting language="Java" role="Java">public
OrganizationServiceImpl(ListenerService listenerService, DatabaseService
dbService);</programlisting>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-01-29
06:55:31 UTC (rev 9094)
@@ -110,7 +110,7 @@
<section id="sect-Authentication_Authorization_Intro-Login_Modules">
<title>Login modules</title>
<para>
-From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss
Portal Platform uses its own security domain (<emphasis
role="bold">gatein-domain</emphasis>) with a set of predefined login
modules. Login module configuration for <emphasis>gatein-domain</emphasis> is
contained in the
<filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/META-INF/gatein-jboss-beans.xml</filename>
file.
+From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss
Portal Platform uses its own security domain (<emphasis
role="bold">gatein-domain</emphasis>) with a set of predefined login
modules. Login module configuration for <emphasis>gatein-domain</emphasis> is
contained in the
<filename>JPP_HOME/gatein/gatein.ear/META-INF/gatein-jboss-beans.xml</filename>
file.
</para>
<para>
Below is the default login modules stack:
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/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 changed in
JPP6. I've made this change based on Marek's feedback. I've
also added this to the File Name Conventions section in the Preface.</remark>
<para>
- For ease of readability the following section uses the notational device
<replaceable>ID_HOME</replaceable> to represent the file path
<filename>JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/</filename>,
as this directory is the root of all JBoss Portal Platform's identity-related
configuration.
+ For ease of readability the following section uses the notational device
<replaceable>ID_HOME</replaceable> to represent the file path
<filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/</filename>,
as this directory is the root of all JBoss Portal Platform's identity-related
configuration.
</para>
</note>
<para>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2_Salesforce_and_Google_Integration.xml
===================================================================
(Binary files differ)
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2013-01-29
06:55:31 UTC (rev 9094)
@@ -384,10 +384,10 @@
<section id="sect-CAS_Portal_SSO_Primary_Configuration_File">
<title>Portal SSO Primary Configuration File</title>
<para>
- The main portal configuration file for SSO integration is
<code>JPP_SERVER/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.
+ The main portal configuration file for SSO integration is
<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
<filename>security-sso-configuration.xml</filename> directly when using JBoss
Portal Platform. The portal architecture allows users to override the base configuration
described in this file using name/value pairs configured in one place:
<filename>JPP_SERVER/standalone/configuration/gatein/configuration.properties</filename>
+ In most cases, it will never be necessary to edit
<filename>security-sso-configuration.xml</filename> directly when using JBoss
Portal Platform. The portal architecture allows users to override the base configuration
described in this file using name/value pairs configured in one place:
<filename>JPP_HOME/standalone/configuration/gatein/configuration.properties</filename>
</para>
<para>
The exception to this rule is where configuration present in
<filename>security-sso-configuration.xml</filename> is fundamentally
unsuitable 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/gatein/configuration.properties</filename>
and locate the SSO sections in the file.
</para>
</step>
<step>
@@ -449,7 +449,7 @@
<term>gatein.sso.login.module.enabled</term>
<listitem>
<para>
- Specifies whether a pre-defined SSO login module declared in
<filename> JPP_SERVER/standalone/configuration/standalone.xml</filename> is
used for authentication. When the property is set to "true", 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 delegate.
+ Specifies whether a pre-defined SSO login module declared in
<filename> JPP_HOME/standalone/configuration/standalone.xml</filename> is used
for authentication. When the property is set to "true", 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 delegate.
</para>
<para>
This parameter removes the need to manually change any login
module configuration in the standalone.xml file, which simplifies platform configuration.
@@ -1227,7 +1227,7 @@
<section
id="sect-Reference_Guide-SSO_Single_Sign_On_-OpenAM-SetuptheOpenAMclient">
<title>JBoss Portal Platform Setup as OpenAM Client</title>
<para>
- On the JBoss Portal Platform server, you need to ensure proper configuration of single
sign-on properties in the
<code>JPP_SERVER/standalone/configuration/gatein/configuration.properties</code>
file. Locate the SSO section in this file and change/add properties in the section as
follows:
+ On the JBoss Portal Platform server, you need to ensure proper configuration of single
sign-on properties in the
<code>JPP_HOME/standalone/configuration/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=true
@@ -1659,7 +1659,7 @@
<title>Configuring SPNEGO Integration with JBoss Portal
Platform</title>
<step>
<para>
- Modify the <literal># SSO</literal> section of the
<filename><replaceable>JPP_SERVER</replaceable>/standalone/configuration/gatein/configuration.properties</filename>
file, replacing the original content with the following properties:
+ Modify the <literal># SSO</literal> section of the
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/gatein/configuration.properties</filename>
file, replacing the original content with the following properties:
</para>
<programlisting>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/Authentication_Identity_SSO/default124.xml"
parse="text"/>
@@ -1703,7 +1703,7 @@
<term>gatein.sso.filter.login.sso.url</term>
<listitem>
<para>
- This value ensures that clicking the <guibutton>Sign
in</guibutton> link will redirect users to the
<literal>/portal/dologin</literal> URL, which is a secured URL declared in the
<filename>security-constraint section of
JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename> file, allowing
the <systemitem>GateInNegotiationAuthenticator</systemitem> valve to intercept
the HTTP request.
+ This value ensures that clicking the <guibutton>Sign
in</guibutton> link will redirect users to the
<literal>/portal/dologin</literal> URL, which is a secured URL declared in the
<filename>security-constraint section of
JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename> file, allowing the
<systemitem>GateInNegotiationAuthenticator</systemitem> 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>SSODelegateValve</systemitem>
is defined in the
<filename>JPP_SERVER/gatein/gatein.ear/portal.war/WEB-INF/jboss-web.xml</filename>
file and is used only if this option is set to <literal>true</literal>. The
purpose of the valve is to delegate the real work to another valve declared in the
<literal>gatein.sso.valve.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>SSODelegateValve</systemitem>
is defined in the
<filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/jboss-web.xml</filename>
file and is used only if this option is set to <literal>true</literal>. The
purpose of the valve is to delegate the real work to another valve declared in the
<literal>gatein.sso.valve.class</literal> property. This eliminates the need
to edit configuration in the <filename>jboss-web.xml</filename> file.
</para>
</listitem>
</varlistentry>
@@ -1737,7 +1737,7 @@
</step>
<step>
<para>
- Modify configuration of the
<systemitem>security</systemitem> subsystem in the
<filename><replaceable>JPP_SERVER</replaceable>/standalone/configuration/standalone.xml</filename>
file:
+ Modify configuration of the
<systemitem>security</systemitem> subsystem in the
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/standalone.xml</filename>
file:
</para>
<substeps>
<step>
@@ -1844,7 +1844,7 @@
As demonstrated in <xref
linkend="proc-Reference_Guide-JBoss_Enterprise_Portal_Platform_Configuration-SPNEGO_Testing"/>,
users trying to sign in without a valid Kerberos ticket are automatically redirected to
the JBoss Portal Platform logon page. There, they can perform standard FORM authentication
using their user name and password.
</para>
<para>
- If you want to disable FORM authentication to allow only users with a valid
Kerberos ticket to sign in, you need to comment out the
<parameter>usernamePasswordDomain</parameter> option in the
<literal>SPNEGOLoginModule</literal> configuration in the
<filename><replaceable>JPP_SERVER</replaceable>/standalone/configuration/standalone.xml</filename>
file.
+ If you want to disable FORM authentication to allow only users with a valid
Kerberos ticket to sign in, you need to comment out the
<parameter>usernamePasswordDomain</parameter> option in the
<literal>SPNEGOLoginModule</literal> configuration in the
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/standalone.xml</filename>
file.
</para>
<programlisting language="XML"><![CDATA[<login-module
code="org.gatein.sso.spnego.SPNEGOLoginModule"
flag="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> subsystem in the
<filename><replaceable>JPP_SERVER</replaceable>/standalone/configuration/standalone.xml</filename>
file:
+ To enable logging of events related to SPNEGO authentication, you can add the
following entries to the <systemitem>logging</systemitem> subsystem in the
<filename><replaceable>JPP_HOME</replaceable>/standalone/configuration/standalone.xml</filename>
file:
</para>
<programlisting language="XML"><![CDATA[<logger
category="org.gatein.sso">
<level name="TRACE"/>
@@ -1893,7 +1893,7 @@
<section
id="sect-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve-Default_Config">
<title>Default Configuration</title>
<para>
- The JBoss SSO valve is enabled by default. The enablement is ensured by
the following JBoss Web subsystem configuration entry in the
<filename>JPP_SERVER/standalone/configuration/standalon-ha.xml</filename>
file:
+ The JBoss SSO valve is enabled by default. The enablement is ensured by
the following JBoss Web subsystem configuration entry in the
<filename>JPP_HOME/standalone/configuration/standalon-ha.xml</filename> file:
</para>
<programlisting language="XML"><![CDATA[
<sso cache-container="web" cache-name="sso"
reauthenticate="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 value.
+ On both servers, open the
<filename><replaceable>JPP_HOME</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 value.
</para>
<programlisting language="XML"><![CDATA[
<sso cache-container="web" cache-name="sso"
reauthenticate="false" domain="yourdomain.com"/>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/Introduction.xml 2013-01-29
06:55:31 UTC (rev 9094)
@@ -1,27 +1,96 @@
<?xml version='1.0' encoding='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="chap-Reference_Guide-Introduction">
<title>Introduction</title>
<para>
-JBoss Portal Platform is based on the GateIn project, which is the merge of two mature
Java projects: JBoss Portal and eXo Portal. This new community project takes the best of
both offerings and incorporates them into a single portal framework. The aim is to provide
an intuitive user-friendly portal, and a framework to address the needs of
today's Web 2.0 applications.
+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's
Web 2.0 applications.
</para>
-<figure>
-<title id="Frontpage">Front Page</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center" scale="100"
fileref="images/Common/Frontpage.png" format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="150mm"
align="center" fileref="images/Common/Frontpage.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ <figure>
+ <title id="Frontpage">Front Page</title>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata width="666"
fileref="images/Common/JPP_Front_Page.png" format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>
- This book provides a deep-dive information about installation and configuration of the
services provided by JBoss Portal Platform.
+ This book provides deep-dive information about installation and configuration of the
services provided by JBoss Portal Platform.
</para>
+ <section id="sect-File_Name_Conventions">
+ <title>File Name Conventions</title>
+ <para>The following naming conventions are used in file paths to improve their
readability. Each convention is styled so that it stands out from the rest of the text:
+ </para>
+ <variablelist id="vari-Reference_Guide-Introduction-Devices">
+ <varlistentry>
+ <term>
+ <replaceable>CAS_DIR</replaceable>
+ </term>
+ <listitem>
+ <para>
+ The installation root of the Central Authentication Service (CAS) single 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="sect-SSO_Single_Sign_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/organization/</filename>
directory, which contains identity-related configuration resources.
+ </para>
+ <para>
+ This convention is mainly used in <xref
linkend="chap-LDAP_Integration"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <replaceable>JPP_DIST</replaceable>
+ </term>
+ <listitem>
+ <para>
+ The installation root of the JBoss Portal Platform instance. For example, 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>,
<filename>gatein-management</filename> and
<filename>gatein-sso</filename> directories, and is used extensively in
sections that contain configuration stored 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
contains the application server and the configuration files necessary to run JBoss Portal
Platform.
+ </para>
+ <para>
+ This directory contains the <filename>gatein</filename>,
<filename>modules</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 examples in this guide to host
single sign-on authentication services.
+ </para>
+ <para>
+ This convention is mainly used in <xref
linkend="sect-Reference_Guide-SSO_Single_Sign_On"/>.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
<section id="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="bold">Installation Guide</emphasis>, and a <emphasis
role="bold">User Guide</emphasis> can be found at <ulink
url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platfo...
type="http">www.redhat.com/docs</ulink>
+Technical documentation, including an <emphasis role="bold">Installation
Guide</emphasis>, and a <emphasis role="bold">User
Guide</emphasis> can be found at <ulink
url="https://access.redhat.com/knowledge/docs/JBoss_Portal_Platform/...
type="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 the portal:
- </para>
-<figure>
-<title id="nontechdocs">Non-technical documentation</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center"
scale="90" fileref="images/Common/Non-tech-docs.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="130mm"
align="center" fileref="images/Common/Non-tech-docs.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ Links to non-technical documents are available by clicking "Portals the
Red Hat way", or "Launch fast with Maven Quick Starts".
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Videos</term>
<listitem>
<para>
- A link to <ulink url="http://vimeo.com/channels/gatein"
type="http">videos</ulink> related to the JBoss Portal Platform is also
included on the front page:
- </para>
-<figure>
-<title id="videos">Videos</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center"
scale="90" fileref="images/Common/Videos.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="130mm"
align="center" fileref="images/Common/Videos.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ A link to <ulink url="http://vimeo.com/channels/gatein"
type="http">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 team members
using development versions of JBoss Portal Platform, and therefore should be used only as
reference examples when configuring your production system. </para>
</listitem>
</varlistentry>
</variablelist>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.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="sect-Reference_Guide-Default_Portal_Configuration-Disabling_a_Portal_Container">
- <title><remark>BZ#794416</remark>Disabling a Portal
Container</title>
- <para>
+ --> <section
id="sect-Reference_Guide-Default_Portal_Configuration-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 your needs, you
may wish to disable a portal container that is no longer required.
</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 Platform
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="XML"
role="XML"><![CDATA[<?xml version="1.0"
encoding="UTF-8"?>
-<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_0.xsd
http://www.exoplaform.org/xml/ns/kernel_1_1.xsd"
- xmlns="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.PortalContainerConfig
- </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 PortalContainerConfig in order
to register the changes on the PortalContainerDefinitions -->
- <set-method>registerDisablePlugin</set-method>
- <!-- The full qualified name of the PortalContainerDefinitionDisablePlugin
-->
-
<type>org.exoplatform.container.definition.PortalContainerDefinitionDisablePlugin</type>
- <init-params>
- <!-- The list of the name of the portal containers to disable -->
- <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 <values-param>
directive will no longer be available at http://{hostname}:{port}/portal</para>
- </step>
- </procedure>
- <taskrelated>
- <note>
- <title/>
- <para>
+ <programlisting language="XML"><!-- Comment 1
-->
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_0.xsd
http://www.exoplaform.org/xml/ns/kernel_1_1.xsd"
+ xmlns="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.PortalContainerConfig
+ </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 PortalContainerConfig in
order to register the changes on the PortalContainerDefinitions -->
+ <set-method>registerDisablePlugin</set-method>
+ <!-- The full qualified name of the
PortalContainerDefinitionDisablePlugin -->
+
<type>org.exoplatform.container.definition.PortalContainerDefinitionDisablePlugin</type>
+ <init-params>
+ <!-- The list of the name of the portal containers to disable
-->
+ <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 <values-param>
directive will no longer be available at
<literal>http://{hostname}:{port}/portal</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 Services 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/PortalDevelopment/JavascriptInterApplicationCommunication.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml 2013-01-29
06:55:31 UTC (rev 9094)
@@ -56,7 +56,7 @@
<section
id="sect-Reference_Guide-JavaScript_Inter_Application_Communication-Library">
<title>Library</title>
<para>
- The Inter Application Communication library is found in
<filename>01eXoResources.war:/javascript/eXo/core/Topic.js</filename>
+ The Inter Application Communication library is found in
<filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/javascript/eXo/core/Topic.js</filename>
</para>
<programlisting language="Java" role="Java"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_JavascriptInterApplicationCommunication/default155.java"
parse="text"/></programlisting>
</section>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-01-29
04:31:05 UTC (rev 9093)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-01-29
06:55:31 UTC (rev 9094)
@@ -153,7 +153,7 @@
<section
id="sect-Reference_Guide-The_Skin_Service-Resource_Request_Filter">
<title>Resource Request Filter</title>
<para>
- Because of JBoss Portal Platform's Right-To-Left support, 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 already done for
<literal>01eXoResources.war</literal> web application which contains the
default skin.
+ Because of JBoss Portal Platform's Right-To-Left support, 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 already 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="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 with 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="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default186.xml"
parse="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-resources.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 updated with your new portal
skin preview.
</para>
-
-<figure>
-<title id="portal-change-skin">Portal_Skin_Change</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center"
scale="100"
fileref="images/PortalDevelopment/Skinning/portal-change-skin.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="150mm"
align="center"
fileref="images/PortalDevelopment/Skinning/portal-change-skin.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ <figure>
+ <title
id="portal-change-skin">Portal_Skin_Change</title>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata width="444" align="center"
scale="100"
fileref="images/PortalDevelopment/Skinning/portal-change-skin.png"
format="PNG"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata width="444" contentwidth="150mm"
align="center"
fileref="images/PortalDevelopment/Skinning/portal-change-skin.png"
format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<para>
The portal skin preview icon is specified through the CSS of the portal
skin. In order for the current portal skin to be able to display the preview it must
specify a specific CSS class and set the icon as the background.
</para>
@@ -264,10 +263,10 @@
</para>
<programlisting language="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default187.xml"
parse="text"/></programlisting>
<para>
- In order for the default skin to display the skin icon for a new portal
skin, the preview screen shot needs to be placed in:
<filename>01eXoResources.war:/skin/DefaultSkin/portal/webui/component/customization/UIChangeSkinForm/background</filename>.
+ In order for the default skin to display the skin icon for a new portal
skin, the preview screen shot needs to be placed in:
<filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/portal/webui/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
<literal>MySkin</literal>, the following needs to be updated:
<filename>01eXoResources.war:/skin/DefaultSkin/portal/webui/component/customization/UIChangeSkinForm/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
<literal>MySkin</literal>, the following needs to be updated:
<filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/skin/DefaultSkin/portal/webui/component/customization/UIChangeSkinForm/Stylesheet.css</filename>.
</para>
<programlisting language="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default188.xml"
parse="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 window when they add a new
application or gadget to a page.
</para>
-<figure>
-<title id="windowStyles">Window Styles</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata width="444" align="center"
scale="100"
fileref="images/PortalDevelopment/Skinning/windowStyles.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="444" contentwidth="150mm"
align="center"
fileref="images/PortalDevelopment/Skinning/windowStyles.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ <figure>
+ <title id="windowStyles">Window Styles</title>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata width="444" align="center"
scale="100"
fileref="images/PortalDevelopment/Skinning/windowStyles.png"
format="PNG"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata width="444" contentwidth="150mm"
align="center"
fileref="images/PortalDevelopment/Skinning/windowStyles.png"
format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<section
id="sect-Reference_Guide-Creating_a_New_Window_Style-Window_Style_Configuration">
<title>Window Style Configuration</title>
<para>
@@ -298,7 +297,7 @@
</para>
<programlisting language="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default189.xml"
parse="text"/></programlisting>
<para>
- The windows style configuration for the default skin is configured in:
<filename>01eXoResources.war/WEB-INF/gatein-resources.xml</filename>.
+ The windows style configuration for the default skin is configured in:
<filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/WEB-INF/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 decorators, it must
have CSS classes specifically named in relation to the window style name. The service will
try and display CSS based on this naming convention. 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/PortletThemes/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/eXoResources.war/skin/PortletThemes/Stylesheet.css</filename>.
</para>
<para/>
<para>
@@ -521,7 +520,7 @@
The portlet specification defines a set of default CSS classes that should
be available for portlets. These classes are included as part of the portal skin. Please
see the portlet specification for a list of the 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/Stylesheet.css</filename>.
+ For the default portal skin, the portlet specification CSS classes are
defined in:
<filename>JPP_HOME/gatein/gatein.ear/eXoResources.war/skin/Portlet/Stylesheet.css</filename>.
</para>
</section>
</section>
@@ -561,14 +560,14 @@
<para>
The decorator is a pattern to create a contour or a curve around an
area. In order to achieve this effect you need to create nine cells. The
<literal>BODY</literal> is the central area that you want to decorate. The
other eight cells are distributed around the <literal>BODY</literal> cell. You
can use the width, height and background image properties to achieve any decoration effect
that you want.
</para>
-<figure>
-<title id="decoratorPattern">Decorator Pattern</title>
- <mediaobject>
- <imageobject>
- <imagedata width="418"
fileref="images/PortalDevelopment/Skinning/decoratorPattern.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ <figure>
+ <title id="decoratorPattern">Decorator Pattern</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata width="418"
fileref="images/PortalDevelopment/Skinning/decoratorPattern.png"
format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<programlisting language="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default193.xml"
parse="text"/></programlisting>
</section>
<section
id="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 blocks side by
side. The left block will have a fixed size and the right block will take the rest of the
available space. When the user resizes the browser the added or removed space will be
taken from the right block.
</para>
-<figure>
-<title id="leftMarginPattern">Left Margin Pattern</title>
- <mediaobject>
- <imageobject role="html">
- <imagedata align="center"
fileref="images/PortalDevelopment/Skinning/leftMarginPattern.png"
format="PNG"/>
- </imageobject>
- <imageobject role="fo">
- <imagedata width="100mm" align="center"
fileref="images/PortalDevelopment/Skinning/leftMarginPattern.png"
format="PNG"/>
- </imageobject>
- </mediaobject>
-</figure>
+ <figure>
+ <title id="leftMarginPattern">Left Margin
Pattern</title>
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata align="center"
fileref="images/PortalDevelopment/Skinning/leftMarginPattern.png"
format="PNG"/>
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata width="100mm" align="center"
fileref="images/PortalDevelopment/Skinning/leftMarginPattern.png"
format="PNG"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
<programlisting language="XML"
role="XML"><xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="../../extras/PortalDevelopment_Skinning/default194.xml"
parse="text"/></programlisting>
</section>
</section>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/ServerIntegration.xml
===================================================================
(Binary files differ)
Modified: epp/docs/branches/6.0/Reference_Guide/publican.cfg
===================================================================
--- 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