08/06/2004Portal Review1 Knowledge Collaborative Portal Review 8 June 2004 Information Systems and Telecommunication Division.

Présentation au sujet: "08/06/2004Portal Review1 Knowledge Collaborative Portal Review 8 June 2004 Information Systems and Telecommunication Division."— Transcription de la présentation:

1 08/06/2004Portal Review1 Knowledge Collaborative Portal Review 8 June 2004 Information Systems and Telecommunication Division

2 08/06/2004Portal Review2 Menu General IT landscape Functional Presentation - XML Referential Albert – search engine Sympa – mass mailing Static and Chef dOrchestre; KO redirection Portal Development Environment Physical Architecture

3 08/06/2004Portal Review3 General IT Landscape Complex network and application architecture –low level physical infrastructure (cabling, active elements); –IP network architecture (addressing, routing, DNS, DHCP, etc.); –Servers & Systems (Windows, Unix, Linux); File, Web, Application, Database, etc. –Connectivity (Internet, WAN, misc.); –Security (Firewall, Proxy, DMZ) authentication, Antivirus, IDS; –Performance, optimization (Packetshaper, Cache, CoS, Redundancy/Loadbalancing, IP compression, etc.);

4 08/06/2004Portal Review4 General IT Landscape Main (ongoing) projects –Active Directory / LDAP –Storage: SAN, NAS, BackUp, Disaster Recovery –Information Life Cycle Management On-line/near-line/off-line ; Archiving E-mail, web, documents, SAP, etc. –Server Consolidation File servers Web servers Application servers

5 08/06/2004Portal Review5 Functional presentation Needs –Cross cutting –Multilinguism –Easy access to the huge amount of data UNESCO publishes online

6 08/06/2004Portal Review6 Functional presentation Actions for the portal –Standardization –Definition of a functional architecture –Pooling of resources Search engine Mailing-lists –Definition of a physical architecture

7 08/06/2004Portal Review7 Functional architecture : past activities Work has been going on for more than 2 years –Installation of Simplify, Albert, etc. –Design of a functional architecture –Work on the data (XML repository) –Work on the presentation The first bricks can now be used

8 08/06/2004Portal Review8 Functionnal Architecture Consultation Internet Other Sites Content Management Static Presentation Profiling News Mailing Multi media Categorization Indexation Metadata repository XML Members directory LDAP Thesaurus Search engine Connectors Discussion Forum

9 08/06/2004Portal Review9 Functional architecture : main directions Quality of data –Editors rarely qualify the content they type –Automatic processing requires qualifiers (meta data) Presentation of data –Definition of themes –Multi channel presentation (web, mailing lists, etc.) –Profiling

10 08/06/2004Portal Review10 Portal data Eventually each document published on the Internet will be referenced in the XML repository –Described by an identity card –Qualified by keywords Work progress –The identity card is defined –The XML Repository is set up –The Repository is feed by Simplify –A connector architecture has been designed to feed the repository

11 08/06/2004Portal Review11 Portal data : data quality Importance of good qualification –Without it data cannot be processed Work progress –Automatic qualification –Qualification statistics –Simplify contributors help –Identity card editing

12 08/06/2004Portal Review12 Portal presentation Present data to better attain target publics No duplication : only links and summaries Multiple channels : HTML, mail, RSS, etc.

13 08/06/2004Portal Review13 Portal presentation : themes How does it work ? –Definition of themes : set of keywords to describe a topic Exemple : theme AIDS in Africa is described by AIDS and Africa –The Repository extracts matching data –An editor selects the documents he wants to present –A portal page is automatically created in Simplify –Eventually, other channels will be added : mailing, RSS, etc.

14 08/06/2004Portal Review14 Portal presentation : demonstration Online demonstation

15 08/06/2004Portal Review15 Moteur de recherche 1/2 Avril 2004 DIT avait installé sur un nouveau serveur les bases de la maquette Albert: le moteur de recherche, lindexation de flux de données hétérogènes: CMS, WEB, UNESDOC.. PB techniques de BD, Thésaurus trop « riche », contenus interne et externe mélangés -> résultats confus. Recadrage du projet avec les secteurs (approche concensuelle) http://portal.unesco.org/search/wg Groupes de travail: Enquête, Pages promo.,Test qualité, indexation contrôlé, stratégie, affichage contextuel des résultats. ->Lancement reporté dAlbert courrant septembre 2004

