You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@portals.apache.org by at...@apache.org on 2012/12/16 23:55:26 UTC
svn commit: r1422709 [4/44] - in /portals/site-live/jetspeed-2.1.3:
2.1/schemas/ adminguide/ adminguide/css/ adminguide/images/
adminguide/images/logos/ css/ deployguide/ deployguide/css/
deployguide/images/ deployguide/images/ldap/ deployguide/images/...
Added: portals/site-live/jetspeed-2.1.3/adminguide/profiler.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/profiler.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/profiler.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/profiler.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,642 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - Profiler Administration Guide</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <a href="roles.html">Roles</a>
+ </li>
+
+ <li class="none">
+ <a href="sso.html">SSO</a>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <a href="site.html">Portal Site</a>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <strong>Profiler</strong>
+ </li>
+
+ <li class="none">
+ <a href="rpad.html">Remote Deployment</a>
+ </li>
+
+ <li class="none">
+ <a href="search.html">Search</a>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"><person name="Jody McAlister" email="jmcalister@onehippo.com"></authors><div class="section"><h2><a name="Profiler_Overview"></a>Profiler Overview</h2>
+<p>
+
+The Jetspeed Profiler is a portal resource location rule-based engine.
+The profiler locates the following kinds of portal resources:
+<ul><li>PSML pages</li>
+<li>Folders</li>
+<li>Menus</li>
+<li>Links</li>
+</ul>
+</p>
+<p><img src="images/profadmin1.png" /></p>
+<p>
+When a request is received by the portal, the profiler will compute a normalized instruction set, known
+as a profile locator. The locator is then added to the request context, from which subsequent components on the
+Jetspeed pipeline, most notably the Page Manager and Portal Site components, can take the profile locator
+and use it to find a requested resource. For example, the Page Manager uses the locator to find a page or folder.
+The Portal Site component uses the locator build the options on a menu.
+</p>
+<p>
+The profile locator is the output from the profiler. The input is a normalized set of runtime parameters and state.
+The profiler input is defined in profiling rules, and can be made of any Java class available on the pipeline.
+Jetspeed comes with quite a few predefined rules for taking criteria from request parameters, HTTP headers,
+security information, language and session attributes. The profiler is invoked during the Jetspeed request
+processing pipeline in the profiler valve.
+</p>
+<p><img src="../devguide/images/profiler-pipeline.jpg" /></p>
+<p>
+All of these runtime parameters are called the <i>profile criterion</i>, which the profiler uses to locate
+portal resources.
+</p>
+</div>
+<div class="section"><h2><a name="Located_Portal_Resources:_Pages"></a>Located Portal Resources: Pages</h2>
+<p>
+The Profiler searches over a directory tree of PSML pages trying to locate a
+PSML page to be displayed. By default, this directory structure is found under WEB-INF/pages.
+The pages directory can also be stored in the database. This directory structure, comprised of
+portal resources (pages, folders, menus, links), is a <i>physical</i> representation of the portal site.
+The Jetspeed team plans to also support <i>logical</i> views of the portal site in future releases.
+</p>
+<p>
+Analogous to a file system, there is one physical root to the portal site. However, using the concept of <i>subsites</i>,
+the Jetspeed site can support entire subsites that are not visible to other subsites, or the main site.
+There are several reserved (system) directories standardized by the profiler:
+<table class="bodyTable"><tr class="a"><th>Reserved Folder</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>_user</td>
+<td>holds all user-specific folders and pages</td>
+</tr>
+<tr class="a"><td>_role</td>
+<td>holds all role-organized folders and pages</td>
+</tr>
+<tr class="b"><td>_group</td>
+<td>holds all group-organized folders and pages</td>
+</tr>
+<tr class="a"><td>_subsite-root</td>
+<td>contains complete subsite trees, exactly like root tree</td>
+</tr>
+</table>
+<img src="../devguide/images/pages.jpg" /></p>
+<p>By applying profiling rules, the profiler locates pages in the portal site directory.</p>
+</div>
+<div class="section"><h2><a name="Profiling_Rules"></a>Profiling Rules</h2>
+<p>
+
+A ProfilingRule defines a list of criteria used when evaluating a request
+to determine the location of a specific resource. Profiling rules are
+used by the profiler to locate portal resources
+based on the decoupled criteria for known portlet request data.
+A rule consists of an ordered list of criteria which should be applied
+in a given order. Following this rule's order, the profiling engine applies
+each criteria of the rule using a less-specific algorithm until the least
+specific resource criterion is considered. When all criteria are exhausted,
+the rule will fail and a fallback resource will be required.
+</p>
+<div class="section"><h3><a name="Rule_Criteria"></a>Rule Criteria</h3>
+<p><img src="images/profadmin3.png" /></p>
+<p>
+A Rule Criterion specifies one criterion in a list of profiling rule criteria.
+The rule is used to build a normalized profiling locator and then
+locate a portal resource based on the current user request.
+Rule Criteria are templates for locating profile properties.
+Criteria consist of:
+<table class="bodyTable"><tr class="b"><td>Type</td>
+<td>The type of criterion. Types are configured in the profiler spring configuraiton.
+ Each type maps to a <i>rule criterion resolver</i>. A resolver is a Java class which maps request input
+ to a normalized location instruction. Valid resolvers are provided in the table below.
+ </td>
+</tr>
+<tr class="a"><td>Fallback Order</td>
+<td>The sequential in which to apply this criterion within the profiling rule.</td>
+</tr>
+<tr class="b"><td>Fallback Type</td>
+<td>After evaluation this criterion, the rule can either continue processing the remaining
+ criteria, or stop processing. The fallback type determines how to continue processing.
+ Valid values are:
+ <table class="bodyTable"><tr class="a"><td>FALLBACK_CONTINUE</td>
+<td>evaluate this criterion and if it fails continue to the next criterion</td>
+</tr>
+<tr class="b"><td>FALLBACK_STOP</td>
+<td>evaluate this criterion and if it fails stop evaluation criteria for this rule</td>
+</tr>
+<tr class="a"><td>FALLBACK_LOOP</td>
+<td>evaluate this criterion and if it fails continue evaluating</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="b"><td>Name</td>
+<td>The unique name (per rule) of this criterion. Upon matches, the name is mapped to the profile locator property name.</td>
+</tr>
+<tr class="a"><td>Value</td>
+<td>The default value (not required) to use for this criterion when resolution fails.</td>
+</tr>
+</table>
+
+More complex implementations will need to use other inputs in mapping to resources such as Cookies, IP Address Ranges, Statistical Resource Usage Analysis, or Business Rules.
+</p>
+</div>
+<div class="section"><h3><a name="Rule_Criterion_Resolvers"></a>Rule Criterion Resolvers</h3>
+<p>
+The table below displays all default rule criterion resolvers available with Jetspeed out of the box.
+Resolvers are Java classes, implementing the interface from the Jetspeed API <i>org.apache.jetspeed.profiler.rules.RuleCriterionResolver</i>.
+You may use this default set of resolvers to build your own profiling rules. Rules are currently stored in the
+Jetspeed database. Portal administrators may edit the rules using an administrative portlet. In the demo system,
+login as the user "admin" to see an example of the Jetspeed Profiler Administration portlet.
+</p>
+<p>Additionally, you may add your own resolvers to Jetspeed. You will need to create a jar file
+ holding your custom resolvers, and then drop them into the Jetspeed webapp's class path. Resolvers
+ will need to be given a unique name. This is done by modifying the profiler.xml in the Spring assembly.
+ See the section below on configuration to see where to add a resolver to the Spring configuration.
+<table class="bodyTable"><tr class="b"><th>Resolver</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>request</td>
+<td>resolve by matching a request parameter by name, returning the request parameter value for a locator property taking the name of the criterion</td>
+</tr>
+<tr class="b"><td>session</td>
+<td>resolve by matching a session attribute by name, returning the session attribute value for a locator property taking the name of the criterion</td>
+</tr>
+<tr class="a"><td>request.session</td>
+<td>resolve by first matching a request parameter by name. If not matched, try matching a session attribute name, returning the request parameter or session attribute value for a locator property taking the name of the criterion</td>
+</tr>
+<tr class="b"><td>path</td>
+<td>resolve by matching the PSML page <i>path</i> value of the current request. The path is typically the path and name of a page, such as <i>default-page</i> for a locator property named <quote>path</quote></td>
+</tr>
+<tr class="a"><td>path.session</td>
+<td>resolve by matching the PSML page <i>path</i> value of the current request. The path is typically the path and name of a page, such as <i>default-page</i>. If fails to find a valid path in the request, will then look in the session for the page value. The locator property will be named <quote>path</quote></td>
+</tr>
+<tr class="b"><td>hard.coded</td>
+<td>resolve to a hard.coded default value, for example, set a locator property named page to <quote>/my-account.psml</quote></td>
+</tr>
+<tr class="a"><td>user</td>
+<td>resolve by matching the name of the current authenticated user. The username is mapped to a locator property named <quote>user</quote></td>
+</tr>
+<tr class="b"><td>role</td>
+<td>resolve by matching all of the security roles of the current authenticated user (in the JAAS Subject of the request context) and putting them in a comma-separated list. The locator property should be named <quote>role</quote>. The role criterion is often used in combination with path criteria, to create a role-fallback rule that searches over all security roles for a given user.</td>
+</tr>
+<tr class="a"><td>group</td>
+<td>resolve by matching all of the groups of the current authenticated user (in the JAAS Subject of the request context) and putting them in a comma-separated list. The locator property should be named <quote>group</quote>. The group criteion is often used in combination with path criteria, to create a group-fallback rule that searches over all security groups for a given user.</td>
+</tr>
+<tr class="b"><td>rolecombo</td>
+<td>resolve by matching all of the security roles of the current authenticated user (in the JAAS Subject of the request context) and putting them in a dash-separated string, for example: (role1-role2-role3). The locator property should be named <quote>role</quote>. The role criterion is often used in combination with path criteria, to create a role-fallback rule that searches over all security roles for a given user.</td>
+</tr>
+<tr class="a"><td>mediatype</td>
+<td>resolve by matching the media type (HTML,XHTML,WML...) from the request context. Sets a locator property named <quote>mediatype</quote></td>
+</tr>
+<tr class="b"><td>language</td>
+<td>resolve by matching the browser's language from the request context locale (originating from the HTML headers). Sets a locator property named <quote>language</quote></td>
+</tr>
+<tr class="a"><td>country</td>
+<td>resolve by matching the browser's country code from the request context locale (originating from the HTML headers). Sets a locator property named <quote>country</quote></td>
+</tr>
+<tr class="b"><td>group.role.user</td>
+<td>resolve by first matching on a request parameter named <quote>group</quote>. If that fails, resolve on a request parameter named <quote>role</quote>. If that fails, resolve by matching the name of the current authenticated user. The username is mapped to a locator property named <quote>user</quote></td>
+</tr>
+<tr class="a"><td>user.attribute</td>
+<td>resolve by matching a Portlet API User Attribute by name, returning the user attribute value for a locator property taking the name of the criterion</td>
+</tr>
+<tr class="b"><td>user.agent</td>
+<td>resolve by matching the browser's (client) user agent from the request context device capabilities (originating from the HTML headers)</td>
+</tr>
+<tr class="a"><td>hostname</td>
+<td>resolve by matching the host name from the server name in the request, returning the host name</td>
+</tr>
+<tr class="b"><td>domain</td>
+<td>resolve by matching the domain from the server name in the request, returning the domain</td>
+</tr>
+<tr class="a"><td>navigation</td>
+<td>A directive to changes the current navigation path during a profile location resolution performed by the page manager. The value can be the location of a folder, for example <quote>/pages/freecontent</quote></td>
+</tr>
+</table>
+<i>Note that all criteria will fall back to the default value when no match is made. Locator property expects a criterion named <quote>navigation</quote></i></p>
+</div>
+<div class="section"><h3><a name="Default_Rules"></a>Default Rules</h3>
+<p>
+Several rules are provided by default with the Jetspeed system.
+The rules in the table below display the criterion in a most-specific to least-specific ordering.
+</p>
+<table class="bodyTable"><tr class="b"><th>Rule</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>j1</td>
+<td><p>Implements the Jetspeed-1 hard-coded profiler fallback algorithm, resolving in a most-specific to least-specific algorithm:</p>
+<table class="bodyTable"><tr class="b"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="a"><td>country</td>
+<td>country</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="b"><td>language</td>
+<td>language</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="a"><td>mediatype</td>
+<td>mediatype</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="b"><td>group.role.user</td>
+<td>user|group|role</td>
+<td></td>
+<td>stop</td>
+</tr>
+<tr class="a"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>stop</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="b"><td>role-fallback</td>
+<td><p>A role based fallback algorithm, trying to find the most-specific resource by searching over all security roles for the current authenticated user.</p>
+<table class="bodyTable"><tr class="a"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="b"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>stop</td>
+</tr>
+<tr class="a"><td>role</td>
+<td>role</td>
+<td></td>
+<td>continue</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="b"><td>group-fallback</td>
+<td><p>A group based fallback algorithm, trying to find the most-specific resource by searching over all security groups for the current authenticated user.</p>
+<table class="bodyTable"><tr class="a"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="b"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>stop</td>
+</tr>
+<tr class="a"><td>group</td>
+<td>group</td>
+<td></td>
+<td>continue</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="b"><td>j2</td>
+<td><p>The default profiling rule for users and mediatype minus language and country.</p>
+<table class="bodyTable"><tr class="a"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="b"><td>mediatype</td>
+<td>mediatype</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="a"><td>group.role.user</td>
+<td>user|group|role</td>
+<td></td>
+<td>stop</td>
+</tr>
+<tr class="b"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>stop</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="a"><td>security</td>
+<td><p>The security profiling rule needed to force credential change requirements.</p>
+<table class="bodyTable"><tr class="b"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="a"><td>hard.coded</td>
+<td>page</td>
+<td>/my-account.psml</td>
+<td>stop</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="b"><td>path</td>
+<td><p>Only criterion applied is the path portion of the portal URL.</p>
+<table class="bodyTable"><tr class="a"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="b"><td>path</td>
+<td>page</td>
+<td>/</td>
+<td>stop</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="a"><td>user-role-fallback</td>
+<td><p>Rule will first look for the resource in the user's home folder. If not found there, a role based fallback algorithm is applied, trying to find the most-specific resource by searching over all security roles for the current authenticated user.</p>
+<table class="bodyTable"><tr class="b"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="a"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>continue</td>
+</tr>
+<tr class="b"><td>role</td>
+<td>role</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="a"><td>navigation</td>
+<td>navigation</td>
+<td>/</td>
+<td>loop</td>
+</tr>
+<tr class="b"><td>user</td>
+<td>user</td>
+<td></td>
+<td>continue</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="a"><td>user-rolecombo-fallback</td>
+<td><p>Rule will first look for the resource in the user's home folder. If not found there, a role based fallback algorithm is applied, trying to find the most-specific resource by searching over all security roles for the current authenticated user. Creates a locater property named <quote>role</quote> that is the concatenation of all roles into one string, such as <i>role1-role2-role3</i>. This combined string is used as the role name in the locator.</p>
+<table class="bodyTable"><tr class="b"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="a"><td>path.session</td>
+<td>page</td>
+<td>default-page</td>
+<td>continue</td>
+</tr>
+<tr class="b"><td>rolecombo</td>
+<td>role</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="a"><td>navigation</td>
+<td>navigation</td>
+<td>/</td>
+<td>loop</td>
+</tr>
+<tr class="b"><td>user</td>
+<td>user</td>
+<td></td>
+<td>continue</td>
+</tr>
+</table>
+</td>
+</tr>
+<tr class="a"><td>subsite-role-fallback-home</td>
+<td><p>A rule based on role fallback algorithm with specified subsite and home page</p>
+<table class="bodyTable"><tr class="b"><th>criterion</th>
+<th>name</th>
+<th>value</th>
+<th>fallback</th>
+</tr>
+<tr class="a"><td>path</td>
+<td>path</td>
+<td>subsite-default-page</td>
+<td>stop</td>
+</tr>
+<tr class="b"><td>role</td>
+<td>role</td>
+<td></td>
+<td>continue</td>
+</tr>
+<tr class="a"><td>navigation</td>
+<td>navigation</td>
+<td>subsite-root</td>
+<td>loop</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="section"><h2><a name="Profile_Locators"></a>Profile Locators</h2>
+<p>
+Profile Locators are used to locate profiled portal resources such as
+pages, folders, menus and links. A locator contains a collection of properties
+(name value pairs) describing the actual resource to be located.
+</p>
+<img src="../devguide/images/parameter-resolution.jpg" /><p>
+The profiler takes runtime information as input, generalized into
+generalized profile locators that are passed on to the page manager to locate a page or menu.
+The profile locators are normalized and not coupled to the profiler or page manager implementation.
+</p>
+<img src="../devguide/images/parameter-resolution-2.jpg" /></div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/profiler.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/adminguide/roles.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/roles.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/roles.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/roles.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,302 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - Role Administration Guide</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <strong>Roles</strong>
+ </li>
+
+ <li class="none">
+ <a href="sso.html">SSO</a>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <a href="site.html">Portal Site</a>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <a href="profiler.html">Profiler</a>
+ </li>
+
+ <li class="none">
+ <a href="rpad.html">Remote Deployment</a>
+ </li>
+
+ <li class="none">
+ <a href="search.html">Search</a>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"><person name="Jody McAlister" email="jmcalister@onehippo.com"><person name="Jeff Maddux" email="jmaddux@onehippo.com"></authors><div class="section"><h2><a name="Role_Administration_Guide"></a>Role Administration Guide</h2>
+<p>
+ Role Management is where you manage individual portal roles. You can create new roles and remove existing roles.
+ You can assign users to roles. The Role Management page is located inside the Jetspeed Administrative Portlets section.
+ The Role Management page is the second tab on the administrative menu across the top. The Role management section is comprised
+ of two portlets, Role Admin and Role Detail Information.
+ </p>
+</div>
+<div class="section"><h2><a name="Role_Admin"></a>Role Admin</h2>
+<p>
+ The Role Admin portlet lists all portal roles and allows you to search for a particular role.
+ </p>
+<p><img src="images/roles.png" /></p>
+<div class="section"><h3><a name="Searching"></a>Searching</h3>
+<p>
+ You can search for a particular role by entering the role name or part of the role name in the search text box.
+ After clicking on the "Search" button, the role listing will show the search results, starting with the user that best matched your
+ search query, followed by the users that normally appear after the matched user in alphabetical order.
+ </p>
+</div>
+<div class="section"><h3><a name="Filtering"></a>Filtering</h3>
+<p>
+ To get only exact matches when searching for (or part of) a particular role name, check the "filter" checkbox below the
+ search text box.
+ </p>
+</div>
+</div>
+<div class="section"><h2><a name="Adding_and_Deleting_Roles"></a>Adding and Deleting Roles</h2>
+<p>
+ The Role Detail Information portlet allows you to add and/or remove roles. Select a role in the Role admin portlet and the Role
+ Detail Information portlet will update with members of that role. The selected role in the Role admin porlet will now have an
+ arrow marking it.
+ </p>
+<p><img src="images/roledetail.png" /></p>
+<div class="section"><h3><a name="Adding_a_Role"></a>Adding a Role</h3>
+<p>
+ To add a role, depending on the Role Detail Information portlets state, you either need to...
+ <ul><li>select "Add New Role", enter a role name and press "Save" (screenshot above), or</li>
+<li>enter a role name and press "Save" (screenshot below).</li>
+</ul>
+</p>
+<p><img src="images/roledetailsimple.png" /></p>
+</div>
+<div class="section"><h3><a name="Removing_a_Role"></a>Removing a Role</h3>
+<p>
+ To remove a role from the system, click on the desired role in the Role Admin portlet. A small arrow will appear in front of the
+ role name to indicate it is currently selected, and the role's existing users will be loaded in the Role Details Information portlet.
+ Click the "Remove Role" button. This action is permanent.
+ </p>
+</div>
+</div>
+<div class="section"><h2><a name="Adding_Users_to_Roles"></a>Adding Users to Roles</h2>
+<p>
+ To add or remove users assigned to a role, click on the role name in the Role Admin portlet. A small arrow will appear in front of the
+ role name to indicate it is currently selected, and the role's existing users will be loaded in the Role Details Information portlet.
+ </p>
+<div class="section"><h3><a name="Paging"></a>Paging</h3>
+<p>
+ If there are more than ten users assigned to a role in the system, the role listing is spread over several pages
+ each displaying ten users. You can navigate through the pages using the buttons right below the listing.
+ Clicking on the "Refresh" button will reset the user listing to the first page.
+ </p>
+<p><img src="images/roledetailpaging.png" /></p>
+</div>
+<div class="section"><h3><a name="Add_Users_to_Role"></a>Add Users to Role</h3>
+<p>
+ The Role Detail Information portlet allows you to add users to a role. Select "Add Users to Role".
+ A pop-up window will appear. Check the users you wish to add and click "Add Users". The Role Detail Information portlet
+ will be populated with the selected users.
+ </p>
+<p><img src="images/roleuserchooser.png" /></p>
+</div>
+<div class="section"><h3><a name="Remove_Checked_Users"></a>Remove Checked Users</h3>
+<p>
+ To remove a user from a role, select the user(s) you wish to remove and click on the "Remove Checked Users" button.
+ Be aware that this action is permanent!
+ </p>
+<p><img src="images/roleremove.png" /></p>
+</div>
+<div class="section"><h3><a name="Search_Users_in_Role"></a>Search Users in Role</h3>
+<p>
+ You can search for a particular user by entering the users name or part of the users name in the search text box.
+ After clicking on the "Search" button, the "Users in Role" listing will show the search results, starting with the user that best matched your
+ search query, followed by the users that normally appear after the matched user in alphabetical order.
+ </p>
+</div>
+<div class="section"><h3><a name="Filter_Users_in_Role"></a>Filter Users in Role</h3>
+<p>
+ To get only exact matches when searching for (or part of) a particular user name, check the "filter" checkbox below the
+ search text box. Clicking on the "Refresh" button will reset the group listing to the first page.
+ </p>
+</div>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/roles.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/adminguide/rpad.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/rpad.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/rpad.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/rpad.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,274 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - Remote Portlet Application Deployment Administration Guide</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <a href="roles.html">Roles</a>
+ </li>
+
+ <li class="none">
+ <a href="sso.html">SSO</a>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <a href="site.html">Portal Site</a>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <a href="profiler.html">Profiler</a>
+ </li>
+
+ <li class="none">
+ <strong>Remote Deployment</strong>
+ </li>
+
+ <li class="none">
+ <a href="search.html">Search</a>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"><person name="Jody McAlister" email="jmcalister@onehippo.com"></authors><div class="section"><h2><a name="Remote_Portlet_Application_Deployment_Administration_Guide"></a>Remote Portlet Application Deployment Administration Guide</h2>
+<p>
+ The Remote Portlet Application Deployer can be found in the Jetspeed Administrative Portlets Tabbed Menu named RPAD. You may use
+ this portlet to deploy War files containing portlets that are not available by default. Once the the War has been deployed, you will find
+ any new portlets by going to <a href="../usersguide/portletmodes.html">edit mode</a> and the <a href="../usersguide/portlets.html#adding_portlets">Add Portlet</a> area.
+ </p>
+<p><img src="images/rpadmain.png" /></p>
+<p><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Group ID</td>
+<td>Name of the organization or company distributing the war file.</td>
+</tr>
+<tr class="a"><td>Artifact ID</td>
+<td>The common way of naming a distributable file.</td>
+</tr>
+<tr class="b"><td>Name</td>
+<td>Name of the portlet application, usually the same as the Artifact ID.</td>
+</tr>
+<tr class="a"><td>Version</td>
+<td>The version of the portlet application.</td>
+</tr>
+<tr class="b"><td>Type</td>
+<td>Portlet applications only, currently always distributed as war artifacts.</td>
+</tr>
+<tr class="a"><td>Action</td>
+<td>Deploy the portlet application within Jetspeed. You can manage the portlet application with the <a href="palm.html">PALM</a> (Portlet Application Lifecycle Manager).</td>
+</tr>
+</table>
+</p>
+<p>
+ The repository drop down menu has a listing of all currently included repositories. By default, all repository items are displayed
+ in groups of 10. Paging at the bottom of the portlet will allow you to navigate through the pages. Choosing one of the repositories
+ in the drop down menu and clicking Select will change the display so that only items from that repository are displayed. Selecting the
+ blank menu option will result in items from all repositories being displayed.
+ </p>
+<p><img src="images/rpadselect.png" /></p>
+<p>
+ The Refresh button is used to redraw the contents of the window. Refreshing is needed after clicking the deploy link as the deploy action will
+ change all deploy links to a non-clickable state. These deploy links will remain unclickable for the duration of the deployment process, regardless
+ of pressing the Refresh Button. The deploy links will return to their normal state after the deployment process has completed and the screen is
+ redrawn through the Refresh Button or any other action requiring the portlet to redraw the window contents.
+ </p>
+<div class="section"><h3><a name="Managing_Repositories"></a>Managing Repositories</h3>
+<p>
+ Repositories may be managed by entering into <a href="../usersguide/portletmodes.html">edit mode</a> from the portlet action bar.
+ </p>
+<p><img src="images/rpadmanage.png" /></p>
+<p>
+ The Edit action link will allow you to change existing information such as repository name and the location of the configuration file for the repository.
+ The window will change similar to the screenshot pictured below for Add Repository.
+ </p>
+<p>
+ The Delete action link remove the repository located in the same row as the link.
+ </p>
+<p>
+ The Reload Repositories button will refresh the configuration xml files for each repository.
+ </p>
+<p>
+ The Add Repository button will take you to another window which will allow you to enter a name for the repository and a Configuration
+ Path to an xml file with the Repository information.
+ </p>
+<p><img src="images/rpadadd.png" /></p>
+</div>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/rpad.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/adminguide/search.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/search.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/search.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/search.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,225 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - Jetspeed-2 Search</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <a href="roles.html">Roles</a>
+ </li>
+
+ <li class="none">
+ <a href="sso.html">SSO</a>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <a href="site.html">Portal Site</a>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <a href="profiler.html">Profiler</a>
+ </li>
+
+ <li class="none">
+ <a href="rpad.html">Remote Deployment</a>
+ </li>
+
+ <li class="none">
+ <strong>Search</strong>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <authors><person name="David Le Strat" email="dlestrat@apache.org"></authors><div class="section"><h2><a name="Using_Jetspeed_Search_Engine"></a>Using Jetspeed Search Engine</h2>
+<p>
+ Jetspeed-2 <code>SearchEngine</code> exposes a <code>search</code> operation returning <code>SearchResults</code>.
+ The <code>SearchResult</code> can be iterated through to display the result of the search.
+ </p>
+<div class="section"><h3><a name="Portlet_Search"></a>Portlet Search</h3>
+<p>
+ Jetspeed-2 <code>SearchEngine</code> is used by the <code>PortletApplicationBrowser</code> portlet to search
+ and retrieve portlet according to a given criteria.
+ <br />
+<img src="images/portlet-search.gif" /></p>
+<p>
+ Performing a search for "security" returns all the matching portlets and portlet definitions.
+ </p>
+</div>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/search.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/adminguide/site.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/site.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/site.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/site.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,571 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - Portal Site Administration Guide</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <a href="roles.html">Roles</a>
+ </li>
+
+ <li class="none">
+ <a href="sso.html">SSO</a>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <strong>Portal Site</strong>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <a href="profiler.html">Profiler</a>
+ </li>
+
+ <li class="none">
+ <a href="rpad.html">Remote Deployment</a>
+ </li>
+
+ <li class="none">
+ <a href="search.html">Search</a>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"><person name="Jody McAlister" email="jmcalister@onehippo.com"><person name="Niels van Kampenhout" email="n.vankampenhout@onehippo.com"></authors><div class="section"><h2><a name="Portal_Site_Administration_Guide"></a>Portal Site Administration Guide</h2>
+<p>
+ The Portal Site Manager can be looked at as a file-system-like tree of portal resources.
+ </p>
+<p>
+ The site is made up of three different kinds of resources:
+ </p>
+<ul><li><a href="#PSML_Pages">PSML Pages</a></li>
+<li><a href="#Folders">Folders</a></li>
+<li><a href="#Links">Links</a></li>
+</ul>
+<p>
+ All portal resources can be customized in Jetspeed. Portal Site Manager is just one of the
+ tools available for customizing. Other tools are the Jetspeed Customizer (both Desktop and Portal), Edit Mode,
+ Configure Mode, Edit Defaults Mode of a portlet and the Portlet Selector.
+ </p>
+<div class="section"><h3><a name="PSML_Pages"></a>PSML Pages</h3>
+<p>
+ The XML dialect for defining resources and elements that make up the site is also known as PSML (Portal Structure Markup Language).
+ PSML is not a standard.
+ </p>
+<p>
+ PSML pages define how and where portlets are placed on a page, as well as how the page is decorated and branded.
+ </p>
+<p>
+ A PSML page defines :
+ <ul><li>metadata, such as titles and descriptions</li>
+<li>decorations (both page and portlet)</li>
+<li>layout fragments (number of columns on the page, and nesting of columns)</li>
+<li>which portlets are displayed on the page, defined by portlet fragments</li>
+<li>the position of the portlet on the page</li>
+<li>properties of the portlets</li>
+<li>preferences of a portlet</li>
+<li>security constraints</li>
+</ul>
+</p>
+<p>
+ To customize a PSML page through the Portal Site Manager, select it in the tree. On the right side of the tree
+ four tabs will appear allowing you to customize various aspects of the page through a form.
+ </p>
+<p>
+ Each of the four tabs is described below.
+ </p>
+<h4>Information Tab</h4>
+<p>
+ The Information Tab allows you to customize the title and appearance of the page.
+ </p>
+<img src="images/psm_psml_info.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Name</td>
+<td>Name of the .psml file.</td>
+</tr>
+<tr class="a"><td>Title</td>
+<td>Name that appears in the xml title field for this object.</td>
+</tr>
+<tr class="b"><td>Short Title</td>
+<td>Name that appears in the xml short title field for this object.</td>
+</tr>
+<tr class="a"><td>Page Decorator</td>
+<td>Drop down menu of all available page decorators.</td>
+</tr>
+<tr class="b"><td>Portlet Decorator</td>
+<td>Drop down menu of all available portlet decorators.</td>
+</tr>
+<tr class="a"><td>Desktop Theme</td>
+<td>Drop down menu of all available desktop themes.</td>
+</tr>
+<tr class="b"><td>Hidden</td>
+<td>Hidden folders do not show up on menus, but can still be navigated to. </td>
+</tr>
+</table>
+<h4>Security Tab</h4>
+<p>
+ The Security Tab allows you to modify a page's security constraints. All security constraints
+ defined for the selected page are shown in a list. To modify a constraint, select it from the list
+ and choose a new value in the dropdown field.
+ </p>
+<img src="images/psm_psml_security.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Constraints</td>
+<td>Any Security and Constraint types will be listed here for the selected item.</td>
+</tr>
+</table>
+<h4>Metadata Tab</h4>
+<p>
+ The Metadata Tab shows a list of metadata properties that might be defined for the page, e.g. translations
+ in different languages of the page title, such as shown in the screenshot below. Clicking on a property
+ will load it in the form right below the list so that the values can be modified.
+ </p>
+<img src="images/psm_psml_metadata.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Name</td>
+<td>Name of attribute in xml file for this object.</td>
+</tr>
+<tr class="a"><td>Language</td>
+<td>Localization of the attribute.</td>
+</tr>
+<tr class="b"><td>Value</td>
+<td>Text to be localized.</td>
+</tr>
+</table>
+<h4>Export Tab</h4>
+<p>
+ The Export Tab provides an XML export of the page. The exported XML file can be used
+ to store customizations made through the user interface in a custom portal project,
+ so that when a new version of the portal is deployed, the customizations do not have
+ to be made again.
+ </p>
+<img src="images/psm_psml_export.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Export Object</td>
+<td>Export the selected item in XML format.</td>
+</tr>
+</table>
+</div>
+<div class="section"><h3><a name="Links"></a>Links</h3>
+<p>
+ Links are URLs to external resources, usually outside of the site.
+ The element is persisted with the .link extension on the file system.
+ </p>
+<p>
+ To customize a link through the Portal Site Manager, select it in the tree. On the right side of the tree
+ four tabs will appear allowing you to customize various aspects of the link through a form.
+ </p>
+<p>
+ Each of the four tabs is described below.
+ </p>
+<h4>Information Tab</h4>
+<p>
+ The Information Tab allows you to change the title and the URL of a link.
+ </p>
+<img src="images/psm_link_info.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Name</td>
+<td>Name of .link file.</td>
+</tr>
+<tr class="a"><td>Title</td>
+<td>Name that appears in the xml title field for this object.</td>
+</tr>
+<tr class="b"><td>Short Title</td>
+<td>Name that appears in the xml short title field for this object.</td>
+</tr>
+<tr class="a"><td>URL</td>
+<td>The resource to be displayed when clicked.</td>
+</tr>
+<tr class="b"><td>Target Window</td>
+<td>The web browser action when the link is clicked on for displaying the Target. (New, Self, Parent, Top)</td>
+</tr>
+<tr class="a"><td>Hidden</td>
+<td>Hidden folders do not show up on menus, but can still be navigated to. </td>
+</tr>
+</table>
+<h4>Security Tab</h4>
+<p>
+ The Security Tab allows you to modify a link's security constraints. All security constraints
+ defined for the selected link are shown in a list. To modify a constraint, select it from the list
+ and choose a new value in the dropdown field.
+ </p>
+<img src="images/psm_link_security.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Constraints</td>
+<td>Any Security and Constraint types will be listed here for the selected item.</td>
+</tr>
+</table>
+<h4>Metadata Tab</h4>
+<p>
+ The Metadata Tab shows a list of metadata properties that might be defined for the link, e.g. translations
+ in different languages of the link title, such as shown in the screenshot below. Clicking on a property
+ will load it in the form right below the list so that the values can be modified.
+ </p>
+<img src="images/psm_link_metadata.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Name</td>
+<td>Name of attribute in xml file for this object.</td>
+</tr>
+<tr class="b"><td>Language</td>
+<td>Localization of the attribute.</td>
+</tr>
+<tr class="a"><td>Value</td>
+<td>Text to be localized.</td>
+</tr>
+</table>
+<h4>Export Tab</h4>
+<p>
+ The Export Tab allows you to export a link to an XML file.
+ </p>
+<img src="images/psm_link_export.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Export Object</td>
+<td>Export the selected item in xml format.</td>
+</tr>
+</table>
+</div>
+<div class="section"><h3><a name="Folders"></a>Folders</h3>
+<p>
+ A folder is a container object that holds:
+ </p>
+<ul><li>subfolders (which in turn can hold subfolders, pages, links...)</li>
+<li>pages</li>
+<li>links</li>
+</ul>
+<p>
+ Folders make up the physical layout of your site and have the following attributes :
+ </p>
+<ul><li>Localizable Metadata (name, title, short-title, description)</li>
+<li>Optional Default-page </li>
+<li>Optional Decorator</li>
+<li>Hidden Flag (hidden folders do not show up on menus, but can still be navigated to)</li>
+<li>Security Constraints </li>
+<li>Menus</li>
+<li>Document Ordering</li>
+</ul>
+<p>
+ To customize a folder through the Portal Site Manager, select it in the tree. On the right side of the tree
+ seven tabs will appear allowing you to customize various aspects of the link through a form.
+ </p>
+<p>
+ Five of the seven tabs are described below (Information, Security, Metadata, Import, Export). The Menus and Order Tabs
+ are placeholders for future functionalities and do not currently contain any information.
+ </p>
+<h4>Information Tab</h4>
+<img src="images/psm_folder_info.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Name</td>
+<td>Name of the folder in the Portal Site Manager tree.</td>
+</tr>
+<tr class="b"><td>Title</td>
+<td>Title of the Folder as it appears in the xml file.</td>
+</tr>
+<tr class="a"><td>Short Title</td>
+<td>Short Tile of the folder as it appears in the xml file.</td>
+</tr>
+<tr class="b"><td>Default Page</td>
+<td>Optional. Page to default to when browsing.</td>
+</tr>
+<tr class="a"><td>Page Decorator</td>
+<td>Drop down menu of all available page decorators.</td>
+</tr>
+<tr class="b"><td>Portlet Decorator</td>
+<td>Drop down menu of all available portlet decorators.</td>
+</tr>
+<tr class="a"><td>Hidden</td>
+<td>Hidden folders do not show up on menus, but can still be navigated to. </td>
+</tr>
+</table>
+<h4>Security Tab</h4>
+<p>
+ The Security Tab allows you to modify a folder's security constraints. All security constraints
+ defined for the selected folder are shown in a list. To modify a constraint, select it from the list
+ and choose a new value in the dropdown field.
+ </p>
+<img src="images/psm_folder_security.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Constraints</td>
+<td>Any Security and Constraint types will be listed here for the selected item.</td>
+</tr>
+</table>
+<h4>Metadata Tab</h4>
+<p>
+ The Metadata Tab shows a list of metadata properties that might be defined for the folder, e.g. translations
+ in different languages of the folder title, such as shown in the screenshot below. Clicking on a property
+ will load it in the form right below the list so that the values can be modified.
+ </p>
+<img src="images/psm_folder_metadata.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>Name</td>
+<td>Name of attribute in xml file for this object.</td>
+</tr>
+<tr class="b"><td>Language</td>
+<td>Localization of the attribute.</td>
+</tr>
+<tr class="a"><td>Value</td>
+<td>Text to be localized.</td>
+</tr>
+</table>
+<h4>Import Tab</h4>
+<p>
+ The Import Tab allows you to import a folder that you previously exported as XML file.
+ </p>
+<img src="images/psm_folder_import.png" /><table class="bodyTable"><tr class="b"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="a"><td>File to Import</td>
+<td>Use the browse button to search local files for the xml file to be imported.</td>
+</tr>
+<tr class="b"><td>File Destination</td>
+<td>The path to place the xml file being imported.</td>
+</tr>
+</table>
+<h4>Export Tab</h4>
+<p>
+ The Export Tab allows you to export a folder to an XML file. Optionally you can resursively
+ export all sub items inside the folder as well by checking the "Export recursively" checkbox.
+ </p>
+<img src="images/psm_folder_export.png" /><table class="bodyTable"><tr class="a"><th>Field</th>
+<th>Description</th>
+</tr>
+<tr class="b"><td>Export Object</td>
+<td>Export folder.metadata in xml format.</td>
+</tr>
+<tr class="a"><td>Export Recursively</td>
+<td>Export all sub-items in the xml format as well as the folder.metadata.</td>
+</tr>
+</table>
+</div>
+<div class="section"><h3><a name="Portal_Tree_vs._User_Tree"></a>Portal Tree vs. User Tree</h3>
+<p>
+ There are system wide portal resources and personalized or user specific portal resources. These are
+ represented by separate trees. The Portal Site Manager allows you to switch between these two
+ trees.
+ </p>
+<h4>Portal Tree</h4>
+<img src="images/psmportal.png" /><h4>User Tree</h4>
+<img src="images/psmusertree.png" /></div>
+<div class="section"><h3><a name="Control_Folders"></a>Control Folders</h3>
+<p>
+ Control folders always start with the underscore _.
+ </p>
+<p>
+ Control folders are used to separate pages based on runtime parameters. For example, you may have a different set of pages for a phone vs. a full web-browser.
+ In that case, you place your pages for the phone under a WML directory, where you may have less portlets per page than the HTML directory.
+ </p>
+<p>
+ There is a special folder named (_subsite_root) :
+ </p>
+<ul><li>Subsites sub-divide your portal site into independent "portal site" trees. This enables use-case scenarios such as hosting two or more
+ portals on the same portal instance (app server)</li>
+<li>Users can be configured to point to a particular subsite which will become their view of the portal</li>
+</ul>
+<p>
+ The User folder (_user) :
+ </p>
+<ul><li>The _user folder holds the home pages of all users. Each user can have a folder with multiple subfolders, pages and links</li>
+<li>A user is not required to have a home folder. Depending on the user profile, the user home page may or may not be used </li>
+<li>Usually, a user's home page is made customizable (editable) to the user, but not to others</li>
+<li>Jetspeed uses "templates" to create default pages for users when the user first registers or is created by an Administrator</li>
+</ul>
+<p>
+ Roles and Group Folders (_role and _group) :
+ </p>
+<ul><li>Role and group folders are useful for sharing pages based on the roles or groups that a user belongs in. Typical use cases are for granting (or denying)
+ access to pages</li>
+<li>Role folder names should be the same as the roles defined in the system, likewise for groups</li>
+<li>A user's profile defines where pages are to be searched</li>
+<li>A user profile called "role-fallback" looks for pages in the _role directory, based on the users's security profile. It will search
+ through all folders based on the roles that a user holds</li>
+<li>A common profile rule is to first search the user's home directory, then each of the role directories for the given user, and the the
+ default root tree to find the page</li>
+</ul>
+</div>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/site.html
------------------------------------------------------------------------------
svn:executable = *
Added: portals/site-live/jetspeed-2.1.3/adminguide/sso.html
URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2.1.3/adminguide/sso.html?rev=1422709&view=auto
==============================================================================
--- portals/site-live/jetspeed-2.1.3/adminguide/sso.html (added)
+++ portals/site-live/jetspeed-2.1.3/adminguide/sso.html Sun Dec 16 22:54:22 2012
@@ -0,0 +1,224 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Jetspeed Administrators Guide - SSO Administration Guide</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/jetspeed-2/" id="bannerLeft">
+
+ <img src="images/jetspeed-logo.gif" alt="" />
+
+ </a>
+ <a href="http://portals.apache.org/jetspeed-2.1.3/adminguide/" id="bannerRight">
+
+ <img src="images/admin-guide.png" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 14 July 2010
+ </div>
+ <div class="xright"> <a href="http://portals.apache.org/applications/" class="externalLink">Applications</a>
+ |
+ <a href="http://portals.apache.org/" class="externalLink">Portals</a>
+ |
+ <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Jetspeed-2.2</a>
+ |
+ <a href="../index.html">Home</a>
+ |
+ <a href="../deployguide/index.html">Deployers Guide</a>
+ |
+ <a href="../devguide/index.html">Developer Guide</a>
+ |
+ <a href="../usersguide/index.html">Users Guide</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>Admin Guide</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Security Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="constraints.html">Constraints</a>
+ </li>
+
+ <li class="none">
+ <a href="credentials.html">Credentials</a>
+ </li>
+
+ <li class="none">
+ <a href="groups.html">Groups</a>
+ </li>
+
+ <li class="none">
+ <a href="permissions.html">Permissions</a>
+ </li>
+
+ <li class="none">
+ <a href="roles.html">Roles</a>
+ </li>
+
+ <li class="none">
+ <strong>SSO</strong>
+ </li>
+
+ <li class="none">
+ <a href="users.html">Users</a>
+ </li>
+ </ul>
+ <h5>Portal Administration</h5>
+ <ul>
+
+ <li class="none">
+ <a href="pam.html">Applications</a>
+ </li>
+
+ <li class="none">
+ <a href="palm.html">Application Lifecycle</a>
+ </li>
+
+ <li class="none">
+ <a href="import.html">Import/Export</a>
+ </li>
+
+ <li class="none">
+ <a href="site.html">Portal Site</a>
+ </li>
+
+ <li class="none">
+ <a href="portlet-selector.html">Portlet Selector</a>
+ </li>
+
+ <li class="none">
+ <a href="profiler.html">Profiler</a>
+ </li>
+
+ <li class="none">
+ <a href="rpad.html">Remote Deployment</a>
+ </li>
+
+ <li class="none">
+ <a href="search.html">Search</a>
+ </li>
+
+ <li class="none">
+ <a href="statistics.html">Statistics</a>
+ </li>
+
+ <li class="none">
+ <a href="subsites.html">Subsites</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <subtitle></subtitle><authors><person name="David Sean Taylor" email="taylor@apache.org"><person name="Jody McAlister" email="jmcalister@onehippo.com"></authors><div class="section"><h2><a name="Jetspeed_Single_Signon"></a>Jetspeed Single Signon</h2>
+<p>Jetspeed-2 (J2) Single Sign-on (SSO) feature is a credential store implemented as a component. It uses J2 security implementation for storing credentials. A management portlet allows the editing of SSO sites and remote credentials. It supports Basic Authentication and Form Based authentication and supports cookies.</p>
+<p>The SSO Management feature enables you to create "single sign-on" access, a permission-based access to applications and underlying tools, which provides an added layer of security and administarative control of Jetspeed-2 content. SSO Management enables the Users of Groups (several Users initially defined in the Group Management tab) to sign-on a single time for jetspeed-2 portal and specified sites and databases.</p>
+</div>
+<div class="section"><h2><a name="SSOProxy_Portlet"></a>SSOProxy Portlet</h2>
+<para>As the name indicates the SSOProxy portlet is the proxy between the portal and authenticated sites. In the preferences a user defines the destination page which might need authentication itself or has links to authenticated pages (inside or outside the portal).</para><para>The SSOProxy Portlet authenticates all SSO sites for the user before it goes to the destination URL defined in the preferences. The SSOProxy keeps a cache of of the proxy client so that the authentication only takes place the first time.</para><para></div>
+<div class="section"><h2><a name="SSO_Provider_service"></a>SSO Provider service</h2>
+<para>The SSO Provider is a part of the jetspeed service framework and is available to any portlet and not just the SSOProxy Portlet. The component takes care of storing the sites and credentials and has an API to get content from a url.</para><para></div>
+<div class="section"><h2><a name="SSO_Management"></a>SSO Management</h2>
+<para>The SSO management portlet helps to administer SSO credentials and assigning them to Portal Users.</para><p><img src="images/sso-manage.png" /></p>
+<p>
+ The Portal Principal field may be populated by clicking on either the user icon or the group icon. A pop up window will display to allow you to
+ select your user or group.
+</p>
+</div>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2010
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Propchange: portals/site-live/jetspeed-2.1.3/adminguide/sso.html
------------------------------------------------------------------------------
svn:executable = *