Top Banner
OpenProdoc ECM Open Source
13

OpenProdoc Overview

Jun 12, 2015

Download

Technology

jhierrot

This document is an overview of OpenProdoc, describing functionality and architecture.

OpenProdoc is an ECM Document Management system with the characteristics:

- A complete portable version that can be used without installation in Linux, Windows, Mac.
- Open Source
- Multi-platform (Java)
- Multi-database (Derby, MySQL, Oracle, DB2, PostgreSQL, SQLServer, SQLLite, HSQLDB)
- Low requirements for the engine (can work without a J2EE server)
- Several ways for Authentication (Ldap, DDBB, OS, Own system)
- Different ways to store documents (FileSystem?, BLOB,ftp, Reference)
- Object oriented definitions for documents and folders (including inheritance)
- Fine granularity of administration and permissions, allowing delegation of different functions.
- Multi-language (English, Spanish and portuguese)
- Thin (Web) and Thick (Swing) Clients

Download: http://code.google.com/p/openprodoc/
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: OpenProdoc Overview

OpenProdoc

ECM Open Source

Page 2: OpenProdoc Overview

Index• Overview

• Architecture

• Functionality

• Security

• Administration

• Requirements

• Roadmap

Page 3: OpenProdoc Overview

Overview• OpenProdoc is a general purpose document management system.

• It has the standard functionality of a ECM system, including the manage of different document and folder types, users, repositories, ACL, etc.

• It is developed in Java with special attention to portability and therefore can be executed in many environments.

• It has a thick client to manage the documents, that also includes all the administration functions, and a Web client developed as a J2EE application.

• It can be integrated easily or, due the small footprint of the core (<1M) , be embedded in other application that needs ECM functionality.

• It is designed so that can be easily extended with a model of plugins.

• In this moments it's in its third beta version.

Page 4: OpenProdoc Overview

Architecture• OpenProdoc is structured in the components:• Core: Contains all the logic and coordination of the system and contains the elements:• MD Connector . The MetaData Connector manages all the metadata of the documents, definitions and structure of security. The current version only supports connector for JDBC-SQL databases, but it's prepared for other kind of databases (Non-SQL, XML,..). • Storage Connector. The Storage Connector manages the storing and retrieval of documents. A installation can contains several repositories for different kind of documents depending on factors as speed of retrieval, size, etc. The current version includes Filesystem, Databases-Blob and ftp.• Authenticator Connector: This connector allows to validate the users during login. Different groups of users can use different systems to authenticate (different Ldap, etc). The current version supports authentication against Ldap, DDBB, OpenProdoc and S.O.

Page 5: OpenProdoc Overview

Architecture

CORE

MD Connector

DD.BB.Metadata

Storage Connector

DD.BB.Documents

Storage Connector

Filesystem

Authenticat.Connector Ldap

Authenticat.Connector

DD.BB.Authentication

Page 6: OpenProdoc Overview

BB.DD.Metadato

Architecture

Java Swing

DD.BB.Metadata

Filesystem

Core

OPD Web Application

Core

Custom J2EE Application

Core

Filesystem

Core

Connector MD OPD

Browser

Browser

Browser

Page 7: OpenProdoc Overview

Functionality• OPD is prepared to define archive structures, document types and folder types to adapt to necessities of different companies and institutions.• The inclusion of inheritance for documents and folders allows an evolution on the model and a more accurate modelling. • Different functions, as searching, can be executed for one element type or extended to all the subclasses, giving more power to the user for retrieving documents or folders.• Also, it's possible to extend the search to all the versions of document, not only the current one.• The use of a paper bin avoids to lost documents by an accidental delete.• Both clients (Web and Swing) share the same interface and menu, providing use either interchangeably.• In the same installation, every user/group can have his own language and graphics style, allowing to be used by different areas in big institutions or as SAS/cloud.• It's possible to import/export the content and metadata of a complete folder tree from/to OPD.

Page 8: OpenProdoc Overview

Security• OPD uses the usual ACL (Access Control Lists) system to manage the access to the elements.• The ACL apply not only to the documents and folders but to other elements as groups.

• The authentication can executed in severals ways. It is possible to define several sources of authentication and apply every one to different users. (I.E. the internal users can be authenticated against the corporate ldap and guest users against OPD or other sources)

• The documents can be encrypted on line before be stored in the repositories, so that users with access to them, or to the backups, can not view the documents.

• It is possible to define roles, limiting the functions allowed to a the users.

• The groups of users can contain users or groups avoiding to necessity to assign the same user to different groups and simplifying the maintenance.

Page 9: OpenProdoc Overview

Administration• The installation using a GUI application is easy and fast.• The CORE API contains all the administration functionality. In the current version the interface for administration is implemented in the Swing client.

• Due its small footprint and the variety of systems supported, can be installed in a large number of systems.

• OpenProdoc is scalable (both scale up and scale out) and have High Availability.

•OPD includes delegate administration; and administration can create roles and grant permissions so different users can manage administration of different functions or even an specific element:

– Documents and folders definitions.

– Security (Users, groups, acl, roles)

– System (Repositories, Authenticators, mimetypes)

– User Interface

Page 10: OpenProdoc Overview

Requirements• For using OpenProdoc it is necessary to have a JVM 1.5 or higher,a DBMS and a Filesystem.• In the database will be stored all the configuration, definitions and metadata. • The documents can be stored in the Filesystem or in a DBMS, depending on requirements of the project • The access to the metadata is through a JDBC driver.• The Swing cliente can be installed in any computer • The Web client must be installed in an application server J2EE.• OPD has been developed with standardization and portability in mind, and has been tested in different environs, so it should be work in most systems.• The next page include the software tested (of course not all the combination of DBMS, APP server, OS, JVM and browser have been tested.

Page 11: OpenProdoc Overview

Requirements•Java JVM 1.5 or higher

•Browsers:

• Firefox 6, 7

• Chrome 13, 14

• Internet Explorer 8

• Opera 10.51

• Safari 4.0.5

• Databases:

• Derby 10.6

• MySQL 5.5

• PostgreSQL 9.1

• Oracle 10g

• DB2 9.1

• MS SQL Server 9.0

• Application Servers:

• Glassfish 3.1

• Tomcat 6

• WebLogic Server 11g R1

Page 12: OpenProdoc Overview

Roadmap• OPD 0.7 Beta. (Spring 2012)

• Multivalued attributes (to add multiple entries to the same attribute)

• Reference repositories (to add documents whose content is in remote or read-only repositories)

• Enhanced Administration.

•OPD .8 RC1 (autumn 2012)• Processes (not BPM but automatic processes and triggers) • Projects (sets of definitions/elements of export/move between installations)• Thesaurus and list of controlled values for attributes• Definition of custom forms for editing documents and folders.

Page 13: OpenProdoc Overview

More Information

• http://code.google.com/p/openprodoc/

• Joaquin Hierro• [email protected]