From do-not-reply at jboss.org Wed Mar 31 20:33:28 2010
Content-Type: multipart/mixed; boundary="===============7867804507576777754=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2425 -
portal/trunk/docs/reference-guide/en/modules.
Date: Wed, 31 Mar 2010 20:33:28 -0400
Message-ID: <201004010033.o310XSYR004106@svn01.web.mwc.hst.phx2.redhat.com>
--===============7867804507576777754==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 20:33:28 -0400 (Wed, 31 Mar 2010)
New Revision: 2425
Modified:
portal/trunk/docs/reference-guide/en/modules/WSRP.xml
Log:
update for Hudson build
Modified: portal/trunk/docs/reference-guide/en/modules/WSRP.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
--- portal/trunk/docs/reference-guide/en/modules/WSRP.xml 2010-03-31 20:41:=
25 UTC (rev 2424)
+++ portal/trunk/docs/reference-guide/en/modules/WSRP.xml 2010-04-01 00:33:=
28 UTC (rev 2425)
@@ -5,8 +5,13 @@
]>
Web Services for Remote Portlets (WSRP)
-
-
+
+ Commented WSRP section out - not ready and breaking Publican builds.
+
+
+ Will re-include once completed.
+
+
-
+
+
+ Was commented out
+
+ we need to use the individual endpoint configuration because the configu=
ration via
+ wsdl forces an immediate attempt to access the web service descr=
iption which is not
+ available yet at this point of deployment
+
+
+
+
http://localhost:8080/portal-wsrp/ServiceDescriptionService
@@ -1094,5 +1104,5 @@
=
-
-
\ No newline at end of file
+ -->
+
--===============7867804507576777754==--
From do-not-reply at jboss.org Wed Mar 31 20:48:50 2010
Content-Type: multipart/mixed; boundary="===============8853426088691746607=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2426 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US.
Date: Wed, 31 Mar 2010 20:48:50 -0400
Message-ID: <201004010048.o310mobB005609@svn01.web.mwc.hst.phx2.redhat.com>
--===============8853426088691746607==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 20:48:49 -0400 (Wed, 31 Mar 2010)
New Revision: 2426
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/Author_Group.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/Book_Info.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/Reference_Guide.ent
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/Reference_Guide.xml
Log:
Updating for Husdson build
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/Author_Group.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Author_Group.xml 2010-04-01 00:33:28 UTC (rev 2425)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Author_Group.xml 2010-04-01 00:48:49 UTC (rev 2426)
@@ -5,22 +5,13 @@
]>
- Scott
- Mumford
-
- Red Hat
- Engineering Content Services
-
- smumford(a)redhat.com
-
- LucTexierRed HatJBoss Engineering
- theute(a)redhat.com
+ ltexier(a)redhat.comThomas
@@ -31,6 +22,15 @@
theute(a)redhat.com
+
+ Scott
+ Mumford
+
+ Red Hat
+ Engineering Content Services
+
+ smumford(a)redhat.com
+ GateIn and <=
ulink type=3D"http" url=3D"http://www.exoplatform.com/portal/public/website=
/">Exo Platform
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/Book_Info.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Book_Info.xml 2010-04-01 00:33:28 UTC (rev 2425)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Book_Info.xml 2010-04-01 00:48:49 UTC (rev 2426)
@@ -6,8 +6,8 @@
Reference GuideAn in-depth guide to Enterprise Portal Platform 5.0
- Enterprise Portal Platform
- 5.0
+ &PRODUCT;
+ &VERSION;11.0
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/Reference_Guide.ent
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Reference_Guide.ent 2010-04-01 00:33:28 UTC (rev 2425)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Reference_Guide.ent 2010-04-01 00:48:49 UTC (rev 2426)
@@ -1,5 +1,7 @@
-
+
+
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Reference_Guide.xml 2010-04-01 00:33:28 UTC (rev 2425)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/Reference_Guide.xml 2010-04-01 00:48:49 UTC (rev 2426)
@@ -3,7 +3,7 @@
%BOOK_ENTITIES;
]>
-
+
@@ -14,7 +14,7 @@
-
+ =
--===============8853426088691746607==--
From do-not-reply at jboss.org Wed Mar 31 21:11:52 2010
Content-Type: multipart/mixed; boundary="===============8598015890584666577=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2427 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_User_Guide.
Date: Wed, 31 Mar 2010 21:11:52 -0400
Message-ID: <201004010111.o311Bq42014568@svn01.web.mwc.hst.phx2.redhat.com>
--===============8598015890584666577==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 21:11:51 -0400 (Wed, 31 Mar 2010)
New Revision: 2427
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_User_Gu=
ide/publican.cfg
Log:
Updating Hudson branding
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
User_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_User_G=
uide/publican.cfg 2010-04-01 00:48:49 UTC (rev 2426)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_User_G=
uide/publican.cfg 2010-04-01 01:11:51 UTC (rev 2427)
@@ -3,7 +3,7 @@
=
xml_lang: en-US
type: Book
-brand: RedHat
+brand: JBoss
#chunk_section_depth: 1
chunk_first: 1
debug:1
--===============8598015890584666577==--
From do-not-reply at jboss.org Wed Mar 31 21:12:22 2010
Content-Type: multipart/mixed; boundary="===============4036689694820802657=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2428 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide.
Date: Wed, 31 Mar 2010 21:12:22 -0400
Message-ID: <201004010112.o311CMBQ014579@svn01.web.mwc.hst.phx2.redhat.com>
--===============4036689694820802657==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 21:12:22 -0400 (Wed, 31 Mar 2010)
New Revision: 2428
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/publican.cfg
Log:
Updating Hudson branding
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/publican.cfg 2010-04-01 01:11:51 UTC (rev 2427)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/publican.cfg 2010-04-01 01:12:22 UTC (rev 2428)
@@ -3,6 +3,6 @@
=
xml_lang: en-US
type: Book
-brand: RedHat
+brand: JBoss
debug:1
=
--===============4036689694820802657==--
From do-not-reply at jboss.org Wed Mar 31 21:35:58 2010
Content-Type: multipart/mixed; boundary="===============3327277937655061207=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2429 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release_Notes.
Date: Wed, 31 Mar 2010 21:35:58 -0400
Message-ID: <201004010135.o311Zwfh017647@svn01.web.mwc.hst.phx2.redhat.com>
--===============3327277937655061207==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 21:35:58 -0400 (Wed, 31 Mar 2010)
New Revision: 2429
Removed:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Release=
_Notes/ReleaseNotes-Notes.txt
Log:
cleaning up
Deleted: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_R=
elease_Notes/ReleaseNotes-Notes.txt
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Releas=
e_Notes/ReleaseNotes-Notes.txt 2010-04-01 01:12:22 UTC (rev 2428)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Releas=
e_Notes/ReleaseNotes-Notes.txt 2010-04-01 01:35:58 UTC (rev 2429)
@@ -1,10 +0,0 @@
-Release_Notes Notes
-
-
-Commit 19/03/10
-
-- Added placeholder image to Section 2 (Thomas to update as indicated in e=
mail)
-- Removed component sub-sections and replaced with Certified Variables (EP=
P_016, EPP_017, EPP_018, EPP_022 from PRD)
-- Commented Source RPMs section (uneccessary)
-- Commented Decumentation section (it doesn't make sense to have live docs=
that are yet to go to staging)
-- Commented Component description section, left placeholders (Martin sugge=
sted he might want something here)
--===============3327277937655061207==--
From do-not-reply at jboss.org Wed Mar 31 23:17:19 2010
Content-Type: multipart/mixed; boundary="===============7349819449711242769=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2430 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide/en-US.
Date: Wed, 31 Mar 2010 23:17:18 -0400
Message-ID: <201004010317.o313HIoS009059@svn01.web.mwc.hst.phx2.redhat.com>
--===============7349819449711242769==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 23:17:18 -0400 (Wed, 31 Mar 2010)
New Revision: 2430
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Book_Info.xml
Log:
fixed filename error preventing build
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Installation_Guide/en-US/Book_Info.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Book_Info.xml 2010-04-01 01:35:58 UTC (rev 2429)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Book_Info.xml 2010-04-01 03:17:18 UTC (rev 2430)
@@ -2,7 +2,7 @@
- Intallation Guide
+ Installation Guidefor Use with JBoss Enterprise Portal Platform 5.0 Beta
1.01
--===============7349819449711242769==--
From do-not-reply at jboss.org Wed Mar 31 23:59:45 2010
Content-Type: multipart/mixed; boundary="===============4712028926873636217=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2431 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide.
Date: Wed, 31 Mar 2010 23:59:45 -0400
Message-ID: <201004010359.o313xjQ8014247@svn01.web.mwc.hst.phx2.redhat.com>
--===============4712028926873636217==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-03-31 23:59:44 -0400 (Wed, 31 Mar 2010)
New Revision: 2431
Removed:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/pom.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/publican.cfg
Log:
removing to add draft installation guide
Deleted: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_I=
nstallation_Guide/pom.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/pom.xml 2010-04-01 03:17:18 UTC (rev 2430)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/pom.xml 2010-04-01 03:59:44 UTC (rev 2431)
@@ -1,216 +0,0 @@
-
- =
- 4.0.0
- org.jboss.project
- ${docname}-${translation}
- 1.0
- jdocbook
- ${bookname}-(${translation})
-
-
- en-US
- Installation_Guide
- Installation Guide
- =
-
-
-
- repository.jboss.org
- JBoss Repository
- default
- http://repository.jboss.org/maven2/
-
- false
-
-
-
-
-
- repository.jboss.org
- JBoss Repository
- default
- http://repository.jboss.org/maven2/
-
- false
-
-
-
- =
- =
-
-
-
-
- all
-
- true
-
-
-
-
- org.jboss.maven.plugins
- maven-jdocbook-plugin
- 2.2.1
- true
-
-
-
- pdf
- classpath:/xslt/org/jboss/pdf.xsl
- ${docname}.pdf
-
-
- html
- classpath:/xslt/org/jboss/xhtml.xsl
- index.html
-
-
- html_single
- classpath:/xslt/org/jboss/xhtml-single.xs=
l
- index.html
-
-
-
-
-
-
-
-
-
-
- html
-
- false
-
-
-
-
- org.jboss.maven.plugins
- maven-jdocbook-plugin
- 2.2.1
- true
-
-
-
- html
- classpath:/xslt/org/jboss/xhtml.xsl
- index.html
-
-
-
-
-
-
-
-
-
-
- html-single
-
- false
-
-
-
-
- org.jboss.maven.plugins
- maven-jdocbook-plugin
- 2.2.1
- true
-
-
-
- html_single
- classpath:/xslt/org/jboss/xhtml-single.xs=
l
- index.html
-
-
-
-
-
-
-
-
-
-
- pdf
-
- false
-
-
-
-
- org.jboss.maven.plugins
- maven-jdocbook-plugin
- 2.2.0
- true
-
-
-
- pdf
- classpath:/xslt/org/jboss/pdf.xsl
- ${docname}.pdf
-
-
-
-
-
-
-
-
-
-
-
-
-
- org.jboss.maven.plugins
- maven-jdocbook-plugin
- 2.2.0
- true
-
-
- org.jboss
- jbossorg-docbook-xslt
- 1.1.0
-
-
- org.jboss
- jbossorg-jdocbook-style
- 1.1.0
- jdocbook-style
-
-
-
- ${docname}.xml
- .
-
- ${translation}
-
- images/*
-
-
-
- true
- saxon
-
-
- 1.72.0
-
-
- javax.xml.parsers.DocumentBuilderFactory
- org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-
-
- javax.xml.parsers.SAXParserFactory
- org.apache.xerces.jaxp.SAXParserFactoryImpl
-
-
-
-
-
- =
-
-
-
-
Deleted: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_I=
nstallation_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/publican.cfg 2010-04-01 03:17:18 UTC (rev 2430)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/publican.cfg 2010-04-01 03:59:44 UTC (rev 2431)
@@ -1,7 +0,0 @@
-# Config::Simple 4.59
-# Thu Mar 18 09:14:12 2010
-
-debug: 1
-xml_lang: en-US
-brand: JBoss
-
--===============4712028926873636217==--
From do-not-reply at jboss.org Thu Apr 1 00:03:14 2010
Content-Type: multipart/mixed; boundary="===============2989166107353948465=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2432 - in
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Installation_Guide:
en-US and 2 other directories.
Date: Thu, 01 Apr 2010 00:03:14 -0400
Message-ID: <201004010403.o3143Ea1015063@svn01.web.mwc.hst.phx2.redhat.com>
--===============2989166107353948465==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-04-01 00:03:11 -0400 (Thu, 01 Apr 2010)
New Revision: 2432
Added:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Accessing.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Author_Group.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Book_Info.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Configuration.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Databases.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Getting_Started.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Installation.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Installation_Guide.ent
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Installation_Guide.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Introduction.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Launching.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Post_Installation.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Preface.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Revision_History.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Test_Your_Installation.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/Uninstall_JBoss.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/Conventions.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/Feedback.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/Legal_Notice.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/book_ent
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/1.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/1.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/10.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/10.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/11.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/11.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/12.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/12.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/13.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/13.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/14.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/14.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/15.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/15.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/16.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/16.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/17.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/17.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/18.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/18.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/19.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/19.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/2.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/2.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/20.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/20.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/21.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/21.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/22.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/22.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/23.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/23.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/3.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/3.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/4.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/4.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/5.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/5.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/6.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/6.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/7.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/7.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/8.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/8.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/9.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/9.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/dot.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/dot2.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/h1-bg.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/image_left.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/image_right.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/important.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/important.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/note.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/note.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/shine.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/stock-go-back.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/stock-go-forward.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/stock-go-up.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/stock-home.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/title_logo.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/title_logo.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/warning.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/warning.svg
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/fallback_content/images/watermark-draft.png
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/en-US/images/
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/pom.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Install=
ation_Guide/publican.cfg
Log:
draft install guide
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Accessing.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Accessing.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Accessing.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,22 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+
+]>
+
+ Accessing &PRODUCT;
+
+ Browser URL
+
+ The URL to a locally installed instance of &PRODUCT; is
+
+
+ This URL will take users to the front page of &PRODUCT; where they can =
log in and begin to undertake actions within the portal itself.
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Author_Group.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Author_Group.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Author_Group.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,36 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+]>
+
+
+ Scott
+ Mumford
+
+ Red Hat
+ Engineering Content Services
+
+ smumford(a)redhat.com
+
+
+ Thomas
+ Heute
+
+ Red Hat
+ JBoss Services R&D
+
+ theute(a)redhat.com
+
+
+
+ GateIn and <=
ulink type=3D"http" url=3D"http://www.exoplatform.com/portal/public/website=
/">Exo Platform
+ Documentation Teams
+
+ Original product documentation by:
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Author_Group.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Book_Info.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Book_Info.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Book_Info.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,42 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+
+]>
+
+ Installation Guide
+ An Installation Guide for &PRODUCT;
+ &PRODUCT;
+ &VERSION;
+ 1
+ 0
+
+
+This book provides information about obtaining, installing and
+running &PRODUCT;. It forms part of the complete document suite
+along with the &PRODUCT; User Guide and the &PRODUCT; Reference
+Guide available at .
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Book_Info.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Configuration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Configuration.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Configuration.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,64 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Database Configuration
+
+
+ Installing an RDBMS JDBC connector
+
+ A relational database management system (RDBMS) Java Database Connectiv=
ity (JDBC) connector is required for &PRODUCT; to communicate with a databa=
se.
+ &PRODUCT; comes bundled with Hypersonic SQL (HSQL) database so that use=
rs can get started up and running quickly without having to setup =
+ database initially. However, HSQL should not be used in production en=
vironment. Removing HSQL is simply a matter of removing =
+ JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql-ds.xm=
l. Test suites have been run against =
+ the Oracle 9, Oracle 10, Microsoft SQL Server, =
+ MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are re=
commended for production use. Please refer to your database documentation f=
or the correct =
+ RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloade=
d from , =
and the
+ PostgreSQL RDBMS JDBC connector can be downloaded from .
+
+
+ Refer to the help files in each download for installation instructions.=
In most cases, the RDBMS JDBC connector comes as a .jar file. Copy this file into the $JBOSS_HOME/server/<=
replaceable>configuration/lib/ directory.
+
+
+ =
+
+ Datasource Descriptors
+
+ A Datasource descriptor is required for JBoss Portal to communicate wit=
h a database. Sample Datasource descriptor files are provided for the Hyper=
sonic SQL, Microsoft SQL Server=
, MySQL, Oracle, and PostgreSQL=
databases. These can be found in the /jboss-as/docs/portal/setup=
/ subdirectory where the EPP x.x.x<=
/replaceable> binary distribution file was extracted to. F=
or example, if EPP was extracted into the /jboss/ dire=
ctory, the sample Datasource descriptors would be in the /jboss/j=
boss-epp-x.x.x/jboss-as/docs/portal/setup directory.
+
+
+ The sample Datasource descriptors will work with default installations =
of external databases; however, you may need to configure the correct usern=
ame and password. As well, the sample MySQL and PostgreSQL Datasource descr=
iptors assume the name of the database to be jbossportal.
+
+
+ When copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the &l=
t;user-name>portal</user-name> and <password>portalpassword</password> sections to reflect the corre=
ct username and password for the user who has access to the jbossportal dat=
abase.
+
+
+ Different Datasource Descriptors
+
+ Only have one Datasource descriptor in the $JBOSS_HOME/serve=
r/configuration/deploy/ directory. Fo=
r example, if you want to use a MySQL database, remove the portal=
-hsqldb-ds.xml file, and other descriptors, if they exists.
+
+
+
+ The following is an example Datasource descriptor file for MySQL 5:
+
+
+
+<?xml version=3D"1.0" encoding=3D"UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>PortalDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/jbossportal?
+ useServerPrepStmts=3Dfalse&;jdbcCompliantTruncation=3Dfalse=
</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name><replaceable>portal</replaceable></user=
-name>
+ <password><replaceable>portalpassword</replaceable>&l=
t;/password> =
+ </local-tx-datasource>
+</datasources>
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Databases.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Databases.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Databases.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,175 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Databases
+
+ The following chapter contains examples for how to use
+ MySQL databases to store JBoss Enterprise Portal user information.
+
+ =
+
+ Using a MySQL Database
+
+ Installing the MySQL RDBMS JDBC connector
+
+ The RDBMS JDBC MySQL connector is required for JBoss Portal to use a =
MySQL database:
+
+
+
+
+
+ Navigate to the JDBC MySQL connector section of dev.mysql.com. Downlo=
ad the Source and Binaries (zip) file.
+
+
+
+
+ Unzip the mysql-java-connector into the desired =
directory. It does not matter which directory is used.
+
+
+
+
+ Change into the directory where the mysql-java-connector was extracted to. Copy the mysql-connector-java-version-number-bin.jar file into the $JBOSS_HOME/server/configuration/lib/ directory.
+
+
+
+
+ Data Truncation Errors
+
+ If you are running MySQL 5, data truncation errors such as the followi=
ng may occur:
+
+
+
+
+ERROR JDBCExceptionReporter Data truncation: Data too long for column '=
;jbp_viewrealemail' at row 1
+
+
+
+ If you are running MySQL in strict mode, remove STRICT_=
TRANS_TABLES from the sql-mode=3D line, in the my.cnf file if you are running L=
inux, and from the my.cfg file if you are running Windows. For further information, p=
lease see .
+
+
+ Creating a MySQL Database
+
+ If you have just installed MySQL, make sure the MySQL server is runnin=
g, and then run the following command to set the root user password:
+
+
+
+
+mysqladmin -u root password 'new-root-user-password'
+
+
+
+
+
+ Run the following command to log in to MySQL. Enter the root user pas=
sword when prompted:
+
+
+
+mysql -u root -p
+
+
+
+
+
+ Use the CREATE DATABASE command to create a new jb=
ossportal database. Note: the rest of this guide, and configuration example=
s following here after, assume the database name to be jbossportal. If you =
change the database name, please change the name in all necessary configura=
tion files:
+
+
+
+mysql> CREATE DATABASE jbossportal;
+
+
+
+ The output should be similar to the following:
+
+
+
+Query OK, 1 row affected (0.00 sec)
+
+
+
+ At this point, the SHOW DATABASES; command should =
display the jbossportal database:
+
+
+
+mysql> SHOW DATABASES;
++--------------------+
+| Database |
++--------------------+
+| information_schema | =
+| jbossportal | =
+| mysql | =
++--------------------+
+3 rows in set (0.00 sec)
+
+
+
+ It is safe to ignore the other databases.
+
+
+
+
+ Add a new user and give that user access to the jbossportal database.=
The following example adds a new user named portal, with the password portalpassword, and gives the portal user access to the jbossportal database. It is reco=
mmended that you change the password. Change portalpassword to change the password:
+
+
+
+mysql> GRANT ALL PRIVILEGES ON jbossportal.* TO 'porta=
l'@'localhost' =
+IDENTIFIED BY 'portalpassword' WITH GRA=
NT OPTION;
+
+
+
+ The output should be similar to the following:
+
+
+
+Query OK, 0 rows affected (0.00 sec)
+
+
+
+ If you changed the portal user's password, also change the passwo=
rd in the MySQL Datasource descriptor.
+
+
+
+
+ MySQL Datasource Descriptor
+
+ To install the MySQL Datasource descriptor:
+
+
+
+
+
+ Change into the setup subdirectory where JBoss P=
ortal was extracted to. Copy the MySQL Datasource descriptor into the $JBOSS_HOME/server/configuration/deploy/ directory. If you are running MySQL 5, use portal-mysql5=
-ds.xml, otherwise use portal-mysql-ds.xml.
+
+
+
+
+ Update the <user-name>portal</user-name> and <passwor=
d>portalpassword</password> sections in the Datasource descriptor to reflect the correct username=
and password for the user who has access to the jbossportal database.
+
+
+
+
+ MySQL Table Errors
+
+ Tables are set up automatically when JBoss Portal first starts. Initia=
lly, two users will be stored in the jbossportal MySQL database: a standard=
user with the username user, and the password user, and an administrative =
user with the username admin, and the password admin. Since the database ta=
bles are created during initial startup, errors such as the following may o=
ccur, but are safe to ignore:
+
+
+
+
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_repositoryent=
ry' doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_version_refs&=
#39; doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_wsp_node'=
doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_cmsentry'=
doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Getting_Started.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Getting_Started.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Getting_Started.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,596 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Getting Started
+
+ Pre-Requisites
+
+ You must have adequate disk space to install JDK a=
nd &PRODUCT; while also allowing enough space for your applications. Before=
installing &PRODUCT; you must have a working installation of Java. Since J=
Boss is 100% pure Java you can have it working on any Operating System / Pl=
atform that supports Java. However, there are a few Operating System-specif=
ic issues that you should be aware of. Refer to for more information.
+
+
+ Hardware and Operating System Requirements
+ =
+ For the latest information on supported Operating System / JVM co=
mbinations and supported Database platforms, please refer to h=
ttp://www.jboss.com/products/platforms/application/testedconfigurations.
+
+
+
+ =
+
+ Configuring Your Java Environment
+
+ You must have a working installation of JDK 1.=
5 before you install &PRODUCT;. You can install the 32-bit or 64=
-bit JVM as per your requirements. In this guide we will show you how to in=
stall a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Micro=
soft Windows Platform. But before we do that let's take a look at some of t=
he benefits of using a 64-bit JVM.
+
+ Benefits of 64-bit JVM on 64-bit OS and Hardware:
+
+
+ Wider datapath: The pipe between RAM and CPU is doubled, which impr=
oves the performance of memory-bound applications.
+
+
+
+
+ 64-bit memory addressing gives virtually unlimited (1 exabyte) heap=
allocation. However large heaps affect garbage collection.
+
+
+
+
+ Applications that run with more than 1.5GB of RAM (including free s=
pace for garbage collection optimization) should utilize the 64-bit JVM.
+
+
+
+
+ Applications that run on a 32-bit JVM and do not require more than =
minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issu=
es, 64-bit hardware with the same relative clock speed and architecture is =
not likely to run Java applications faster than their 32-bit cousin.
+
+
+
+
+ Installing and Configuring 32-bit Sun JDK 5.0 using RHN
+
+
+ Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplemen=
tary channel for your Linux variant and architecture. Depending on the arch=
itecture, the channel names are:
+
+
+ rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementa=
ry-5
+
+
+ The java-1.5.0-bea,
+ java-1.5.0-ibm and
+ java-1.5.0-sun SDKs are availa=
ble from
+ these channels. Make sure you also install the
+ -devel subpackages.
+
+
+ =
+
+
+ Selecting alternatives for java, javac and java_sdk_1.5.0 (setting java_sdk_1.5.0 is optional). =
+
+ =
+
+ This is only needed if you want to use the SysV service script
+ and/or want this installed SDK to be the default java and javac
+ in the system. This choice can often be overridden by setting
+ the JAVA_HOME environment vari=
able.
+
+ =
+
+ The alternatives system allows=
different versions of Java, from different sources, to co-exist on your sy=
stem. You should make sure the desired one is selected so that the service =
script uses the one you want.
+
+ =
+
+ As root, issue the following command:
+
+
+ /usr/sbin/alternatives --config java
+
+
+ and make sure the desired one is selected (marked with a '+'), or s=
elect it by entering its number as prompted.
+
+ =
+
+ Make sure you do the same for javac and java_sdk_1.5.0. We recommend=
that all point to the same manufacturer and version.
+
+
+
+
+ Installing and Configuring 32-bit Sun JDK 5.0 on a generic Lin=
ux platform
+
+
+ Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we=
bsite: <=
/ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu=
mber) for download and then select "RPM in self-extracting" file for Linux<=
footnote>Make sure you choose the appropriate file for your platform.=
. Read the instructions on Sun's website for installi=
ng the JDK.
+
+
+
+
+ If you don't want to use SysV service scripts you can install t=
he "self-extracting file" for Linux instead of choosing the "RPM in self-ex=
tracting" file. In that case you can skip the next step mentioned here. But=
it is recommended to use the SysV service scripts for production servers.
+
+
+
+
+ Download and install the appropriate -compat RPM=
from JPackage here.
+
+Please ensure you choose a matching version of the -compat package to the JDK you installed.
+
+
+
+
+
+ Create an environment variable that points to the JDK installation =
directory and call it JAVA_HOME. Add $JAVA_HOME=
/bin to the system path to be able to run java=
from the command line. You can do this by adding the following lines to th=
e .bashrc file in your home directory.
+#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory.
+export JAVA_HOME=3D/usr/java/jdk1.5.0_11
+export PATH=3D$PATH:$JAVA_HOME/bin
+
+ Set this variable for the user account doing the installation and =
also for the user account that will run the server.
+
+
+
+
+ If you have more than one version of JVM installed in your machine,=
make sure you are using the JDK1.5 installation as the default ja=
va and javac. You can do this using the altern=
atives system. The alternatives system allows different versions of Java, f=
rom different sources to co-exist on your system.
+
+ Select alternatives for java, javac and java_sdk_1.5.0
+
+
+ As root, type the following command at the shell prompt and you =
should see something like this:
+[root(a)vsr ~]$ /usr/sbin/alternatives --config java
+There are 2 programs which provide 'java'.
+Selection Command
+-----------------------------------------------
+ 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
+*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
+Enter to keep the current selection[+], or type selection number:
+
+ Make sure the Sun version [jre-1.5.0-sun in =
this case] is selected (marked with a '+' in the output), or select=
it by entering its number as prompted.
+
+
+
+
+ Repeat the same for javac and java_sdk_1.5.0.
+[root(a)vsr ~]$ /usr/sbin/alternatives --config javac
+There are 1 programs which provide 'javac'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac
+Enter to keep the current selection[+], or type selection number:
+
+
+[root(a)vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0
+There are 1 programs which provide 'java_sdk_1.5.0'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun
+Enter to keep the current selection[+], or type selection number:
+
+ You should verify that java, javac and java_sdk_1.5.0 all point=
to the same manufacturer and version.
+
+
+
+
+
+
+ You can always override this step by setting the JAVA_HOM=
E environment variable as explained in the previous step.
+
+
+
+
+
+ Make sure that the java executable is in your pa=
th and that you are using an appropriate version. To verify your Java envir=
onment, type java -version at the shell prompt and you s=
hould see something like this:
+[root(a)vsr ~]$ java -version
+java version "1.5.0_11"
+Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
+Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
+
+
+
+
+
+ Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Win=
dows
+
+
+ Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we=
bsite: <=
/ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu=
mber) for download and then select your Windows Platform options to perform=
the installation.
+
+
+
+
+ Create an environment variable called JAVA_HOME =
that points to the JDK installation directory, for example: C:\Pro=
gram Files\Java\jdk1.5.0_11\. In order to run java from the comma=
nd line add the jre\bin directory to your path, for exam=
ple: C:\Program Files\Java\jdk1.5.0_11\jre\bin. To do th=
is, open the Control Panel from the Start Menu, switch to Classic View if n=
ecessary, open the System Control Panel applet, select the Advanced Tab, an=
d click on the Environment Variables button.
+
+
+
+
+
+
+
+ =
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Installation.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,78 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Installation
+ =
+
+ Download
+ =
+
+ You can download the zip file from the JBoss Customer Service Portal (C=
SP), located at https://network.jb=
oss.com. =
+
+
+ =
+
+ Installing
+ =
+
+ To install from a zip file, simply unzip the downloaded file to a dire=
ctory of your choice. You can unzip the platform on any operating system th=
at supports the zip format. Four types of server configurations will be inc=
luded in your installation - minimal, default, production and all. =
+ The Getting Started Guide of &JBEAP; as well as http://www.jboss.org/co=
mmunity/docs/DOC-12942 explain in detail the different server configuration=
file sets. =
+ =
+
+
+
+ Unzip jboss-epp-<release>.=
zip to extract the archive contents into the location of your cho=
ice. You can do this using the JDK jar tool (or any othe=
r ZIP extraction tool).
+ [vsr]$ cd jbeppinstallationdir
+ [vsr]$ jar -xvf jboss-epp-<release>.zip
+
+
+
+
+ You are done with the installation! You should now have a directory =
called jboss-epp-<release>. Refer to the Getting Started Guide to understand and explore the Pla=
tform Directory Structure.
+
+
+
+ =
+
+ =
+
+ Choosing a server configuration
+
+ The important differences as far as Portal is concerned are:
+
+
+
+
+ minimal server configuration has no Portal bits. =
It's there for the sake of consistency with &JBEAP;
+
+
+
+
+ default server configuration has non-clustered Po=
rtal bits jboss-portal.sar in =
+ deploy folder. =
+
+
+
+
+ all server configuration has clustered Portal bit=
s jboss-portal-ha.sar in =
+ deploy folder. =
+
+
+
+
+ production server configuration has clustered Por=
tal bits jboss-portal-ha.sar and this is =
+ the sever that gets started by default. This server configuration ha=
s several optimizations such as logging, memory size etc.
+ If you do not need clustered portal version and want to use this opt=
imized server configuration, you simply need to copy the directory
+ jboss-portal.sar from default/deploy to production/deploy. Don't forget to
+ remove jboss-portal-ha.sar though. =
+
+ =
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Installation_Guide.ent
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation_Guide.ent (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation_Guide.ent 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,7 @@
+
+
+
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Installation_Guide.ent
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Installation_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation_Guide.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Installation_Guide.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,22 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+
+]>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Installation_Guide.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Introduction.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Introduction.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,50 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Introduction
+ =
+ &PRODUCT; is the open source implementation of the Java EE suite of serv=
ices and Portal services running atop &JBEAP;. It comprises a set of offeri=
ngs =
+ for enterprise customers who are looking for preconfigured profiles of J=
Boss Enterprise Middleware components that have been tested and certified t=
ogether
+ to provide an integrated experience. Its easy-to-use server architectur=
e and high flexibility makes JBoss the ideal choice for users just starting=
out with J2EE, as well as senior architects looking for a customizable mid=
dleware platform.
+
+
+ Because it is Java-based, &PRODUCT; is cross-platform and easy to instal=
l and use on any operating system that supports Java. The readily available=
source code is a powerful learning tool to debug the server and understand=
it. It also gives you the flexibility to create customized versions for yo=
ur personal or business use.
+
+
+ Installing &PRODUCT; is simple and easy. You can have it installed and r=
unning in no time. This guide will teach you to install and uninstall JBoss=
.
+
+
+ Other Manuals
+
+ If you are looking for detailed product information refer to the manual=
s available online at .
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Launching.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Launching.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Launching.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,118 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+
+]>
+
+ Launching &PRODUCT;
+
+ Launching a Zip installation
+
+
+
+ Navigate to the directory created during the extraction process discu=
ssed in
+
+
+
+
+ Within this directory navigate to /jboss-as/bin.
+
+
+
+
+
+
+ Launching from a terminal
+
+
+ Run the command ./run.sh (for Linux/UNIX) or run.bat (for Microsoft Windows) to start the product with t=
he default profile.
+
+
+
+
+ Graphical Launch
+
+
+ Microsoft Windows users can double-click on the run.bat=
filename> file to launch the product.
+
+
+ Linux/UNIX users can double-click on the run.sh file to launch the application. Ensure the file browser is set to either =
Run executable files, or prompt the user=
for action (select Run in Terminal if t=
his is the case).
+
+
+
+
+
+ =
+
+ &PRODUCT; will be launched. A verbose output will display in the termin=
al and the product is ready to use when the following message appears:
+
+ =
+Started in Xm: Y=
replaceable>s: Zms
+
+
+ =
+
+ Shutting Down
+
+ The methods to shut the &PRODUCT; down are similiar to those for launch=
ing it.
+
+
+
+
+ Navigate to the /jboss-as/bin directory as discu=
ssed in .
+
+
+
+
+
+
+ Shutting Down from a terminal
+
+
+ Run the command ./shutdown.sh (for Linux/UNIX) o=
r shutdown.bat (for Microsoft Windows).
+
+
+
+
+ Graphical Shutdown
+
+
+ Microsoft Windows users can double-click on the shutdown.=
bat file to close the product.
+
+
+ Linux/UNIX users can double-click on the shutdown.sh file.
+
+
+
+
+
+ =
+
+ An alternative shutdown method is to 'kill' the process running=
the product. This can be done by:
+
+
+
+
+ Using the Ctrl+C key-combination in the terminal r=
unning the process.
+
+
+
+
+ Issuing the following command with the product's process ID (PID) in another terminal instance: =
+kill PID
+
+
+
+
+
+ Using your operating system's native System Monitor to shut the p=
rocess down graphically.
+
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Post_Installation.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Post_Installation.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Post_Installation.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,209 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Post Installation Configuration
+
+
+ Set JBOSS_HOME Environment Variable
+
+
+
+ On a Linux Platform
+
+
+ Create an environment variable that points to the installation directo=
ry (JBOSS_DIST/jboss-as) and call it JBOSS_HO=
ME. Add $JBOSS_HOME/bin to the system path to =
be able to run the server from the command line. You can do this by adding =
the following lines to the .bashrc file in your home d=
irectory.
+
+#In this example /home/user/jboss-epp-4.3/jboss-as is the installation dir=
ectory.
+ export JBOSS_HOME=3D/home/user/jboss-epp-4.3/jboss-as
+ export PATH=3D$PATH:$JBOSS_HOME/bin =
+
+ Set this variable for the user account(s) that will run the server. =
+
+
+
+
+ On Microsoft Windows
+
+
+ Create an environment variable called JBOSS_HOME th=
at points to the installation directory, for example: C:\Program Files\jbos=
s-epp-4.3\jboss-as\. In order to run the server from the command line add t=
he bin directory to your path, for example: C:\Program=
Files\jboss-epp-4.3\jboss-as\bin. To do this, open the Control Panel from =
the Start Menu, switch to Classic View if necessary, open the System Contro=
l Panel applet, select the Advanced Tab, and click on the Environment Varia=
bles button.
+
+
+ =
+
+ Adjust memory settings
+
+ The default configuration for the server to start with, if no other con=
figuration is specified, is the production configuration. It is recommended=
to run the example Seam applications that are included with the documentat=
ion using the production configuration. =
+
+
+ To avoid memory issues, adjust the memory settings before deploying the=
applications. You can do this by updating JAVA_OPTS set=
tings in the file JBOSS_DIST/jboss-as/server/production/run.conf<=
/filename> with these recommended values: =
+
+ -Xms1303m -Xmx1303m -XX:PermSize=3D256m -XX:MaxPermSize=3D256m
+
+
+
+
+
+ Post Installation Security Configuration
+
+
+ When installed from the zip archive, all JBoss services require authent=
ication to access most JBoss services, including administrative services. A=
dditionally no user accounts are set up. This is to stop default user/passw=
ord-based attacks.
+
+ =
+
+ Set up Accounts for jmx-console and the invok=
ers by modifying:
+
+
+ $JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties
+
+
+
+
+ Set up Accounts for web-console users by modi=
fying:
+
+
+ $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/
+ web-console.war/WEB-INF/classes/web-console-users.properties
+
+ Where $JBOSS_HOME is the install directory and $CONFIG is the server configuration being used.
+
+
+
+ Set SuckerPassword for JBoss Messaging:
+
+ JBoss Messaging makes internal connections between nodes in order to r=
edistribute messages between clustered destinations. These connections are =
made with the user name of a special reserved user whose password is specif=
ied by this parameter SuckerPassword in the Server Peer =
configuration file:
+
+ $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/messaging-service.=
xml
+
+ Where $JBOSS_HOME is the install directory and $CONFIG is the server configuration being used.
+ To avoid a security risk, you MUST specify the value of the attribute =
SuckerPassword, failing which the default value will be =
used. Any one who knows the default password will be able to gain access to=
any destinations on the server. The following fragment should be uncomment=
ed and modified:
+
+ <mbean code=3D"org.jboss.jms.server.ServerPeer"
+ name=3D"jboss.messaging:service=3DServerPeer"
+ xmbean-dd=3D"xmdesc/ServerPeer-xmbean.xml">
+ ...
+ ...
+ ...
+ ...
+ <!-- The password used by the message sucker connections to create c=
onnections.
+ THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM =
-->
+ <attribute name=3D"SuckerPassword"></attribute>
+
+ ...
+ ...
+ ...
+ </mbean> =
+
+
+
+
+
+ Disabling Authentication =
+
+ It is also possible to disable authentication on specific services. All=
specified paths in the sections below are relative to $JBOSS_HOME=
.
+
+
+ Disabling Authentication for JXM Console:
+
+ To disable authentication for the JMX console, edit the following file=
and comment out the security-constraint section:
+
+server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml
+
+ The following fragment should be commented out:
+
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows
+users with the
+role JBossAdmin to access the HTML JMX console web application
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+</security-constraint>
+
+
+
+
+ Disabling Authentication for Web Console:
+
+ To disable authentication for the Web console, edit the following file=
to comment out the security-constraint section:
+
+server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/w=
eb.xml
+
+ The following fragment should be commented out:
+
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows
+users with the role JBossAdmin to access the HTML JMX console web applicat=
ion
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+</security-constraint>
+
+
+
+
+ Disabling Authentication for HTTP Invoker:
+
+ To disable authentication for the http invoker, JNDIFactory=
literal>, EJBInvokerServlet, and JMXInvokerServ=
let need to be removed from the security realm in the file:
+
+server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml
+
+ For example, the security-constraint element should look as follows:
+
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HttpInvokers</web-resource-name>
+ <description>An example security config that only allows =
+users with the role HttpInvoker to access the HTTP invoker servlets
+ </description>
+ <url-pattern>/restricted/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>HttpInvoker</role-name>
+ </auth-constraint>
+ </security-constraint>
+
+
+
+
+ Disabling Authentication for JMX Invoker:
+
+ To disable authentication for the JMX invoker, edit the following file=
to comment out the security interceptor passthrough:
+
+server/$CONFIG/deploy/jmx-invoker-service.xml
+
+ Locate the mbean section with the class org.jboss.jmx.connect=
or.invoker.InvokerAdaptorService. In that section comment out the=
line that relates to authenticated users:
+
+<descriptors>
+ <interceptors>
+ <!-- Uncomment to require authenticated users -->
+ <interceptor code=3D"org.jboss.jmx.connector.invoker.Authentica=
tionInterceptor"
+ securityDomain=3D"java:/jaas/jmx-console"/>
+ <!-- Interceptor that deals with non-serializable results -->
+ <interceptor code=3D"org.jboss.jmx.connector.invoker.Serializab=
leInterceptor"
+ policyClass=3D"StripModelMBeanInfoPolicy"/>
+ </interceptors>
+</descriptors>
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Preface.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Preface.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,28 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+]>
+
+ Preface
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Preface.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Revision_History.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Revision_History.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,30 @@
+
+
+%BOOK_ENTITIES;
+
+%BOOK_ENTITIES;
+
+]>
+
+ Revision History
+
+
+
+ 1
+ Tue Nov 24 2009
+
+ Scott
+ Mumford
+ smumford(a)redhat.com
+
+
+
+ Initial creation of book in Publican
+
+
+
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/Revision_History.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Test_Your_Installation.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Test_Your_Installation.xml (rev =
0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Test_Your_Installation.xml 2010-04-01 04:03:11 UTC (rev =
2432)
@@ -0,0 +1,64 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Test your Installation
+
+ After you have installed the JBoss Enterprise Portal Platform, it is wis=
e to perform a simple startup test to validate that there are no major prob=
lems with your Java VM/operating system combination. Make sure you have set=
the JBOSS_HOME envirnoment variables as explained in . To test your installation, =
move to JBOSS_DIST/jboss-as/bin directory and execute =
the run.bat (for Windows) or run.sh (for Linux) script, as appropriate for your operating system. Your outpu=
t should look like the following (accounting for installation directory dif=
ferences) and contain no error or exception messages:
+
+
+[user(a)localhost bin]$ ./run.sh =
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
+
+ JBoss Bootstrap Environment
+
+ JBOSS_HOME: /home/user/jboss-eap-4.3/jboss-as
+
+ JAVA: /usr/java/jdk1.5.0_11/bin/java
+
+ JAVA_OPTS: -Dprogram.name=3Drun.sh -server -Xms1503m -Xmx1503m -Dsun.rmi=
.dgc.cli ent.gcInterval=3D3600000 =
+ -Dsun.rmi.dgc.server.gcInterval=3D3600000 -Djava.net.prefer I=
Pv4Stack=3Dtrue
+
+ CLASSPATH: /home/user/jboss-eap-4.3/jboss-as/bin/run.jar:/u sr/java/jdk1=
.5.0_11/lib/tools.jar
+
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
+
+18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)...
+.
+.
+.
+.
+18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems In=
c.
+18:45:50,449 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_=
11-b03 ,Sun Microsystems Inc.
+18:45:50,449 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386
+18:45:51,824 INFO [Server] Core system initialized
+18:45:59,622 INFO [WebService] Using RMI server codebase: http://127.0.0.=
1:8083 /
+18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: =
resour ce:jboss-log4j.xml
+
+
+
+ Note that there is no "Server Started" message shown at the console whe=
n the server is started using the production profile, wh=
ich is the default profile used when no other is specified. This message ma=
y be observed in the server.log file located in the server/production/log subdirectory.
+
+
+
+ Now open http://localhost:8080/portal in your web bro=
wser. (Make sure you dont have anything else already on your machine using =
that port).
+ Note that on some machines, the name localhost won=E2=80=99t resolve pro=
perly and you should use the local loopback address 127.0.0.1 instead. The contents of your page should look similar to this: .
+
+
+
+ Test your Installation
+
+
+
+
+
+
+
+
+ You are now ready to use the JBoss Enterprise Portal Platform. Refer to =
the User Guide and Reference Guide for more information about the platform=
layout and example applications showcasing JBoss Portal in action.
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/Uninstall_JBoss.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Uninstall_JBoss.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/Uninstall_JBoss.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,13 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Uninstall JBoss
+
+ As JBoss Enterprise Portal Platform was installed from a zipfile, you ma=
y uninstall it by simply deleting the &PRODUCT; installed directory. =
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/Conventions.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Conventions.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Conventions.xml 2010-04-01 04:03:11 UTC=
(rev 2432)
@@ -0,0 +1,167 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Document Conventions
+
+ This manual uses several conventions to highlight certain words and phra=
ses and draw attention to specific pieces of information.
+
+
+ In PDF and paper editions, this manual uses typefaces drawn from the
Liberation Fonts
set. The Liberation Fonts set is also used in HTML editions if the set=
is installed on your system. If not, alternative but equivalent typefaces =
are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Libe=
ration Fonts set by default.
+
+
+ Typographic Conventions
+
+ Four typographic conventions are used to call attention to specific wor=
ds and phrases. These conventions, and the circumstances they apply to, are=
as follows.
+
+
+ Mono-spaced Bold
+
+
+ Used to highlight system input, including shell commands, file names an=
d paths. Also used to highlight keycaps and key combinations. For example:
+
+
+
+ To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_=
bestselling_novel command at the shell prompt and press E=
nter to execute the command.
+
+
+
+ The above includes a file name, a shell command and a keycap, all prese=
nted in mono-spaced bold and all distinguishable thanks to context.
+
+
+ Key combinations can be distinguished from keycaps by the hyphen connec=
ting each part of a key combination. For example:
+
+
+
+ Press Enter to execute the command.
+
+
+ Press CtrlAltF1 to switch to the first virtual terminal. Press =
CtrlAltF7 to =
return to your X-Windows session.
+
+
+
+ The first paragraph highlights the particular keycap to press. The seco=
nd highlights two key combinations (each a set of three keycaps with each s=
et pressed simultaneously).
+
+
+ If source code is discussed, class names, methods, functions, variable =
names and returned values mentioned within a paragraph will be presented as=
above, in mono-spaced bold. For example:
+
+
+
+ File-related classes include filesystem for fil=
e systems, file for files, and dir for directories. Each class has its own associated set of permissions.
+
+
+
+ Proportional Bold
+
+
+ This denotes words or phrases encountered on a system, including applic=
ation names; dialog box text; labeled buttons; check-box and radio button l=
abels; menu titles and sub-menu titles. For example:
+
+
+
+ Choose SystemPreferencesMouse from the main menu =
bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse =
check box and click Close to switch the primary mous=
e button from the left to the right (making the mouse suitable for use in t=
he left hand).
+
+
+ To insert a special character into a gedit =
file, choose ApplicationsAccesso=
riesCharacter Map from=
the main menu bar. Next, choose SearchFind… from the Chara=
cter Map menu bar, type the name of the character in the Search field and click Next. The ch=
aracter you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose EditPaste from the gedit menu bar.
+
+
+
+ The above text includes application names; system-wide menu names and i=
tems; application-specific menu names; and buttons and text found within a =
GUI interface, all presented in proportional bold and all distinguishable b=
y context.
+
+
+ Mono-spaced Bold Italic o=
r Proportional Bold Italic
+
+
+ Whether mono-spaced bold or proportional bold, the addition of italics =
indicates replaceable or variable text. Italics denotes text you do not inp=
ut literally or displayed text that changes depending on circumstance. For =
example:
+
+
+
+ To connect to a remote machine using ssh, type ssh username@domain.name =
at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john(a)examp=
le.com.
+
+
+ The mount -o remount file-system=
command> command remounts the named file system. For example, to remount th=
e /home file system, the command is mount -o =
remount /home.
+
+
+ To see the version of a currently installed package, use the =
rpm -q package command. It will return=
a result as follows: package-version-release.
+
+
+
+ Note the words in bold italics above — username, domain.name, fil=
e-system, package, version and release. Each word is a placeholder, either =
for text you enter when issuing a command or for text displayed by the syst=
em.
+
+
+ Aside from standard usage for presenting the title of a work, italics d=
enotes the first use of a new and important term. For example:
+
+
+
+ Publican is a DocBook publishing system.
+
+
+
+ =
+
+ Pull-quote Conventions
+
+ Terminal output and source code listings are set off visually from the =
surrounding text.
+
+
+ Output sent to a terminal is set in mono-spaced roman=
computeroutput> and presented thus:
+
+ =
+books Desktop documentation drafts mss photos stuf=
f svn
+books_tests Desktop1 downloads images notes scripts svgs
+
+
+ Source-code listings are also set in mono-spaced roman<=
/computeroutput> but add syntax highlighting as follows:
+
+ =
+package org.jboss.book.jca.ex1;
+
+import javax.naming.InitialContext;
+
+public class ExClient
+{
+ public static void main(String args[]) =
+ throws Exception
+ {
+ InitialContext iniCtx =3D new InitialContext();
+ Object ref =3D iniCtx.lookup("EchoBean");
+ EchoHome home =3D (EchoHome) ref;
+ Echo echo =3D home.create();
+
+ System.out.println("Created Echo");
+
+ System.out.println("Echo.echo('Hello') =3D " + echo.echo("Hello"));
+ }
+}
+
+
+ =
+
+ Notes and Warnings
+
+ Finally, we use three visual styles to draw attention to information th=
at might otherwise be overlooked.
+
+
+ Note
+
+ Notes are tips, shortcuts or alternative approaches to the task at han=
d. Ignoring a note should have no negative consequences, but you might miss=
out on a trick that makes your life easier.
+
+
+
+ Important
+
+ Important boxes detail things that are easily missed: configuration ch=
anges that only apply to the current session, or services that need restart=
ing before an update will apply. Ignoring a box labeled 'Important' won't c=
ause data loss but may cause irritation and frustration.
+
+
+
+ Warning
+
+ Warnings should not be ignored. Ignoring warnings will most likely cau=
se data loss.
+
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/Feedback.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Feedback.xml (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Feedback.xml 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,23 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ We Need Feedback!
+
+ feedback
+ contact information for this manual
+
+
+ If you find a typographical error in this manual, or if you have thought=
of a way to make this manual better, we would love to hear from you! Pleas=
e submit a report in Bugzilla: http://bugzilla.redhat.com/bugzilla/ against the product &PRODUCT;.
+
+
+ When submitting a bug report, be sure to mention the manual's identifier=
: &BOOKID;
+
+
+ If you have a suggestion for improving the documentation, try to be as s=
pecific as possible when describing it. If you have found an error, please =
include the section number and some of the surrounding text so we can find =
it easily.
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/Legal_Notice.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Legal_Notice.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/Legal_Notice.xml 2010-04-01 04:03:11 UT=
C (rev 2432)
@@ -0,0 +1,11 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+ Copyright &YEAR; &HOLDER; Th=
is material may only be distributed subject to the terms and conditions set=
forth in the GNU Free Documentation License (GFDL), V1.2 or later (the lat=
est version is presently available at http://www.gnu.org/licenses/fdl.txt).
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/book_ent
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/book_ent (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/book_ent 2010-04-01 04:03:11 UTC (rev 2=
432)
@@ -0,0 +1,5 @@
+#!/usr/bin/env bash
+for file in *.xml; do
+ sed -i -e 's/docbookx.dtd" \[/docbookx.dtd" \[\n\n%BOOK_ENTITIES\;/' ${file}; \
+done
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/book_ent
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/1.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/1.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/1.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/1.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/10.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/10.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/10.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/10.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/10.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/11.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/11.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/11.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/11.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/11.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/12.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/12.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/12.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/12.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/12.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/13.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/13.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/13.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/13.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/13.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/14.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/14.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/14.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/14.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/14.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/15.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/15.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/15.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/15.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/15.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/16.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/16.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/16.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/16.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/16.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/17.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/17.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/17.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/17.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/17.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/18.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/18.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/18.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/18.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/18.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/19.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/19.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/19.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/19.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/19.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/2.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/2.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/2.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/2.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/20.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/20.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/20.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/20.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/20.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/21.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/21.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/21.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/21.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/21.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/22.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/22.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/22.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/22.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/22.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/23.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/23.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/23.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/23.svg (=
rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/23.svg 2010-04-01 04:03:11 UTC (=
rev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/3.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/3.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/3.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/3.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/4.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/4.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/4.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/4.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/5.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/5.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/5.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/5.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/5.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/6.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/6.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/6.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/6.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/6.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/7.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/7.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/7.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/7.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/7.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/8.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/8.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/8.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/8.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/9.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/9.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/9.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/9.svg (r=
ev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/9.svg 2010-04-01 04:03:11 UTC (r=
ev 2432)
@@ -0,0 +1,22 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/dot.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/dot.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/dot2.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/dot2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/h1-bg.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/h1-bg.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/image_left.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/image_left.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/image_right.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/image_right.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/important.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/important.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/important.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/important.svg =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/important.svg 2010-04-01 04:03:1=
1 UTC (rev 2432)
@@ -0,0 +1,30 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/note.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/note.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/note.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/note.svg =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/note.svg 2010-04-01 04:03:11 UTC=
(rev 2432)
@@ -0,0 +1,28 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/shine.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/shine.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/stock-go-back.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/stock-go-back.p=
ng
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/stock-go-forward.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/stock-go-forwar=
d.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/stock-go-up.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/stock-go-up.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/stock-home.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/stock-home.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/title_logo.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/title_logo.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/title_logo.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/title_logo.svg =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/title_logo.svg 2010-04-01 04:03:=
11 UTC (rev 2432)
@@ -0,0 +1,96 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/warning.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/warning.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/warning.svg
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/warning.svg =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/en-US/fallback_content/images/warning.svg 2010-04-01 04:03:11 =
UTC (rev 2432)
@@ -0,0 +1,130 @@
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/en-US/fallback_content/images/watermark-draft.png
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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)
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/en-US/fallback_content/images/watermark-draft=
.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_Guide/pom.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/pom.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/pom.xml 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,216 @@
+
+ =
+ 4.0.0
+ org.jboss.project
+ ${docname}-${translation}
+ 1.0
+ jdocbook
+ ${bookname}-(${translation})
+
+
+ en-US
+ Installation_Guide
+ Installation Guide
+ =
+
+
+
+ repository.jboss.org
+ JBoss Repository
+ default
+ http://repository.jboss.org/maven2/
+
+ false
+
+
+
+
+
+ repository.jboss.org
+ JBoss Repository
+ default
+ http://repository.jboss.org/maven2/
+
+ false
+
+
+
+ =
+ =
+
+
+
+
+ all
+
+ true
+
+
+
+
+ org.jboss.maven.plugins
+ maven-jdocbook-plugin
+ 2.2.0
+ true
+
+
+
+ pdf
+ classpath:/xslt/org/jboss/pdf.xsl
+ ${docname}.pdf
+
+
+ html
+ classpath:/xslt/org/jboss/xhtml.xsl
+ index.html
+
+
+ html_single
+ classpath:/xslt/org/jboss/xhtml-single.xs=
l
+ index.html
+
+
+
+
+
+
+
+
+
+
+ html
+
+ false
+
+
+
+
+ org.jboss.maven.plugins
+ maven-jdocbook-plugin
+ 2.2.0
+ true
+
+
+
+ html
+ classpath:/xslt/org/jboss/xhtml.xsl
+ index.html
+
+
+
+
+
+
+
+
+
+
+ html-single
+
+ false
+
+
+
+
+ org.jboss.maven.plugins
+ maven-jdocbook-plugin
+ 2.2.0
+ true
+
+
+
+ html_single
+ classpath:/xslt/org/jboss/xhtml-single.xs=
l
+ index.html
+
+
+
+
+
+
+
+
+
+
+ pdf
+
+ false
+
+
+
+
+ org.jboss.maven.plugins
+ maven-jdocbook-plugin
+ 2.2.0
+ true
+
+
+
+ pdf
+ classpath:/xslt/org/jboss/pdf.xsl
+ ${docname}.pdf
+
+
+
+
+
+
+
+
+
+
+
+
+
+ org.jboss.maven.plugins
+ maven-jdocbook-plugin
+ 2.2.0
+ true
+
+
+ org.jboss
+ jbossorg-docbook-xslt
+ 1.1.0
+
+
+ org.jboss
+ jbossorg-jdocbook-style
+ 1.1.0
+ jdocbook-style
+
+
+
+ ${docname}.xml
+ .
+
+ ${translation}
+
+ images/*
+
+
+
+ true
+ saxon
+
+
+ 1.72.0
+
+
+ javax.xml.parsers.DocumentBuilderFactory
+ org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
+
+
+ javax.xml.parsers.SAXParserFactory
+ org.apache.xerces.jaxp.SAXParserFactoryImpl
+
+
+
+
+
+ =
+
+
+
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/pom.xml
___________________________________________________________________
Name: svn:executable
+ =
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ins=
tallation_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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/publican.cfg (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Instal=
lation_Guide/publican.cfg 2010-04-01 04:03:11 UTC (rev 2432)
@@ -0,0 +1,9 @@
+# Config::Simple 4.59
+# Wed Nov 25 09:17:17 2009
+
+ =
+xml_lang: en-US
+type: Book
+brand: JBoss
+debug:1 =
+
Property changes on: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Porta=
l_Platform_Installation_Guide/publican.cfg
___________________________________________________________________
Name: svn:executable
+ =
--===============2989166107353948465==--
From do-not-reply at jboss.org Thu Apr 1 02:52:17 2010
Content-Type: multipart/mixed; boundary="===============4612702996958571159=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2435 -
portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/page.
Date: Thu, 01 Apr 2010 02:52:17 -0400
Message-ID: <201004010652.o316qHoP020892@svn01.web.mwc.hst.phx2.redhat.com>
--===============4612702996958571159==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: hoang_to
Date: 2010-04-01 02:52:16 -0400 (Thu, 01 Apr 2010)
New Revision: 2435
Modified:
portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/pag=
e/UIPageActionListener.java
Log:
GTNPORTAL-802: Have problem when delete last tab in Dashboard page inspecia=
l case
Modified: portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/we=
bui/page/UIPageActionListener.java
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/pa=
ge/UIPageActionListener.java 2010-04-01 06:39:36 UTC (rev 2434)
+++ portal/trunk/webui/portal/src/main/java/org/exoplatform/portal/webui/pa=
ge/UIPageActionListener.java 2010-04-01 06:52:16 UTC (rev 2435)
@@ -64,6 +64,7 @@
//This code snippet is to make sure that Javascript/Skin is fully=
loaded at the first request
UIWorkingWorkspace uiWorkingWS =3D uiPortalApp.getChildById(UIPor=
talApplication.UI_WORKING_WS_ID);
PortalRequestContext pcontext =3D Util.getPortalRequestContext();
+ pcontext.setFullRender(true);
pcontext.addUIComponentToUpdateByAjax(uiWorkingWS);
=
PageNavigation currentNav =3D showedUIPortal.getSelectedNavigatio=
n();
@@ -111,7 +112,6 @@
showedUIPortal.setSelectedNode(targetPageNode);
showedUIPortal.setSelectedPath(targetedPathNodes);
showedUIPortal.refreshUIPage();
- pcontext.setFullRender(true);
return;
}
}
@@ -121,7 +121,6 @@
// First, we try to find a cached UIPortal
uiWorkingWS.setRenderedChild(UIPortalApplication.UI_VIEWING_WS=
_ID);
uiPortalApp.setModeState(UIPortalApplication.NORMAL_MODE);
- pcontext.setFullRender(true);
UIPortal cachedUIPortal =3D uiPortalApp.getCachedUIPortal(newN=
avType, newNavId);
if (cachedUIPortal !=3D null)
{
--===============4612702996958571159==--
From do-not-reply at jboss.org Thu Apr 1 04:01:05 2010
Content-Type: multipart/mixed; boundary="===============5314578275399807863=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2436 -
portal/branches/EPP_5_0_Branch/web/portal/src/main/webapp/groovy/portal/webui/workspace.
Date: Thu, 01 Apr 2010 04:01:05 -0400
Message-ID: <201004010801.o31815Tx002791@svn01.web.mwc.hst.phx2.redhat.com>
--===============5314578275399807863==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: thomas.heute(a)jboss.com
Date: 2010-04-01 04:01:03 -0400 (Thu, 01 Apr 2010)
New Revision: 2436
Modified:
portal/branches/EPP_5_0_Branch/web/portal/src/main/webapp/groovy/portal/=
webui/workspace/UIPortalApplication.gtmpl
Log:
JBEPP-193: Security issue in portal URL handler
Modified: portal/branches/EPP_5_0_Branch/web/portal/src/main/webapp/groovy/=
portal/webui/workspace/UIPortalApplication.gtmpl
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_Branch/web/portal/src/main/webapp/groovy/portal=
/webui/workspace/UIPortalApplication.gtmpl 2010-04-01 06:52:16 UTC (rev 243=
5)
+++ portal/branches/EPP_5_0_Branch/web/portal/src/main/webapp/groovy/portal=
/webui/workspace/UIPortalApplication.gtmpl 2010-04-01 08:01:03 UTC (rev 243=
6)
@@ -62,25 +62,21 @@
<%}%>
- <% }
- } else {
- %>
+ <%}%>
+
+ =
+ <%} else {%>
<%}%>
+
+
+
+
+ ]]>
+
+ -->
+
+ =
+
+ Seam Setup and Configuration Options
+
+ Configuration
+
+ The ExceptionHandler is used to clean Seam contexts and transactions a=
fter errors.
+
+ =
+
+ <context-param>
+ <param-name>org.jboss.portletbridge.ExceptionHandler</pa=
ram-name>
+ <param-value>
+ org.jboss.portletbridge.SeamExceptionHandlerImpl
+ </param-value>
+ </context-param>
+
+
+ If you are using this bridge version from 2.0.0.BETA through 2.0.0.CR1=
, you must define the following web.xml parameter to use the JBoss Portlet =
Bridge provided Seam Phase Listener.
+ This is done by the bridge automatically (if needed) in 2.0.0.FINAL.
+
+
+
+ <context-param>
+ <param-name>javax.faces.LIFECYCLE_ID</param-name>
+ <param-value>SEAM_PORTLET</param-value>
+ </context-param>
+
+
+
+
+ =
+
+ Portlet 2.0 Coordination
+
+ One very important thing to note before using either of the following m=
echanisms, is that you must have the proper 2.0 schema and xsd definition a=
t the top of your portlet.xml.
+
+ =
+
+ <portlet-app xmlns=3D"http://java.sun.com/xml/ns/portlet/portlet-ap=
p_2_0.xsd"
+ version=3D"2.0"
+ xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation=3D"http://java.sun.com/xml/ns/portlet/port=
let-app_2_0.xsd
+ http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd">
+
+
+ Sending and Receiving Events
+
+ Configuration
+
+ Just like with any portlet 2.0 event consumer and receiver, you must =
define them in the portlet.xml. To see a working example, checkout the Seam=
Booking Demo portlet.
+
+
+ You must also define the following init params in your portlet.xml.
+
+ =
+
+ </init-param>
+ <init-param>
+ <name>javax.portlet.faces.autoDispatchEvents</name>
+ <value>true</value>
+ </init-param>
+ <init-param>
+ <name>javax.portlet.faces.bridgeEventHandler</name>
+ <value>org.foo.eventhandler</value>
+ </init-param>
+
+
+ For now, you must dipatch the event in the JSF or Seam backing bean. =
Future versions on the 2.0 bridge will automate the dispatching and consumi=
ng of events.
+
+ =
+
+ if (response instanceof StateAwareResponse) {
+ StateAwareResponse stateResponse =3D (StateAwareResponse) response;
+ stateResponse.setEvent(Foo.QNAME, new Bar());
+ }
+
+
+ Then you must also create the event handler class by implementing the=
BridgeEventHandler interface to process the event payload.
+
+ =
+
+ public class BookingEventHandler implements BridgeEventHandler
+ {
+ public EventNavigationResult handleEvent(FacesContext context, Even=
t event)
+ {
+ //process event payload here
+ }
+
+ }
+
+
+
+
+ =
+
+ Public Render Parameters
+
+ Configuration
+
+ Public Render Parameters (or PRPs) are one of the most powerful and s=
imple Portlet 2.0 features. Several portlets (JSF or not) can share the sam=
e render parameters. This feature can be use to present a cohesive UI to th=
e user across all portlets on the page (i.e. using an employee ID to displa=
y relative data).
+
+
+ The bridge maps a render parameter to a backing bean using settings i=
n your faces-config.xml and portlet.xml. A clear and working example can be=
found in the Seam Booking Demo portlet.
+
+
+ You must define the following init params in your portlet.xml.
+
+ =
+
+ <init-param>
+ <name>javax.portlet.faces.bridgePublicRenderParameterHandler&l=
t;/name>
+ <value>org.foo.PRPHandler</value>
+ </init-param>
+ ...
+ <supported-public-render-parameter>myCoolPRP</supported-publi=
c-render-parameter>
+
+
+ Create a managed bean and public-parameter-mappings in your faces-con=
fig.xml. This should be a basic bean that you can bind the passed parameter=
to a string with getter and setter.
+
+ =
+
+ <managed-bean>
+ <managed-bean-name>bookingPRP</managed-bean-name>
+ <managed-bean-class>your.class.Name</managed-bean-class&g=
t;
+ <managed-bean-scope>session</managed-bean-scope>
+ </managed-bean>
+
+ <application>
+ <application-extension>
+ <bridge:public-parameter-mappings>
+ <bridge:public-parameter-mapping>
+ <parameter>"the name of your portlet":hotelName</=
parameter>
+ <model-el>#{bookingPRP.hotelName}</model-el>
+ </bridge:public-parameter-mapping>
+ </bridge:public-parameter-mappings>
+ </application-extension>
+ </application>
+
+
+ You must set the parameter in the JSF or Seam backing bean, if you ar=
e providing one from your portlet.
+
+ =
+
+ if (response instanceof StateAwareResponse) {
+ StateAwareResponse stateResponse =3D (StateAwareResponse) response;
+ stateResponse.setRenderParameter("hotelName",selectedHotel.getName=
());
+ }
+
+
+ Then you must also implement the BridgePublicRenderParameterHandler i=
nterface to process any updates from the received parameter.
+
+ =
+
+ public void processUpdates(FacesContext context)
+ {
+ ELContext elContext =3D context.getELContext();
+ BookingPRPBean bean =3D (BookingPRPBean) elContext.getELResolver().g=
etValue(elContext, null, "bookingPRP");
+
+ if(null !=3D bean){
+ //Do something with bean.getHotelName());
+ } else {
+
+ }
+ }
+
+
+
+
+ =
+
+ Serving Your JSF Resources in a Portlet
+
+ Configuration
+
+ We have setup a few examples to show you how to use EL and a simple b=
ean that will allow you to use the portlet resource serving mechanism withi=
n a JSF portlet.
+
+
+ In ResourceBean.java, you can see a very sim=
ple implementations of a Map object that uses the bridge to get and encode =
a resource url served from the portlets web application.
+
+
+ So, when you have the normal "/images", "/styles" and other resource =
folders in your web app, you can use the following EL expression to serve t=
hem in your JSF application.
+
+ =
+
+ #{resource['/img/the-path-to-my-image.png']}
+
+
+ Just copy the ResourceBean.java code above, and add an entry to you f=
aces-config.xml for the bean:
+
+ =
+
+ <managed-bean>
+ <managed-bean-name>resource</managed-bean-name>
+ <managed-bean-class>org.richfaces.demo.common.ResourceBean<=
/managed-bean-class>
+ <managed-bean-scope>application</managed-bean-scope>
+ </managed-bean>
+
+
+
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.=
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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml=
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml=
2010-04-28 15:59:53 UTC (rev 2880)
@@ -0,0 +1,249 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Getting started with JBoss Portlet Bridge
+
+ JBoss Portlet Bridge not only gives you the ability to run JSF web appli=
cations in a portlet, but also gives you the benefit of running supported J=
Boss frameworks like Seam and RichFaces.
+
+
+ What's New in 2.0?
+
+ Eventing
+
+ The bridge considers a portlet event a model event. I.e. the event is =
targeted to the applications data model not its view. As JSF events primari=
ly concern its view, the bridge processes the portlet events manually, howe=
ver provisions are made to make sure that any model changes that result fro=
m processing the event are updated in the view. Since event payloads are ar=
bitrarily complex, the manual processing of the data, though managed by the=
bridge, is left to the (portlet) application to support.
+
+
+ See for details and examples.
+
+
+ =
+
+ Portlet Served Resources
+
+ The bridge deals with portlet served resources in one of two ways. If =
the request is for a non-JSF resource, the bridge handles the request by ac=
quiring a request dispatcher and forwarding the request to the named resour=
ce. If the request is for a JSF resource, the bridge runs the full JSF life=
cycle ensuring that data is processed and the resource (markup) is rendered.
+
+
+ See for details a=
nd examples.
+
+
+ =
+
+ Public Render Parameters
+
+ The bridge automates the processing of public render parameters. A pub=
lic render parameter can be mapped to an object's accessor (get/set method)=
designed to handle a String representation of the value via a Faces ValueE=
xpression. When a new public render parameter value is received in a reques=
t, the bridge sets the value by calling the ValueExpression's setValue(). A=
t the end of a request, if the current value of any mapped public render pa=
rameter doesn't match the current incoming value, the bridge sets the new v=
alue in an outgoing public render parameter (if feasible in the given phase=
).
+
+
+ See for details and examples.
+
+
+
+
+ =
+
+ Bridge Frameworks and Extensions
+
+ The JBoss Portlet Bridge currently supports JBoss Portal, GateIn, JSF 1=
.2, JBoss Seam, and JBoss Richfaces. There are configurations that apply to=
supporting each framework. See section for instructions.
+
+
+ The JBoss Portlet Bridge project is also actively developing extensions=
, and to differentiate from just another "project" that has boring ol' "ext=
ensions" we coined the term "Bridgelets" - because what would a project wit=
h Java and JSF be without having "*let" on the end of it? Not very cool in =
my opinion ;) With that said, in this current release we decided to bring a=
ll of our bridgelets into the impl code base since they are critical in mos=
t JSF portlet applications. Now it only takes a single line of configuratio=
n to utilize these features.
+
+
+ Seam Bridgelets
+
+ For example, the PortalIdentity seam component allows you to instantly=
have SSO between Seam and GateIn or JBoss Portal. This extension is config=
ured in your Seam application's components.xml file as follows.
+
+ =
+
+ <security:portal-identity authenticate-method=3D"#{authenticator.a=
uthenticate}"/>
+
+
+ =
+
+ RichFaces Bridgelets
+
+ Richfaces does not account for multiple components on the same portal =
page by default. This following web.xml renders all RichFaces component jav=
ascript to be portal friendly.
+
+ =
+
+ <context-param>
+ <param-name>org.jboss.portletbridge.WRAP_SCRIPTS</param-n=
ame>
+ <param-value>true</param-value>
+ </context-param>
+
+
+
+
+
+ Don't forget that the bridge is still in Beta and so are any extensi=
ons. If you would like to contribute to any part of this project, we encour=
age you to be active on the user forum and bring iss=
ues/enhancements to attention.
+
+
+
+
+
+
+ =
+
+ Before you start
+
+ Current version and compatibilty information can be easily located on t=
he JB=
PB wiki. Ensure you are using compatible versions of all integrated=
frameworks before you begin.
+
+
+ JBoss Portal and GateIn provides it's latest distribution included in J=
Boss Application Server. All of the guesswork has been eliminated so that y=
ou can unzip and run the Portal with a few clicks. Get the latest here (ensure you choos=
e the Portal + JBoss AS link)
+
+
+ Next, all that's left is to download the JBoss Portlet Bridge distribution and=
cofigure your portlet to use the bridge. Or, you can run a provided archet=
ype and deploy the generated=
war in a few easy steps. This will also give you an empty project to play =
around with or start from scratch.
+
+
+
+ =
+
+ Maven Archetypes
+
+ This project utilizes Maven archetypes which al=
low you get up and running with different flavors of the bridge quickly. =
+
+
+
+ =
+
+ Video Tutorials
+
+ Episode 1: Getting Started =
With The Bridge
+
+
+ Episode 2: Portlet 1.0 Adva=
nced Seam and RichFaces
+
+
+ Episode 3: Seam and Portlet=
2.0 Eventing
+
+
+ Episode 4: Running the 2.0 =
bridge on GateIn and deploy using JBoss Tools
+
+
+ Episode 5: GateIn JMX Metri=
cs and Dashboard Demo
+
+
+ Check here for t=
he latest videos.
+
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml 2010-=
04-28 15:59:53 UTC (rev 2880)
@@ -0,0 +1,82 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ JBoss Portlet Bridge Overview
+
+ To get an idea of the JBoss Portlet Bridge community, the developers, an=
d for wiki information, checkout the project page.
+
+
+ What is the JBoss Portlet Bridge?
+
+ The JBoss Portlet Bridge (or JBPB for short) is a non-final draft imple=
mentation of the JSR-3=
29 specification which supports the JSF 1.2 runtime within a JSR 28=
6 portlet and with added enhancements to support other web frameworks (such=
as Seam and RichFaces). It allows an=
y Java developer to get started quickly with their JSF web application runn=
ing in a portal environment. The developer no longer needs to worry about t=
he underlying portlet development, portlet concepts, or the API.
+
+
+
+ Understanding how JSF works with Portal
+
+ The portlet bridge isn't a portlet. It's the mediator between the two e=
nvironments and allows JSF and Portal to be completely unaware of each othe=
r. The bridge is used to execute Faces requests on behalf of the portlet. D=
uring each request, the Faces environment is setup and handled by the bridg=
e. Part of this implementation acts as a Faces controller much as the Faces=
Servlet does in the direct client request world. The other part of this imp=
lementation is provided by implementating a variety of (standard) Faces ext=
ensions.
+
+
+
+
+ This draft specification for the JSR 329 specification is not final. A=
ny final specification that may be published will likely contain difference=
s, some of which may be substantial. Publication of this draft specificatio=
n is not intended to provide the basis for implementations of the specifica=
tion. This draft specification is provided AS IS, with all faults. THERE AR=
E NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF CONDITION OF T=
ITLE OR NONINFRINGEMENT. You may copy and display this draft specification =
provided that you include this notice and any existing copyright notice. Ex=
cept for the limited copyright license granted above, there are no other li=
censes granted to any intellectual property owned or controlled by any of t=
he authors or developers of this material. No other rights are granted by i=
mplication, estoppel or otherwise.
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_develop=
ment.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_developmen=
t.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_developmen=
t.xml 2010-04-28 15:59:53 UTC (rev 2880)
@@ -0,0 +1,311 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Developing Portlets with the Bridge
+
+ This chapter demonstrates common development tasks described by the 329 =
specification.
+
+
+ Excluding Attributes from the Bridge Request Scope
+
+ When your application uses request attributes on a per request basis an=
d you do not want that particular attribute to be managed in the extended b=
ridge request scope, you must use the following configuration in your faces=
-config.xml. Below you will see that any attribute namespaced as foo.bar or=
any attribute beginning with foo.baz(wildcard) will be excluded from the b=
ridge request scope and only be used per that application's request.
+
+ =
+
+ <application>
+ <application-extension>
+ <bridge:excluded-attributes>
+ <bridge:excluded-attribute>foo.bar</bridge:excl=
uded-attribute>
+ <bridge:excluded-attribute>foo.baz.*</bridge:ex=
cluded-attribute>
+ </bridge:excluded-attributes>
+ </application-extension>
+ </application>
+
+
+ =
+
+ Supporting PortletMode Changes
+
+ A PortletMode represents a distinct render path within an application. =
There are three standard modes: view, edit, and help. The bridge's External=
Context.encodeActionURL recognizes the query string parameter javax.portlet=
.faces.PortletMode and uses this parameter's value to set the portlet mode =
on the underlying portlet actionURL or response. Once processed it then rem=
oves this parameter from the query string. This means the following navigat=
ion rule causes one to render the \edit.jspx viewId in the portlet edit mod=
e:
+
+ =
+
+ <navigation-rule>
+ <from-view-id>/register.jspx</from-view-id>
+ <navigation-case>
+ <from-outcome>edit</from-outcome>
+ <to-view-id>/edit.jspx?javax.portlet.faces.PortletMode=
=3Dedit</to-view-id>
+ </navigation-case>
+ </navigation-rule>
+
+
+ =
+
+ Navigating to a mode's last viewId
+
+ By default a mode change will start in the mode's default view without =
any (prior) existing state. One common portlet pattern when returning to th=
e mode one left after entering another mode (e.g.. view -> edit -> vi=
ew) is to return to the last view (and state) of this origin mode. The brid=
ge will explicitly encode the necessary information so that when returning =
to a prior mode it can target the appropriate view and restore the appropri=
ate state. The session attributes maintained by the bridge are intended to =
be used by developers to navigate back from a mode to the last location and=
state of a prior mode. As such a developer needs to describe a dynamic nav=
igation: "from view X return to the last view of mode y". This is most easi=
ly expressed via an EL expression. E.g.
+
+ =
+
+ <navigation-rule>
+ <from-view-id>/edit.jspx*</from-view-id>
+ <navigation-case>
+ <from-outcome>view</from-outcome>
+ <to-view-id>#{sessionScope['javax.portlet.faces.viewIdH=
istory.view']}</to-view-id>
+ </navigation-case>
+ </navigation-rule>
+
+
+ Note to Portlet Developers
+
+ Depending on the bridge implementation, when using values from these=
session scoped attributes or any viewIds which may contain query string pa=
rameters it may be necessary to use the wildcard syntax when identifying th=
e rule target. For example, the above =
+
+
+<to-view-id>
+
+
+ expression returns a viewId of the form =
+
+/viewId?javax.portlet.faces.PortletMode=3Dview&....
+
+
+ Without wildcarding, when a subsequent navigation occurs from this n=
ew view, the navigation rules wouldn't resolve because there wouldn't be an=
exact match. Likewise, the above edit.jspx =
+
+<from-view-id>
+
+
+ is wildcarded because there are navigation rules that target it that=
use a query string:
+
+<to-view-id> /edit.jspx?javax.portlet.faces.PortletM=
ode=3Dedit </to-view-id>
+
+
+ Developers are encouraged to use such wildcarding to ensure they exec=
ute properly in the broadest set of bridge implementations.
+
+
+
+
+
+ Clearing The View History When Changing Portlet Modes
+
+ By default the bridge remembers the view history when you switch to a d=
ifferent portlet mode (like "Help" or "Edit"). You
+ can use the following parameter in your portlet.xml to use the de=
fault viewId each time you switch modes.
+
+
+
+ javax.portlet.faces.extension.resetModeViewId
+ true
+
+ ]]>
+
+ =
+
+ General Error Handling
+
+
+ If you're developing a Seam portlet you can now use pages.xml for all =
error handling.
+
+
+
+ The following configuration may be used to handle exceptions. This is a=
lso useful for handling session timeout and ViewExpiredExceptions.
+
+
+ Pay attention to the location element. It must contain the /faces/ mapp=
ing to work properly.
+
+ =
+
+ <error-page>
+ <exception-type>javax.servlet.ServletException</excep=
tion-type>
+ <location>/faces/error.xhtml</location>
+ </error-page>
+ <error-page>
+ <exception-type>javax.faces.application.ViewExpiredExcep=
tion</exception-type>
+ <location>/faces/error.xhtml</location>
+ </error-page>
+
+
+ =
+
+ Custom Ajax Error Handling
+
+ By default, error handling is sent to a standard servlet page for Ajax =
requests. To handle the error inside the portlet, use the following javascr=
ipt:
+
+ =
+
+ <script type=3D"text/javascript">
+ A4J.AJAX.onError =3D function(req,status,message){
+ window.alert("Custom onError handler "+message);
+ }
+
+ A4J.AJAX.onExpired =3D function(loc,expiredMsg){
+ if(window.confirm("Custom onExpired handler "+expiredMsg+" fo=
r a location: "+loc)){
+ return loc;
+ } else {
+ return false;
+ }
+ }
+ </script>
+
+
+ Also, add the following to web.xml. Read more about these settings here=
Reque=
st Errors and Session Expiration Handling
+
+ =
+
+ <context-param>
+ <param-name>org.ajax4jsf.handleViewExpiredOnClient</param=
-name>
+ <param-value>true</param-value>
+ </context-param>
+
+
+ =
+
+ Communication Between Your Portlets
+
+ There are roughly 4 different ways to send messages, events, and parame=
ters between portlets which are contained in different ears/wars or contain=
ed in the same war. The Portlet Container does not care if you have 2 portl=
ets in the same war or if they are separated, because each portlet has a di=
fferent HttpSession.
+
+
+ Of course, with the Portlet 2.0 spec, the recommended way to share a pa=
rameter or event payload between 2 or more portlets are the and mecha=
nisms. This allows you to decouple your application from surgically managin=
g objects in the PortletSession.APPLICATION_SCOPE.
+
+
+ But, if these do not meet your usecase or you have a different strategy=
, you can use one of the following methods.
+
+
+ @PortletScope(PortletScope.ScopeType.APPLICATION_SCOPE)
+
+
+ Then you would pull the statefull object from the session:
+
+ =
+
+ YourSessionClass yourSessionClass =3D (YourSessionClass)getRende=
rRequest().getAttribute("javax.portlet.p./default/seamproject/seamprojectPo=
rtletWindow?textHolder");
+
+
+ This method is demonstrated in this video: Lesson 2: Portlet 1.0 Advanced Seam and RichFaces
+
+
+ =
+
+ Using the PortletSession
+
+ If you need to access the PortletSession to simply share a parameter/v=
alue across multiple portlets, you can use the following to do so.
+
+ =
+
+ Object objSession =3D FacesContext.getCurrentInstance().getExternalC=
ontext().getSession(false);
+ try
+ {
+ if (objSession instanceof PortletSession)
+ {
+ PortletSession portalSession =3D (PortletSession)objSession;
+ portalSession.setAttribute("your parameter name","parameter va=
lue",PortletSession.APPLICATION_SCOPE);
+ ...
+
+
+ Then, in your JSP or Facelets page, you can use:
+
+ =
+
+ #{httpSessionScope['your parameter name']}
+
+
+
+ Note to Portlet Developers
+
+ #{httpSessionScope} was implemented after 2.0.0.BETA. If you are usi=
ng the 1.0 bridge or pre 2.0.0.BETA, you must use the el variable #{session=
ApplicationScope}
+
+
+ For more information about which EL variables are provided by the bri=
dge, read section 6.5.1 of the JSR-329 specification.
+
+
+
+
+ =
+
+ Linking to Portlet/JSF Pages Using h:outputink
+
+ For linking to any JSF/Facelets page within your portlet web applicatio=
n, you may use the following.
+
+ =
+
+ <h:outputLink value=3D"#{facesContext.externalContext.requestCont=
extPath}/home.xhtml">
+ <f:param name=3D"javax.portlet.faces.ViewLink" value=3D"true"/&=
gt;
+ navigate to the test page
+ </h:outputLink>
+
+
+
+
+ Redirecting to an External Page or Resource
+
+ To link to a non JSF view (i.e. jboss.org) you can use the following pa=
rameter.
+
+
+
+ <h:commandLink actionListener=3D"#{yourBean.yourListenr}">
+ <f:param name=3D"javax.portlet.faces.DirectLink" value=3D"true"=
/>
+ navigate to the test page
+ </h:commandLink>
+
+
+ Then in your backing bean, you must call a redirect().
+
+
+
+
+
+ Using Provided EL Variables
+
+ All EL variables found in the JSR-329 (Portlet 2.0) specification are a=
vailable in the JBoss Portlet Bridge. For
+ example, you can use the following to edit the portlet preference=
s on the UI.
+
+
+
+
+
+
+]]>
+
+ Then in your backing bean, you must call the PortletPreferences.store()=
method.
+
+
+
+
+
+
+
+
+
+
+ =
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/PortletDevelopment/PortletBridge.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml 2010-04-28 15:=
59:53 UTC (rev 2880)
@@ -0,0 +1,13 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+ Building JSF Portlets
+
+
+
+
+
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortletDevelopment.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment.xml 2010-04-28 15:51:00 UTC (rev=
2879)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortletDevelopment.xml 2010-04-28 15:59:53 UTC (rev=
2880)
@@ -7,6 +7,6 @@
Portlet development
=
-
+
=
--===============0909511158273854265==--
From do-not-reply at jboss.org Wed Apr 28 12:16:57 2010
Content-Type: multipart/mixed; boundary="===============4554996772691739689=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2881 -
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide.
Date: Wed, 28 Apr 2010 12:16:57 -0400
Message-ID: <201004281616.o3SGGvrX030958@svn01.web.mwc.hst.phx2.redhat.com>
--===============4554996772691739689==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: thomas.heute(a)jboss.com
Date: 2010-04-28 12:16:56 -0400 (Wed, 28 Apr 2010)
New Revision: 2881
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/pom.xml
Log:
Making the images work
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/pom.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/pom.xml 2010-04-28 15:59:53 UTC (rev 2880)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/pom.xml 2010-04-28 16:16:56 UTC (rev 2881)
@@ -52,7 +52,7 @@
org.jboss.maven.pluginsmaven-jdocbook-plugin
- 2.2.0
+ 2.2.1true
@@ -89,7 +89,7 @@
org.jboss.maven.pluginsmaven-jdocbook-plugin
- 2.2.0
+ 2.2.1true
@@ -116,7 +116,7 @@
org.jboss.maven.pluginsmaven-jdocbook-plugin
- 2.2.0
+ 2.2.1true
@@ -187,7 +187,7 @@
${translation}
- images/*
+ images/**/*
--===============4554996772691739689==--
From do-not-reply at jboss.org Wed Apr 28 14:20:19 2010
Content-Type: multipart/mixed; boundary="===============1567297626459439523=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2882 - in
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests:
src/suite/org/exoplatform/portal/selenium and 1 other directory.
Date: Wed, 28 Apr 2010 14:20:19 -0400
Message-ID: <201004281820.o3SIKJvX026197@svn01.web.mwc.hst.phx2.redhat.com>
--===============1567297626459439523==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: mvanco(a)redhat.com
Date: 2010-04-28 14:20:18 -0400 (Wed, 28 Apr 2010)
New Revision: 2882
Modified:
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/pom.xml
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_POR_25_05_001_CutPasteNodeToSamePlace.h=
tml
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_POR_25_05_002_CutPasteNodeToSameNavigat=
ion.html
Log:
EPP5 UI Tests: excluded test 32 (change skin), fixed tests POR_25_025*
Modified: portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/pom.=
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
--- portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/pom.xml 20=
10-04-28 16:16:56 UTC (rev 2881)
+++ portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/pom.xml 20=
10-04-28 18:20:18 UTC (rev 2882)
@@ -131,6 +131,11 @@
**/Test_UserExtensions.java
-->
**/selenium/Test_*.java
+
+ **/selenium/Test_*PRL_22*.java
+
+ **/selenium/Test_*PRL_32*.java
+ selenium.port
Modified: portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/=
suite/org/exoplatform/portal/selenium/Test_POR_25_05_001_CutPasteNodeToSame=
Place.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/=
org/exoplatform/portal/selenium/Test_POR_25_05_001_CutPasteNodeToSamePlace.=
html 2010-04-28 16:16:56 UTC (rev 2881)
+++ portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/=
org/exoplatform/portal/selenium/Test_POR_25_05_001_CutPasteNodeToSamePlace.=
html 2010-04-28 18:20:18 UTC (rev 2882)
@@ -77,6 +77,16 @@
+
+
+
+ Copy <jcr.ear> into
+ <%jboss_home%/server/default/deploy>
+
+
+
+ Put exo-configuration.xml to the root
+ <%jboss_home%/exo-configuration.xml>
+
+
+
+ Configure JAAS by inserting XML fragment shown below into
+ <%jboss_home%/server/default/conf/login-config.xml>
+
+ <application-policy name=3D"exo-domain">
+ <authentication>
+ <login-module code=3D"org.exoplatform.services.security.j2ee.Jbos=
sLoginModule" flag=3D"required"></login-module>
+ </authentication>
+</application-policy>
+
+
+
+ Ensure that you use JBossTS Transaction Service and
+ JBossCache Transaction Manager=
link>.
+ Your exo-configuration.xml must contain such parts:
+
+ <component>
+ <key>org.jboss.cache.transaction.TransactionManagerLookup</key=
>
+ <type>org.jboss.cache.GenericTransactionManagerLookup</type>=
;^
+</component>
+
+<component>
+ <key>org.exoplatform.services.transaction.TransactionService</=
key>
+ <type>org.exoplatform.services.transaction.jbosscache.JBossTransa=
ctionsService</type>
+ <init-params>
+ <value-param>
+ <name>timeout</name>
+ <value>300</value>
+ </value-param>
+ </init-params>
+</component>
+
+
+
+ Start server:
+
+
+
+ bin/run.sh for Unix
+
+
+
+ bin/run.bat for Windows
+
+
+
+
+
+ Try accessing http://localhost:8080/brow=
ser
+ with root/exo as login/password if you have done everything righ=
t,
+ you'll get access to repository browser.
+
+
+
+
+
+ Configuring JCR to use external configuration
+
+
+
+ To manually configure repository create a new configuration
+ file (f.e. exo-jcr-configuration.xml). For details see JCR
+ Configuration. Your configuration must look like:
+
+ <repository-service default-repository=3D"rep=
ository1">
+ <repositories>
+ <repository name=3D"repository1" system-workspace=3D"ws1" default=
-workspace=3D"ws1">
+ <security-domain>exo-domain</security-domain>
+ <access-control>optional</access-control>
+ <authentication-policy>org.exoplatform.services.jcr.impl.co=
re.access.JAASAuthenticator</authentication-policy>
+ <workspaces>
+ <workspace name=3D"ws1">
+ <container class=3D"org.exoplatform.services.jcr.impl.st=
orage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" /=
>
+ <property name=3D"dialect" value=3D"oracle" />
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"update-storage" value=3D"false" =
/>
+ <property name=3D"max-buffer-size" value=3D"200k" =
/>
+ <property name=3D"swap-directory" value=3D"../temp=
/swap/production" />
+ </properties>
+ <value-storages>
+ see "Value stora=
ge configuration" part.
+ </value-storages>
+ </container>
+ <initializer class=3D"org.exoplatform.services.jcr.impl.=
core.ScratchWorkspaceInitializer">
+ <properties>
+ <property name=3D"root-nodetype" value=3D"nt:unstr=
uctured" />
+ </properties>
+ </initializer>
+ <cache enabled=3D"true" class=3D"org.exoplatform.service=
s.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache"&=
gt;
+ see "Cache configuratio=
n" part.
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.imp=
l.core.query.lucene.SearchIndex">
+ see "Indexer configurati=
on" part.
+ </query-handler>
+ <lock-manager class=3D"org.exoplatform.services.jcr.impl=
.core.lock.jbosscache.CacheableLockManagerImpl">
+ see "Lock Manager c=
onfiguration" part.
+ </lock-manager>
+ </workspace>
+ <workspace name=3D"ws2">
+ ...
+ </workspace>
+ <workspace name=3D"wsN">
+ ...
+ </workspace>
+ </workspaces>
+ </repository>
+ </repositories>
+</repository-service>
+
+
+
+ and update RepositoryServiceConfiguration configuration in
+ exo-configuration.xml to use this file:<compo=
nent>
+ <key>org.exoplatform.services.jcr.config.RepositoryServiceConfigu=
ration</key>
+ <type>org.exoplatform.services.jcr.impl.config.RepositoryServiceC=
onfigurationImpl</type>
+ <init-params>
+ <value-param>
+ <name>conf-path</name>
+ <description>JCR configuration file</description>
+ <value>exo-jcr-configuration.xml</value>
+ </value-param>
+ </init-params>
+</component>
+
+
+
+
+
+
+ Requirements
+
+
+ Enviorenment requirements
+
+
+
+ Every node of cluster MUST have the same mounted Network F=
ile
+ System with read and write permissions on it.
+
+ "/mnt/tornado" - path to the mounted Network File System (=
all
+ cluster nodes must use the same NFS)
+
+
+
+ Every node of cluster MUST use the same database
+
+
+
+ Same Clusters on different nodes MUST have the same cluster
+ names (f.e if Indexer cluster in workspace production on the fir=
st
+ node has name "production_indexer_cluster", then indexer cluster=
s in
+ workspace production on all other nodes MUST have the same name
+ "production_indexer_cluster" )
+
+
+
+
+
+ Enviorenment requirements
+
+ Configuration of every workspace in repository must contains of
+ such parts:
+
+
+
+ Value Storage configuration:
+
+ <value-storages>
+ <value-storage id=3D"system" class=3D"org.exoplatform.services.jcr.i=
mpl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"/mnt/tornado/temp/values/prod=
uction" /> <!--path within NFS where ValueStorage will hold it's d=
ata-->
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" />
+ </filters>
+ </value-storage>
+</value-storages>
+
+
+
+ Cache configuration:
+
+ <cache enabled=3D"true" class=3D"org.exoplatf=
orm.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceSto=
rageCache">
+ <properties>
+ <property name=3D"jbosscache-configuration" value=3D"jar:/conf/po=
rtal/test-jbosscache-data.xml" /> <!-- path to JBoss Cache con=
figuration for data storage -->
+ <property name=3D"jgroups-configuration" value=3D"jar:/conf/porta=
l/udp-mux.xml" /> <!-- path to JGroups configu=
ration -->
+ <property name=3D"jbosscache-cluster-name" value=3D"JCR_Cluster_c=
ache_production" /> <!-- JBoss Cache data storag=
e cluster name -->
+ <property name=3D"jgroups-multiplexer-stack" value=3D"true" />
+ </properties>
+</cache>
+
+
+
+ Indexer configuration:
+
+ <query-handler class=3D"org.exoplatform.servi=
ces.jcr.impl.core.query.lucene.SearchIndex">
+ <properties>
+ <property name=3D"changesfilter-class" value=3D"org.exoplatform.s=
ervices.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter" />
+ <property name=3D"index-dir" value=3D"/mnt/tornado/temp/jcrlucene=
db/production" /> <!-- path within NFS where=
ValueStorage will hold it's data -->
+ <property name=3D"jbosscache-configuration" value=3D"jar:/conf/po=
rtal/test-jbosscache-indexer.xml" /> <!-- path to JBoss Cache c=
onfiguration for indexer -->
+ <property name=3D"jgroups-configuration" value=3D"jar:/conf/porta=
l/udp-mux.xml" /> <!-- path to JGroups confi=
guration -->
+ <property name=3D"jbosscache-cluster-name" value=3D"JCR_Cluster_i=
ndexer_production" /> <!-- JBoss Cache indexer c=
luster name -->
+ <property name=3D"jgroups-multiplexer-stack" value=3D"true" />
+ </properties>
+</query-handler>
+
+
+
+ Lock Manager configuration:
+
+ <lock-manager class=3D"org.exoplatform.servic=
es.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl">
+ <properties>
+ <property name=3D"time-out" value=3D"15m" />
+ <property name=3D"jbosscache-configuration" value=3D"jar:/conf/po=
rtal/test-jbosscache-lock.xml" /> <!-- path to JBoss Cache c=
onfiguration for lock manager -->
+ <property name=3D"jgroups-configuration" value=3D"jar:/conf/porta=
l/udp-mux.xml" /> <!-- path to JGroups confi=
guration -->
+ <property name=3D"jgroups-multiplexer-stack" value=3D"true" />
+ <property name=3D"jbosscache-cluster-name" value=3D"JCR_Cluster_l=
ock_production" /> <!-- JBoss Cache locks clu=
ster name -->
+ =
+ <property name=3D"jbosscache-cl-cache.jdbc.table.name" value=3D"j=
crlocks_production"/> <!-- the name of the DB ta=
ble where lock's data will be stored -->
+ <property name=3D"jbosscache-cl-cache.jdbc.table.create" value=3D=
"true"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.table.drop" value=3D"f=
alse"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.table.primarykey" valu=
e=3D"jcrlocks_production_pk"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.fqn.column" value=3D"f=
qn"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.node.column" value=3D"=
node"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.parent.column" value=
=3D"parent"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.datasource" value=3D"j=
dbcjcr"/>
+ </properties>
+</lock-manager>
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/configuration-persister.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/configuration-persister.xml 2010-04-28=
19:10:24 UTC (rev 2883)
@@ -0,0 +1,124 @@
+
+
+
+
+ JCR Configuration persister
+
+
+ Idea
+
+ JCR Repository Service uses
+ org.exoplatform.services.jcr.config.RepositoryServiceConfig=
uration
+ component to read its configuration.
+
+ <component>
+ <key>org.exoplatform.services.jcr.config.RepositoryServiceConfig=
uration</key>
+ <type>org.exoplatform.services.jcr.impl.config.RepositoryService=
ConfigurationImpl</type>
+ <init-params>
+ <value-param>
+ <name>conf-path</name>
+ <description>JCR configuration file</description>
+ <value>/conf/standalone/exo-jcr-config.xml</value>
+ </value-param>
+ </init-params>
+ </component>
+
+ In the example Repository Service will read the configuration fr=
om
+ the file /conf/standalone/exo-jcr-config.xml.
+
+ But in some cases it's required to change the configuration on t=
he
+ fly. And know that the new one will be used. Additionally we wish not =
to
+ modify the original file.
+
+ In this case we have to use the configuration persister feature
+ which allows to store the configuration in different locations.
+
+
+
+ Usage
+
+ On startup RepositoryServiceConfiguration
+ component checks if a configuration persister was configured. In that =
case
+ it uses the provided ConfigurationPersister
+ implementation class to instantiate the persister object.
+
+ Configuration with persister:<component>
+ <key>org.exoplatform.services.jcr.config.RepositoryServiceConfig=
uration</key>
+ <type>org.exoplatform.services.jcr.impl.config.RepositoryService=
ConfigurationImpl</type>
+ <init-params>
+ <value-param>
+ <name>conf-path</name>
+ <description>JCR configuration file</description>
+ <value>/conf/standalone/exo-jcr-config.xml</value>
+ </value-param>
+ <properties-param>
+ <name>working-conf</name>
+ <description>working-conf</description>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"mysql" />
+ <property name=3D"persister-class-name" value=3D"org.exoplatfor=
m.services.jcr.impl.config.JDBCConfigurationPersister" />
+ </properties-param>
+ </init-params>
+ </component>
+
+ Where:
+
+ source-name - JNDI source name
+ configured in InitialContextInitializer
+ component. (sourceName prior v.1.9.) Find
+ more in database
+ configuration.
+
+
+
+ dialect - SQL dialect which will be
+ used with database from source-name. Find
+ more in database
+ configuration.
+
+
+
+ persister-class-name - class name of
+ ConfigurationPersister interface
+ implementation. (persisterClassName prior
+ v.1.9.)
+
+
+
+ ConfigurationPersister interface:/**
+ * Init persister.
+ * Used by RepositoryServiceConfiguration on init. =
+ * @return - config data stream
+ */
+ void init(PropertiesParam params) throws RepositoryConfigurationExceptio=
n;
+ =
+ /**
+ * Read config data.
+ * @return - config data stream
+ */
+ InputStream read() throws RepositoryConfigurationException;
+ =
+ /**
+ * Create table, write data.
+ * @param confData - config data stream
+ */
+ void write(InputStream confData) throws RepositoryConfigurationException;
+ =
+ /**
+ * Tell if the config exists.
+ * @return - flag
+ */
+ boolean hasConfig() throws RepositoryConfigurationException;
+
+ JCR Core implementation contains a persister which stores the
+ repository configuration in the relational database using JDBC calls -
+ org.exoplatform.services.jcr.impl.config.JDBCConfigurationP=
ersister.
+
+ The implementation will crate and use table JCR_CONFIG in the
+ provided database.
+
+ But the developer can implement his own persister for his partic=
ular
+ usecase.
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/configuration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/configuration.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/configuration.xml 2010-04-28 19:10:24 =
UTC (rev 2883)
@@ -0,0 +1,436 @@
+
+
+
+
+
+ eXo JCR configuration
+
+
+ Related documents
+
+
+
+ Search
+ Configuration
+
+
+
+ JDBC Data Container
+ config
+
+
+
+ External Value
+ Storages
+
+
+
+
+
+ Portal and Standalone configuration
+
+ Like other eXo services eXo JCR can be configured and used in po=
rtal
+ or embedded mode (as a service embedded in eXo Portal) and in standalo=
ne
+ mode.
+
+ In Embedded mode, JCR services are registered in the Portal
+ container and the second option is to use a Standalone container. The =
main
+ difference between these container types is that the first one is inte=
nded
+ to be used in a Portal (Web) environment, while the second one can be =
used
+ standalone (TODO see the comprehensive page Service Configuration for
+ Beginners for more details).
+
+ The following setup procedure is used to obtain a Standalone
+ configuration (TODO find more in Container configuration):
+
+
+
+ Configuration that is set explicitly using
+ StandaloneContainer.addConfigurationURL(String url) or
+ StandaloneContainer.addConfigurationPath(String path) before
+ getInstance()
+
+
+
+ Configuration from $base:directory/exo-configuration.xml or
+ $base:directory/conf/exo-configuration.xml file. Where $base:direc=
tory
+ is either AS's home directory in case of J2EE AS environment or ju=
st
+ the current directory in case of a standalone application.
+
+
+
+ /conf/exo-configuration.xml in the current classloader (e.g.
+ war, ear archive)
+
+
+
+ Configuration from
+ $service_jar_file/conf/portal/configuration.xml. WARNING: do not r=
ely
+ on some concrete jar's configuration if you have more than one jar
+ containing conf/portal/configuration.xml file. In this case choosi=
ng a
+ configuration is unpredictable.
+
+
+
+ JCR service configuration looks like:
+
+ <component>
+ <key>org.exoplatform.services.jcr.RepositoryService</key>
+ <type>org.exoplatform.services.jcr.impl.RepositoryServiceImpl<=
;/type>
+ </component>
+ <component>
+ <key>org.exoplatform.services.jcr.config.RepositoryServiceConfig=
uration</key>
+ <type>org.exoplatform.services.jcr.impl.config.RepositoryService=
ConfigurationImpl</type>
+ <init-params>
+ <value-param>
+ <name>conf-path</name>
+ <description>JCR repositories configuration file</descrip=
tion>
+ <value>jar:/conf/standalone/exo-jcr-config.xml</value>
+ </value-param>
+ <properties-param>
+ <name>working-conf</name>
+ <description>working-conf</description>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"hsqldb" />
+ <property name=3D"persister-class-name" value=3D"org.exoplatfor=
m.services.jcr.impl.config.JDBCConfigurationPersister" />
+ </properties-param>
+ </init-params>
+ </component>
+
+ conf-path : a path to a RepositoryService JCR Configuration
+
+ working-conf : optional; JCR configuration persister configurati=
on.
+ If there isn't a working-conf the persister will be disabled
+
+
+ JCR Configuration
+
+ The Configuration is defined in an XML file (see DTD
+ below).
+
+ JCR Service can use multiple Repositories and each repository =
can
+ have multiple Workspaces.
+
+ Repositories configuration parameters support human-readable
+ formats of values. They are all case-insensitive:
+
+
+
+ Numbers formats: K,KB - kilobytes, M,MB - megabytes, G,GB -
+ gigabytes, T,TB - terabytes.
+
+ Examples: 100.5 - digit 100.5, 200k - 200 Kbytes, 4m - 4
+ Mbytes, 1.4G - 1.4 Gbytes, 10T - 10 Tbytes
+
+
+
+ Time format endings: ms - milliseconds, s - seconds, m -
+ minutes, h - hours, d - days, w - weeks, if no ending -
+ seconds.
+
+ Examples: 500ms - 500 milliseconds, 20 or 20s - 20 seconds,
+ 30m - 30 minutes, 12h - 12 hours, 5d - 5 days, 4w - 4 weeks.
+
+
+
+
+
+
+
+ Repository service configuration
+
+ Default configuration of the Repository Service located in
+ jar:/conf/portal/exo-jcr-config.xml, it will be available for portal=
and
+ standalone modes.
+
+ In portal mode it is overriden and located in the portal web
+ application portal/WEB-INF/conf/jcr/repository-configuration.xml.
+
+ Example of Repository Service configuration for standalone
+ mode:
+
+ <repository-service default-repository=3D"reposit=
ory">
+ <repositories>
+ <repository name=3D"db1" system-workspace=3D"ws" default-workspac=
e=3D"ws">
+ <security-domain>exo-domain</security-domain>
+ <access-control>optional</access-control>
+ <session-max-age>1h</session-max-age>
+ <authentication-policy>org.exoplatform.services.jcr.impl.co=
re.access.JAASAuthenticator</authentication-policy>
+ <workspaces>
+ <workspace name=3D"production">
+ <!-- for system storage -->
+ <container class=3D"org.exoplatform.services.jcr.impl.st=
orage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" /=
>
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"update-storage" value=3D"false" =
/>
+ <property name=3D"max-buffer-size" value=3D"200k" =
/>
+ <property name=3D"swap-directory" value=3D"../temp=
/swap/production" />
+ </properties>
+ <value-storages>
+ <value-storage id=3D"system" class=3D"org.exoplatf=
orm.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"../temp/val=
ues/production" />
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" />
+ </filters>
+ </value-storage>
+ </value-storages>
+ </container>
+ <initializer class=3D"org.exoplatform.services.jcr.impl.=
core.ScratchWorkspaceInitializer">
+ <properties>
+ <property name=3D"root-nodetype" value=3D"nt:unstr=
uctured" />
+ </properties>
+ </initializer>
+ <cache enabled=3D"true" class=3D"org.exoplatform.service=
s.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl">
+ <properties>
+ <property name=3D"max-size" value=3D"10k" />
+ <property name=3D"live-time" value=3D"1h" />
+ </properties>
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.imp=
l.core.query.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"../temp/jcrl=
ucenedb/production" />
+ </properties>
+ </query-handler>
+ <lock-manager>
+ <time-out>15m</time-out>
+ <persister class=3D"org.exoplatform.services.jcr.impl=
.core.lock.FileSystemLockPersister">
+ <properties>
+ <property name=3D"path" value=3D"../temp/lock/s=
ystem" />
+ </properties>
+ </persister>
+ </lock-manager>
+ </workspace>
+
+ <workspace name=3D"backup">
+ <container class=3D"org.exoplatform.services.jcr.impl.st=
orage.jdbc.optimisation.CQJDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" /=
>
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"update-storage" value=3D"false" =
/>
+ <property name=3D"max-buffer-size" value=3D"200k" =
/>
+ <property name=3D"swap-directory" value=3D"../temp=
/swap/backup" />
+ </properties>
+ <value-storages>
+ <value-storage id=3D"draft" class=3D"org.exoplatfo=
rm.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"../temp/val=
ues/backup" />
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" />
+ </filters>
+ </value-storage>
+ </value-storages>
+ </container>
+ <initializer class=3D"org.exoplatform.services.jcr.impl.=
core.ScratchWorkspaceInitializer">
+ <properties>
+ <property name=3D"root-nodetype" value=3D"nt:unstr=
uctured" />
+ </properties>
+ </initializer>
+ <cache enabled=3D"true" class=3D"org.exoplatform.service=
s.jcr.impl.dataflow.persistent.LinkedWorkspaceStorageCacheImpl">
+ <properties>
+ <property name=3D"max-size" value=3D"10k" />
+ <property name=3D"live-time" value=3D"1h" />
+ </properties>
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.imp=
l.core.query.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"../temp/jcrl=
ucenedb/backup" />
+ </properties>
+ </query-handler>
+ </workspace>
+ </workspaces>
+ </repository>
+ </repositories>
+</repository-service>
+
+
+ Repository Service configuration:
+
+ default-repository - the name of a default repository (one
+ returned by RepositoryService.getRepository())
+
+ repositories - the list of repositories
+
+ Repository configuration:
+
+ name - the name of a repository
+
+ default-workspace - the name of a workspace obtained using
+ Session's login() or login(Credentials) methods (ones without an
+ explicit workspace name)
+
+ system-workspace - name of workspace where /jcr:system node is
+ placed
+
+ security-domain - the name of a security domain for JAAS
+ authentication
+
+ access-control - the name of an access control policy. There c=
an
+ be 3 types: optional - ACL is created on-demand(default), disable - =
no
+ access control, mandatory - an ACL is created for each added node(not
+ supported yet)
+
+ authentication-policy - the name of an authentication policy
+ class
+
+ workspaces - the list of workspaces
+
+ session-max-age - the time after which an idle session will be
+ removed (called logout). If not set, the idle session will never be
+ removed.
+
+ Workspace configuration:
+
+ name - the name of a workspace
+
+ auto-init-root-nodetype - DEPRECATED in JCR 1.9 (use initializ=
er).
+ The node type for root node initialization
+
+ container - workspace data container (physical storage)
+ configuration
+
+ initializer - workspace initializer configuration
+
+ cache - workspace storage cache configuration
+
+ query-handler - query handler configuration
+
+ Workspace data container configuration:
+
+ class - A workspace data container class name
+
+ properties - the list of properties (name-value pairs) for the
+ concrete Workspace data container
+
+ value-storages - the list of value storage plugins
+
+ Value Storage plugin configuration (optional feature):
+
+
+ The value-storage element is optional. If you don't include =
it,
+ the values will be stored as BLOBs inside the database.
+
+
+ value-storage - Optional value Storage plugin definition
+
+ class- a value storage plugin class name (attribute)
+
+ properties - the list of properties (name-value pairs) for a
+ concrete Value Storage plugin
+
+ filters - the list of filters defining conditions when this pl=
ugin
+ is applicable
+
+ Initializer configuration (optional):
+
+ class - initializer implementation class.
+
+ properties - the list of properties (name-value pairs). Proper=
ties
+ are supported:
+
+ root-nodetype - The node type for root node initialization
+
+ root-permissions - Default permissions of the root node. It is
+ defined as a set of semicolon-delimited permissions containing a gro=
up
+ of space-delimited identities (user, group etc, see Organization ser=
vice
+ documentation for details) and the type of permission. For example a=
ny
+ read;:/admin read;:/admin add_node;:/admin set_property;:/admin remo=
ve
+ means that users from group admin have all permissions and other use=
rs
+ have only a 'read' permission.
+
+ Configurable initializer adds a capability to override workspa=
ce
+ initial startup procedure.
+
+ Cache configuration:
+
+ enabled - if workspace cache is enabled
+
+ class - cache implementation class, optional from 1.9. Default
+ value is
+ org.exoplatform.services.jcr.impl.dataflow.persistent.LinkedWorkspac=
eStorageCacheImpl.
+
+ Cache can be configured to use concrete implementation of
+ WorkspaceStorageCache interface. JCR core has two implementation to =
use:
+ * LinkedWorkspaceStorageCacheImpl - default, with configurable read
+ behavior and statistic. * WorkspaceStorageCacheImpl - pre 1.9, still=
can
+ be used.
+
+ properties - the list of properties (name-value pairs) for
+ Workspace cache:
+
+ max-size - cache maximum size.
+
+ live-time - cached item live time.
+
+ LinkedWorkspaceStorageCacheImpl supports additional optional
+ parameters TODO
+
+ Query Handler configuration:
+
+ class - A Query Handler class name
+
+ properties - the list of properties (name-value pairs) for a Q=
uery
+ Handler (indexDir) properties and advanced features described in *Se=
arch
+ Configuration*
+
+ Lock Manager configuration:
+
+ time-out - time after which the unused global lock will be
+ removed.
+
+ persister - a class for storing lock information for future us=
e.
+ For example, remove lock after jcr restart.
+
+ path - a lock folder, each workspace has its own.
+
+
+
+ Configuration definition:
+
+ <!ELEMENT repository-service (repositories)>
+ <!ATTLIST repository-service default-repository NMTOKEN #REQUIRED>
+ <!ELEMENT repositories (repository)>
+ <!ELEMENT repository (security-domain,access-control,session-max-age,=
authentication-policy,workspaces)>
+ <!ATTLIST repository
+ default-workspace NMTOKEN #REQUIRED
+ name NMTOKEN #REQUIRED
+ system-workspace NMTOKEN #REQUIRED
+ >
+ <!ELEMENT security-domain (#PCDATA)>
+ <!ELEMENT access-control (#PCDATA)>
+ <!ELEMENT session-max-age (#PCDATA)>
+ <!ELEMENT authentication-policy (#PCDATA)>
+ <!ELEMENT workspaces (workspace+)>
+ <!ELEMENT workspace (container,initializer,cache,query-handler)>
+ <!ATTLIST workspace name NMTOKEN #REQUIRED>
+ <!ELEMENT container (properties,value-storages)>
+ <!ATTLIST container class NMTOKEN #REQUIRED>
+ <!ELEMENT value-storages (value-storage+)>
+ <!ELEMENT value-storage (properties,filters)>
+ <!ATTLIST value-storage class NMTOKEN #REQUIRED>
+ <!ELEMENT filters (filter+)>
+ <!ELEMENT filter EMPTY>
+ <!ATTLIST filter property-type NMTOKEN #REQUIRED>
+ <!ELEMENT initializer (properties)>
+ <!ATTLIST initializer class NMTOKEN #REQUIRED>
+ <!ELEMENT cache (properties)>
+ <!ATTLIST cache =
+ enabled NMTOKEN #REQUIRED
+ class NMTOKEN #REQUIRED
+ >
+ <!ELEMENT query-handler (properties)>
+ <!ATTLIST query-handler class NMTOKEN #REQUIRED>
+ <!ELEMENT access-manager (properties)>
+ <!ATTLIST access-manager class NMTOKEN #REQUIRED>
+ <!ELEMENT lock-manager (time-out,persister)>
+ <!ELEMENT time-out (#PCDATA)>
+ <!ELEMENT persister (properties)>
+ <!ELEMENT properties (property+)>
+ <!ELEMENT property EMPTY>
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/external-value-storages.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/external-value-storages.xml 2010-04-28=
19:10:24 UTC (rev 2883)
@@ -0,0 +1,218 @@
+
+
+
+
+
+ External Value Storages
+
+
+ Introduction
+
+ By default JCR Values are stored in the Workspace Data container
+ along with the JCR structure (i.e. Nodes and Properties). eXo JCR offe=
rs
+ an additional option of storing JCR Values separately from Workspace D=
ata
+ container, which can be extremely helpful to keep Binary Large Objects
+ (BLOBs) for example (see [TODOBinary values processing link]).
+
+ Value storage configuration is a part of Repository configuratio=
n,
+ find more details there.
+
+ Tree-based storage is recommended for most of cases. If you run =
an
+ application on Amazon EC2 - the S3 option may be interesting for
+ architecture. Simple 'flat' storage is good in speed of creation/delet=
ion
+ of values, it might be a compromise for a small storages.
+
+
+
+ Tree File Value Storage
+
+ Holds Values in tree-like FileSystem files.
+ path property points to the root directory to sto=
re
+ the files.
+
+ This is a recommended type of external storage, it can contain l=
arge
+ amount of files limited only by disk/volume free space.
+
+ A disadvantage it's a higher time on Value deletion due to unused
+ tree-nodes remove.
+
+ <value-storage id=3D"Storage #1" class=3D"org.exopl=
atform.services.jcr.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"data/values"/>
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" min-value-size=3D"1M"/>
+ </filters>
+
+ Where :
+ id - the value storage unique
+ identifier, used for linking with properties stored in workspace
+ container
+
+ path - a location where value files
+ will be stored
+
+
+ Each file value storage can have the filter(s)
+ for incoming values. A filter can match values by property type
+ (property-type), property name
+ (property-name), ancestor path
+ (ancestor-path) and/or size of values stored
+ (min-value-size, in bytes). In code sample we use=
a
+ filter with property-type and min-value-size only. I.e. storage for bi=
nary
+ values with size greater of 1MB. It's recommended to store properties =
with
+ large values in file value storage only.
+
+ Another example shows a value storage with different locations f=
or
+ large files (min-value-size a 20Mb-sized filter).=
A
+ value storage uses ORed logic in the process of filter selection. That
+ means the first filter in the list will be asked first and if not matc=
hed
+ the next will be called etc. Here a value matches the 20 MB-sized filt=
er
+ min-value-size and will be stored in the path
+ "data/20Mvalues", all other in "data/values".
+
+ <value-storages>
+ <value-storage id=3D"Storage #1" class=3D"org.exoplatform.services.jc=
r.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"data/20Mvalues"/>
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" min-value-size=3D"20M"/>
+ </filters>
+ <value-storage>
+ <value-storage id=3D"Storage #2" class=3D"org.exoplatform.services.jc=
r.impl.storage.value.fs.TreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"data/values"/>
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" min-value-size=3D"1M"/>
+ </filters>
+ <value-storage>
+<value-storages>
+
+
+
+ Simple File Value Storage
+
+
+ Not recommended to use in production due to low capacity
+ capabilities on most file systems.
+
+ But if you're sure in your file-system or data amount is small=
it
+ may be useful for you as haves a faster speed of Value removal.
+
+
+ Holds Values in flat FileSystem files. path
+ property points to root directory in order to store files
+
+ <value-storage id=3D"Storage #1" class=3D"org.exopl=
atform.services.jcr.impl.storage.value.fs.SimpleFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"data/values"/>
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary" min-value-size=3D"1M"/>
+ </filters>
+
+
+
+ Content Addressable Value storage (CAS) support
+
+ eXo JCR supports Content-addressable storage
+ feature for Values storing.
+
+
+ Content-addressable storage, also referred to as associative
+ storage and abbreviated CAS, is a mechanism for storing information =
that
+ can be retrieved based on its content, not its storage location. It =
is
+ typically used for high-speed storage and retrieval of fixed content,
+ such as documents stored for compliance with government
+ regulations.
+
+
+ Content Addressable Value storage stores unique content once.
+ Different properties (values) with same content will be stored as one =
data
+ file shared between those values. We can tell the Value content will be
+ shared across some Values in storage and will be stored on one physical
+ file.
+
+ Storage size will be decreased for application which governs
+ potentially same data in the content.
+
+
+ For example: if you have 100 different properties containing t=
he
+ same data (e.g. mail attachment) the storage stores only one single
+ file. The file will be shared with all referencing properties.
+
+
+ If property Value changes it is stored in an additional file.
+ Alternatively the file is shared with other values, pointing to the sa=
me
+ content.
+
+ The storage calculates Value content address each time the prope=
rty
+ was changed. CAS write operations are much more expensive compared to =
the
+ non-CAS storages.
+
+ Content address calculation based on java.security.MessageDigest
+ hash computation and tested with MD5 and
+ SHA1 algorithms.
+
+
+ CAS storage works most efficiently on data that does not change
+ often. For data that changes frequently, CAS is not as efficient as
+ location-based addressing.
+
+
+ CAS support can be enabled for Tree and
+ Simple File Value Storage types.
+
+ To enable CAS support just configure it in JCR Repositories
+ configuration like we do for other Value Storages.
+
+ <workspaces>
+ <workspace name=3D"ws">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage=
.jdbc.JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr"/>
+ <property name=3D"dialect" value=3D"oracle"/>
+ <property name=3D"multi-db" value=3D"false"/>
+ <property name=3D"update-storage" value=3D"false"/>
+ <property name=3D"max-buffer-size" value=3D"200k"/>
+ <property name=3D"swap-directory" value=3D"target/temp/sw=
ap/ws"/>
+ </properties>
+ <value-storages>
+<!------------------- here ----------------------->
+ <value-storage id=3D"ws" class=3D"org.exoplatform.service=
s.jcr.impl.storage.value.fs.CASableTreeFileValueStorage">
+ <properties>
+ <property name=3D"path" value=3D"target/temp/values/w=
s"/>
+ <property name=3D"digest-algo" value=3D"MD5"/>
+ <property name=3D"vcas-type" value=3D"org.exoplatform=
.services.jcr.impl.storage.value.cas.JDBCValueContentAddressStorageImpl"/&g=
t;
+ <property name=3D"jdbc-source-name" value=3D"jdbcjcr"=
/>
+ <property name=3D"jdbc-dialect" value=3D"oracle"/>
+ </properties>
+ <filters>
+ <filter property-type=3D"Binary"/>
+ </filters>
+ </value-storage>
+ </value-storages>
+
+ Properties:
+ digest-algo - digest hash algorithm
+ (MD5 and SHA1 were tested);
+
+ vcas-type - Value CAS internal data
+ type, JDBC backed is currently implemented
+ org.exoplatform.services.jcr.impl.storage.value.cas.JDBCValueConte=
ntAddressStorageImp;l
+
+ jdbc-source-name -
+ JDBCValueContentAddressStorageImpl specific parameter, database wi=
ll
+ be used to save CAS metadata. It's simple to use same as in worksp=
ace
+ container;
+
+ jdbc-dialect -
+ JDBCValueContentAddressStorageImpl specific parameter, database
+ dialect. It's simple to use same as in workspace container;
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/intro.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/intro.xml (rev=
0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/intro.xml 2010-04-28 19:10:24 UTC (rev=
2883)
@@ -0,0 +1,69 @@
+
+
+
+
+ Introduction in eXoJCR
+
+
+ JCR (JSR-170) API main concepts
+
+ Java Content Repository API as well as other Java language relat=
ed
+ standards is created within the Java Community Process http://jcp.org/=
as
+ a result of collaboration of an expert group and the Java community and
+ known as JSR-170 (Java Specification Request)
+ http://www.jcp.org/en/jsr/detail?id=3D170.
+
+
+ Data model
+
+ As the main purpose of content repository is to maintain the d=
ata
+ - the heart of CR is the data model:
+
+
+
+ The main data storage abstraction of JCR's data model is=
a
+ workspace
+
+
+
+ Each repository should have one or more workspaces
+
+
+
+ The content is stored in a workspace as a hierarchy of
+ items
+
+
+
+ Each workspace has its own hierarchy of items
+
+
+
+ Node is intended to support the data hierarchy. They are typed
+ using namespaced names which allows the content to be structured
+ according to standardized constraints. A node may be versioned throu=
gh
+ an associated version graph (optional feature)
+
+ Property stored data are values of predefined types (String,
+ Binary, Long, Boolean, Double, Date, Reference, Path).
+
+ It is important to note that the data model for the interface =
(the
+ repository model) is rarely the same as the data models used by the
+ repository's underlying storage subsystems. The repository knows how=
to
+ make the client's changes persistent because that is part of the
+ repository configuration, rather than part of the application
+ programming task.
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.=
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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml=
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jbosscache-configuration-templates.xml=
2010-04-28 19:10:24 UTC (rev 2883)
@@ -0,0 +1,266 @@
+
+
+
+
+
+
+ JBoss Cache configuration
+
+
+ JBoss cache configuration for indexer, lock manager and data
+ container
+
+ Each mentioned components uses instances of JBoss Cache product =
for
+ caching in clustered environment. So every element has it's own transp=
ort
+ and has to be configured in proper way. As usual, workspaces has simil=
ar
+ configuration but with different cluster-names and may-be some other
+ parameters. The simplest way to configure them is to define their's own
+ configuration files for each component in each workspace:
+
+ <property name=3D"jbosscache-configuration" value=
=3D"conf/standalone/test-jbosscache-lock-db1-ws1.xml" />
+
+ But if there are few workspaces, configuring them in such a way =
can
+ be painful and hard-manageable. eXo JCR offers a template-based
+ configuration for JBoss Cache instances. You can have one template for
+ Lock Manager, one for Indexer and one for data container and use them =
in
+ all the workspaces, defining the map of substitution parameters in main
+ configuration file. Just simply define ${jbosscache-<parameter
+ name>} inside xml-template and list correct value in JCR configurat=
ion
+ file just below "jbosscache-configuration", as shown:
+
+ template:
+
+ ...
+<clustering mode=3D"replication" clusterName=3D"${jbosscache-cluster-na=
me}">
+ <stateRetrieval timeout=3D"20000" fetchInMemoryState=3D"false" />
+...
+
+ and JCR configuration file:
+
+ ...
+<property name=3D"jbosscache-configuration" value=3D"jar:/conf/portal/j=
bosscache-lock.xml" />
+<property name=3D"jbosscache-cluster-name" value=3D"JCR-cluster-locks-d=
b1-ws" />
+...
+
+
+
+ JGroups configuration
+
+ JGroups is used by JBoss Cache for network communications and
+ transport in clustered environment. If property "jgroups-configuration=
" is
+ defined in component configuration, it will be injected into the JBoss
+ Cache instance on startup.
+
+ <property name=3D"jgroups-configuration" value=3D"y=
our/path/to/modified-udp.xml" />
+
+ As mentioned above, each component (lock manager, data container=
and
+ query handler) for each workspace requires it's own clustered environm=
ent.
+ Saying with another words, they have their own clusters with unique na=
mes.
+ By default each cluster should perform multi-casts on separate port. T=
his
+ configuration leads to great unnecessary overhead on cluster. Thats why
+ JGroups offers multiplexer feature, providing ability to use one single
+ channel for set of clusters. This feature reduces network overheads
+ increasing performance and stability of application. To enable multipl=
exer
+ stack, You should define appropriate configuration file (upd-mux.xml is
+ pre-shipped one with eXo JCR) and set "jgroups-multiplexer-stack" into
+ "true".
+
+ <property name=3D"jgroups-configuration" value=3D"j=
ar:/conf/portal/udp-mux.xml" />
+<property name=3D"jgroups-multiplexer-stack" value=3D"true" />
+
+
+
+ Shipped JBoss Cache configuration templates
+
+ Exo JCR implementation is shipped with ready-to-use JBoss Cache
+ configuration templates for JCR's components. They are situated in
+ application package in /conf/porta/ folder.
+
+
+ Data container template
+
+ Data container template is "jbosscache-data.xml" It's
+
+ <?xml version=3D"1.0" encoding=3D"UTF-8"?>
+<jbosscache xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xml=
ns=3D"urn:jboss:jbosscache-core:config:3.1">
+
+ <locking useLockStriping=3D"false" concurrencyLevel=3D"50000" lockPa=
rentForChildInsertRemove=3D"false"
+ lockAcquisitionTimeout=3D"20000" />
+
+ <clustering mode=3D"replication" clusterName=3D"${jbosscache-cluster=
-name}">
+ <stateRetrieval timeout=3D"20000" fetchInMemoryState=3D"false" /&=
gt;
+ <jgroupsConfig multiplexerStack=3D"jcr.stack" />
+ <sync />
+ </clustering>
+
+ <!-- Eviction configuration -->
+ <eviction wakeUpInterval=3D"5000">
+ <default algorithmClass=3D"org.jboss.cache.eviction.LRUAlgorithm"
+ actionPolicyClass=3D"org.exoplatform.services.jcr.impl.dataflow.p=
ersistent.jbosscache.ParentNodeEvictionActionPolicy"
+ eventQueueSize=3D"1000000">
+ <property name=3D"maxNodes" value=3D"1000000" />
+ <property name=3D"timeToLive" value=3D"120000" />
+ </default>
+ </eviction>
+</jbosscache>
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jbossts-transaction-service.xml 2010-0=
4-28 19:10:24 UTC (rev 2883)
@@ -0,0 +1,42 @@
+
+
+
+
+
+ JBossTransactionsService
+
+
+ Introduction
+
+ JBossTransactionsService implements eXo TransactionService and provi=
des
+ access to JBoss Transacti=
on
+ Service (JBossTS) JTA implementation via eXo container
+ dependency.
+
+ TransactionService used in JCR cache
+ org.exoplatform.services.jcr.impl.dataflow.persistent.jbossc=
ache.JBossCacheWorkspaceStorageCache
+ implementaion. See Cluster
+ configuration for example.
+
+
+
+ Configuration
+
+ Example configuration:
+
+ <component>
+ <key>org.exoplatform.services.transaction.TransactionService<=
/key>
+ <type>org.exoplatform.services.transaction.jbosscache.JBossTrans=
actionsService</type>
+ <init-params>
+ <value-param>
+ <name>timeout</name>
+ <value>3000</value>
+ </value-param>
+ </init-params> =
+ </component>
+
+ timeout - XA transaction timeout in seconds
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/jdbc-data-container-config.xml 2010-04=
-28 19:10:24 UTC (rev 2883)
@@ -0,0 +1,592 @@
+
+
+
+
+
+ JDBC Data Container Config
+
+
+ Introduction
+
+ eXo JCR persistent data container can work in two configuration
+ modes:
+
+ Multi-database: one database for each
+ workspace (used in standalone eXo JCR service mode)
+
+
+
+ Single-database: all workspaces persisted=
in
+ one database (used in embedded eXo JCR service mode, e.g. in eXo
+ portal)
+
+
+
+ The data container uses the JDBC driver to communicate with the
+ actual database software, i.e. any JDBC-enabled data storage can be us=
ed
+ with eXo JCR implementation.
+
+ Currently the data container is tested with the following
+ RDBMS:
+
+ MySQL (5.x including UTF8 support)
+
+
+
+ PostgreSQL (8.x)
+
+
+
+ Oracle Database (9i, 10g)
+
+
+
+ Microsoft SQL Server (2005)
+
+
+
+ Sybase ASE (15.0)
+
+
+
+ Apache Derby/Java DB (10.1.x, 10.2.x)
+
+
+
+ IBM DB2 (8.x, 9.x)
+
+
+
+ HSQLDB (1.8.0.7)
+
+
+
+ Each database software supports ANSI SQL standards but has its o=
wn
+ specifics too. So, each database has its own configuration in eXo JCR =
as a
+ database dialect parameter. If you need a more detailed configuration =
of
+ the database it's possible to do that by editing the metadata SQL-scri=
pt
+ files.
+
+ In case the non-ANSI node name is used it's necessary to use a
+ database with MultiLanguage support[TODO link to MultiLanguage]. Some =
JDBC
+ drivers need additional parameters for establishing a Unicode friendly
+ connection. E.g. under mysql it's necessary to add an additional param=
eter
+ for the JDBC driver at the end of JDBC URL. For instance:
+ jdbc:mysql://exoua.dnsalias.net/portal?characterEncoding=3Dutf8<=
/code>
+
+ There are preconfigured configuration files for HSQLDB. Look for
+ these files in /conf/portal and /conf/standalone folders of the jar-fi=
le
+ exo.jcr.component.core-XXX.XXX.jar or
+ source-distribution of eXo JCR implementation.
+
+ By default the configuration files are located in service jars
+ /conf/portal/configuration.xml (eXo services
+ including JCR Repository Service) and
+ exo-jcr-config.xml (repositories configuration). =
In
+ eXo portal product JCR is configured in portal web application
+ portal/WEB-INF/conf/jcr/jcr-configuration.xml (JCR
+ Repository Service and related serivces) and repository-configuration.=
xml
+ (repositories configuration).
+
+ Read more about Repository
+ configuration.
+
+
+
+ Multi-database Configuration
+
+ You need to configure each workspace in a repository. You may ha=
ve
+ each one on different remote servers as far as you need.
+
+ First of all configure the data containers in the
+ org.exoplatform.services.naming.InitialContextInitializer=
classname>
+ service. It's the JNDI context initializer which registers (binds) nam=
ing
+ resources (DataSources) for data containers.
+
+ Example (standalone mode, two data containers
+ jdbcjcr - local HSQLDB,
+ jdbcjcr1 - remote MySQL):<co=
mponent>
+ <key>org.exoplatform.services.naming.InitialContextInitializer&l=
t;/key>
+ <type>org.exoplatform.services.naming.InitialContextInitializer&=
lt;/type>
+ <component-plugins>
+ <component-plugin>
+ <name>bind.datasource</name>
+ <set-method>addPlugin</set-method>
+ <type>org.exoplatform.services.naming.BindReferencePlugin<=
;/type>
+ <init-params>
+ <value-param>
+ <name>bind-name</name>
+ <value>jdbcjcr</value>
+ </value-param>
+ <value-param>
+ <name>class-name</name>
+ <value>javax.sql.DataSource</value>
+ </value-param>
+ <value-param>
+ <name>factory</name>
+ <value>org.apache.commons.dbcp.BasicDataSourceFactory<=
;/value>
+ </value-param>
+ <properties-param>
+ <name>ref-addresses</name>
+ <description>ref-addresses</description>
+ <property name=3D"driverClassName" value=3D"org.hsqldb.jdbc=
Driver"/>
+ <property name=3D"url" value=3D"jdbc:hsqldb:file:target/tem=
p/data/portal"/>
+ <property name=3D"username" value=3D"sa"/>
+ <property name=3D"password" value=3D""/>
+ </properties-param>
+ </init-params>
+ </component-plugin>
+ <component-plugin>
+ <name>bind.datasource</name>
+ <set-method>addPlugin</set-method>
+ <type>org.exoplatform.services.naming.BindReferencePlugin<=
;/type>
+ <init-params>
+ <value-param>
+ <name>bind-name</name>
+ <value>jdbcjcr1</value>
+ </value-param>
+ <value-param>
+ <name>class-name</name>
+ <value>javax.sql.DataSource</value>
+ </value-param>
+ <value-param>
+ <name>factory</name>
+ <value>org.apache.commons.dbcp.BasicDataSourceFactory<=
;/value>
+ </value-param>
+ <properties-param>
+ <name>ref-addresses</name>
+ <description>ref-addresses</description>
+ <property name=3D"driverClassName" value=3D"com.mysql.jdbc.=
Driver"/>
+ <property name=3D"url" value=3D"jdbc:mysql://exoua.dnsalias=
.net/jcr"/>
+ <property name=3D"username" value=3D"exoadmin"/>
+ <property name=3D"password" value=3D"exo12321"/>
+ <property name=3D"maxActive" value=3D"50"/>
+ <property name=3D"maxIdle" value=3D"5"/>
+ <property name=3D"initialSize" value=3D"5"/>
+ </properties-param>
+ </init-params>
+ </component-plugin>
+ <component-plugins>
+ <init-params>
+ <value-param>
+ <name>default-context-factory</name>
+ <value>org.exoplatform.services.naming.SimpleContextFactory&=
lt;/value>
+ </value-param>
+ </init-params>
+ </component>
+
+ We configure the database connection parameters:
+
+ driverClassName, e.g.
+ "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver",
+ "org.postgresql.Driver"
+
+
+
+ url, e.g.
+ "jdbc:hsqldb:file:target/temp/data/portal",
+ "jdbc:mysql://exoua.dnsalias.net/jcr"
+
+
+
+ username, e.g. "sa", "exoadmin"
+
+
+
+ password, e.g. "", "exo12321"
+
+
+
+ There can be connection pool configuration parameters
+ (org.apache.commons.dbcp.BasicDataSourceFactory):
+
+ maxActive, e.g. 50
+
+
+
+ maxIdle, e.g. 5
+
+
+
+ initialSize, e.g. 5
+
+
+
+ and other according to Apache
+ DBCP configuration
+
+
+
+ When the data container configuration is done we can configure t=
he
+ repository service. Each workspace will be configured for its own data
+ container.
+
+ Example (two workspaces ws - jdbcjcr,
+ ws1 - jdbcjcr1):<workspaces&=
gt;
+ <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr"/>
+ <property name=3D"dialect" value=3D"hsqldb"/>
+ <property name=3D"multi-db" value=3D"true"/>
+ <property name=3D"max-buffer-size" value=3D"200K"/>
+ <property name=3D"swap-directory" value=3D"target/temp/swap/ws"/&=
gt; =
+ </properties>
+ </container>
+ <cache enabled=3D"true">
+ <properties>
+ <property name=3D"max-size" value=3D"10K"/><!-- 10Kbytes =
-->
+ <property name=3D"live-time" value=3D"30m"/><!-- 30 min -=
->
+ </properties>
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.impl.core.quer=
y.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"target/temp/index"/>
+ </properties>
+ </query-handler>
+ <lock-manager>
+ <time-out>15m</time-out><!-- 15 min -->
+ <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil=
eSystemLockPersister">
+ <properties>
+ <property name=3D"path" value=3D"target/temp/lock/ws"/>
+ </properties>
+ </persister>
+ </lock-manager>
+ </workspace>
+ <workspace name=3D"ws1" auto-init-root-nodetype=3D"nt:unstructured"&g=
t;
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr1"/>
+ <property name=3D"dialect" value=3D"mysql"/>
+ <property name=3D"multi-db" value=3D"true"/>
+ <property name=3D"max-buffer-size" value=3D"200K"/>
+ <property name=3D"swap-directory" value=3D"target/temp/swap/ws1"/=
> =
+ </properties>
+ </container>
+ <cache enabled=3D"true">
+ <properties>
+ <property name=3D"max-size" value=3D"10K"/>
+ <property name=3D"live-time" value=3D"5m"/>
+ </properties>
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.impl.core.quer=
y.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"target/temp/index"/>
+ </properties>
+ </query-handler>
+ <lock-manager>
+ <time-out>15m</time-out><!-- 15 min -->
+ <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil=
eSystemLockPersister">
+ <properties>
+ <property name=3D"path" value=3D"target/temp/lock/ws1"/>
+ </properties>
+ </persister>
+ </lock-manager>
+ </workspace>
+</workspaces>
+
+ source-name - a javax.sql.DataSource
+ name configured in InitialContextInitializer component (was
+ sourceName prior JCR 1.9);
+
+
+
+ dialect - a database dialect, one of
+ "hsqldb", "mysql", "mysql-utf8", "pgsql", "oracle", "oracle-oci",
+ "mssql", "sybase", "derby", "db2", "db2v8" or "auto" for dialect
+ autodetection;
+
+
+
+ multi-db - enable multi-database
+ container with this parameter (set value "true");
+
+
+
+ max-buffer-size - a threshold (in
+ bytes) after which a javax.jcr.Value content will be swapped to a
+ file in a temporary storage. I.e. swap for pending changes.
+
+
+
+ swap-directory - a path in the file
+ system used to swap the pending changes.
+
+
+
+ In this way we have configured two workspace which will be persi=
sted
+ in two different databases (ws in HSQLDB, ws1 in MySQL).
+
+
+ Starting from v.1.9 reposit=
ory
+ configuration parameters supports human-readable formats of
+ values (e.g. 200K - 200 Kbytes, 30m - 30 minutes etc)
+
+
+
+
+ Single-database configuration
+
+ It's more simple to configure a single-database data container. =
We
+ have to configure one naming resource.
+
+ Example (embedded mode for jdbcjcr data
+ container):<external-component-plugins>
+ <target-component>org.exoplatform.services.naming.InitialContext=
Initializer</target-component>
+ <component-plugin>
+ <name>bind.datasource</name>
+ <set-method>addPlugin</set-method>
+ <type>org.exoplatform.services.naming.BindReferencePlugin<=
;/type>
+ <init-params>
+ <value-param>
+ <name>bind-name</name>
+ <value>jdbcjcr</value>
+ </value-param>
+ <value-param>
+ <name>class-name</name>
+ <value>javax.sql.DataSource</value>
+ </value-param>
+ <value-param>
+ <name>factory</name>
+ <value>org.apache.commons.dbcp.BasicDataSourceFactory<=
;/value>
+ </value-param>
+ <properties-param>
+ <name>ref-addresses</name>
+ <description>ref-addresses</description>
+ <property name=3D"driverClassName" value=3D"org.postgresql.=
Driver"/>
+ <property name=3D"url" value=3D"jdbc:postgresql://exoua.dns=
alias.net/portal"/>
+ <property name=3D"username" value=3D"exoadmin"/>
+ <property name=3D"password" value=3D"exo12321"/>
+ <property name=3D"maxActive" value=3D"50"/>
+ <property name=3D"maxIdle" value=3D"5"/>
+ <property name=3D"initialSize" value=3D"5"/>
+ </properties-param>
+ </init-params>
+ </component-plugin>
+ </external-component-plugins>
+
+ And configure repository workspaces in repositories configuration
+ with this one database. Parameter "multi-db" must be switched off (set
+ value "false").
+
+ Example (two workspaces ws - jdbcjcr,
+ ws1 - jdbcjcr):<workspaces&g=
t;
+ <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr"/>
+ <property name=3D"dialect" value=3D"pgsql"/>
+ <property name=3D"multi-db" value=3D"false"/>
+ <property name=3D"max-buffer-size" value=3D"200K"/>
+ <property name=3D"swap-directory" value=3D"target/temp/swap/ws"/&=
gt;
+ </properties>
+ </container>
+ <cache enabled=3D"true">
+ <properties>
+ <property name=3D"max-size" value=3D"10K"/>
+ <property name=3D"live-time" value=3D"30m"/>
+ </properties>
+ </cache>
+ <query-handler class=3D"org.exoplatform.services.jcr.impl.core.quer=
y.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"../temp/index"/>
+ </properties>
+ </query-handler>
+ <lock-manager>
+ <time-out>15m</time-out>
+ <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil=
eSystemLockPersister">
+ <properties>
+ <property name=3D"path" value=3D"target/temp/lock/ws"/>
+ </properties>
+ </persister>
+ </lock-manager>
+ </workspace>
+ <workspace name=3D"ws1" auto-init-root-nodetype=3D"nt:unstructured"&g=
t;
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr"/>
+ <property name=3D"dialect" value=3D"pgsql"/>
+ <property name=3D"multi-db" value=3D"false"/>
+ <property name=3D"max-buffer-size" value=3D"200K"/>
+ <property name=3D"swap-directory" value=3D"target/temp/swap/ws1"/=
>
+ </properties>
+ </container>
+ <cache enabled=3D"true">
+ <properties>
+ <property name=3D"max-size" value=3D"10K"/>
+ <property name=3D"live-time" value=3D"5m"/>
+ </properties>
+ </cache>
+ <lock-manager>
+ <time-out>15m</time-out>
+ <persister class=3D"org.exoplatform.services.jcr.impl.core.lock.Fil=
eSystemLockPersister">
+ <properties>
+ <property name=3D"path" value=3D"target/temp/lock/ws1"/>
+ </properties>
+ </persister>
+ </lock-manager>
+ </workspace>
+</workspaces>
+
+ In this way we have configured two workspaces which will be
+ persisted in one database (PostgreSQL).
+
+
+ Configuration without DataSource
+
+ Repository configuration without using of the
+ javax.sql.DataSource bounded in JNDI.
+
+ This case may be usable if you have a dedicated JDBC driver
+ implementation with special features like XA transactions,
+ statements/connections pooling etc:
+
+ You have to remove the configuration in
+ InitialContextInitializer for your data=
base
+ and configure a new one directly in the workspace
+ container.
+
+
+
+ Remove parameter "source-name" and add next lines instea=
d.
+ Describe your values for a JDBC driver, database url and
+ username.
+
+
+
+
+ But be careful in this case JDBC driver should implement and
+ provide connection pooling. Connection pooling is very recommended=
for
+ use with JCR to prevent a database overload.
+
+
+ <workspace name=3D"ws" auto-init-root-nodetype=3D=
"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.JD=
BCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"dialect" value=3D"hsqldb"/>
+ <property name=3D"driverClassName" value=3D"org.hsqldb.jdbcDriver=
"/>
+ <property name=3D"url" value=3D"jdbc:hsqldb:file:target/temp/data=
/portal"/>
+ <property name=3D"username" value=3D"su"/>
+ <property name=3D"password" value=3D""/> =
+ ......
+
+
+
+ Dynamic Workspace Creation
+
+ Workspaces can be added dynamically during runtime.
+
+ This can be performed in two steps:
+
+ Firstly,
+ ManageableRepository.configWorkspace(WorkspaceEntry
+ wsConfig) - register a new configuration in
+ RepositoryContainer and create a WorkspaceContainer.
+
+
+
+ Secondly, the main step,
+ ManageableRepository.createWorkspace(String
+ workspaceName) - creation of a new workspace.
+
+
+
+
+
+
+ Simple and Complex queries
+
+ eXo JCR provides two ways for interact with Database -
+ JDBCStorageConnection that uses simple queries =
and
+ CQJDBCStorageConection that uses complex queries
+ for reducing amount of database callings.
+
+ Simple queries will be used if you chose
+ org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspac=
eDataContainer:<workspaces>
+ <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
JDBCWorkspaceDataContainer">
+ ...
+ </workspace>
+</worksapces>
+
+ Complex queries will be used if you chose
+ org.exoplatform.services.jcr.impl.storage.jdbc.optimisation=
.CQJDBCWorkspaceDataContainer:<workspaces>
+ <workspace name=3D"ws" auto-init-root-nodetype=3D"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.=
optimisation.CQJDBCWorkspaceDataContainer">
+ ...
+ </workspace>
+</worksapces>
+
+ Why we should use a Complex Queries?
+ They are optimised to reduce amount of requests to
+ database.
+ Why we should use a Simple Queries?
+ Simple queries implemented in way to support as many datab=
ase
+ dialects as possible.
+
+ Simple queries do not use sub queries, left or right
+ joins.
+
+
+
+
+ Forse Query Hints
+
+ Some databases supports hints to increase query performance (like
+ Oracle, MySQL, etc). eXo JCR have separate Complex Query implementation
+ for Orcale dialect, that uses query hints to increase performance for =
few
+ important queries.
+
+ To enable this option put next configuration
+ property:<workspace name=3D"ws" auto-init-root-node=
type=3D"nt:unstructured">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage.jdbc.JD=
BCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"dialect" value=3D"oracle"/>
+ <property name=3D"force.query.hints" value=3D"true" />
+ ......
+
+ Query hints enabled by default.
+
+ eXo JCR uses query hints only for Complex Query Oracle dialect. =
For
+ all other dialects this parameter is ignored.
+
+
+
+ Notes for Microsoft Windows users
+
+ The current configuration of eXo JCR uses Apache DBCP connection
+ pool
+ (org.apache.commons.dbcp.BasicDataSourceFactory=
).
+ It's possible to set a big value for maxActive parameter in
+ configuration.xml. That means usage of lots of TC=
P/IP
+ ports from a client machine inside the pool (i.e. JDBC driver). As a
+ result the data container can throw exceptions like "Address already in
+ use". To solve this problem you have to configure the client's machine
+ networking software for the usage of shorter timeouts for opened TCP/IP
+ ports.
+
+ Microsoft Windows has MaxUserPort,
+ TcpTimedWaitDelay registry keys in the node
+ HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParam=
eters,
+ by default these keys are unset, set each one with values like
+ these:
+
+ "TcpTimedWaitDelay"=3Ddword:0000001e, sets TIME_WAIT param=
eter
+ to 30 seconds, default is 240.
+
+
+
+ "MaxUserPort"=3Ddword:00001b58, sets the maximum of open p=
orts
+ to 7000 or higher, default is 5000.
+
+
+
+ A sample registry file is below:Windows Registry=
Editor Version 5.00
+
+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
+"MaxUserPort"=3Ddword:00001b58
+"TcpTimedWaitDelay"=3Ddword:0000001e
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/lock-manager-config.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/lock-manager-config.xml 2010-04-28 19:=
10:24 UTC (rev 2883)
@@ -0,0 +1,442 @@
+
+
+
+
+
+ LockManager configuration
+
+
+ Introduction
+
+ What LockManager does?
+
+ In common words, LockManager stores lock objects, so it can give
+ Lock object or can release it, etc.
+
+ Also LockManager is responsible for removing Locks that live too
+ long. This parameter may be configured with "time-out" property.
+
+ JCR provide two base implementation of LockManager:
+
+
+
+ org.exoplatform.services.jcr.impl.core.lock.LockM=
anagerImpl;
+
+
+
+ org.exoplatform.services.jcr.impl.core.lock.jboss=
cache.CacheableLockManagerImpl;
+
+
+
+ In this article we will talk mostly about
+ CacheableLockManagerImpl.
+
+ You can enable LockManager by adding lock-manager-configuration =
to
+ workspace-configuration.
+
+ For example:
+
+ <workspace name=3D"ws">
+ ...
+ <lock-manager class=3D"org.exoplatform.services.jcr.impl.core.lock.j=
bosscache.CacheableLockManagerImpl">
+ <properties>
+ <property name=3D"time-out" value=3D"15m" />
+ ...
+ </properties>
+ </lock-manager> =
+ ...
+</workspace>
+
+
+
+ LockManagerImpl
+
+ LockManagerImpl is simple implementation of LockManager, and also
+ faster than CacheableLockManager. It stores Lock objects in HashMap and
+ may also persist Locks if LockPersister is configured. LockManagerImpl=
do
+ not support replication in any way.
+
+ See more about LockManager Configuration here.
+
+
+
+ CacheableLockManagerImpl
+
+ CacheableLockManagerImpl stores Lock object in JBoss-cache, so L=
ocks
+ are replicable and affects on cluster, not only a single node. Also
+ JBoss-cache has JDBCCacheLoader, so locks will be stored to
+ database.
+
+ Both implementation supports Expired Locks removing. There is
+ LockRemover - separate thread, that periodically ask LockManager for L=
ocks
+ that lives to much and must be removed. So, timeout for LockRemover ma=
y be
+ set as follows, default value is 30m.
+
+ <properties>
+ <property name=3D"time-out" value=3D"10m" />
+ ...
+</properties>
+
+
+ Configuration
+
+ Replication requirements are same as for Cache
+
+ Full JCR configuration example you can see here.
+
+ Common tips:
+
+
+
+ clusterName ("jbosscache-cluster-na=
me")
+ must be unique;
+
+
+
+ cache.jdbc.table.name must be unique
+ per datasource;
+
+
+
+ cache.jdbc.fqn.type must and
+ cache.jdbc.node.type must be configured according to used
+ database;
+
+
+
+ There is few ways how to configure CacheableLockManagerImpl, a=
nd
+ all of them configures JBoss-cache and JDBCCacheLoader.
+
+ See ht=
tp://community.jboss.org/wiki/JBossCacheJDBCCacheLoader
+
+
+
+ Simple JbossCache Configuraion
+
+ First one is - put JbossCache configuraion file path to
+ CacheableLockManagerImpl
+
+
+ This configuration is not so good, as you can think. Becau=
se
+ repository may contain many workspaces, and each workspace must
+ contain LockManager configuration, and LockManager config may
+ contain JbossCache config file. So total configuration is growing
+ up. But it is usefull if we want a single LockManager with speci=
al
+ configuration.
+
+
+ Config is:
+
+ <lock-manager class=3D"org.exoplatform.services.j=
cr.impl.core.lock.jbosscache.CacheableLockManagerImpl">
+ <properties>
+ <property name=3D"time-out" value=3D"15m" />
+ <property name=3D"jbosscache-configuration" value=3D"conf/standalo=
ne/cluster/test-jbosscache-lock-config.xml" />
+ </properties>
+</lock-manager>
+
+ test-jbosscache-lock-config.xml<?xml version=3D"1.0" encoding=3D"UTF-8"?>
+<jbosscache xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xml=
ns=3D"urn:jboss:jbosscache-core:config:3.2">
+
+ <locking useLockStriping=3D"false" concurrencyLevel=3D"50000" lockPare=
ntForChildInsertRemove=3D"false" lockAcquisitionTimeout=3D"20000" />
+
+ <clustering mode=3D"replication" clusterName=3D"JBoss-Cache-Lock-Clust=
er_Name">
+ <stateRetrieval timeout=3D"20000" fetchInMemoryState=3D"false" nonBlo=
cking=3D"true" />
+ <jgroupsConfig>
+
+ <TCP bind_addr=3D"127.0.0.1" start_port=3D"9800" loopback=3D"true" r=
ecv_buf_size=3D"20000000" send_buf_size=3D"640000" discard_incompatible_pac=
kets=3D"true"
+ max_bundle_size=3D"64000" max_bundle_timeout=3D"30" use_incoming_packe=
t_handler=3D"true" enable_bundling=3D"false" use_send_queues=3D"false" sock=
_conn_timeout=3D"300"
+ skip_suspected_members=3D"true" use_concurrent_stack=3D"true" thread_p=
ool.enabled=3D"true" thread_pool.min_threads=3D"1" thread_pool.max_threads=
=3D"25"
+ thread_pool.keep_alive_time=3D"5000" thread_pool.queue_enabled=3D"fals=
e" thread_pool.queue_max_size=3D"100" thread_pool.rejection_policy=3D"run"
+ oob_thread_pool.enabled=3D"true" oob_thread_pool.min_threads=3D"1" oob=
_thread_pool.max_threads=3D"8" oob_thread_pool.keep_alive_time=3D"5000"
+ oob_thread_pool.queue_enabled=3D"false" oob_thread_pool.queue_max_size=
=3D"100" oob_thread_pool.rejection_policy=3D"run" />
+ <MPING timeout=3D"2000" num_initial_members=3D"2" mcast_port=3D"3454=
0" bind_addr=3D"127.0.0.1" mcast_addr=3D"224.0.0.1" />
+
+
+ <MERGE2 max_interval=3D"30000" min_interval=3D"10000" />
+ <FD_SOCK />
+ <FD max_tries=3D"5" shun=3D"true" timeout=3D"10000" />
+ <VERIFY_SUSPECT timeout=3D"1500" />
+ <pbcast.NAKACK discard_delivered_msgs=3D"true" gc_lag=3D"0" retransm=
it_timeout=3D"300,600,1200,2400,4800" use_mcast_xmit=3D"false" />
+ <UNICAST timeout=3D"300,600,1200,2400,3600" />
+ <pbcast.STABLE desired_avg_gossip=3D"50000" max_bytes=3D"400000" sta=
bility_delay=3D"1000" />
+ <pbcast.GMS join_timeout=3D"5000" print_local_addr=3D"true" shun=3D"=
false" view_ack_collection_timeout=3D"5000" view_bundling=3D"true" />
+ <FRAG2 frag_size=3D"60000" />
+ <pbcast.STREAMING_STATE_TRANSFER />
+ <pbcast.FLUSH timeout=3D"0" />
+
+ </jgroupsConfig
+
+ <sync />
+ </clustering>
+
+ <loaders passivation=3D"false" shared=3D"true">
+ <preload>
+ <node fqn=3D"/" />
+ </preload>
+ <loader class=3D"org.jboss.cache.loader.JDBCCacheLoader" async=3D"fal=
se" fetchPersistentState=3D"false" ignoreModifications=3D"false" purgeOnSta=
rtup=3D"false">
+ <properties>
+ cache.jdbc.table.name=3Djcrlocks_ws
+ cache.jdbc.table.create=3Dtrue
+ cache.jdbc.table.drop=3Dfalse
+ cache.jdbc.table.primarykey=3Djcrlocks_ws_pk
+ cache.jdbc.fqn.column=3Dfqn
+ cache.jdbc.fqn.type=3DVARCHAR(512)
+ cache.jdbc.node.column=3Dnode
+ cache.jdbc.node.type=3D<BLOB> =
+ cache.jdbc.parent.column=3Dparent
+ cache.jdbc.datasource=3Djdbcjcr
+ </properties>
+ </loader>
+
+ </loaders>
+
+</jbosscache>
+
+ Configuration requirements:
+
+
+
+ <clustering mode=3D"replication"
+ clusterName=3D"JBoss-Cache-Lock-Cluster_Name"> - cluster name=
must
+ be unique;
+
+
+
+ cache.jdbc.table.name must be unique
+ per datasource;
+
+
+
+ cache.jdbc.node.type and
+ cache.jdbc.fqn.type must be configured
+ according to using database. See .
+
+
+
+
+
+ Template JBossCache Configuration
+
+ Second one is - use template JBoss-cache configuration for all
+ LockManagers
+
+ Lock template configuration
+
+ test-jbosscache-lock.xml
+
+ <?xml version=3D"1.0" encoding=3D"UTF-8"?>
+<jbosscache xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xml=
ns=3D"urn:jboss:jbosscache-core:config:3.1">
+
+ <locking useLockStriping=3D"false" concurrencyLevel=3D"50000" lockPa=
rentForChildInsertRemove=3D"false"
+ lockAcquisitionTimeout=3D"20000" />
+
+ <clustering mode=3D"replication" clusterName=3D"${jbosscache-cluster=
-name}">
+ <stateRetrieval timeout=3D"20000" fetchInMemoryState=3D"false" /&=
gt;
+ <jgroupsConfig multiplexerStack=3D"jcr.stack" />
+ <sync />
+ </clustering>
+
+ <loaders passivation=3D"false" shared=3D"true">
+ <!-- All the data of the JCR locks needs to be loaded at startup =
-->
+ <preload>
+ <node fqn=3D"/" />
+ </preload> =
+ <!--
+ For another cache-loader class you should use another template with
+ cache-loader specific parameters
+ ->
+ <loader class=3D"org.jboss.cache.loader.JDBCCacheLoader" async=3D=
q"false" fetchPersistentState=3D"false"
+ ignoreModifications=3D"false" purgeOnStartup=3D"false">
+ <properties>
+ cache.jdbc.table.name=3D${jbosscache-cl-cache.jdbc.table.name}
+ cache.jdbc.table.create=3D${jbosscache-cl-cache.jdbc.table.cre=
ate}
+ cache.jdbc.table.drop=3D${jbosscache-cl-cache.jdbc.table.drop}
+ cache.jdbc.table.primarykey=3D${jbosscache-cl-cache.jdbc.table=
.primarykey}
+ cache.jdbc.fqn.column=3D${jbosscache-cl-cache.jdbc.fqn.column}
+ cache.jdbc.fqn.type=3D${jbosscache-cl-cache.jdbc.fqn.type}
+ cache.jdbc.node.column=3D${jbosscache-cl-cache.jdbc.node.colum=
n}
+ cache.jdbc.node.type=3D${jbosscache-cl-cache.jdbc.node.type}
+ cache.jdbc.parent.column=3D${jbosscache-cl-cache.jdbc.parent.c=
olumn}
+ cache.jdbc.datasource=3D${jbosscache-cl-cache.jdbc.datasource}
+ </properties>
+ </loader>
+ </loaders>
+</jbosscache>
+
+ As you see, all configurable paramaters filled by templates and
+ will be replaced by LockManagers conf parameters:
+
+ <lock-manager class=3D"org.exoplatform.services.j=
cr.impl.core.lock.jbosscache.CacheableLockManagerImpl">
+ <properties>
+ <property name=3D"time-out" value=3D"15m" />
+ <property name=3D"jbosscache-configuration" value=3D"test-jbossca=
che-lock.xml" />
+ <property name=3D"jgroups-configuration" value=3D"udp-mux.xml" /&=
gt;
+ <property name=3D"jgroups-multiplexer-stack" value=3D"true" />
+ <property name=3D"jbosscache-cluster-name" value=3D"JCR-cluster-l=
ocks-ws" />
+ <property name=3D"jbosscache-cl-cache.jdbc.table.name" value=3D"j=
crlocks_ws" />
+ <property name=3D"jbosscache-cl-cache.jdbc.table.create" value=3D=
"true" />
+ <property name=3D"jbosscache-cl-cache.jdbc.table.drop" value=3D"f=
alse" />
+ <property name=3D"jbosscache-cl-cache.jdbc.table.primarykey" valu=
e=3D"jcrlocks_ws_pk" />
+ <property name=3D"jbosscache-cl-cache.jdbc.fqn.column" value=3D"f=
qn" />
+ <property name=3D"jbosscache-cl-cache.jdbc.fqn.type" value=3D"AUT=
O"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.node.column" value=3D"=
node" />
+ <property name=3D"jbosscache-cl-cache.jdbc.node.type" value=3D"AU=
TO"/>
+ <property name=3D"jbosscache-cl-cache.jdbc.parent.column" value=
=3D"parent" />
+ <property name=3D"jbosscache-cl-cache.jdbc.datasource" value=3D"j=
dbcjcr" />
+ </properties>
+</lock-manager>
+
+ Configuration requirements:
+
+ jbosscache-cl-cache.jdbc.fqn.column
+ and jbosscache-cl-cache.jdbc.node.type =
is
+ nothing else as cache.jdbc.fqn.type and cache.jdbc.node.type in
+ JBoss-Cache configuration. You can set those data types accord=
ing
+ to database type (See ) or set it as AUTO (or do not se=
t at
+ all) and data type will by detected automaticaly.
+
+
+
+ as you see, jgroups-configuration moved to separate conf=
ig
+ file - udp-mux.xml; In our case udp-mux.xml is common JGroup
+ config for all components (QueryHandler, cache, LockManager). =
But
+ we, still, can create own config.
+
+
+
+ our-udp-mux.xml<protoc=
ol_stacks>
+ <stack name=3D"jcr.stack">
+ <config>
+ <UDP mcast_addr=3D"228.10.10.10" mcast_port=3D"45588" tos=3D"8=
" ucast_recv_buf_size=3D"20000000"
+ ucast_send_buf_size=3D"640000" mcast_recv_buf_size=3D"25000000=
" mcast_send_buf_size=3D"640000" loopback=3D"false"
+ discard_incompatible_packets=3D"true" max_bundle_size=3D"64000=
" max_bundle_timeout=3D"30"
+ use_incoming_packet_handler=3D"true" ip_ttl=3D"2" enable_bundl=
ing=3D"true" enable_diagnostics=3D"true"
+ thread_naming_pattern=3D"cl" use_concurrent_stack=3D"true" thr=
ead_pool.enabled=3D"true" thread_pool.min_threads=3D"2"
+ thread_pool.max_threads=3D"8" thread_pool.keep_alive_time=3D"5=
000" thread_pool.queue_enabled=3D"true"
+ thread_pool.queue_max_size=3D"1000" thread_pool.rejection_poli=
cy=3D"discard" oob_thread_pool.enabled=3D"true"
+ oob_thread_pool.min_threads=3D"1" oob_thread_pool.max_threads=
=3D"8" oob_thread_pool.keep_alive_time=3D"5000"
+ oob_thread_pool.queue_enabled=3D"false" oob_thread_pool.queue_=
max_size=3D"100" oob_thread_pool.rejection_policy=3D"Run" />
+
+ <PING timeout=3D"2000" num_initial_members=3D"3" />
+ <MERGE2 max_interval=3D"30000" min_interval=3D"10000" />
+ <FD_SOCK />
+ <FD timeout=3D"10000" max_tries=3D"5" shun=3D"true" />
+ <VERIFY_SUSPECT timeout=3D"1500" />
+ <BARRIER />
+ <pbcast.NAKACK use_stats_for_retransmission=3D"false" exponent=
ial_backoff=3D"150" use_mcast_xmit=3D"true"
+ gc_lag=3D"0" retransmit_timeout=3D"50,300,600,1200" discard_de=
livered_msgs=3D"true" />
+ <UNICAST timeout=3D"300,600,1200" />
+ <pbcast.STABLE stability_delay=3D"1000" desired_avg_gossip=3D"=
50000" max_bytes=3D"1000000" />
+ <VIEW_SYNC avg_send_interval=3D"60000" />
+ <pbcast.GMS print_local_addr=3D"true" join_timeout=3D"3000" sh=
un=3D"false" view_bundling=3D"true" />
+ <FC max_credits=3D"500000" min_threshold=3D"0.20" />
+ <FRAG2 frag_size=3D"60000" />
+ <!--pbcast.STREAMING_STATE_TRANSFER /-->
+ <pbcast.STATE_TRANSFER />
+ <!-- pbcast.FLUSH /-->
+ </config>
+ </stack>
+</protocol_stacks>
+
+
+
+ Data Types in Different Databases
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/multilanguage-support.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/multilanguage-support.xml 2010-04-28 1=
9:10:24 UTC (rev 2883)
@@ -0,0 +1,170 @@
+
+
+
+
+
+ Multilanguage support in eXo JCR RDB backend
+
+
+ Intro
+
+ Whenever relational database is used to store multilingual text =
data
+ of eXo Java Content Repository we need to adapt configuration in order=
to
+ support UTF-8 encoding. Here is a short HOWTO instruction for several
+ supported RDBMS with examples.
+
+ The configuration file you have to modify:
+ .../webapps/portal/WEB-INF/conf/jcr/repository-configuration.xml
+
+
+ Datasource jdbcjcr used in examples can=
be
+ configured via InitialContextInitializer
+ component.
+
+
+
+
+ Oracle
+
+ In order to run multilanguage JCR on an Oracle backend Unicode
+ encoding for characters set should be applied to the database. Other
+ Oracle globalization parameters don't make any impact. The only proper=
ty
+ to modify is NLS_CHARACTERSET.
+
+ We have tested NLS_CHARACTERSET =3D
+ AL32UTF8 and it's works well for many European and
+ Asian languages.
+
+ Example of database configuration (used for JCR
+ testing):NLS_LANGUAGE AMERICAN
+NLS_TERRITORY AMERICA
+NLS_CURRENCY $
+NLS_ISO_CURRENCY AMERICA
+NLS_NUMERIC_CHARACTERS .,
+NLS_CHARACTERSET AL32UTF8
+NLS_CALENDAR GREGORIAN
+NLS_DATE_FORMAT DD-MON-RR
+NLS_DATE_LANGUAGE AMERICAN
+NLS_SORT BINARY
+NLS_TIME_FORMAT HH.MI.SSXFF AM
+NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
+NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
+NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
+NLS_DUAL_CURRENCY $
+NLS_COMP BINARY
+NLS_LENGTH_SEMANTICS BYTE
+NLS_NCHAR_CONV_EXCP FALSE
+NLS_NCHAR_CHARACTERSET AL16UTF16
+
+
+ JCR 1.12.x doesn't use NVARCHAR columns, so that the value of =
the
+ parameter NLS_NCHAR_CHARACTERSET does not matter for JCR.
+
+
+ Create database with Unicode encoding and use Oracle dialect for=
the
+ Workspace Container:
+
+ <workspace name=3D"collaboration">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage=
.jdbc.JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"oracle" />
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"max-buffer-size" value=3D"200k" />
+ <property name=3D"swap-directory" value=3D"target/temp/sw=
ap/ws" />
+ </properties>
+ .....
+
+
+
+ DB2
+
+ DB2 Universal Database (DB2 UDB) supports UTF-8
+ and UTF-16/UCS-2. When a Unicode database is created, CHAR,
+ VARCHAR, LONG VARCHAR data are stored in UTF-8 form. It's enough for J=
CR
+ multi-lingual support.
+
+ Example of UTF-8 database creation:DB2 CREATE DA=
TABASE dbname USING CODESET UTF-8 TERRITORY US
+
+ Create database with UTF-8 encoding and use db2 dialect for
+ Workspace Container on DB2 v.9 and higher:<workspac=
e name=3D"collaboration">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage=
.jdbc.JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"db2" />
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"max-buffer-size" value=3D"200k" />
+ <property name=3D"swap-directory" value=3D"target/temp/sw=
ap/ws" />
+ </properties>
+ .....
+
+
+ For DB2 v.8.x support change the property "dialect" to
+ db2v8.
+
+
+
+
+ MySQL
+
+ JCR MySQL-backend requires special dialect MySQL-UTF8 =
to be
+ used for internationalization support. But the database default charset
+ should be latin1 to use limited index space effectively (1000 bytes for
+ MyISAM engine, 767 for InnoDB). If database default charset is multiby=
te,
+ a JCR database initialization error is thrown concerning index creation
+ failure. In other words JCR can work on any singlebyte default charset=
of
+ database, with UTF8 supported by MySQL server. But we have tested it o=
nly
+ on latin1 database default charset.
+
+ Repository configuration, workspace container entry
+ example:<workspace name=3D"collaboration">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage=
.jdbc.JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"mysql-utf8" />
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"max-buffer-size" value=3D"200k" />
+ <property name=3D"swap-directory" value=3D"target/temp/sw=
ap/ws" />
+ </properties>
+ .....
+
+
+
+ PostgreSQL
+
+ On PostgreSQL-backend multilingual support can be enabled in
di=
fferent
+ ways:
+
+ Using the locale features of the operating system to provi=
de
+ locale-specific collation order, number formatting, translated
+ messages, and other aspects. UTF-8 is widely used on Linux
+ distributions by default, so it can be useful in such case.
+
+
+
+ Providing a number of different character sets defined in =
the
+ PostgreSQL server, including multiple-byte character sets, to
+ support storing text any language, and providing character set
+ translation between client and server. We recommend to use UTF-8
+ database charset, it will allow any-to-any conversations and make
+ this issue transparent for the JCR.
+
+
+
+ Create database with UTF-8 encoding and use PgSQL dialect for
+ Workspace Container:<workspace name=3D"collaboratio=
n">
+ <container class=3D"org.exoplatform.services.jcr.impl.storage=
.jdbc.JDBCWorkspaceDataContainer">
+ <properties>
+ <property name=3D"source-name" value=3D"jdbcjcr" />
+ <property name=3D"dialect" value=3D"pgsql" />
+ <property name=3D"multi-db" value=3D"false" />
+ <property name=3D"max-buffer-size" value=3D"200k" />
+ <property name=3D"swap-directory" value=3D"target/temp/sw=
ap/ws" />
+ </properties>
+ .....
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/query-handler-config.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/query-handler-config.xml 2010-04-28 19=
:10:24 UTC (rev 2883)
@@ -0,0 +1,194 @@
+
+
+
+
+
+ QueryHandler configuration
+
+
+ How does it work?
+
+ Lets talk about indexing content in cluster.
+
+ For couple of reasons, we can't replicate index. That's means, s=
ome
+ data added and indexed on one cluster node, will be replicated to anot=
her
+ cluster node, but will not be indexed on that node.
+
+ So, how do the indexing works in cluster
+ environment?
+
+ As, we can not index same data on all nodes of cluster, we must
+ index it on one node. Node, that can index data and do changes on luce=
ne
+ index, is called "coordinator". Coordinator-node is choosen automatica=
ly,
+ so we do not need special configuration for coordinator.
+
+ But, how can another nodes save their changes to lucene
+ index?
+
+ First of all, data is already saved and replicated to another
+ cluster-nodes, so we need only deliver message like "we need to index =
this
+ data" to coordinator. Thats why Jboss-cache is used.
+
+ All nodes of cluster writes messages into JBoss-cache but only
+ coordinator takes those messages and makes changes Lucene index.
+
+ How do the search works in cluster
+ environment?
+
+ Search engine do not works with indexer, coordinator, etc. Search
+ needs only lucene index. But only one cluster node can change lucene i=
ndex
+ - asking you. Yes - lucene index is shared. So, all cluster nodes must=
be
+ configured to use lucene index from shared directory.
+
+ A little bit about indexing process (no matter, cluster or not)
+ Indexer do not writes changes to FS lucene index immediately. At first,
+ Indexer writes changes to Volatile index. If Volatile index size become
+ 1Mb or more it is flushed to FS. Also there is timer, that flushes
+ volatile index by timeout. Volatile index timeout configured by
+ "max-volatile-time" paremeter.
+
+ See more about Search
+ Configuration.
+
+ Common scheme of Shared Index
+
+
+
+
+
+
+
+ Configuration
+
+
+ Common requirements
+
+ Now, lets see what we need to run Search engine in cluster
+ environment.
+
+ shared directory for storing Lucene index (i.e. NFS);
+
+
+
+ changes filter configured as
+ org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossC=
acheIndexChangesFilter;
+
+
+ This filter ignore changes on non-coordinator nodes, a=
nd
+ index changes on coordinator node.
+
+
+
+
+ configure JBoss-cache, course;
+
+
+
+
+
+ Query-handler configuration
+
+ Configuration example:<workspace name=3D"ws=
">
+ <query-handler class=3D"org.exoplatform.services.jcr.impl.core.query=
.lucene.SearchIndex">
+ <properties>
+ <property name=3D"index-dir" value=3D"shareddir/index/db1/ws" =
/>
+ <property name=3D"changesfilter-class"
+ value=3D"org.exoplatform.services.jcr.impl.core.query.jbosscac=
he.JBossCacheIndexChangesFilter" />
+ <property name=3D"jbosscache-configuration" value=3D"jbosscach=
e-indexer.xml" />
+ <property name=3D"jgroups-configuration" value=3D"udp-mux.xml"=
/>
+ <property name=3D"jgroups-multiplexer-stack" value=3D"true" /&=
gt;
+ <property name=3D"jbosscache-cluster-name" value=3D"JCR-cluste=
r-indexer-ws" />
+ <property name=3D"max-volatile-time" value=3D"60" />
+ </properties>
+ </query-handler>
+</workspace>
+ Config properties description
+
+
+
+
+ Property name
+
+ Description
+
+
+
+
+
+ index-dir
+
+ path to index
+
+
+
+ jbosscache-configuration
+
+ template of JBoss-cache configuration for all
+ query-handlers in repository
+
+
+
+ jgroups-configuration
+
+ jgroups-configuration is template configuration for=
all
+ components (search, cache, locks) [Add link to document
+ describing template configurations]
+
+
+
+ jgroups-multiplexer-stack
+
+ [TODO about jgroups-multiplexer-stack - add link to
+ JBoss doc]
+
+
+
+ jbosscache-cluster-name
+
+ cluster name (must be unique)
+
+
+
+ max-volatile-time
+
+ max time to live for Volatile Index
+
+
+
+
+
+
+
+
+
+ Parameter
+
+ Default
+
+ Description
+
+ Since
+
+
+
+
+
+ index-dir
+
+ none
+
+ The location of the index directory. This parameter is
+ mandatory. Up to 1.9 this parameter called "indexDir"
+
+ 1.0
+
+
+
+ use-compoundfile
+
+ true
+
+ Advises lucene to use compound files for the index
+ files.
+
+ 1.9
+
+
+
+ min-merge-docs
+
+ 100
+
+ Minimum number of nodes in an index until segments are
+ merged.
+
+ 1.9
+
+
+
+ volatile-idle-time
+
+ 3
+
+ Idle time in seconds until the volatile index part is m=
oved
+ to a persistent index even though minMergeDocs is not
+ reached.
+
+ 1.9
+
+
+
+ max-merge-docs
+
+ Integer.MAX_VALUE
+
+ Maximum number of nodes in segments that will be merged.
+ The default value changed in JCR 1.9 to Integer.MAX_VALUE.
+
+ 1.9
+
+
+
+ merge-factor
+
+ 10
+
+ Determines how often segment indices are merged.
+
+ 1.9
+
+
+
+ max-field-length
+
+ 10000
+
+ The number of words that are fulltext indexed at most p=
er
+ property.
+
+ 1.9
+
+
+
+ cache-size
+
+ 1000
+
+ Size of the document number cache. This cache maps uuid=
s to
+ lucene document numbers
+
+ 1.9
+
+
+
+ force-consistencycheck
+
+ false
+
+ Runs a consistency check on every startup. If false, a
+ consistency check is only performed when the search index dete=
cts
+ a prior forced shutdown.
+
+ 1.9
+
+
+
+ auto-repair
+
+ true
+
+ Errors detected by a consistency check are automatically
+ repaired. If false, errors are only written to the log.
+
+ 1.9
+
+
+
+ query-class
+
+ QueryImpl
+
+ Class name that implements the javax.jcr.query.Query
+ interface.This class must also extend from the class:
+ org.exoplatform.services.jcr.impl.core.query.AbstractQueryImpl=
.
+
+ 1.9
+
+
+
+ document-order
+
+ true
+
+ If true and the query does not contain an 'order by'
+ clause, result nodes will be in document order. For better
+ performance when queries return a lot of nodes set to
+ 'false'.
+
+ 1.9
+
+
+
+ result-fetch-size
+
+ Integer.MAX_VALUE
+
+ The number of results when a query is executed. Default
+ value: Integer.MAX_VALUE (-> all).
+
+ 1.9
+
+
+
+ excerptprovider-class
+
+ DefaultXMLExcerpt
+
+ The name of the class that implements
+ org.exoplatform.services.jcr.impl.core.query.lucene.ExcerptPro=
vider
+ and should be used for the rep:excerpt() function in a
+ query.
+
+ 1.9
+
+
+
+ support-highlighting
+
+ false
+
+ If set to true additional information is stored in the
+ index to support highlighting using the rep:excerpt()
+ function.
+
+ 1.9
+
+
+
+ synonymprovider-class
+
+ none
+
+ The name of a class that implements
+ org.exoplatform.services.jcr.impl.core.query.lucene.SynonymPro=
vider.
+ The default value is null (-> not set).
+
+ 1.9
+
+
+
+ synonymprovider-config-path
+
+ none
+
+ The path to the synonym provider configuration file. Th=
is
+ path interpreted relative to the path parameter. If there is a
+ path element inside the SearchIndex element, then this path is
+ interpreted relative to the root path of the path. Whether this
+ parameter is mandatory depends on the synonym provider
+ implementation. The default value is null (-> not set).
+
+ 1.9
+
+
+
+ indexing-configuration-path
+
+ none
+
+ The path to the indexing configuration file.
+
+ 1.9
+
+
+
+ indexing-configuration-class
+
+ IndexingConfigurationImpl
+
+ The name of the class that implements
+ org.exoplatform.services.jcr.impl.core.query.lucene.IndexingCo=
nfiguration.
+
+ 1.9
+
+
+
+ force-consistencycheck
+
+ false
+
+ If set to true a consistency check is performed dependi=
ng
+ on the parameter forceConsistencyCheck. If set to false no
+ consistency check is performed on startup, even if a redo log =
had
+ been applied.
+
+ 1.9
+
+
+
+ spellchecker-class
+
+ none
+
+ The name of a class that implements
+ org.exoplatform.services.jcr.impl.core.query.lucene.SpellCheck=
er.
+
+ 1.9
+
+
+
+ errorlog-size
+
+ 50(Kb)
+
+ The default size of error log file in Kb.
+
+ 1.9
+
+
+
+ upgrade-index
+
+ false
+
+ Allows JCR to convert an existing index into the new
+ format. Also it is possible to set this property via system
+ property, for example: -Dupgrade-index=3Dtrue Indexes before J=
CR
+ 1.12 will not run with JCR 1.12. Hence you have to run an
+ automatic migration: Start JCR with -Dupgrade-index=3Dtrue. Th=
e old
+ index format is then converted in the new index format. After =
the
+ conversion the new format is used. On the next start you don't
+ need this option anymore. The old index is replaced and a back
+ conversion is not possible - therefore better take a backup of=
the
+ index before. (Only for migrations from JCR 1.9 and
+ later.)
+
+ 1.12
+
+
+
+ analyzer
+
+ org.apache.lucene.analysis.standard.StandardAnalyzer
+
+ Class name of a lucene analyzer to use for fulltext
+ indexing of text.
+
+ 1.12
+
+
+
+
+
+
+
+ Global Search Index
+
+
+ Global Search Index Configuration
+
+ The global search index is configured in the above-mentioned
+ configuration file
+ (portal/WEB-INF/conf/jcr/repository-configuration.xml)
+ in the tag "query-handler".
+
+ <query-handler class=3D"org.exoplatform.services.=
jcr.impl.core.query.lucene.SearchIndex">
+
+ In fact when using Lucene you always should use the same analy=
zer
+ for indexing and for querying - otherwise the results are unpredicta=
ble.
+ You don't have to worry about this, eXo JCR does this for you
+ automatically. If you don't like the StandardAnalyzer configured by
+ default just replace it by your own.
+
+ If you don't have a handy QueryHandler you will learn how crea=
te a
+ customized Handler in 5 minutes.
+
+
+
+ Customized Search Indexes and Analyzers
+
+ By default Exo JCR uses the Lucene standard Analyzer to index
+ contents. This analyzer uses some standard filters in the method that
+ analyzes the content:public TokenStream tokenStream(=
String fieldName, Reader reader) {
+ StandardTokenizer tokenStream =3D new StandardTokenizer(reader, replac=
eInvalidAcronym);
+ tokenStream.setMaxTokenLength(maxTokenLength);
+ TokenStream result =3D new StandardFilter(tokenStream);
+ result =3D new LowerCaseFilter(result);
+ result =3D new StopFilter(result, stopSet);
+ return result;
+ }
+
+ The first one (StandardFilter) removes 's (as 's in
+ "Peter's") from the end of words and removes dots from
+ acronyms.
+
+
+
+ The second one (LowerCaseFilter) normalizes token text to
+ lower case.
+
+
+
+ The last one (StopFilter) removes stop words from a token
+ stream. The stop set is defined in the analyzer.
+
+
+
+ For specific cases, you may wish to use additional filters like
+ ISOLatin1AccentFilter, which replaces accented
+ characters in the ISO Latin 1 character set (ISO-8859-1) by their
+ unaccented equivalents.
+
+ In order to use a different filter, you have to create a new
+ analyzer, and a new search index to use the analyzer. You put it in a
+ jar, which is deployed with your application.
+
+
+ Create the filter
+
+ The ISOLatin1AccentFilter is not present in the current Luce=
ne
+ version used by Exo. You can use the attached file. You can also
+ create your own filter, the relevant method ispubl=
ic final Token next(final Token reusableToken) throws java.io.IOException=
programlisting>which
+ defines how chars are read and used by the filter.
+
+
+
+ Create the analyzer
+
+ The analyzer have to extends
+ org.apache.lucene.analysis.standard.StandardAnalyzer, and overload=
the
+ methodpublic TokenStream tokenStream(String fieldN=
ame, Reader reader)to
+ put your own filters. You can have a glance at the example analyzer
+ attached to this article.
+
+
+
+ Create the search index
+
+ Now, we have the analyzer, we have to write the SearchIndex,
+ which will use the analyzer. Your have to extends
+ org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex. Y=
ou
+ have to write the constructor, to set the right analyzer, and the
+ methodpublic Analyzer getAnalyzer() {
+ return MyAnalyzer;
+ }to return your analyzer. You can see the attached
+ SearchIndex.
+
+
+ Since 1.12 version we can set Analyzer directly in
+ configuration. So, creation new SearchIndex only for new Analyze=
r is
+ redundant.
+
+
+
+
+ Configure your application to use your SearchIndex
+
+ In
+ portal/WEB-INF/conf/jcr/repository-configuration.xml,
+ you have to replace each<query-handler class=3D=
"org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">by
+ your own class<query-handler class=3D"mypackage=
.indexation.MySearchIndex">
+
+
+
+ Configure your application to use your Analyzer
+
+ In
+ portal/WEB-INF/conf/jcr/repository-configuration.xml,
+ you have to add parameter "analyzer" to each query-handler
+ config:<query-handler class=3D"org.exoplatform.=
services.jcr.impl.core.query.lucene.SearchIndex">
+ <properties>
+ ...
+ <property name=3D"analyzer" value=3D"org.exoplatform.services.jcr=
.impl.core.MyAnalyzer"/>
+ ...
+ </properties>
+</query-handler>
+
+ When you start exo, your SearchIndex will start to index
+ contents with the specified filters.
+
+
+
+
+
+ Index Adjustments
+
+
+ IndexingConfiguration
+
+ Starting with version 1.9, the default search index implementa=
tion
+ in JCR allows you to control which properties of a node are indexed.=
You
+ also can define different analyzers for different nodes.
+
+ The configuration parameter is called indexingConfiguration and
+ per default is not set. This means all properties of a node are
+ indexed.
+
+ If you wish to configure the indexing behavior you need to add=
a
+ parameter to the query-handler element in your configuration
+ file.
+
+ <param name=3D"indexing-configuration-path" value=
=3D"/indexing_configuration.xml"/>
+
+
+
+ Index rules
+
+
+ Node Scope Limit
+
+ To optimize the index size you can limit the node scope so t=
hat
+ only certain properties of a node type are
+ indexed.
+
+ With the below configuration only properties named Text are
+ indexed for nodes of type nt:unstructured. This configuration also
+ applies to all nodes whose type extends from nt:unstructured.
+
+ <?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured">
+ <property>Text</property>
+ </index-rule>
+</configuration>
+
+ Please note that you have to declare the namespace
+ prefixes in the configuration element that you are using
+ throughout the XML file!
+
+
+
+ Index Boost Value
+
+ It is also possible to configure a boost value
+ for the nodes that match the index rule. The default boost value is
+ 1.0. Higher boost values (a reasonable range is 1.0 - 5.0) will yi=
eld
+ a higher score value and appear as more relevant.
+
+ <?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"2.0">
+ <property>Text</property>
+ </index-rule>
+</configuration>
+
+ If you do not wish to boost the complete node but only certa=
in
+ properties you can also provide a boost value for the listed
+ properties:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured">
+ <property boost=3D"3.0">Title</property>
+ <property boost=3D"1.5">Text</property>
+ </index-rule>
+</configuration>
+
+
+
+ Conditional Index Rules
+
+ You may also add a condition to the index r=
ule
+ and have multiple rules with the same nodeType. The first index ru=
le
+ that matches will apply and all remaining ones are
+ ignored:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"2.0"
+ condition=3D"@priority =3D 'high'">
+ <property>Text</property>
+ </index-rule>
+ <index-rule nodeType=3D"nt:unstructured">
+ <property>Text</property>
+ </index-rule>
+</configuration>
+
+ In the above example the first rule only applies if the
+ nt:unstructured node has a priority property with a value 'high'. =
The
+ condition syntax supports only the equals operator and a string
+ literal.
+
+ You may also reference properties in the condition that are =
not
+ on the current node:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"2.0"
+ condition=3D"ancestor::*/@priority =3D 'high'">
+ <property>Text</property>
+ </index-rule>
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"0.5"
+ condition=3D"parent::foo/@priority =3D 'low'">
+ <property>Text</property>
+ </index-rule>
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"1.5"
+ condition=3D"bar/@priority =3D 'medium'">
+ <property>Text</property>
+ </index-rule>
+ <index-rule nodeType=3D"nt:unstructured">
+ <property>Text</property>
+ </index-rule>
+</configuration>
+
+ The indexing configuration also allows you to specify the ty=
pe
+ of a node in the condition. Please note however that the type match
+ must be exact. It does not consider sub types of the specified node
+ type.
+
+ <?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured"
+ boost=3D"2.0"
+ condition=3D"element(*, nt:unstructured)/@priority =3D 'high=
'">
+ <property>Text</property>
+ </index-rule>
+</configuration>
+
+
+
+ Exclusion from the Node Scope Index
+
+ Per default all configured properties are fulltext indexed if
+ they are of type STRING and included in the node scope index. A no=
de
+ scope search finds normally all nodes of an index. That is, the se=
lect
+ jcr:contains(., 'foo') returns all nodes that have a string proper=
ty
+ containing the word 'foo'. You can exclude explicitly a property f=
rom
+ the node scope index:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <index-rule nodeType=3D"nt:unstructured">
+ <property nodeScopeIndex=3D"false">Text</property>
+ </index-rule>
+</configuration>
+
+
+
+
+ Index Aggregates
+
+ Sometimes it is useful to include the contents of descendant n=
odes
+ into a single node to easier search on content that is scattered acr=
oss
+ multiple nodes.
+
+ JCR allows you to define index aggregates based on relative pa=
th
+ patterns and primary node types.
+
+ The following example creates an index aggregate on nt:file th=
at
+ includes the content of the jcr:content node:<?xm=
l version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:jcr=3D"http://www.jcp.org/jcr/1.0"
+ xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <aggregate primaryType=3D"nt:file">
+ <include>jcr:content</include>
+ </aggregate>
+</configuration>
+
+ You can also restrict the included nodes to a certain
+ type:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:jcr=3D"http://www.jcp.org/jcr/1.0"
+ xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <aggregate primaryType=3D"nt:file">
+ <include primaryType=3D"nt:resource">jcr:content</include>
+ </aggregate>
+</configuration>
+
+ You may also use the * to match all child nodes:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:jcr=3D"http://www.jcp.org/jcr/1.0"
+ xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <aggregate primaryType=3D"nt:file">http://wiki.exoplatform.com/xwi=
ki/bin/edit/JCR/Search+Configuration
+ <include primaryType=3D"nt:resource">*</include>
+ </aggregate>
+</configuration>
+
+ If you wish to include nodes up to a certain depth below the
+ current node you can add multiple include elements. E.g. the nt:file
+ node may contain a complete XML document under
+ jcr:content:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:jcr=3D"http://www.jcp.org/jcr/1.0"
+ xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <aggregate primaryType=3D"nt:file">
+ <include>*</include>
+ <include>*/*</include>
+ <include>*/*/*</include>
+ </aggregate>
+</configuration>
+
+
+
+ Property-Level Analyzers
+
+
+ Example
+
+ In this configuration section you define how a property has =
to
+ be analyzed. If there is an analyzer configuration for a property,
+ this analyzer is used for indexing and searching of this property.=
For
+ example:<?xml version=3D"1.0"?>
+<!DOCTYPE configuration SYSTEM "http://www.exoplatform.org/dtd/indexing=
-configuration-1.0.dtd">
+<configuration xmlns:nt=3D"http://www.jcp.org/jcr/nt/1.0">
+ <analyzers> =
+ <analyzer class=3D"org.apache.lucene.analysis.KeywordAnalyzer"&=
gt;
+ <property>mytext</property>
+ </analyzer>
+ <analyzer class=3D"org.apache.lucene.analysis.WhitespaceAnalyze=
r">
+ <property>mytext2</property>
+ </analyzer>
+ </analyzers> =
+</configuration>
+
+ The configuration above means that the property "mytext" for=
the
+ entire workspace is indexed (and searched) with the Lucene
+ KeywordAnalyzer, and property "mytext2" with the WhitespaceAnalyze=
r.
+ Using different analyzers for different languages is particularly
+ useful.
+
+ The WhitespaceAnalyzer tokenizes a property, the KeywordAnal=
yzer
+ takes the property as a whole.
+
+
+
+ Characteristics of Node Scope Searches
+
+ When using analyzers, you may encounter an unexpected behavi=
or
+ when searching within a property compared to searching within a no=
de
+ scope. The reason is that the node scope always uses the global
+ analyzer.
+
+ Let's suppose that the property "mytext" contains the text :
+ "testing my analyzers" and that you haven't configured any analyze=
rs
+ for the property "mytext" (and not changed the default analyzer in
+ SearchIndex).
+
+ If your query is for example:xpath =3D "//*[=
jcr:contains(mytext,'analyzer')]"
+
+ This xpath does not return a hit in the node with the proper=
ty
+ above and default analyzers.
+
+ Also a search on the node scopexpath =3D "//=
*[jcr:contains(.,'analyzer')]"won't
+ give a hit. Realize, that you can only set specific analyzers on a
+ node property, and that the node scope indexing/analyzing is always
+ done with the globally defined analyzer in the SearchIndex
+ element.
+
+ Now, if you change the analyzer used to index the "mytext"
+ property above to<analyzer class=3D"org.apache.=
lucene.analysis.Analyzer.GermanAnalyzer">
+ <property>mytext</property>
+</analyzer>and you do the same search again, then
+ forxpath =3D "//*[jcr:contains(mytext,'analyzer')]=
"you
+ would get a hit because of the word stemming (analyzers -
+ analyzer).
+
+ The other search,xpath =3D "//*[jcr:contains=
(.,'analyzer')]"still
+ would not give a result, since the node scope is indexed with the
+ global analyzer, which in this case does not take into account any
+ word stemming.
+
+ In conclusion, be aware that when using analyzers for specif=
ic
+ properties, you might find a hit in a property for some search tex=
t,
+ and you do not find a hit with the same search text in the node sc=
ope
+ of the property!
+
+
+ Both index rules and index aggregates influence how conten=
t is
+ indexed in JCR. If you change the configuration the existing con=
tent
+ is not automatically re-indexed according to the new rules. You
+ therefore have to manually re-index the content when you change =
the
+ configuration!
+
+
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/statistics.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/statistics.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/statistics.xml 2010-04-28 19:10:24 UTC=
(rev 2883)
@@ -0,0 +1,465 @@
+
+
+
+
+
+ eXo JCR statistics
+
+
+ Statistics on the Database Access Layer
+
+ In order to have a better idea of the time spent into the databa=
se
+ access layer, it cans be interesting to get some statistics on that pa=
rt
+ of the code, knowing that most of the time spent into eXo JCR is mainly
+ the database access. This statistics will then allow you to identify
+ without using any profiler what is anormally slow in this layer, which
+ could help to fix the problem quickly.
+
+ In case you use
+ org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJ=
DBCWorkspaceDataContainer
+ or
+ org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDat=
aContainer
+ as WorkspaceDataContainer, you can get statistics on the
+ time spent into the database access layer. The database access layer (=
in
+ eXo JCR) is represented by the methods of the interface
+ org.exoplatform.services.jcr.storage.WorkspaceStorageConnection=
,
+ so for all the methods defined in this interface, we can have the
+ following figures:
+
+
+
+ The minimum time spent into the method.
+
+
+
+ The maximum time spent into the method.
+
+
+
+ The average time spent into the method.
+
+
+
+ The total amount of time spent into the method.
+
+
+
+ The total amount of times the method has been called.
+
+
+
+ Those figures are also available globaly for all the methods whi=
ch
+ gives us the global behavior of this layer.
+
+ If you want to enable the statistics, you just need to set the J=
VM
+ parameter called
+ JDBCWorkspaceDataContainer.statistics.enabled to
+ true. The corresponding CSV file is
+ StatisticsJDBCStorageConnection-${creation-timestamp}.csv
+ for more details about how the csv files are managed please refer to t=
he
+ section dedicated to the statistics manager.
+
+ The format of each column header is ${method-alias}-${metric-ali=
as}.
+ The metric alias are described in the statistics manager section.
+
+
+ Method Alias
+
+
+
+
+ global
+
+ This is the alias for all the methods.
+
+
+
+ getItemDataById
+
+ This is the alias for the method
+ getItemData(String identifier).
+
+
+
+ getItemDataByNodeDataNQPathEntry
+
+ This is the alias for the method
+ getItemData(NodeData parentData, QPathEntry
+ name).
+
+
+
+ getChildNodesData
+
+ This is the alias for the method
+ getChildNodesData(NodeData parent).
+
+
+
+ getChildNodesCount
+
+ This is the alias for the method
+ getChildNodesCount(NodeData parent).
+
+
+
+ getChildPropertiesData
+
+ This is the alias for the method
+ getChildPropertiesData(NodeData
+ parent).
+
+
+
+ listChildPropertiesData
+
+ This is the alias for the method
+ listChildPropertiesData(NodeData
+ parent).
+
+
+
+ getReferencesData
+
+ This is the alias for the method
+ getReferencesData(String
+ nodeIdentifier).
+
+
+
+ commit
+
+ This is the alias for the method
+ commit().
+
+
+
+ addNodeData
+
+ This is the alias for the method add(NodeData
+ data).
+
+
+
+ addPropertyData
+
+ This is the alias for the method add(Property=
Data
+ data).
+
+
+
+ updateNodeData
+
+ This is the alias for the method update(NodeD=
ata
+ data).
+
+
+
+ updatePropertyData
+
+ This is the alias for the method
+ update(PropertyData data).
+
+
+
+ deleteNodeData
+
+ This is the alias for the method delete(NodeD=
ata
+ data).
+
+
+
+ deletePropertyData
+
+ This is the alias for the method
+ delete(PropertyData data).
+
+
+
+ renameNodeData
+
+ This is the alias for the method rename(NodeD=
ata
+ data).
+
+
+
+ rollback
+
+ This is the alias for the method
+ rollback().
+
+
+
+ isOpened
+
+ This is the alias for the method
+ isOpened().
+
+
+
+ close
+
+ This is the alias for the method
+ close().
+
+
+
+
+
+
+
+ Statistics on the JCR API accesses
+
+ In order to know exactly how your application uses eXo JCR, it c=
ans
+ be interesting to register all the JCR API accesses in order to easily
+ create real life test scenario based on pure JCR calls and also to tune
+ your eXo JCR to better fit your requirements.
+
+ In order to allow you to specify into the configuration which pa=
rt
+ of eXo JCR needs to be monitored whitout applying any changes in your =
code
+ and/or building anything, we choosed to rely on the Load-time Weaving
+ proposed by AspectJ.
+
+ To enable this feature, you will have to add in your classpath t=
he
+ following jar files:
+
+
+
+ exo.jcr.component.statistics-X.Y.Z.jar
+ corresponding to your eXo JCR version that you can get from the jb=
oss
+ maven repository http://repository.jboss.com/maven2/org/exoplatfor=
m/jcr/exo.jcr.component.statistics.
+
+
+
+ aspectjrt-1.6.8.jar that you can get from the main maven
+ repository http://repo2.maven.org/maven2/org/aspectj/aspectj=
rt.
+
+
+
+ You will also need to get aspectjweaver-1.6.8.jar from the main
+ maven repository http://repo2.maven.org/maven2/org/aspectj/aspectjweaver.
+ At this stage, to enable the statistics on the JCR API accesses, you w=
ill
+ need to add the JVM parameter
+ -javaagent:${pathto}/aspectjweaver-1.6.8.jar to y=
our
+ command line, for more details please refer to http://www.eclipse.org/aspectj/doc/released/devguide/ltw-c=
onfiguration.html.
+
+ By default, the configuration will collect statistcs on all the
+ methods of the internal interfaces
+ org.exoplatform.services.jcr.core.ExtendedSession=
and
+ org.exoplatform.services.jcr.core.ExtendedNode, a=
nd
+ the JCR API interface javax.jcr.Property. To add
+ and/or remove some interfaces to monitor, you have two configuration f=
iles
+ to change that are bundled into the jar
+ exo.jcr.component.statistics-X.Y.Z.jar, which are
+ conf/configuration.xml and
+ META-INF/aop.xml.
+
+ The file content below is the content of
+ conf/configuration.xml that you will need to modi=
fy
+ to add and/or remove the full qualified name of the interfaces to moni=
tor,
+ into the list of parameter values of the init param called
+ targetInterfaces.
+
+ <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_0.xsd"
+ xmlns=3D"http://www.exoplaform.org/xml/ns/kernel_1_0.xsd">
+
+ <component>
+ <type>org.exoplatform.services.jcr.statistics.JCRAPIAspectConfig&=
lt;/type>
+ <init-params>
+ <values-param>
+ <name>targetInterfaces</name>
+ <value>org.exoplatform.services.jcr.core.ExtendedSession</=
value>
+ <value>org.exoplatform.services.jcr.core.ExtendedNode</val=
ue>
+ <value>javax.jcr.Property</value>
+ </values-param>
+ </init-params>
+ </component>
+</configuration>
+
+ The file content below is the content of
+ META-INF/aop.xml that you will to need to modify =
to
+ add and/or remove the full qualified name of the interfaces to monitor,
+ into the expression filter of the pointcut called
+ JCRAPIPointcut. As you can see below, by default =
only
+ JCR API calls from the exoplatform packages are took into account, don=
't
+ hesistate to modify also this filter to add your own package names.
+
+ <aspectj>
+ <aspects>
+ <concrete-aspect name=3D"org.exoplatform.services.jcr.statistics.JC=
RAPIAspectImpl" extends=3D"org.exoplatform.services.jcr.statistics.JCRAPIAs=
pect">
+ <pointcut name=3D"JCRAPIPointcut"
+ expression=3D"(target(org.exoplatform.services.jcr.core.ExtendedSe=
ssion) || target(org.exoplatform.services.jcr.core.ExtendedNode) || target(=
javax.jcr.Property)) && call(public * *(..))" />
+ </concrete-aspect>
+ </aspects>
+ <weaver options=3D"-XnoInline">
+ <include within=3D"org.exoplatform..*" />
+ </weaver>
+</aspectj>
+
+ The corresponding CSV files are of type
+ Statistics${interface-name}-${creation-timestamp}.csv
+ for more details about how the csv files are managed please refer to t=
he
+ section dedicated to the statistics manager.
+
+ The format of each column header is ${method-alias}-${metric-ali=
as}.
+ The method alias will be of type ${method-name}(list of parameter types
+ separeted by ; to be compatible with the CSV format).
+
+ The metric alias are described in the statistics manager
+ section.
+
+ Please note that this feature will affect the performances of =
eXo
+ JCR so it must be used with caution.
+
+
+
+ Statistics Manager
+
+ The statistics manager manages all the statistics provided by eXo
+ JCR, it is responsible of printing the data into the CSV files but als=
o to
+ expose the statistics through JMX and/or Rest.
+
+ The statistics manager will create all the CSV files for each
+ category of statistics that it manages, the format of those files is
+ Statistics${category-name}-${creation-timestamp}.csv.
+ Those files will be created into the user directory if it is possible
+ otherwise it will create them into the temporary directory. The format=
of
+ those files is CSV (i.e. Comma-Seperated Values), one n=
ew
+ line will be added regularily (every 5 seconds by default) and one last
+ line will be added at JVM exit. Each line, will be composed of the 5
+ figures described below for each method and globaly for all the
+ methods.
+
+
+ Metric Alias
+
+
+
+
+ Min
+
+ The minimum time spent into the method.
+
+
+
+ Max
+
+ The maximum time spent into the method.
+
+
+
+ Total
+
+ The total amount of time spent into the method.
+
+
+
+ Avg
+
+ The average time spent into the method.
+
+
+
+ Times
+
+ The total amount of times the method has been
+ called.
+
+
+
+
You can disable the persistence of the statistics by setting=
the
+ JVM parameter called
+ JCRStatisticsManager.persistence.enabled to
+ false, by default it is set to
+ true. You can aslo define the period of time betw=
een
+ each record (i.e. line of data into the file) by setting the JVM param=
eter
+ called JCRStatisticsManager.persistence.timeout to
+ your expected value expressed in milliseconds, by default it is set to
+ 5000.
+
+ You can also access to the statistics thanks to JMX, the availab=
le
+ methods are the following:
+
+
+ JMX Methods
+
+
+
+
+ getMin
+
+ Gives the minimum time spent into the method
+ corresponding to the given category name and statistics name.
+ The expected arguments are the name of the category of the
+ statistics (e.g. JDBCStorageConnection) and the name of the
+ expected method or global for the global value.
+
+
+
+ getMax
+
+ Gives the maximum time spent into the method
+ corresponding to the given category name and statistics name.
+ The expected arguments are the name of the category of the
+ statistics (e.g. JDBCStorageConnection) and the name of the
+ expected method or global for the global value.
+
+
+
+ getTotal
+
+ Gives the total amount of time spent into the method
+ corresponding to the given category name and statistics name.
+ The expected arguments are the name of the category of the
+ statistics (e.g. JDBCStorageConnection) and the name of the
+ expected method or global for the global value.
+
+
+
+ getAvg
+
+ Gives the average time spent into the method
+ corresponding to the given category name and statistics name.
+ The expected arguments are the name of the category of the
+ statistics (e.g. JDBCStorageConnection) and the name of the
+ expected method or global for the global value.
+
+
+
+ getTimes
+
+ Gives the total amount of times the method has been
+ called corresponding to the given category name and statisti=
cs
+ name. The expected arguments are the name of the category of=
the
+ statistics (e.g. JDBCStorageConnection) and the name of the
+ expected method or global for the global value.
+
+
+
+ reset
+
+ Reset the statistics for the given category name and
+ statistics name. The expected arguments are the name of the
+ category of the statistics (e.g. JDBCStorageConnection) and =
the
+ name of the expected method or global for the global
+ value.
+
+
+
+ resetAll
+
+ Reset all the statistics for the given category name.=
The
+ expected argument is the name of the category of the statist=
ics
+ (e.g. JDBCStorageConnection).
+
+
+
+
The full name of the related MBean is
+ exo:service=3Dstatistic, view=3Djcr.
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml =
(rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR/transaction-manager-lookup.xml 2010-04=
-28 19:10:24 UTC (rev 2883)
@@ -0,0 +1,24 @@
+
+
+
+
+
+ TransactionManagerLookup
+
+
+ Configuration
+
+ It's JBossCache class registered as eXo container component in
+ configuration.xml file.
+
+ <component>
+ <key>org.jboss.cache.transaction.TransactionManagerLookup</k=
ey>
+ <type>org.jboss.cache.transaction.JBossStandaloneJTAManagerLook=
up</type>
+ </component>
+
+ JBossStandaloneJTAManagerLookup used in standalone environment. =
Bur
+ for Application Server environment use GenericTransactionManagerLookup.
+
+
+
Added: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Ref=
erence_Guide/en-US/modules/Advanced/JCR.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR.xml (rev 0)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR.xml 2010-04-28 19:10:24 UTC (rev 2883)
@@ -0,0 +1,58 @@
+
+
+
+ eXoJCR
+
+
+
+
+
+ =
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/Advanced.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced.xml 2010-04-28 18:20:18 UTC (rev 2882)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced.xml 2010-04-28 19:10:24 UTC (rev 2883)
@@ -6,5 +6,6 @@
Advanced Development
+
=
--===============2399905953526589523==--
From do-not-reply at jboss.org Wed Apr 28 15:26:08 2010
Content-Type: multipart/mixed; boundary="===============2270319393800809619=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2884 - in
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules:
Advanced and 2 other directories.
Date: Wed, 28 Apr 2010 15:26:08 -0400
Message-ID: <201004281926.o3SJQ8wk007797@svn01.web.mwc.hst.phx2.redhat.com>
--===============2270319393800809619==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: thomas.heute(a)jboss.com
Date: 2010-04-28 15:26:07 -0400 (Wed, 28 Apr 2010)
New Revision: 2884
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/Advanced.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/Advanced/Foundations.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/Advanced/JCR.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.x=
ml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurati=
on.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfigurati=
on.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.=
xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunic=
ation.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/Skinning.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortletDevelopment.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortletDevelopment/Standard.xml
Log:
Splitting into parts, makes 1 level less in sections
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/Advanced/Foundations.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/Foundations.xml 2010-04-28 19:10:24 UTC (r=
ev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/Foundations.xml 2010-04-28 19:26:07 UTC (r=
ev 2884)
@@ -3,7 +3,7 @@
%BOOK_ENTITIES;
]>
-
+
=
Foundations
@@ -730,4 +730,4 @@
=
=
-
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/Advanced/JCR.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR.xml 2010-04-28 19:10:24 UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced/JCR.xml 2010-04-28 19:26:07 UTC (rev 2884)
@@ -1,7 +1,7 @@
-
+eXoJCR
=
=
-
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/Advanced.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced.xml 2010-04-28 19:10:24 UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Advanced.xml 2010-04-28 19:26:07 UTC (rev 2884)
@@ -3,9 +3,9 @@
%BOOK_ENTITIES;
]>
-
+Advanced Development
-
+
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactiv=
ation.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.=
xml 2010-04-28 19:10:24 UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.=
xml 2010-04-28 19:26:07 UTC (rev 2884)
@@ -3,7 +3,7 @@
%BOOK_ENTITIES;
]>
-
+Deactivation of the Ajax Loading Mask Layer
-
+
=
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2010-04-28 19:10=
:24 UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2010-04-28 19:26=
:07 UTC (rev 2884)
@@ -3,7 +3,7 @@
%BOOK_ENTITIES;
]>
-
+RTL (Right To Left) Framework
The text orientation depends on the current locale setting. The orientat=
ion is a Java 5 enum that provides a set of functionalities:
@@ -203,6 +203,6 @@
=
-
+
=
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-28 19:10:24 =
UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-28 19:26:07 =
UTC (rev 2884)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
-
+Skinning the portal
=
@@ -866,4 +866,4 @@
-
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/UploadComponent.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml 2010-04-28 19=
:10:24 UTC (rev 2883)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml 2010-04-28 19=
:26:07 UTC (rev 2884)
@@ -3,7 +3,7 @@
%BOOK_ENTITIES;
]>
-
+Upload Component**/selenium/Test_*.java
- **/selenium/Test_*PRL_22*.java**/selenium/Test_*PRL_32*.java
--===============4623362838509680443==--
From do-not-reply at jboss.org Fri Apr 30 03:57:05 2010
Content-Type: multipart/mixed; boundary="===============1277982051600492718=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2909 - in
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Reference_Guide/en-US/modules:
PortalDevelopment and 1 other directory.
Date: Fri, 30 Apr 2010 03:57:04 -0400
Message-ID: <201004300757.o3U7v4c6013286@svn01.web.mwc.hst.phx2.redhat.com>
--===============1277982051600492718==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-04-30 03:57:03 -0400 (Fri, 30 Apr 2010)
New Revision: 2909
Modified:
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/Introduction.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.x=
ml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurati=
on.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfigurati=
on.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.=
xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunic=
ation.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/Skinning.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml
portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Referen=
ce_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml
Log:
JBEPP-276: First edits of Part 1
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Introduction.xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/Introduction.xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -10,10 +10,10 @@
-
+
-
+
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactiv=
ation.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.=
xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/AjaxLoadingMaskLayerDeactivation.=
xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -36,8 +36,8 @@
However, the mask layer may need to be deactivated in instances where t=
he portal requires user instructions before previous instructions have been=
carried out.
-
- How to deactivate the ajax-loading mask
+
+ How to Deactivate the Ajax-Loading Mask
Generate a script to make an asynchronous ajax-call. Use the uicomponent.doAsync() method rather than the uicomponen=
t.event() method.
@@ -57,15 +57,16 @@
This request is asynchronous and the ajax-loading mask will not deplo=
yed.
+ Asynchronous Requests Using uicomponent.event()
- An asynchronous request can still be made using the uicompo=
nent.event(). When using this method, however, the asyncparam mus=
t be added manually.
+ An asynchronous request can still be made using the uicompo=
nent.event(). When using this method, however, the async=
param must be added manually.
=
- The GUI will be blocked to ensure a user can only request one action at=
a time and while the request seems to be synchronous, all ajax requests ar=
e, in fact always asynchronous. For further information refer to .
+ The GUI will be blocked to ensure a user can only request one action at=
a time and while the request seems to be synchronous, all ajax requests ar=
e, in fact, always asynchronous. For further information refer to .
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 20=
10-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 20=
10-04-30 07:57:03 UTC (rev 2909)
@@ -8,8 +8,14 @@
Overview
- &PRODUCT; default home page URL is http://{hostname}:{port}/po=
rtal/. There may be multiple independent portals deployed in para=
llel at any given time, each of which has its root context (i.e.: =
http://{hostname}:{port}/sample-portal/). Each portal is internal=
ly composed of one or more, what we again call 'portals'. There needs to be=
at least one such portal - the default one is called 'classic'. When acces=
sing &PRODUCT; default home page URL, you are automatically redirected to '=
classic' portal. The default portal performs another important task. When s=
tarting up &PRODUCT; for the first time, its JCR database will be empty (th=
at's where portals keep their runtime-configurable settings). It's the defa=
ult portal that's used to detect this, and to trigger automatic data initia=
lization.
+ &PRODUCT; default home page URL is http://{hostname}:{port}/po=
rtal/. There may be multiple independent portals deployed in para=
llel at any given time, each of which has its root context (i.e.: =
http://{hostname}:{port}/sample-portal/).
+
+ Each portal is internally composed of one or more 'portals'. This is be=
cause there needs to be at least one such portal available. The default one=
is called 'classic'. When accessing &PRODUCT;'s default home page URL, you=
are automatically directed to the 'classic' portal.
+
+
+ The default portal performs another important task. When starting up &=
PRODUCT; for the first time, its JCR database (where portal runtime-configu=
rable settings are stored) will be empty . The default portal detects this =
and triggers automatic data initialization.
+
=
@@ -42,11 +48,12 @@
In this example the classic portal h=
as been set as the default.
-
-
- Components, component-plugins, and init-params are explained in Founda=
tions chapter. For now just note how NewPortalConfigListener component-plugin is used to add configuration to UserPortalCo=
nfigService, which is designed in this way to allow other compone=
nts to add configuration to it.
-
-
+
+ Notice that the NewPortalConfigListenerco=
mponent-plugin is used to add configuration to UserPort=
alConfigService, which is designed in this way to allow other com=
ponents to add configuration to it.
+
+
+ Components, component-plugins, and init-params are explained in a later chapter of=
this document.
+
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConf=
iguration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurat=
ion.xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfigurat=
ion.xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -97,8 +97,11 @@
</component-plugins>
- This XML configuration defines where in the portal's war to look for co=
nfiguration, and what portals, groups, and user specific views to include i=
n portal/group/user navigation. Those files will be used to create an initi=
al navigation, the first time the portal is launched. That information will=
then be stored in JCR content repository, and can then be modified, and ma=
naged from the portal UI.
+ This XML configuration defines where in the portal's WAR to look for configuration settings, and which portals, groups, and use=
r specific views to include in portal/group/user navigation.
+
+ The first time the portal is launched those files will be used to creat=
e an initial navigation. That information will then be stored in the JCR co=
ntent repository and can be modified and managed from the portal UI.
+
=
@@ -107,7 +110,7 @@
The portal navigation incorporates the pages that can be accessed even =
when a user is not logged in (assuming the applicable permissions allow pub=
lic access). For example; several portal navigations are used when a compan=
y owns multiple trademarks, and sets up a web site for each of them.
- The classic portal is configured by =
four XML files in 02portal.war:/WEB-INF/conf/portal/portal/classi=
c directory:
+ The classic portal is configured by =
four XML files in the 02portal.war:/WEB-INF/conf/portal/portal/cl=
assic directory:
@@ -170,10 +173,10 @@
navigation.xml
- This file defines all the navigation nodes the portal will have. The=
syntax is simple, using nested node tags. Each node references a page defi=
ned in pages.xml file (explained next).
+ This file defines all the navigation nodes the portal will have. The=
syntax is simple and uses nested node tags. Each node references a page de=
fined in pages.xml file.
- When #{...} syntax is used, the enclosed property=
name serves as a key that is automatically passed to internationalization =
mechanism so the literal property name is replaced by a localized value tak=
en from the associated properties file matching the current locale.
+ When the #{...} syntax is used, the enclosed prop=
erty name serves as a key that is automatically passed to internationalizat=
ion mechanism so the literal property name is replaced by a localized value=
taken from the associated properties file matching the current locale.
=
<?xml version=3D"1.0" encoding=3D"UTF-8"?&=
gt;
@@ -202,8 +205,11 @@
- For top nodes, the uri and the <=
emphasis role=3D"bold">name of your navigation nodes must have t=
he same value. For other nodes the uri is a relative path. For example, content=
management/fileexplorer where 'contentmanagement<=
/literal> ' is the name of the parent node and 'fileexplorer' is the name of the node ( <name>fileexplorer</name=
> ).
+ For top nodes, the uri and the <=
emphasis role=3D"bold">name of your navigation nodes must have t=
he same value. For other nodes the uri is a relative path.
+
+ For example; contentmanagement/fileexplorer=
emphasis> where 'contentmanagement ' is the name of the =
parent node and 'fileexplorer' is the name of the node (=
<name>fileexplorer</name> ).
+
@@ -255,7 +261,8 @@
portlet-preferences.xml
- Porlet instances can be associated with portlet-preferences=
that override the ones defined in portlet.xml of the portlet application war (TODO: clarify which f=
ile in which war).
+ Porlet instances can be associated with portlet-preferences=
that override the ones defined in portlet.xml of the portlet application war.
+ (TODO: clarify which file in which war).
=
<?xml version=3D"1.0" encoding=3D"ISO-8859=
-1"?>
@@ -503,7 +510,7 @@
Group Navigation
- Group navigations are dynamically added to the user navigation at login=
. This allows users to see in the menu all the pages assigned to any groups=
they belong to.
+ Group navigations are dynamically added to the user navigation at login=
. This allows users to see the pages assigned to any groups they belong to =
in the menu.
The group navigation menu is configured by three XML files (n=
avigation.xml, pages.xml and port=
let-preferences.xml). The syntax used in these files is the same=
as those covered in .
@@ -573,7 +580,7 @@
Direct External Links
- If you wish to add a link to a URL outside the portal you first have t=
o define a "page" that will only serve as a navigation placeholder for exte=
rnal redirect - it will not be used for any portlets. Then add the URL to t=
he navigation. (TODO: check for correctness)
+ If you wish to add a link to a URL outside the portal you must first d=
efine a "page" that will only serve as a navigation placeholder for an exte=
rnal redirect. This page will not be used for any portlets. Then add the UR=
L to the navigation. (TODO: check for correctness)
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConf=
iguration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfigurat=
ion.xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfigurat=
ion.xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -8,7 +8,7 @@
Overview
- The default permission configuration for the portal is defined through =
org.exoplatform.portal.config.UserACL component configur=
ation in the file 02portal.war:/WEB-INF/conf/portal/portal-config=
uration.xml.
+ The default permission configuration for the portal is defined through =
the org.exoplatform.portal.config.UserACL component conf=
iguration in the file 02portal.war:/WEB-INF/conf/portal/portal-co=
nfiguration.xml.
It defines 5 permissions types:
@@ -50,7 +50,7 @@
access.control.workspace
- Defines the users that have access to the control workspace. In the =
demo version the control workspace is accessible only to root and john. They can expand/collapse the workspa=
ce at the left hand side. The format is membership:/group/subgroup=
- an asterisk '*' gives permission to all memberships.
+ Defines the users that have access to the control workspace. In the =
demontration (demo) version the control workspace is accessible only to root and john. They can expand/colla=
pse the workspace at the left hand side. The format is membership:=
/group/subgroup. An asterisk (*) gives permission to all membersh=
ips.
@@ -94,7 +94,7 @@
Overwrite Portal Default Permissions
- When creating custom portals and portal extensions it's possible to ove=
rride the default configuration by using org.exoplatform.portal.co=
nfig.PortalACLPlugin, configuring it as an external-plugin of
org.exoplatform.portal.config.UserACL service:
+ When creating custom portals and portal extensions it is possible to ov=
erride the default configuration by using org.exoplatform.portal.c=
onfig.PortalACLPlugin, configuring it as an external-plugin of org.exoplatform.portal.config.UserACL service:
=
<external-component-plugins>
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfigu=
ration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration=
.xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration=
.xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -20,13 +20,13 @@
All &PRODUCT; applications contain property files for various languages=
. They are packaged with the portlets applications in a WEB-INF/c=
lasses/locale/ directory.
- These files are located in the classes folder of the=
WEB-INF directory, so as to be loaded by the ClassLoader.
+ These files are located in the classes folder of t=
he WEB-INF directory, so as to be loaded by the ClassLoader.
All resource files are in a subfolder named locale.
- For instance; the translations for the NavigationPortlet are located in web.war/WEB-INF/classes/locale/portlet/porta=
l
+ For instance; the translations for the NavigationPortlet are located in web.war/WEB-INF/classes/locale/portlet/port=
al
=
NavigationPortlet_de.properties
@@ -39,7 +39,7 @@
NavigationPortlet_ar.xml
- Inside those file are typical key=3Dvalue Java EE pr=
operties. For example the French one:
+ Inside those file are typical key=3Dvalue Java EE pr=
operties. For example; in the French file:
=
javax.portlet.title=3DPortlet Navigation
@@ -51,18 +51,21 @@
From a portlet you can then access translations from the portlet itself=
or shared at the portal level, both are aggregated when you need them.
- Translation in XML format
+ Translation in XML Format
- It is also possible to use a proprietary XML format to define translat=
ions. This is a more convenient way to translate a document for some langua=
ges such as Japanese, Arabic or Russian. Property files have te be ASCII en=
coded, while the XML file can define its encoding. As a result it's easier =
for a human being to read (and fix) a translation in XML instead of having =
to decode and encode the property file.
+ It is also possible to use a proprietary XML format to define translat=
ions. This is a more convenient way to translate a document for some langua=
ges such as Japanese, Arabic or Russian.
+ Property files have te be ASCII encoded, while the XML file can define=
its encoding. As a result it's easier for a human being to read a translat=
ion in XML instead of having to decode and encode the property file.
+
+
For more information refer to:
=
- Locales configuration
+ Locales Configuration
Various languages are available in the portal package. The configuratio=
n below will define which languages are shown in the "Change Language" sect=
ion and made available to users.
@@ -134,17 +137,17 @@
- input-encoding In the java implementation, the =
encoding parameters will be used for the request response stream. The input=
-encoding parameter will be used for request setCharacterEncoding(..).
+ input-encoding In the java implementation, the =
encoding parameters will be used for the request response stream. The input=
-encoding parameter will be used for request setCharacterEncoding(=
..).
- description Description for the language
+ description A description of the language
- orientation The default orientation of text and=
images is Left-To-Right. &PRODUCT; supports Right-=
To-Left orientation. Modifying text orientation is explained in =
.
+ orientation Although the default orientation of=
text and images is Left-To-Right, &PRODUCT; supports Right-To-Left orientation. Modifying text orientation is expl=
ained in .
@@ -231,13 +234,13 @@
The previous example shows bundle definitions for the navigation of the=
classic portal and of four different groups. Each of these resource bundle=
s occupies a different sphere, they are independent of each other and they =
are not included in the portal.resource.names parame=
ter.
- The properties for a group must be in the WEB-INF/classes/loc=
ale/navigation/group/ folder. /WEB-INF/classes/locale/n=
avigation/group/organization/management/executive-board_en.properties, for example.
+ The properties for a group must be in the WEB-INF/classes/loc=
ale/navigation/group/ folder. For example; /WEB-INF/cla=
sses/locale/navigation/group/organization/management/executive-board_en.pro=
perties.
- The folder and file names must correspond to the group hierarchy. The g=
roup name "executive-board" is followed by the iso 6=
39 code.
+ The folder and file names must correspond to the group hierarchy. The g=
roup name "executive-board" is followed by the iso 639 code.
- For each language defined in LocalesConfig must =
have a resource file defined. If the name of a group is changed the name of=
the folder and/or files of the correspondent navigation resource bundles m=
ust also be changed.
+ Each language defined in LocalesConfig must have=
a resource file defined. If the name of a group is changed the name of the=
folder and/or files of the correspondent navigation resource bundles must =
also be changed.
Content of executive-board_en.properties: =
@@ -252,7 +255,7 @@
=
- Portlets
+ Portlets
Portlets are independent applications and deliver their own resource fi=
les.
@@ -273,7 +276,7 @@
- In portlet.xml, add Spanish as a supported-locale ('es' is the 2 =
letters code for Spanish), the resource-bundle is already declared and is the same for all languages :
+ In portlet.xml, add Spanish as a supported-locale ('es' is the two letter code for Spanish). The resource-bundle is already declared and is the s=
ame for all languages :
=
<supported-locale>en</supported-loca=
le>
@@ -286,10 +289,10 @@
See the portlet specification for more details about portlet internatio=
nalization.
-
- Standard portlet resource keys
+
+ Standard Portlet Resource Keys
- The portlet specifications defines three standard keys: Title, Short T=
itle and Keywords. Keywords is formatted as a comma-separated list of tags.
+ The portlet specifications defines three standard keys: Titl=
e, Short Title and Keywords. Keywords is formatted as a comma-separated list of tags.
=
javax.portlet.title=3DBreadcrumbs Portlet
@@ -298,8 +301,8 @@
=
-
- Debugging resource bundle usage
+
+ Debugging Resource Bundle Usage
When translating an application it can sometimes be difficult to find =
the right key for a given property.
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2010-=
04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2010-=
04-30 07:57:03 UTC (rev 2909)
@@ -9,13 +9,13 @@
Managing Javascript scripts in an application like &PRODUCT; is a critic=
al part of the configuration work. Configuring the scripts correctly will r=
esult in a faster response time from the portal.
- Every portlet can have its own javscript code but in many cases it is mo=
re convenient to reuse some existing shared libraries. For that reason, &PR=
ODUCT; has a mechanism to easily register the libraries that will be loaded=
when the first page will be rendered.
+ Every portlet can have its own javscript code but in many cases it is mo=
re convenient to reuse some existing shared libraries. For that reason, &PR=
ODUCT; has a mechanism to easily register the libraries that will be loaded=
when the first page is rendered.
To do so, every WAR deployed in &PRODUCT; can register the .js=
files with the groovy script WEB-INF/conf/script/groo=
vy/JavascriptScript.groovy. (TODO: this file doesn't seem to exi=
st)
- The example file below is found in the 01eXoResources.war
+ The example file below is found in the 01eXoResources.war
=
JavascriptService.addJavascript("eXo", "/jav=
ascript/eXo.js", ServletContext);
@@ -77,10 +77,10 @@
To see or use the merged file set this property to false.
- The property can be passed as a JVM parameter with the -D option in your GateIn.sh or GateIn.bat startup script.
+ The property can be passed as a JVM parameter with the -D option in your run.sh or run.bat=
startup script.
- Every javascript file is associated with a module name which acts as a n=
amespace. The module name is passed as a first parameter to JavascriptServi=
ce.addJavascript() function as in the following example:
+ Every javascript file is associated with a module name which acts as a n=
amespace. The module name is passed as a first parameter to Javasc=
riptService.addJavascript() function as in the following example:
=
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationC=
ommunication.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommuni=
cation.xml 2010-04-30 07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommuni=
cation.xml 2010-04-30 07:57:03 UTC (rev 2909)
@@ -186,7 +186,7 @@
Publish
- The publish function is used to publish an event =
to the other subscribered applications through the given channels. Its para=
meters are:
+ The publish function is used to publish an event =
to the other subscribed applications through the given channels. Its parame=
ters are:
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2010-04-30 07=
:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml 2010-04-30 07=
:57:03 UTC (rev 2909)
@@ -4,21 +4,21 @@
%BOOK_ENTITIES;
]>
- Portal Lifecycle
+ Portal Life-cycleOverview
- This chapter describes the portal lifecycle from the application server=
start to its stop as well as how requests are handled.
+ This chapter describes the portal life-cycle from the application serve=
r start to its stop as well as how requests are handled.
=
Application Server start and stop
- A portal instance is simply a web application deployed as a WAR in an a=
pplication server. Portlets are also part of an enhanced WAR called a portl=
et application.
+ A portal instance is simply a web application deployed as a WA=
R in an application server. Portlets are also part of an enhanced=
WAR called a portlet application.
- &PRODUCT; doesn't require any particular setup for your portlet in most=
common scenarios and the web.xml file can remain with=
out any &PRODUCT; specific configuration.
+ &PRODUCT; does not require any particular setup for your portlet in mos=
t common scenarios and the web.xml file can remain wit=
hout any &PRODUCT; specific configuration.
During deployment, &PRODUCT; will automatically and transparently injec=
t a servlet into the portlet application to be able to interact with it. Th=
is feature is dependent on the underlying servlet container but will work o=
ut of the box on the proposed bundles.
@@ -91,12 +91,13 @@
The Command Servlet
- The servlet is the main entry point for incoming requests, it also incl=
udes some init code when the portal is launched. This servlet (org=
.gatein.wci.command.CommandServlet) is automatically added during=
deployment and mapped to /tomcatgateinservlet.
+ The servlet is the main entry point for incoming requests, it also incl=
udes some init code when the portal is launched. This se=
rvlet (org.gatein.wci.command.CommandServlet) is automat=
ically added during deployment and mapped to /tomcatgateinservlet<=
/literal>.
This is equivalent to adding the following into web.xml.
+ Servlet Configuration
As the servlet is already configured this example is for information o=
nly.
@@ -115,7 +116,7 @@
</servlet-mapping>
- It is possible to filter on the CommandServlet by filtering the URL pat=
tern used by the Servlet mapping.
+ It is possible to filter on the CommandServlet by fi=
ltering the URL pattern used by the servlet mapping.
The example below would create a servlet filter that calculates the tim=
e of execution of a portlet request.
@@ -157,8 +158,11 @@
}
- The Java EE web application configuration file (web.xml) of the portlet on which we want to know the time to serve a portlet =
request. As mentioned above nothing specific to &PRODUCT; needs to be inclu=
ded, only the URL pattern to set has to be known.
+ The Java EE web application configuration file (web.xml) of the portlet is the file on which we want to know the time to serv=
e a portlet request.
+
+ As mentioned above nothing specific to &PRODUCT; needs to be included, =
only the URL pattern to set has to be known.
+
=
<?xml version=3D"1.0"?>
@@ -183,7 +187,7 @@
INCLUDE dispatcher
- It is important to set INCLUDE as dispatcher as th=
e portal will always hit the CommandServlet through a request dispatcher. W=
ithout this, the filter will not be triggered, unless direct access to a re=
source (such as an image).
+ It is important to set INCLUDE as dispatcher as th=
e portal will always hit the CommandServlet through a re=
quest dispatcher. Without this, the filter will not be triggered, unless di=
rect access to a resource (such as an image).
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2010-04-30 07:23=
:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2010-04-30 07:57=
:03 UTC (rev 2909)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
- RTL (Right To Left) Framework
+ Right To Left (RTL) Framework
The text orientation depends on the current locale setting. The orientat=
ion is a Java 5 enum that provides a set of functionalities:
@@ -38,7 +38,7 @@
Orientation
- The current orientation as an Orientation
+ The current orientation as an Orientation.
@@ -46,7 +46,7 @@
isLT
- The value of orientation.isLT()
+ The value of orientation.isLT().
@@ -54,7 +54,7 @@
isRT
- The value of orientation.isRT()
+ The value of orientation.isRT().
@@ -62,7 +62,7 @@
dir
- The string 'ltr' if the orientation is LT or the string 'rtl' if the=
orientation is RT.
+ The string 'ltr' if the orientati=
on is LT or the string 'rtl' if the orie=
ntation is RT.
@@ -162,8 +162,8 @@
=
-
- Client side JavaScript
+
+ Client Side JavaScript
The eXo.core.I18n object provides the following para=
meters for orientation:
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-30 07:23:12 =
UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2010-04-30 07:57:03 =
UTC (rev 2909)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
- Skinning the portal
+ Skinning the PortalOverview
@@ -15,14 +15,14 @@
Skin Components
- The complete skinning of a page can be decomposed into three main parts:
+ The complete skinning of a page is composed of three main parts:
Portal Skin
- The portal skin contains the css styles for the portal and its vario=
us UI components. This should include all the UI components except for the =
window decorators and portlet specific styles.
+ The portal skin contains the CSS styles for the portal and its vario=
us UI components. This should include all the UI components except for the =
window decorators and portlet specific styles.
@@ -45,7 +45,7 @@
Portlet Specification CSS Classes
- The portlet specification defines a set of css classes that shoul=
d be available to portlets. &PRODUCT; provides these classes as part of the=
portal skin. This allows each portal skin to define its own look and feel =
for these default values.
+ The portlet specification defines a set of CSS classes that shoul=
d be available to portlets. &PRODUCT; provides these classes as part of the=
portal skin. This allows each portal skin to define its own look and feel =
for these default values.
@@ -53,7 +53,7 @@
Portlet Skins
- &PRODUCT; provides a means for portlet css files to be loaded bas=
ed on the current portal skin. This allows a portlet to provide different c=
ss styles to better match the current portal look and feel. Portlet skins p=
rovide a much more customizable css experience than just using the portlet =
specification css classes.
+ &PRODUCT; provides a means for portlet CSS files to be loaded bas=
ed on the current portal skin. This allows a portlet to provide different C=
SS styles to better match the current portal look and feel. Portlet skins p=
rovide a much more customizable CSS experience than just using the portlet =
specification CSS classes.
@@ -64,10 +64,10 @@
CSS Classes
- The window decorators and the default portlet specification css classe=
s should be considered separate types of skinning components, but they need=
to be included as part of the overall portal skin. The portal skin must in=
clude these components' css classes or they will not be displayed correctly.
+ The window decorators and the default portlet specification CSS classe=
s should be considered separate types of skinning components, but they need=
to be included as part of the overall portal skin. The portal skin must in=
clude these components' CSS classes or they will not be displayed correctly.
- A portlet skin doesn't need to be included as part of the portal skin =
and can be included within the portlets web application.
+ A portlet skin does not need to be included as part of the portal skin=
and can be included within the portlets web application.
@@ -77,7 +77,7 @@
Skin Selection Through the User Interface
- There are a few means in which a skin can be selected to be displayed =
to the user. The easiest way to change the skin is select it through the us=
er interface. An admin can change the default skin for the portal, or a log=
ged in user can select which skin they would prefer to be displayed.
+ There are a few means in which a skin can be selected to be displayed =
to the user. The easiest way to change the skin is select it through the us=
er interface. An administrator can change the default skin for the portal, =
or a logged in user can select which skin they would prefer to be displayed.
Please see the User Guide for information on how to change =
the skin using the user interface.
@@ -87,7 +87,7 @@
Setting the Default Skin within the Configuration Files
- The default skin can also be configured through the portal configurati=
on files if using the admin user interface is not desired. This will allow =
for the portal to have the new default skin ready when &PRODUCT; is first s=
tarted.
+ The default skin can also be configured using the portal configuration=
files. This allows the portal to have the new default skin ready for use w=
hen &PRODUCT; is first started.
The default skin of the portal is called Default. T=
o change this value add a skin tag in the 02por=
tal.war/WEB-INF/conf/portal/portal/classic/portal.xml configurati=
on file.
@@ -111,17 +111,17 @@
Skins in Page Markups
- A &PRODUCT; skin contains css styles for the portal's components but al=
so shares components that may be reused in portlets. When &PRODUCT; generat=
es a portal page markup, it inserts stylesheet links in the page's head tag.
+ A &PRODUCT; skin contains CSS styles for the portal's components but al=
so shares components that may be reused in portlets. When &PRODUCT; generat=
es a portal page markup, it inserts stylesheet links in the page's head tag.
- There are two main types of css links that will appear in the =
head tag: a link to the portal skin css file and a link to the po=
rtlet skin css files.
+ There are two main types of CSS links that will appear in the =
head tag: a link to the portal skin CSS file and a link to the po=
rtlet skin CSS files.
Portal Skin
- The portal skin will appear as a single link to a css file. This lin=
k will contain contents from all the portal skin classes merged into one fi=
le. This allow for the portal skin to be transfered more quickly as a singl=
e file instead of many multiple smaller files. Included with every page ren=
der.
+ The portal skin will appear as a single link to a CSS file. This lin=
k will contain contents from all the portal skin classes merged into one fi=
le. This allows the portal skin to be transfered as a single file instead o=
f multiple smaller files. Included with every page render >-- =
Unsure what this is referring to.
@@ -129,7 +129,7 @@
Portlet Skin
- Each portlet on a page may contribute its own style. The link to the=
portlet skin will only appear on the page if that portlet is loaded on the=
current page. A page may contain many portlet skin css links or none.
+ Each portlet on a page may contribute its own style. The link to the=
portlet skin will only appear on the page if that portlet is loaded on the=
current page. A page may contain many portlet skin CSS links or none.
@@ -141,18 +141,18 @@
<head>
...
<!-- The portal skin -->
-<link id=3D"CoreSkin" rel=3D"stylesheet" type=3D"text/css" href=3D"/eXo=
Resources/skin/Stylesheet.css" />
+<link id=3D"CoreSkin" rel=3D"stylesheet" type=3D"text/CSS" href=3D"/eXo=
Resources/skin/Stylesheet.CSS" />
=
<!-- The portlet skins -->
-<link id=3D"web_FooterPortlet" rel=3D"stylesheet" type=3D"text/css" hre=
f=3D "/web/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet.cs=
s" />
-<link id=3D"web_NavigationPortlet" rel=3D"stylesheet" type=3D"text/css"=
href=3D "/web/skin/portal/webui/component/UINavigationPortlet/DefaultStyle=
sheet.css" />
-<link id=3D"web_HomePagePortlet" rel=3D"stylesheet" type=3D"text/css" h=
ref=3D "/portal/templates/skin/webui/component/UIHomePagePortlet/DefaultSty=
lesheet.css" />
-<link id=3D"web_BannerPortlet" rel=3D"stylesheet" type=3D"text/css" hre=
f=3D "/web/skin/portal/webui/component/UIBannerPortlet/DefaultStylesheet.cs=
s" />
+<link id=3D"web_FooterPortlet" rel=3D"stylesheet" type=3D"text/CSS" hre=
f=3D "/web/skin/portal/webui/component/UIFooterPortlet/DefaultStylesheet.CS=
S" />
+<link id=3D"web_NavigationPortlet" rel=3D"stylesheet" type=3D"text/CSS"=
href=3D "/web/skin/portal/webui/component/UINavigationPortlet/DefaultStyle=
sheet.CSS" />
+<link id=3D"web_HomePagePortlet" rel=3D"stylesheet" type=3D"text/CSS" h=
ref=3D "/portal/templates/skin/webui/component/UIHomePagePortlet/DefaultSty=
lesheet.CSS" />
+<link id=3D"web_BannerPortlet" rel=3D"stylesheet" type=3D"text/CSS" hre=
f=3D "/web/skin/portal/webui/component/UIBannerPortlet/DefaultStylesheet.CS=
S" />
...
</head>
- CSS classes
+ CSS Classes
Window styles and the portlet specification CSS classes are included w=
ithin the portal skin.
@@ -162,7 +162,7 @@
The Skin Service
- The skin service is a &PRODUCT; service which manages the various types=
of skins. It is reponsible for discovering and deploying the skins into th=
e portal.
+ The skin service is a service which manages the various types of skins.=
It is reponsible for discovering and deploying the skins into the portal.
Skin configuration
@@ -174,13 +174,13 @@
=
- Here is an example where we define a skin (MySkin) with its CSS locati=
on, and specify a few window decorator skins:
+ Here is an example where we define a skin (MySkin) =
with its CSS location, and specify a few window decorator skins:
=
<gatein-resources>
<portal-skin>
<skin-name>MySkin</skin-name>
- <css-path>/skin/myskin.css</css-path>
+ <CSS-path>/skin/myskin.CSS</CSS-path>
<overwrite>false</overwrite>
</portal-skin>
</gatein-resources>
@@ -201,10 +201,10 @@
Resource Request Filter
- Because of the Right-To-Left support all CSS files need to be retrieve=
d through a Servlet filter and the web application needs to be configured t=
o activate this filter. This is already done for 01eXoResources.war web app=
lication which contains the default skin.
+ Because of &PRODUCT;'s Right-To-Left support, all CSS files need to be=
retrieved through a Servlet filter and the web application needs to be con=
figured to activate this filter. This is already done for 01eXoRes=
ources.war web application which contains the default skin.
- Any new web applications containing skinning css files will need to ha=
ve the following added to their web.xml :
+ Any new web applications containing skinning CSS files will need to ha=
ve the following added to their web.xml :
=
<filter>
@@ -214,12 +214,12 @@
=
<filter-mapping>
<filter-name>ResourceRequestFilter</filter-name>
- <url-pattern>*.css</url-pattern>
+ <url-pattern>*.CSS</url-pattern>
</filter-mapping>
=
- display-name
+ The display-name Element
The display-name element will also need to be speci=
fied in the web.xml for the skinning service to work pro=
perly with the web application.
@@ -230,9 +230,9 @@
The Default Skin
- The default skin for &PRODUCT; is located as part of the 01eXo=
Resource.war. The main files associated with the skin is show bel=
ow:
+ The default skin for &PRODUCT; is located as part of the 01eXo=
Resource.war. The main files associated with the skin are:
-
+
+
+
+
+ WEB-INF/gatein-resources.xml
+
+
+
+
+ WEB-INF/web.xml
+
+
+
+
+ skin/Stylesheet.CSS
+
+
+ gatein-resources.xml
- For the default portal skin, this file contains definitions for the =
portal skin, the window decorations that this skin provides and well as def=
ining some javascript resources which are not related to the skin. The defa=
ult portal skin doesn't directly define portlet skins, these should be prov=
ided by the portlets themeselves.
+ For the default portal skin, this file contains definitions for the =
portal skin, the window decorations that this skin provides and well as def=
ining some javascript resources which are not related to the skin. The defa=
ult portal skin doesn't directly define portlet skins, these should be prov=
ided by the portlets themselves.
@@ -275,15 +291,15 @@
web.xml
- For the default portal skin, the web.xml of the=
eXoResources.war will contains a lot of information whi=
ch is mostly irrelevant to the portal skining. The areas of interest in thi=
s file is the resourcerequestfilter and the fact that the display-name is s=
et.
+ For the default portal skin, the web.xml of the=
eXoResources.war will contains a lot of information whi=
ch is mostly irrelevant to the portal skinning. The area of interest in thi=
s file is the resourcerequestfilter and the fact that th=
e display-name is set.
- Stylesheet.css
+ Stylesheet.CSS
- The main portal skin stylesheet. The file is the main entry point to=
the css class definitions for the skin. Below is shown the contents of thi=
s file:
+ This file is the main portal skin stylesheet. It is the main entry p=
oint to the CSS class definitions for the skin. The main content points of =
this file are:
@@ -293,15 +309,15 @@
=
-@import url(DefaultSkin/portal/webui/component/UIPortalApp=
licationSkin.css);
-(a)import url(DefaultSkin/webui/component/Stylesheet.css);
-(a)import url(PortletThemes/Stylesheet.css);
-(a)import url(Portlet/Stylesheet.css);
+@import url(DefaultSkin/portal/webui/component/UIPortalApp=
licationSkin.CSS);
+(a)import url(DefaultSkin/webui/component/Stylesheet.CSS);
+(a)import url(PortletThemes/Stylesheet.CSS);
+(a)import url(Portlet/Stylesheet.CSS);
- Skin for the main portal page.
+ The skin for the main portal page.
@@ -316,25 +332,25 @@
- The portlet specificiation css classes.
+ The portlet specification CSS classes.
=
- Instead of defining all the CSS classes in this one file we are inst=
ead importing other css stylesheet files, some of which may also import oth=
er CSS stylesheets. The css classes are split up between multiple files to =
make it easier for new skins to reuse parts of the default skin.
+ Instead of defining all the CSS classes in this one file, we are ins=
tead importing other CSS stylesheet files, some of which may also import ot=
her CSS stylesheets. Splitting the CSS classes between multiple files allow=
s new skins to reuse parts of the default skin.
- To reuse a CSS stylesheet from the default portal skin you would nee=
d to reference the default skin from eXoResources. For example, to include =
the window decorators from the default skin within a new portal skin you wo=
uld need to use this import:
+ To reuse a CSS stylesheet from the default portal skin you would nee=
d to reference the default skin from eXoResources. For e=
xample; to include the window decorators from the default skin within a new=
portal skin you would need to use this import:
=
-@import url(/eXoResources/skin/Portlet/Stylesheet.css);
+@import url(/eXoResources/skin/Portlet/Stylesheet.CSS);
Stylesheet Merging
- When the portal skin is added to the page, it merge all the css sty=
lesheets into a single file.
+ When the portal skin is added to the page, it merge all the CSS sty=
lesheets into a single file.
@@ -347,18 +363,18 @@
Creating a New Portal Skin
- A new portal will need to be added to the portal through the skin serv=
ice. As such the web application which contains the skin will need to be pr=
operly configured for the skin service to discover them. This means properl=
y configuring the ResourceRequestFilter and gatein-resources.xml.
+ A new portal skins will need to be added to the portal through the ski=
n service. Therefore, the web application which contains the skins will nee=
d to be properly configured for the skin service to discover them. This mea=
ns properly configuring the ResourceRequestFilter and gatein-resources.xml.
Portal Skin Configuration
- The gatein-resources.xml will need to specify the new portal skin. Th=
is will include specifying the name of the new skin, where to locate its cs=
s stylesheet file and whether to overwrite an existing portal theme with th=
e same name.
+ The gatein-resources.xml will need to specify th=
e new portal skin. This will include the name of the new skin, where to loc=
ate its CSS stylesheet file and whether to overwrite an existing portal the=
me with the same name.
=
<gatein-resources>
<portal-skin>
<skin-name>MySkin</skin-name>
- <css-path>/skin/myskin.css</css-path>
+ <CSS-path>/skin/myskin.CSS</CSS-path>
<overwrite>false</overwrite>
</portal-skin>
</gatein-resources>
@@ -369,7 +385,7 @@
CSS
- The css for the portal skin needs to contain the css for all the win=
dow decorations and the portlet specification css classes.
+ The CSS for the portal skin needs to contain the CSS for all the win=
dow decorations and the portlet specification CSS classes.
@@ -377,8 +393,11 @@
Portal Skin Preview Icon
- When selecting a skin it is possible to see a preview of what the ski=
n will look like. The current skin needs to know about the skin icons for a=
ll the available skins, otherwise it will not be able to show the previews.=
When creating a new portal it is recommended to include the preview icons =
of the other skins and to update the other skins with your new portal skin =
preview.
+ When selecting a skin it is possible to see a preview of what the ski=
n will look like. The current skin needs to know about the skin icons for a=
ll the available skins, otherwise it will not be able to show the previews.
+
+ 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 y=
our new portal skin preview.
+
@@ -400,7 +419,7 @@
In order for the default skin to know about the skin icon for a new p=
ortal skin, the preview screenshot needs to be place in: 01eXoRes=
ources.war:/skin/DefaultSkin/portal/webui/component/customization/UIChangeS=
kinForm/background.
- The CSS stylesheet for the default portal needs to have the following=
updated with the preview icon css class. For a skin named MySkin then the following needs to be updated: 01eXoResources.war:/skin/DefaultSkin/portal/webui/component/customizatio=
n/UIChangeSkinForm/Stylesheet.css.
+ The CSS stylesheet for the default portal needs to have the following=
updated with the preview icon CSS class. For a skin named MySkin then the following needs to be updated: 01eXoResources.war:/skin/DefaultSkin/portal/webui/component/customizatio=
n/UIChangeSkinForm/Stylesheet.CSS.
.UIChangeSkinForm .UIItemSelector .TemplateContainer .MySkinImage {
margin: auto;
@@ -416,9 +435,11 @@
Creating a New Window Style
- Window styles are the CSS applied to window decoration. When an admini=
strator choose a new application to add on a page he can decide which style=
of decoration would go around the window if any.
+ Window styles are the CSS applied to window decorations. An administra=
tor can decide which style of decoration should go around the window when h=
e adds a new application to a page.
- PortalDevelopment/Skinning/windowStyles
+
+ PortalDevelopment/Skinning/windowStyles
+
@@ -427,14 +448,14 @@
-
+
Window Style Configuration
- Window Styles are defined within a gatein-resources.xml file which is=
used by the skin service to deploy the window style into the portal. Windo=
w styles can belong in with a window style category, this category and the =
window styles will need to be specified in resources file.
+ Window Styles are defined within a gatein-resources.xml file which is used by the skin service to deploy the window style i=
nto the portal. Window styles can belong in with a window style category, t=
his category and the window styles will need to be specified in resources f=
ile.
- The following gatein-resource.xml fragment will add MyThemeBlue and M=
yThemeRed to the MyTheme category.
+ The following gatein-resource.xml fragment will =
add MyThemeBlue and MyThemeRed to the=
MyTheme category.
=
<window-style>
@@ -453,7 +474,7 @@
Window Styles and Portal Skins
- When a window style is defined in gatein-resources.xml file, it will be available to all portlets regardless if the curren=
t portal skin supports the window decorator or not. It is recommended that =
when a new window decorator is added that it is added to all portal skins o=
r that portal skins share a common stylesheet for window decorators.
+ When a window style is defined in gatein-resources.xml file, it will be available to all portlets regardless of whether th=
e current portal skin supports the window decorator or not. It is recommend=
ed that when a new window decorator is added that it be added to all portal=
skins or that all portal skins share a common stylesheet for window decora=
tors.
@@ -461,10 +482,10 @@
Window Style CSS
- In order for the skin service to display the window decorators, it mu=
st have CSS classes with specific naming in relation to the window style na=
me. The service will try and display css based on this naming. The css clas=
s must be included as part of the current portal skin for the window decora=
tors to be displayed.
+ In order for the skin service to display the window decorators, it mu=
st 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 wind=
ow decorators to be displayed.
- The location of the window decorator css classes for the default port=
al theme is located at: 01eXoResources.war/skin/PortletThemes/Sty=
lesheet.css.
+ The location of the window decorator CSS classes for the default port=
al theme is located at: 01eXoResources.war/skin/PortletThemes/Sty=
lesheet.CSS.
@@ -605,12 +626,12 @@
How to Set the Default Window Style
- To set the default window style to be used for a portal, you will t=
o specify the css classes for a theme called DefaultTheme.
+ To set the default window style to be used for a portal, you will t=
o specify the CSS classes for a theme called DefaultTheme.
=
DefaultTheme
- You do not need to specify the DefaultTheme in gatein-res=
ources.xml.
+ You do not need to specify the DefaultTheme in <=
filename>gatein-resources.xml.
@@ -618,7 +639,7 @@
=
- How to Create New Portlet skins
+ How to Create New Portlet Skins
Portlets often require additional styles that may not be defined by th=
e portal skin. &PRODUCT; allows portlets to define additional stylesheets f=
or each portlet and will append the corresponding link t=
ags to the head.
@@ -631,30 +652,30 @@
<application-name>portletAppName</application-name>
<portlet-name>PortletName</portlet-name>
<skin-name>Default</skin-name>
- <css-path>/skin/DefaultStylesheet.css</css-path>
+ <CSS-path>/skin/DefaultStylesheet.CSS</CSS-path>
</portlet-skin>
=
<portlet-skin>
<application-name>portletAppName</application-name>
<portlet-name>PortletName</portlet-name>
<skin-name>OtherSkin</skin-name>
- <css-path>/skin/OtherSkinStylesheet.css</css-path>
+ <CSS-path>/skin/OtherSkinStylesheet.CSS</CSS-path>
</portlet-skin>
- This will load the DefaultStylesheet.css when the Default skin is used=
and the OtherSkinStylesheet.css when the OtherSkin is used.
+ This will load the DefaultStylesheet.css when the D=
efault skin is used and the OtherSkinStylesheet.css when=
the OtherSkin is used.
- Updating portlet skins
+ Updating Portlet Skins
- If the current portal skin is not defined as part of the supported sk=
ins, then the portlet css class will not be loaded. It is recommended to up=
date portlet skins whenever a new portal skin is created.
+ If the current portal skin is not defined as part of the supported sk=
ins, then the portlet CSS class will not be loaded. It is recommended that =
portlet skins are updated whenever a new portal skin is created.
- Change portlet icons
+ Change Portlet Icons
- Each portlet can be represented by an unique icon that you can see in=
the portlet registry or page editor. This icon can be changed by adding an=
image to the directory of the portlet webapplication:
+ Each portlet can be represented by an unique icon in the portlet regi=
stry or page editor. This icon can be changed by adding an image to the dir=
ectory of the portlet webapplication:
@@ -667,7 +688,7 @@
To be used correctly the icon must be named after the portlet.
- For example, the icon for an account portlet named AccountPortlet wou=
ld be located at:
+ For example; the icon for an account portlet named AccountPo=
rtlet would be located at:
@@ -677,7 +698,7 @@
- Portlet icons directory
+ Portlet Icons Directory
You must use skin/DefaultSkin/portletIcons/ for t=
he directory to store the portlet icon regardless of what skin is going to =
be used.
@@ -687,12 +708,12 @@
=
- How to create a new Portlet Specification CSS Classes
+ Create New Portlet Specification CSS Classes
- The portlet specification defines a set of default css classes that sh=
ould be available for portlets. These classes are included as part of the p=
ortal skin. Please see the portlet specification for a list of the default =
classes that should be available.
+ The portlet specification defines a set of default CSS classes that sh=
ould be available for portlets. These classes are included as part of the p=
ortal skin. Please see the portlet specification for a list of the default =
classes that should be available.
- For the default portal skin, the portlet specification CSS classes are=
defined in: eXoResources.war/skin/Portlet/Stylesheet.css.
+ For the default portal skin, the portlet specification CSS classes are=
defined in: eXoResources.war/skin/Portlet/Stylesheet.CSS.
=
@@ -701,34 +722,33 @@
=
Tips and Tricks
-
- Easier css debugging
+
+ Easier CSS Debugging
By default, CSS files are cached and their imports are merged into a s=
ingle CSS file at the server side. This reduces the number of HTTP requests=
from the browser to the server.
- The optimization code is quite simple as all the CSS files are parsed =
at the server startup time and all the @import and url(...) references are =
rewritten to support a single flat file. The result is stored in a cache di=
rectly used from the ResourceRequestFilter.
+ The optimization code is quite simple as all the CSS files are parsed =
at the server startup and all the @import and u=
rl(...) references are rewritten to support a single flat file. T=
he result is stored in a cache directly used from the ResourceRequ=
estFilter.
- Although the optimization is useful for a production environments, it =
may be easier to deactivate this optimization while debugging stylesheets. =
To do so, set the java system property exo.product.developing to true.
+ Although the optimization is useful for a production environment, it m=
ay be easier to deactivate this optimization while debugging stylesheets. S=
et the java system property exo.product.developing to true to disable the optimization.
- For example, the property can be passed as a JVM parameter with -D option when running GateIn.
+ For example, the property can be passed as a JVM parameter with -D option when running &PRODUCT;.
=
sh $JBOSS_HOME/bin/run.sh -Dexo.product.developing=3Dtrue
-
-
-
- warning("This option may cause display bugs with certain browsers li=
ke Internet Explorer")
-
-
-
+
+
+
+ This option may cause display bugs with certain browsers (Internet Exp=
lorer, for example).
+
+
=
- Some CSS techniques
+ Some CSS Techniques
It is recommended that users have some experience with CSS before stud=
ying &PRODUCT; CSS.
@@ -736,9 +756,9 @@
&PRODUCT; relies heavily on CSS to create the layout and effects for t=
he UI. Some common techniques for customizing &PRODUCT; CSS are explained b=
elow.
- Decorator pattern
+ Decorator Pattern
- The decorator is a pattern to create a contour or a curve around an a=
rea. In order to achieve this effect you need to create 9 cells. The BODY i=
s the central area that you want to decorate. The other 8 cells are distrib=
uted around the BODY cell. You can use the width, height and background ima=
ge properties to achieve any decoration effect that you want.
+ The decorator is a pattern to create a contour or a curve around an a=
rea. In order to achieve this effect you need to create nine cells. The
BODY is the central area that you want to decorate. The oth=
er eight cells are distributed around the BODY cell. You=
can use the width, height and background image properties to achieve any d=
ecoration effect that you want.
@@ -768,9 +788,9 @@
=
- Left margin left pattern
+ Left Margin Left Pattern
- Left margin left pattern is a technique to create 2 blocks side by si=
de. 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 o=
r removed space will be taken from the right block.
+ 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 t=
he rest of the available space. When the user resizes the browser the added=
or removed space will be taken from the right block.
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/UploadComponent.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml 2010-04-30 07=
:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/UploadComponent.xml 2010-04-30 07=
:57:03 UTC (rev 2909)
@@ -36,7 +36,7 @@
Upload Service
- The service is defined by the class: org.exoplatform.upload.Up=
loadService;
+ This service is defined by the class: org.exoplatform.upload.U=
ploadService;
This can be configured with the following xml code:
@@ -118,12 +118,12 @@
- The upload service stores a temporary file on the filesystem during t=
he upload process. When the upload is finished, the service must be cleaned=
in order to:
+ The upload service stores a temporary file on the file system during =
the upload process. When the upload is finished, the service must be cleane=
d in order to:
- Delete the temporary file.
+ Delete the temporary file and...
@@ -133,7 +133,7 @@
- Use theremoveUpload() method defined in the upload=
service to purge the file:
+ Use the removeUpload() method defined in the uploa=
d service to purge the file:
=
UploadService uploadService =3D uiForm.getAp=
plicationComponent(UploadService.class) ;
Modified: portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_=
Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.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
--- portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2010-04-30=
07:23:12 UTC (rev 2908)
+++ portal/branches/EPP_5_0_0_Branch_Docs/Enterprise_Portal_Platform_Refere=
nce_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2010-04-30=
07:57:03 UTC (rev 2909)
@@ -13,12 +13,12 @@
- The XML format declares the encoding of the file. This avoids use of =
the native2ascii program which can interfere with encoding.
+ The XML format declares the encoding of the file. This avoids use of =
the native2ascii program which can interfere with encodi=
ng.
- Property files generally use ISO 8859-1 character encoding which does=
not cover the full unicode charset. As a result, languages such as Arabic =
would not be natively supported.
+ Property files generally use ISO 8859-1 character =
encoding which does not cover the full unicode charset. As a result, langua=
ges such as Arabic would not be natively supported.
@@ -71,8 +71,8 @@
=
-
- Portal support
+
+ Portal Support
In order to be loaded by the portal at runtime (actually the resource b=
undle service), the name of the file must be the same as a property file an=
d it must use the .xml suffix.
--===============1277982051600492718==--
From do-not-reply at jboss.org Fri Apr 30 05:30:21 2010
Content-Type: multipart/mixed; boundary="===============8293764458847341003=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r2910 -
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/org/exoplatform/portal/selenium.
Date: Fri, 30 Apr 2010 05:30:21 -0400
Message-ID: <201004300930.o3U9ULxO004493@svn01.web.mwc.hst.phx2.redhat.com>
--===============8293764458847341003==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: mvanco(a)redhat.com
Date: 2010-04-30 05:30:21 -0400 (Fri, 30 Apr 2010)
New Revision: 2910
Modified:
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_POR_10_002_DeleteCurrentPortalByLegalUs=
er.html
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_POR_22_019_ChangeEditRightOnPortalPageW=
hileEditingPortalPageProperties.html
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_POR_25_05_004_CutPasteNodeByAddPageWiza=
rd.html
portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/o=
rg/exoplatform/portal/selenium/Test_SNF_PRL_25_EditPageOfNode.html
Log:
EPP5 UI Tests: improved tests POR_25_05_004, POR_10_002, POR_22_019, SNF_PR=
L_25
Modified: portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/=
suite/org/exoplatform/portal/selenium/Test_POR_10_002_DeleteCurrentPortalBy=
LegalUser.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/=
org/exoplatform/portal/selenium/Test_POR_10_002_DeleteCurrentPortalByLegalU=
ser.html 2010-04-30 07:57:03 UTC (rev 2909)
+++ portal/branches/EPP_5_0_Branch/testsuite/selenium-snifftests/src/suite/=
org/exoplatform/portal/selenium/Test_POR_10_002_DeleteCurrentPortalByLegalU=
ser.html 2010-04-30 09:30:21 UTC (rev 2910)
@@ -228,7 +228,7 @@
waitForElementPresent
-
//div[@class=3D'Content']/div[@class=3D'Label' and text()=3D'Test_POR=
_10_002']
+
//td[@class=3D'Content']/div[@class=3D'Label' and text()=3D'Test_POR_=
10_002']
xpath=3D//div[@id=3D'UIPortalApplication']/div[@class=3D'UIPopupWindo=
w UIDragObject']//div[@class=3D'MiddleLeftSideDecorator']//div[@class=3D'UI=
PopupMessages']/div[@class=3D'MessageActionBar']//a
-
-
-
-
clickAt
-
xpath=3D//div[@id=3D'UIPortalApplication']/div[@class=3D'UIPopupWindo=
w UIDragObject']//div[@class=3D'MiddleLeftSideDecorator']//div[@class=3D'UI=
PopupMessages']/div[@class=3D'MessageActionBar']//a
-
-
-
-
echo
-
--Delete page of group--
-
-
-
-
waitForElementPresent
-
xpath=3D//img[@title=3D'Delete Page']
-
-
-
-
clickAt
-
xpath=3D//img[@title=3D'Delete Page']
-
-
-
-
assertConfirmation
-
Do you want to delete this page?
-
-
-
-
waitForElementPresent
-
xpath=3D//div[@id=3D'UIPortalApplication']/div[@class=3D'UIPopupWindo=
w UIDragObject']//div[@class=3D'MiddleLeftSideDecorator']//div[@class=3D'UI=
PopupMessages']/div[@class=3D'MessageActionBar']//a
-
-
-
-
clickAt
-
xpath=3D//div[@id=3D'UIPortalApplication']/div[@class=3D'UIPopupWindo=
w UIDragObject']//div[@class=3D'MiddleLeftSideDecorator']//div[@class=3D'UI=
PopupMessages']/div[@class=3D'MessageActionBar']//a