16 08/06/2004Portal Review16 Moteur Albert 2/2 Réutilisation de lAPI simplify->RefXML pour Albert. Maîtrise des données injectées: –Meta data Simplify (type, keywords, auteur,….) –Indexation tous les 15mn des Kos simplify(CMS). Indexation des sites WEB en fonction du contenu –Elaboration de descripteur de site DIT-BFC Définition des metadonnées à injecter. Réécriture de la partie affichage des résultats. Assistance technique.

17 08/06/2004Portal Review17 Mass-Mailling –SYMPA v3- 71 listes 10 > 1000 abonnés. 15 > 100 abonnés 22 > 10 abonnés. 24 <10 abonnés. 800 à 4000 emails par semaine envoyés en mai. Facilité dutilisation Moins bien adapté pour les groupes de discussion que UBB. Bonne tenu en charge. Version 4 à tester: Soap interface CAS SingOn system

18 08/06/2004Portal Review18 Architecture Simplify actuelle FireWall Simplify1 BD Simplify3Simplify2Simplify4 BD Frontal Public Privé Frontal Public Privé s_water s_clt s_shs ….. s_ci s_intra s_wwap s_edus_unesco Recommendations Tomoye: -4 instances / serveurs <50 000 Kos -Déploiement des applications sur plusieurs serveurs

19 08/06/2004Portal Review19 Gateway Unique Webmaster Architecture Simplify FireWall Simplify1 BD Simplify3Simplify2Simplify4 BD Frontal Public Privé Frontal Public Privé Frontal HA Haute disponibilité (HA) Sécurité Facilité daccès Base de données MasterBase de données Slave HA Servers WWW Architecture WEB Accélérateur FireWall HA

20 08/06/2004Portal Review20 Liste des serveurs Portal0 Actuel Front + quelques instances Simplify Srvportal01 – Albert Installé Srvportal02 – Mysql master Srvportal03 – Mysql esclave Srvportal04 – Serveur dapplication – XmlRef Srvportal05 – Serveur Simplify Srvportal06 – Seveur Simplify+application Web Srvportal07 – Serveur Simplify Clustering Front –Srvfront01 – Serveur Frontal01 –Srvfront02 – Serveur Frontal02 2 autres serveurs pour la HauteDispo

21 08/06/2004Portal Review21 Static site Problem –Simplify servers were slow because overloaded –Response time for visitors too long –Contribution rendered difficult Solution –Simplify sites are quasi-static –Create a static (HTML) site from Simplify –Optimal response time for visitors Simplify sites are being transformed into static

22 08/06/2004Portal Review22 Static site Limitations –Reactivity –Template modification Solution : chef dorchestre/conductor application –Schedules static transformation –Immediate generation of topics –Generation of topics after a template has changed –Deletion of topics

23 08/06/2004Portal Review23 Static site : nice URL URL problem –Simplify URLs are complex and obfuscated –http://portal.unesco.org/en/ev.php- URL_ID=15006&URL_DO=DO_TOPIC&URL_SECT ION=201.htmlhttp://portal.unesco.org/en/ev.php- URL_ID=15006&URL_DO=DO_TOPIC&URL_SECT ION=201.html nice URL feature –www.unesco.org/culture maps to a Simplify URL

24 08/06/2004Portal Review24 Static site : nice URL How does it work ? –Create a new topic of alias/redirection type –For each language, map a nice URL to a static Simplify URL

25 08/06/2004Portal Review25 Administration des applications portails Gateway Unique Webmaster Permettre laccès centralisé aux serveurs: Un seul point dentrée une seule authentification Sécurise laccès via HTTPS, SFTP, SSH.

26 08/06/2004Portal Review26 Mutualisation des développements Les développements PHP, PERL, JAVA, XML… et les documentations sont hébergés sur un serveur (repository) Concurrent Version Systèm: –Le + utilisé dans lOpenSource, le + connu. –Programmation collaborative via internet. –La programmation des modules du portail peuvent être faite à partir de partout dans le monde et peuvent être partagé. –Par son ouverture, permet un meilleur contrôle des développements. –Mise à disposition des sources et packages.

27 08/06/2004Portal Review27 Lexpériences CMS Multilingue Etude sur des CMS multilingue « open source » en java, php, python. Loption retenu a été OpenCMS. –BackOffice évolué, bonne réputation. –Frameworks « lourd » à mettre en œuvre. –Notion dobject (KO) manquante -> Développement spécifique -> trop cher. Nouvelle proposition avec « Infoglue ». Arrêt de létude à cause du manque de visibilité et de financement

28 08/06/2004Portal Review28 End Thank you for your attention