Important note

Due to some limitations using AJAX in esup-commons portlet, this tools can only be used in servlet mode. This isn't a big problem
because this tool is only used by anonymous users who wish to activate their LDAP account.

Installation

esup-activation relies on esup-commons, so it can be installed as an described in esup-commons documentation : http://sourcesup.cru.fr/esup-commons/admin/index.html

• Download esup-activaccount-<version>.zip from the projectsite
• Unzip the file somewhere on a working directory

  To configure this application you have to adapt some configuration files. Every time you will find a <fileName>-example.<extension> example file that you can copy to <fileName>.<extension> before adapting.

• Adapt build.properties
• Adapt properties/config.properties for exception handling configuration, SMTP configuration

  esup-activaccount doesn't use any database.

  By default, exception reports are also sent to an archived bugs mailing list, accessible to the developers of the project only. This feature is used to be warned of all the possible exceptions occuring on the applciation anywhere; this way, most bugs can be corrected as soon as they happen. If you do not want the exceptions to be sent to this list, you can manually set property doNotSendExceptionReportsToDevelopers to true.

• Test your configuration:
  • ant test-config
  • ant test-smtp

• Deploy the application:
  • ant deploy

• Since 1.2: Import lecture.css in main portal css page.
  For example with esup skin in a esup-portail package:
  • copy esup.css form update/uPortal/webpages/media/org/jasig/portal/layout/tab-column/xhtml-theme/esup to custom/uPortal/webpages/media/org/jasig/portal/layout/tab-column/xhtml-theme/esup/skin
  • adap esup.css by adding :

    @import url("lecture.css");
    

  • copy lecture.css in custom/uPortal/webpages/media/org/jasig/portal/layout/tab-column/xhtml-theme/esup/skin
  • use ant init deploy

Configuration

You can configure your application. For this: adapt file(s) in properties directory and use ant deploy to deploy again your application.

Technical configuration

Adapt to your environment these configuration files:

• logging/log4j.properties for logging configuration
• esup-lecture.xml for global configuration

  esup-lecture.xml

This file contents some global configuration properties:

• element guestUser in esup-lecture.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE channelConfig SYSTEM "lecture-config.dtd" >
<channelConfig>
  <guestUser>guest</guestUser>

guestUser is an optional propertie. Default value is "guest".
If current connected user name equals guestUserproperty then all controls used for personalisation (change tree size buttons, mark an item as read button, edit button, etc.) are hidden.
This is used in Portlet mode when esup-lecture is used in a portal unauthenticated view.

Content configuration

To adapt to your environment, edit these configuration files:

• esup-lecture.xml: main configuration file. Contexts and CategoryProfiles definition.
  It also deals with <category>.xml: remote xml file referecend by CategoryProfiles.
  
• mappings.xml: declarations about xslt transformation for interface display
• portlet.xml: it needs declaration of portal user attributes used by Lecture Portlet
• auth.xml: auth configuration

  XML Elements or attributes not explained here (but in dtd) implements features that are not yet supported.

  esup-lecture.xml and <category>.xml

These files describe contexts, category profiles and userId definition. Here is the structure of this file (for more information, look at dtd lecture-config.dtd):

• element channelConfig in esup-lecture.xml:
  

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE channelConfig SYSTEM "lecture-config.dtd" >
  <channelConfig>
  
    <!-- contexts definition -->
    <context> ... </context>
    <context> ... </context>
    ...
  
    <!-- category profile definition -->
    <categoryProfile> ... </categoryProfile>
    <categoryProfile> ... </categoryProfile>
    ...
  
  </channelConfig>
  

• element context:
  

  <context
     name = "Démonstration Esup-Lecture"
     id = "default">
     <description>Context de démo</description>
     <refCategoryProfile refId="demo1"/>
     <refCategoryProfile refId="demo2"/>
     ...
  </context>
  

  Here are defined context with:
