The document discusses the objectives and overall description of an ECB-NET document management and workflow project. The major goals are to create a centralized document repository with document management and workflow tracking capabilities. It provides details on the portal, document types, uploading and searching documents, versioning, and technical standards and architecture used.

1. ECB-NET Document Management and Workflow Ole Norager Diego Bragato

2. Objectives of the Project Major Goals of the project Document management Procedure Tracking Workflow Schedules to fulfill End of actual IDA for 2004

3. Overall Description A web portal with single sign on A centrally based dossier / document repository A workflow system FURTHER INFORMATION ... http:// ecb . jrc . it / ecbnet / http:// ecbnet . jrc . it :8080

4. The portal

5. The Document management

6. Functional organisation I A context Based Menu A set of available Actions

7. The actions Create Dossier View Dossier Upload Document Create Form Search Version View Access Control Lists Set Access Control Lists

8. The Dossiers

9. The dossier Types Configurable Dossier Types

10. The documents

11. The document Types Configurable Document Types

12. Uploading Documents

13. Validation Form Fields are validated with a configurable set of validation rules

14. Data Privacy Access Control Lists

15. Searching features are based on Webdav DASL Searching features are available to other software components Searching

16. Versioning Versioning features are based on Webdav DeltaV Versioning features are available to other software components

17. User Management

18. Document ation avail a ble New Updates of the documentation Documentation will be available together with the runtime test environment

19. Question & Answers

20. The Technology Strategy Standard Based Architecture Standards change on a 10 year scale Open Source components Free software We can interchange free software with proprietary implementations for better performance Full J2EE implementation All software is implemented in java, J2EE compliant and platform independent

21. Chosen Standards I Application server J2EE Users management LDAP Document Management WEBDAV Searching DASL www.webdav.org/dasl/ Versioning DeltaV www.webdav.org/deltav/

22. Chosen Standards II Workflow JBPM JPDL Enhydra SHARK XPDL – WFMC FURTHER INFORMATION ... dbr @ terma .com

23. The solution A Web based system A Web portal A Web application A document server A user server

24. The W eb DAV Web Distributed Authoring and Versioning Protocol Multiple clients Differentiated access according to usage Single sign on FURTHER INFORMATION ... www. webdav . org

25. Easiest access to the data layer through WebDAV Windows WebDAV folders

26. Easy MS windows configuration Windows Webdav folders Configuration

27. Web DAV: single sign on

28. The Webdav Browser

29. Webdav The slide client

30. The Slide Webdav Servlet

31. Webdav access V Office 2000 is WEBDAV compliant

32. LDAP access Java Clients LDAP browser Mail clients Outlook Browsers Mozilla Text based clients Ldif files

33. LDAP servers Openldap Windows 2000 server Active directory Oracle LDAP Commercial J 2EE LDAP services Sun One LDAP

34. J2EE application server Jboss Free (Less GPL license) 37% market share best performances BEA The most known commercial application server Oracle IAS Well known within the commission Weblogic IBM’s application server

35. The Workflow A workflow Engine An alarm engine A rule engine A workflow process definition file Workflow procedures can be updated at no cost

36. Question & Answers

37. The software implementation tasks The roll out of the software The implementation phase

38. Tasks for the end of the development phase Roll out of the test environment (phase I) Sample Configuration of the system Dossier Types Document Types Form Types Load up of the system Sample Legacy data load up Test Users accessing the system System Administration Support

39. Tasks for the Implementation phase I Full Roll out of the test environment (phase II) Full Configuration of the system Load up of the system Large Scale Test for Legacy data load up Users accessing the system System Administration Support Tuning of the test environment

40. Tasks for the Implementation phase II Definition of the target HW Production Environment Roll out of the Production Environment Load up of the system Full Legacy data load up Users accessing the system Tuning of the system HW / SW tuning

41. System Tuning Hardware tuning Optical / Network storages Server Racks Java tuning Standard tuning available in other systems such as IDA ZOPE Software Architecture tuning Added value of the standard based approach

42. How we are working System integration software Maximize output Local support Transparency FURTHER INFORMATION ... Diego Bragato dbr @ terma . com +39 0332 773983 Richard Morris rim @ terma . com +39 0332 773982

43. Project P lan The IDA phases FURTHER INFORMATION ... dbr @ terma . com Dec 2004 Preparatory feasibility Development Implementation Jan 2001 Jan 2003 May 2004

44. Project status Development phase Final A rchitecture is there We have a good set of components that are nicely working together Testing and bug fixing Workflow engine

45. Project Needs Roll out of the software Test environment Customer Validation Contract Closure

46. Question & Answers