• id (You can use a specific context by configuring your portlet with a portlet preference. This portlet preference must have a name "context" and a value equals to the id you want for this portlet. If you don't define any context preference for your portlet then context with id "default" is used. With this mechanism you can define many channels with many contexts definitions in your portal environment with just one instance of the portlet.

  Before uPortal 2.5.4, because of a bug (http://www.ja-sig.org/issues/browse/UP-1040) you can't use this feature.

• name (displayed on interface) 
• description (displayed on interface) 
• refCategoryProfile references on category profile declared in this context (using category profile id)You can declare as many category profiles as you want in a context. Each category profile must be defined in an element categoryProfile. A same categoryProfile can be declared in many contexts. 
• element categoryProfile:

<categoryProfile   name="Categorie de démo"
   id="demo1"
   urlCategory="http://partages.univ-rennes1.fr/files/partages/Services/CRI/SI/conf_lecture_gwe_ray/demo1.xml"
   trustCategory="no"
   access="public"
   ttl = "3600"
   timeout = "3000">
   <visibility> ... </visibility>
</categoryProfile>

Here are defined category profile id, name, and

• • urlCategory : url to get back a xml category file on a remote server 
  • trustCategory ( yes | no ) : If it is "yes", visibility rights used are those of remote category and sources. If it is "no", visibility rights on category and sources used are those of this category profile, defined in visibility element.
  • access ( public | cas ) : access of the category is public or cas because it needs CAS proxy ticket for authentication (for more information about CAS configuration see Configuration en déploiement portlet of the ESUP-Commons documentation and CAS en mode portletof the part Utilisation de CAS (French) of the of ESUP-Lecture documentation)
  • ttl (seconds) : time to live of the remote category and its sources
  • timeout (milliseconds) : time trying to get the category
  • visibility : define group visibility for category referenced by this category profile. It is used only if trustCategory is set to "no"

• elementvisibility:
  

  <visibility>
     <allowed/>
     <autoSubscribed/>
     <obliged>
        <group name="local.0"/>
        <group .../>
        ...
        <regular attribute="sn" value="user" />
        <regular .../>
        ...
     </obliged>
  </visibility>
  

  In this element, you define 3 groups of visibility;
  • allowed : user inside are "allowed" to subscribe to a category
  • autoSubscribed : user inside are auto subscribed to this category and is allowed to unsubscribe
  • obliged : user inside are automatically subscribe to this category and can't unsubscribe - for the moment, it is the only way for users to see category -

A user is in a visibility group by two ways :* group : user is in the portal group referenced by attribute name, in the example : user in in group "local.0" - see "portlet.xml" section.

• regular : user check regular, in the example : user value of portal attribute "sn" is "user" - see "portlet.xml" section.* element categoryin xml category file (describe by dtd category.dtd), provided by remote server, requested by urlCategory of esup-lecture.xml :
  

  <?xml version="1.0" encoding="ISO-8859-1"?>
  <!DOCTYPE category SYSTEM "category.dtd">
  <category name="Différents RSS">
    <description>Très belle description !</description>
    <sourceProfiles>
      <sourceProfile> ... </sourceProfiles>
      <sourceProfile> ... </sourceProfiles>
      ...
    </sourceProfiles>
    <visibility> ... </visibility>
  </category>
  

  A category has a name and a description (displayed on interface), and
  • a list of source profiles
  • visibility : define group visibility for this category. It is used only if trustCategory attribute of referencing categoryProfile is set to "yes" else visibility of category profile is used - optional -

• element sourceProfile in xml category file :
  

  <sourceProfile
    id="un" access="public" name="Incidents techniques Rennes 1"
    specificUserContent="no" url="http://info.cri.univ-rennes1.fr/rss/rss.php">
    <visibility> ... </visibility>
  
  </sourceProfile>
  

  A source profile has an id, a name (displayed on interface) and
  • access ( public | cas ) : access of the source is public or cas because it needs CAS proxy ticket for authentication (for more information about CAS configuration see Configuration en déploiement portlet of the ESUP-Commons documentation and CAS en mode portletof the part Utilisation de CAS (French) of the of ESUP-Lecture documentation)
  • specificUserContent ( yes | no) : if it is "yes", source content is specific to user. If it is "no", source content is the same for every users (If your configure with "yes" then application assumes that content can be deferent for each user (may be because of specific content due to profiling according to authentication). In this case application doesn't use any cache for the source. So be careful before use "yes" for this property.)
  • url : url to get xml stream of the source
  • timeout (milliseconds) : Time trying to get the source. Parent category timeout is used is it is not defined here
  • visibility : define group visibility for source refered by this source profile. It is used only if trustCategory attribute of referencing categoryProfile is set to "yes" else visibility category profile is used - optional -

    Be carefull to manage unique id for every sources profiles defined in categories : application does not yet manage it.

mappings.xml

mappings.xml: it describes a list of mappings used to parse xml stream of a source (see mappings.dtd):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mappings SYSTEM "mappings.dtd" >
<mappings>
  <mapping> ... </mapping>
  <mapping> ... </mapping>
  ...
</mappings>

A source is composed of a list of items that will be parsed to be all displayed on interface . A mapping is used to define xsltFile and itemXPath to apply on a source. Sometimes, to define itemXPath, namespaces definition are required. Here is a mapping :

<mapping
  sourceURL="http://info.cri.univ-rennes1.fr/rss/rss.php"
  xsltFile="http://partages.univ-rennes1.fr/files/partages/Services/CRI/SI/conf_lecture_gwe_ray/stylesheet01.xsl"
  itemXPath="/rdf:RDF/default:item">
  <XPathNameSpace prefix="rdf" uri="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
  <XPathNameSpace prefix="default" uri="http://purl.org/rss/1.0/" />
</mapping>

• xsltFile : url of the xslt file used to parse an item
• itemXPath : xpath expression to locate an item in the xml stream source
• element XPathNameSpace : used by itemXPath definition - optionnal
• sourceURL : url of the source, key entry of this mapping
• dtd : dtd of the source, key entry of this mapping
• xmlns : xml namespace of the source, key entry of this mapping
• xmlType : xmlType of the source, key entry of this mapping
• rootElement : rootElement of the source,key entry of this mapping

Priority to find xslt informations on key entry of a mapping are : sourceURL, DTD, xmlType, xmlns and finally rootElement.

portlet.xml

All portal user attributes used by portlet must be declared in the webapp/WEB-INF/portlet.xml, here is an example:

<user-attribute>
  <description>the username of the portal user</description>
  <name>username</name>
</user-attribute>
<user-attribute>
  <description>the displayName of the portal user</description>
  <name>displayName</name>
</user-attribute>
<user-attribute>
  <description>the sn of the portal user</description>
  <name>sn</name>
</user-attribute>

auth.xlm

This file (properties/auth.xml) is used to define auth mecanism. For example when using CAS in servlet mode or a portal in portlet mode:

<bean id="authenticationService"
  class="org.esupportail.commons.services.authentication.PortalOrCasFilterAuthenticator">
  <description>The name of the Portal attribute that holds the uid of users, as set in portlet.xml.</description>
  <property name="uidPortalAttribute" value="uid" />
</bean>

Servlet mode

Introduction

You can used esup-lecture in servlet mode. In this mode you don't have the notion of Portlet preference and you can't define more than one context in your esup-lecture.xml file. In servlet mode this context must have an id with value "default" ("context" before 1.1.0 version). Example:

<context name="Simple context" id="default">
  <description>Simple context</description>
  <refCategoryProfile refId="rss" />
</context>

To used serlvet mode you just have to adapt buil.properties with deploy.type=servlet before using ant deploy.

Authentication

In servlet mode you can't used your portal for authentication. If you used CAS you don't have to modify the auth.xml file but you have to adapt CAS parameters. For this, you will find properties :

• tomcat.host, tomcat.port in buil.properties file.
• casService.bean (it MUST be valued at servletCasService), ccasService.url, casService.proxyCallbackUrl in properties/config.properties file.

  With these properties ant deploy will automatically make appropriate changes in your web.xml file.

Authorization

Authorizations defined in your esup-lecture.xml file or provided by news portlet are based in attributes or groups issued form uPortal. Of course, in servlet mode you don't have access to these informations naturally. So, you have to install (if not yet present in your uPortal distribution) esup-portal-ws (see http://sourcesup.cru.fr/projects/esup-portal-ws/).

After, you have to configure esup-lecture to used this Web Service. For this, you have portalService.url, portalService.testUserId, portalService.testGroupId, portalService.testGroupName properties in the config.properties file. Finally, you can test the Web Service with ant test-portal.

Guest mode

If want to have a guest mode for esup-lecture in servlet mode you have to define a new context in your application server. You have to deploy a new esup-lecture in this new context.