Surveying Collaborative and Content Management Platforms ... Collaborative and Content Management Platforms for Enterprise ... Surveying Collaborative and Content Management Platforms for ... Spring

  • Published on
    25-Apr-2018

  • View
    214

  • Download
    1

Transcript

  • HAL Id: hal-00812686https://hal.archives-ouvertes.fr/hal-00812686

    Submitted on 12 Apr 2013

    HAL is a multi-disciplinary open accessarchive for the deposit and dissemination of sci-entific research documents, whether they are pub-lished or not. The documents may come fromteaching and research institutions in France orabroad, or from public or private research centers.

    Larchive ouverte pluridisciplinaire HAL, estdestine au dpt et la diffusion de documentsscientifiques de niveau recherche, publis ou non,manant des tablissements denseignement et derecherche franais ou trangers, des laboratoirespublics ou privs.

    Surveying Collaborative and Content ManagementPlatforms for Enterprise

    Salsabil Dhouib, Riadh Ben Halima

    To cite this version:Salsabil Dhouib, Riadh Ben Halima. Surveying Collaborative and Content Management Platforms forEnterprise. IEEE International Conference on Enabling Technologies: Infrastructures for Collabora-tive Enterprises ( WETICE ), Jun 2013, Hammamet, Tunisia. 8p., 2013.

    https://hal.archives-ouvertes.fr/hal-00812686https://hal.archives-ouvertes.fr

  • 1

    Surveying Collaborative and Content Management Platforms for Enterprise

    Salsabil DHOUIB1 Riadh BEN HALIMA1,2,3 1University of Sfax, ReDCAD Laboratory, B.P. 1173, Sfax-Tunisia

    2CNRS, LAAS, 7 avenue du colonel Roche, F-31400 Toulouse, France 3Univ de Toulouse, LAAS, F-31400 Toulouse, France dhouib.salsabil@gmail.com, riadh.benhalima@enis.rnu.tn

    Abstract The continuous increasing of the information

    quantity in enterprises encourages the adoption of an Enterprise Content Management (ECM) that evolves as an integrated approach to information management. By observing the trend toward adoption of Web based collaboration tools in the enterprise, we focus, in this paper, on ECM platforms that involve collaboration and content management aspects in an integrated solution. Thus, to help enterprises that want to move toward a collaborative ECM platform, we provide a detailed analysis of the following ECM platforms: Alfresco, Nuxeo and Microsoft Office SharePoint Server (MOSS). Then, we proceed to the evaluation of Alfresco and MOSS as they are the most used. This allows us to choose the platform that fit most the context of industrial engineering design offices. Therefore, we explored their customization possibilities to meet those offices organizational requirements. We conclude that MOSS is more appropriate to that context. We carry out experiments on a sandboxed solution on-premises (Microsoft SharePoint 2010) and on Cloud (SharePoint Online) to demonstrate that, on Cloud, we can have a better performance associated to a cheaper cost.

    Key words ECM, MOSS, Alfresco, Nuxeo, Cloud Computing, SharePoint Online, Comparison.

    I. INTRODUCTION Many enterprises are facing difficulties in information

    management due to the multiplication of file servers, mail servers, documentary data bases, Web sites and collaborative tools without neither consistency, nor traceability or clear business objectives. The management of such a huge amount of content is a challenge. Enterprises have started to perceive the value of the content in their possession and the importance of handling it efficiently. This is exactly the aim of an Enterprise Content Management (ECM) platform [1].

    By following the trend towards cooperation, the gradual navigation of Web 2.0 technologies to the enterprise world and the ever increasing need for collaborative tools and social sharing applied for enterprise content [2][5], we think that the deployment of a collaborative ECM platform is a good choice for enterprises. But, it is difficult to choose the most suitable ECM for an enterprise out of many available solutions. This papers main aim is to show the strength of each ECM platform, to explore its customization possibilities and to provide a guide in order to choose the suitable one for a specific need.

    As a first indicator, we looked at the Gartner magic quadrant [7] and the Forrester wave [6]. We identified the ECM platforms that fit most the business content approach.

    Alfresco [8], Nuxeo [9] and MOSS [10] belong to them. Then, we elaborated a comparative study that shows their technical aspects and their business content approach components.

    As business content oriented ECM platforms and industrial design engineering offices present a natural synergy, we took a closer look at Alfresco and MOSS. Thus, we explored their customization possibilities in order to meet the organizational requirements of industrial design engineering offices. We concluded that MOSS fits better this context. We then built a sandboxed solution for the project management area that includes a performance assessment. We used Microsoft SharePoint 2010 for the on-premises evaluation and SharePoint Online - the Cloud-based version of Microsoft SharePoint 2010 - for the Cloud evaluation. The obtained result confirms that Cloud gives a cheaper infrastructure and is more competitive.

    This paper is structured as follows. In Section 2, we give an overview of the three ECM: Alfresco, Nuxeo and MOSS. Section 3 explores the customization possibilities of Alfresco and MOSS platforms. In Section 4, we evaluate SharePoint Online. We conclude with a summary and suggestions for further research.

    II. ECM PLATFORMS CLASSIFICATION ECM is an integrated approach to manage all of enterprise

    content which can be any datum, document, business application content or multimedia asset related to an organizational business process. According to AIIM [3], an ECM is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists [4].

    Since the only description available of Alfresco, Nuxeo and MOSS is in the form of natural language marketing whitepapers, we have to study deeply those descriptions in order to identify a set of consistent classification criteria. Given the collaborative aspect of such platforms, we believe that three main criteria make the difference and guide the choice decision: i), the architecture, ii) the evolution capacities, and iii) the performances. The conviviality and the user interface ergonomics are also determining criteria. In addition to technical aspects, fundamental and business content components are also taken in consideration because they are essential to manage effectively the content. A synthesis of the studied technical aspects is presented in TABLE I.

  • 2

    TABLE I. TECHNICAL ASPECTS OF ALFRESCO, NUXEO AND MOSS

    According to TABLE I, Alfresco and Nuxeo are open

    source platforms. However, MOSS is a closed source one. MOSS is a Microsoft product which means that its very sustainable but can only be run on a Windows environment,

    unlike Alfresco and Nuxeo which can be run on other operating systems. For Alfresco and Nuxeo, we use JSR 168 API to develop portlets, except for MOSS for which we use Web Part. Unlike Nuxeo and MOSS, Alfresco provides CIFS

    Technical Aspects ECM platforms

    Alfresco 3.3> [8][11] Nuxeo 5.5> [9] MOSS 2007 and Microsoft SharePoint 2010 [10][11]

    Source code - Enterprise version is closed source however Community version is open source

    - Its a real open source model because code is available for the Enterprise version

    - Closed source

    Price - Subscription fees for the Enterprise version - Freeware - License fees for Microsoft package Sustainability - Sustainable - Sustainable - Very sustainable

    Supported operating systems -Windows, Linux, MacOS, Solaris, etc.

    -Windows Server 2003, Mac OS X, Unix, Linux, etc. -Every system on which we can install a Sun 1.5 or Sun 1.6 JVM

    - MOSS 2007 : Windows Server 2003 (x86 or x64) or Windows Server 2008 (x86 or x64) - Microsoft SharePoint 2010: Windows Server 2008 x64, Windows 7 x64 and Vista x64

    Supported DBMS - MySQL, MS SQL, Oracle, PostGre SQL, etc. - PostGre SQL et MySQL - MOSS 2007: MS SQL Express or MS SQL 2005 - Microsoft SharePoint 2010: MS SQL Express or 2005 x64 or 2008 x64

    Supported application servers

    - Tomcat, Jboss, Oracle WebLogic, Oracle WebSphere, etc. - Jboss, Tomcat

    - The application server role is installed through the server manager. Thus, the PC is transformed into an application server

    API used for the portal

    - Is based on portlets development API Java Specification Requests (JSR) 168

    - Is based on portlets development API JSR 168 - Web Part

    Other APIs

    - JSR 170, Java, JavaScript, Content Management Interoperability Services (CMIS), Simple Object Access Protocol (SOAP), REpresentational State Transfer (REST)

    - JSR 170, Java, CMIS, SOAP, REST - MOSS 2007: CMIS, SOAP and Server OM - Microsoft SharePoint 2010: CMIS, SOAP, Server OM, Client OM, LINQ and REST

    Protocols - FTP, CIFS, WebDAV, NFS, Windows SharePoint Services (WSS) protocol, IMAP - WebDAV, WSS protocol - WebDAV

    Used technologies and technical standards respect

    - J2EE platform, Spring Framework - Uses the best open source technologies - Alfresco Explorer interface is developed using JSF - Alfresco Share interface is developed using Spring Surf Framework

    - J2EE platform - Is developed based on existing open source Frameworks and libraries - Uses JSF for the presentation layer - Uses EJB3

    - .NET platform, ASP.NET

    Software architecture and technical platform

    - Has a distributed, modular and service oriented architecture - Uses Aspect Oriented Programming (AOP)

    - Has a modular, components based and service oriented architecture - Uses OSGi and a powerful runtime extension point system - Is based on Nuxeo EP Framework

    - Has a service oriented architecture - Windows SharePoint Services 3.0 (WSS v3) is MOSS 2007s application Framework - Microsoft SharePoint Foundation 2010 is Microsoft SharePoint 2010s application Framework

    Usability

    Has two interfaces : - The old one called Alfresco Explorer is slow, unintuitive, and needs a large number of clicks for the lesser action - The new one called Alfresco Share is more clear and adds many functionalities

    Its the easiest platform to pick up : - Clear and intuitive user interface - A tabbed and very organized interface - An interface which has interesting functionalities like the right click - Rich in AJAX functionalities

    - An intuitive and easy to use interface - Microsoft SharePoint 2010 uses a ribbon that is similar to the Microsoft Office one

    Availability and load balancing

    - Strong availability - Alfresco Shares availability is stronger than Alfresco Explorer - Alfresco benefits from a replication mechanism - Supports perfectly load balancing

    - Strong availability - Its possible to establish an application cluster, and multiply Nuxeo EP instances that points to a data base

    - Strong availability - Allows high loads: There is no topology by itself, thus, its quite possible to compose any SharePoint server farm

    Deployment on-premises

    - Quick deployment: Application comes under a WAR file. Alfresco comes in Tomcat application server and MySQL data base - Configuration after deployment is hard because we should manually edit a configuration file

    - Quick deployment. Nuxeo comes packaged, uses a preconfigured turnkey Tomcat, and is centralized in a unique folder - Once application is launched, we customize settings directly through Web interface

    - Quick deployment - Once the application is launched, we connect, and we customize settings directly through the central administration Web interface

    Cloud support - Yes (Alfresco) - Yes (Nuxeo Cloud ECM Edition) - Yes (SharePoint Online)

  • 3

    option to access repository which is very useful in some enterprise case. Nuxeo and MOSS provide a clear and intuitive user interface. However, Alfresco offers two interfaces called Alfresco Share, addressed to final users, and Alfresco Explorer, addressed to administrators. Alfresco is based on the J2EE platform and uses the best open source technologies and AOP. Nuxeo is also based on the J2EE platform. However,

    MOSS is based on the .NET platform and uses ASP.NET. We notice that the configuration after deployment is hard for Alfresco, except for Nuxeo and MOSS, where we can customize settings directly through the Web user interface. In addition to technical aspects, fundamental and business content components are also taken into consideration. They are highlighted in TABLE II.

    TABLE II. BUSINESS AND FUNDAMENTAL CONTENT COMPONENTS OF ALFRESCO, NUXEO AND MOSS

    As TABLE II shows, Alfresco is based on an extensible,

    flexible and evolutionary content model. MOSS is based on a structure called list which is the equivalent of an Excel table but provided through a Web interface. It contains columns and

    items. Its a very powerful tool. Alfresco offers a powerful rules engine. Nuxeo offers also a rules engine but it doesnt emerge in the Web interface. However, MOSS offers two modules called Custom Action and Event Receiver.

    Business and fundamental content components

    ECM platforms

    Alfresco 3.3> [8][11] Nuxeo 5.5> [9] MOSS 2007 and Microsoft SharePoint 2010 [10][11]

    Indexing and search - Lucene - For Alfrescos 4.0 version, Lucene has been replaced by the search engine Solr

    - Embedded search engine based on Lucene

    - Has its own indexing and search engine which is completely independent from SQL Server indexing service

    Metadata management

    - Alfresco is based on a content model (types, properties, constraints, associations, and aspects) - Aspects can be attached to documents on the fly - Requires XML development

    - Through facets - Requires development

    - MOSS is based on a structure called list. Its a highly configurable component that generally represents a business object. Columns can easily be added and/or associated to a content type - It is just a configuration of the standard Web interface but a content type or a list structure can also be developed using XML

    Email management

    - Incoming and outgoing email configuration is manually done. Emails can then be sent when inviting a user to a space or when a business rule - including send email action - is executed A repository node can be configured to receive emails - Offers emails drag and drop functionality

    - Incoming and outgoing email configuration is manually done - Offers a folder type which can be linked to an inbox

    - Incoming and outgoing email configuration is easy and is done through the central administration Web interface. SharePoint alerts can then be used, a document library can be configured to store emails received from a particular email address - Offers emails drag and drop functionality

    Business rules management

    - Integrates a powerful actions orchestration mechanism - Has complex business rules that a user can define without programming (when a document enter a workspace, do some steps, like versioning). We have then smart workspaces - Business rules benefit from AOP technology which allows changing the server behavior without changing code. Nevertheless, business rules can be developed using Alfresco JavaScript API

    - Offers a rules engine that doesnt emerge on the interface, thus, its only a strong tool provided to developers

    - Has an Event Receiver module which offers the possibility to easily add business rules using a simple development. It includes the business action that will be triggered when an event occurs. An event receiver can be attached to a content type which is a powerful feature - Has a Custom Action module which offers the possibility to insert buttons and links in MOSS standard menus. A custom action can be created without using any line of code. However, in some cases, it is necessary to write code

    Business Intelligence (BI) - Integrates with Jasper Report

    - Has a reporting module by integrating BIRT solution

    - Excel - PerformancePoint Server integration in MOSS Enterprise

    Security and access rights management

    - Supports Single Sign On (SSO) - Supports any LDAP server - Manages roles. A role is a set of permissions. A role can be assigned to users and/or groups for a document or a workspace through the invitation mechanism - Creating a new role requires development

    - Supports SSO - Supports Active Directory and Open LDAP - Doesnt include a permissions set neither as a role like Alfresco nor as an authorization level like MOSS - Provides four access rights that can be applied on workspaces and three access rights that can be applied on the metadata of a document

    - Supports SSO - Supports only Active Directory - Manages authorization levels. An authorization level is a set of authorizations - Creating a new authorization level can be simply done using the standard Web interface - Security can be applied on site collections, sites, lists, libraries, list items, and libraries items - Manages audiences. An audience allows targeting content items, Web Part components and navigation links

    Business Process Management (BPM) - Uses the jBPM Workflow engine - Uses the jBPM Workflow engine

    - Workflow functionality is built on Windows Workflow Foundation

    Collaboration - Medium - Medium - Strong Portal - Medium - Strong - Strong

    http://www.jboss.org/jbossjbpm/http://www.jboss.org/jbossjbpm/

  • 4

    III. ECM PLATFORMS EVALUATION Feature by feature comparison of ECM platforms does not

    give enough information. We should then develop a practical model. We decided to study the case of industrial engineering design offices. Thus, we installed, set and experimented Alfresco and MOSS. In native mode, they provide the basis features for classic administration and provision team site with tools for collaboration allowing us to focus only on the business part.

    We did customizations to meet industrial engineering offices business requirements which consist of being able to reach all the information related to each project, ensuring collaboration between all the projects team members and managing business processes in order to obtain efficiency, reliability and traceability of all operations. Therefore, we explored three areas as follows: Project management, Business Process Management and collaboration.

    A. Project management provided technologies MOSS is structured into sites. A site constitutes the

    collaboration environment that can be used in any context, professional as social. We used it in the context of project management. Each site contains lists. A list is the best feature of MOSS. There is no alternative to the list in open source platforms. Every list offers a lot of features. We can connect lists by using a lookup field, which provides a perfect data coherence. We can also create models of a list or a site.

    In Alfresco Share, we find whatever we need in order to perform project management. Alfresco Share sites have their dedicated collaborative tools. A site can be considered as a project workspace (Fig. 1). Like MOSS, Alfresco makes possible to define a workspace template.

    Fig. 1. Structure used for project management in Alfresco and MOSS

    B. Business Process Management The out-of-the-box Workflows are simple and generic. An

    industrial engineering office needs to establish complex business Workflows. We implemented a documents approval Workflow using the structure illustrated in Fig. 2.

    Fig. 2. Structure used to implement the documents approval Workflow

    We used jBPM to implement the documents approval Workflow for Alfresco: We installed jPDL Process Designer plugin on Eclipse. We establish business processes with the plugin Graphical Designer environment. We defined the Workflow graph using jBPM Process Definition Language (jPDL), the native Workflow language of jBPM. Then, we called jPDL primitives. We created new interfaces. We found that this is very complicated. In fact, although Alfresco is an open source platform, its complicated in terms of configuration: an XML file to extend Alfrescos content model, an XML file to describe the Workflow, an XML file responsible for graphical interface displaying, etc.

    We used custom actions and event receivers to implement the documents approval Workflow for MOSS. So, we created a SharePoint list on which we implemented a custom action per project user role. When a custom action is selected, a business code is executed and changes are applied on the selected SharePoint list item and its corresponding in the SharePoint document library. Its easier than Alfresco.

    C. Access rights management and collaborative tools As Alfresco doesnt allow us to define custom roles via its

    standard Web interface, we created a Web Script application which enables access rights management by acting on Alfresco repository to assign the required access rights to the appropriate nodes of the collaborative site.

    When using MOSS, we can assign authorizations to each team site item via the standard Web interface. We can simply use default authorization levels as well as defining new ones via a simple configuration. Moreover, MOSS contains a very strong tool called audience. In fact, all navigation links can be targeted for specific audiences via a simple configuration. Thus, we created custom authorization levels. Then, we assigned authorizations to the team site items using two methods: configuration and programming. Also, we developed code to assign access rights to custom actions.

    Alfresco Share doesnt offer advanced collaborative features and presents many limits. Thus, we decided to couple it with Liferay portal [15]. Liferay will use Alfresco as its documents repository. Then, we tried two solutions. In the first one, we integrated Alfresco Document Library with Liferay. This solution offers a real communication between Alfresco and Liferay. But, its impossible to search added documents neither via Alfresco nor Liferay and there is a lack of many features. Therefore, we decided to switch to the second solution which consists in the integration of Alfresco DocLib portlet in Liferay. Using this solution, we can access to all Alfresco Share sites, benefit from the great power of Document Library and avoid coding. However, its impossible to add sites through Liferay. The only way is to access to Alfresco in order to create a new site. In conclusion, its clear that there is a general problem of Alfresco and Liferay versions compatibility. In addition, we note that there is a communication but not an integration. Indeed, to integrate Alfresco with Liferay, we must use Alfrescos SOAP API and integrate Web services in portlets applications deployable in Liferay. However, MOSS offers appetizing collaborative

  • 5

    features. Thus, we dont need to perform modifications at this level.

    D. 9BSynthesis In one hand, Alfresco extensibility is quite difficult in terms

    of programming. It presents a lack of flexibility at deployment level and requires apprenticeship and a mastering of its implementation. On the other hand, Alfresco presents a powerful rules engine, offers the possibility to add aspects on the fly, and doesnt require a Client Access License (CAL). It is privileged if the project simply uses the offered standard function. MOSS is simple in its forms and Workflows management. It is only a 20% of code and 80% of declarative logic (no code) and settings associated to the platform. We conclude that Alfresco remains an interesting solution. However, MOSS seems to be the best fit with our issues, but it is a closed source solution and requires a lot of licenses.

    IV. 3BSHAREPOINT ONLINE ASSESSMENT The deployment cost of a small Microsoft SharePoint 2010

    farm on-premises is high [13]. Nevertheless, Microsoft hosts a version of Microsoft SharePoint 2010 product in its own Data Centers. According to NIST [16], Cloud Computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This Cloud model is composed of five essential characteristics, three service models, and four deployment models [17].

    A. 10BMicrosoft Office 365 Microsoft Office 365 [14] is the Microsoft Cloud SaaS

    offer. It comes after and replaces Business Productivity Online Suite (BPOS). Its a service in the form of User Subscription License (USL). It addresses all enterprises regardless of size for collaboration and communication services hosted on Cloud. It includes Office Professional Plus, Exchange Online, SharePoint Online and Lync Online.

    Two families of offers are available, Office 365 for Professionals and Small Businesses P (contains one package called P1) and Office 365 for Medium and Large Businesses E (contains four packages called E1, E2, E3 and E4). Those two families of offers include many services which are completely appropriate for the enterprise structure, its number of employees and its equipment. There are two different versions of Office 365: The standard one which is held in reserve for small and medium-sized enterprises and is based on a multi-tenant architecture; and the dedicated version, which is held in reserve for large-sized enterprises and is based on a multi-instance architecture.

    B. 11BSharePoint Online customization We can upload custom code to SharePoint Online with the

    use of the Client Object Model and the new sandboxed solution feature inherited from Microsoft SharePoint 2010 [14]:

    Client Object Model: Its a new feature of Microsoft SharePoint 2010. It provides features to program

    against a SharePoint site using .NET Managed Code or JavaScript. It provides almost the programming features of the Server Object Model plus advantages in deployment.

    Sandboxed solutions: They are run using a restrictive set of code access security policies and are limited to a specific subset of the Server Object Model. They are also monitored. Among the components that can be deployed, we can find: Web Parts, Event Receivers, Feature Receivers, etc. The process of deploying such a solution on SharePoint Online is illustrated in Fig. 3.

    Fig. 3. The process of deploying a sandboxed solution on SharePoint Online

    C. 12BExperimental study To validate our orientation toward Cloud [18], we

    developed a sandboxed solution based on an event receiver. This solution contains a mechanism allowing automation of documents creation process thereby providing and ensuring data consistency. In order to perform this, we created a SharePoint list which contains the project items metadata, and a SharePoint document library which contains the project documents grouped by disciplines. The Event Receiver is triggered when a new item is added to the list, in order to automatically create a folder (if necessary) and a file in the document library. To measure the response time relative to the treatment being executed in the event receiver, we used the technique of the timer inserted in the code [12].

    For the on-premises development, we used a machine having the following software and hardware configuration: A processor: Intel Core2 Duo Processor P7350, a RAM: 4 Go, a hard disk: 100 Go, an OS: Windows Server 2008 R2 and the IDE Microsoft Visual Studio 2010. We did 390 requests and we measured, in each one, the response time. For SharePoint Online, we decided to evaluate Standard Office 365 P1 and E3 plans because they offer 30-day free trial. We created the same SharePoint components and defined the same data structure, we used the same sandboxed solution and the same test machine. Then, we activated the feature, used in the sandboxed solution, on SharePoint Online. We used the same requests number and we measured the response time. We classified results into intervals of 26 requests and we mentioned the minimal and the maximal response time value obtained in each interval as shown in TABLE III. In order to have a better results exploitation, we dressed the response time measurement curves for the three case studies as illustrated in Fig. 4.

  • 6

    TABLE III. RESPONSE TIME EVOLUTION ON-PREMISES AND ON CLOUD

    Interval of

    requests

    Response time on-premises (ms)

    Response time plan P1 (ms)

    Response time plan E3 (ms)

    Min Max Min Max Min Max [1, 26] 418 635 172 391 297 484 [27, 52] 534 929 281 487 469 656 [53, 78] 745 1102 422 719 609 797

    [79, 104] 859 1232 547 782 750 937 [105, 130] 1141 1425 672 906 859 1109 [131, 156] 1264 1625 844 1156 1031 1234 [157, 182] 1438 1944 1000 1329 1187 1406 [183, 208] 1808 2288 1157 1376 1218 1484 [209, 234] 1862 2283 1266 1591 1266 1547 [235, 260] 2014 2437 1375 1657 1422 1672 [261, 286] 2213 2590 1469 1845 1500 1937 [287, 312] 2330 2824 1516 1954 1859 2171 [313, 338] 2511 2965 1782 2094 2000 2203 [339, 364] 2617 3071 1829 2220 2093 2375 [365, 390] 2818 3195 1875 2329 2171 2399

    Fig. 4. Response time evolution on-premises versus on Cloud

    As its shown in Fig. 4, when the number of tests increases, response time increases too. In addition, the response times of the plans P1 and E3 are similar. Its clear that the execution of the sandboxed solution on Cloud is more efficient than its execution on-premises. With a number of request less than 100, there is a little difference in response time between on-premises and on Cloud. However, with a high number of requests, the difference is becoming significantly important.

    V. CONCLUSION AND FUTURE WORK In this paper, we elaborated a comparative study of three

    ECM platforms called Alfresco, Nuxeo and MOSS, showing their technical aspects and their business content approach components. Afterward, we explored, evaluated, and customized Alfresco and MOSS in the context of industrial engineering design offices. At Alfresco level, we developed a Web Script application to manage access rights, created a business Workflow and integrated Alfresco with Liferay portal. At MOSS level, we developed a business Workflow. Then, we evaluated the performance of MOSS on-premises and on Cloud. For this purpose, we applied the process of deploying a sandboxed solution on SharePoint Online. We showed that in Cloud, we have a better performance. Our short-time goal is to include other ECM platforms in our comparative study. In the long term, we intend to draw up dashboards for ECM platforms

    in order to offer a global vision of the application's functional part progress as well as the monitoring part.

    REFERENCES [1] Tim A. Rickenberg, Markus Neumann, Bernd Hohler and

    Michael Breitner, Enterprise Content Management - A Literature Review, in Proceedings of the 18th Americas Conference on Information Systems (AMCIS), Seattle, Washington, 2012. AISeL.

    [2] Ginika C. Onyechi and Geetha Abeysinghe, Adoption of Web Based Collaboration Tools in the Enterprise: Challenges and Opportunities, in Proceedings of the International Conference on the Current Trends in Information Technology (CTIT), Dubai, UAE, 2009, pp. 1-6. IEEE.

    [3] AIIM. http://www.aiim.org/. [4] AIIM. What is Enterprise Content Management, [Online].

    Available: http://www.aiim.org/What-is-ECM-Enterprise-Content-Management [Accessed: Sep. 12, 2011].

    [5] Muhammad Usman, Abdul Wahab Muzaffar and Abdul Rauf, Enterprise Content Management (ECM): Needs, Challenges and Recommendations, in Proceedings of the 2nd IEEE International Conference on Computer Science and Information Technology (ICCSIT), Beijing, 2009, pp. 283-289. IEEE.

    [6] Alan Weintraub. The Forrester Wave: Enterprise Content Management, Q4 2011. November 2011.

    [7] Mark R. Gilbert, Karen M. Shegda, Kenneth Chin, Gavin Tay and Hanns Koehler-Kruener (2012, Oct. 18). Magic Quadrant for Enterprise Content Management, [Online]. Available: http://www.project-consult.de/files/Oracle_Gartner-Magic-Quadrant-ECM_20121018.pdf [Accessed: Nov. 18, 2012].

    [8] Alfresco. http://www.alfresco.com/. [9] Nuxeo. http://www.nuxeo.com/. [10] MOSS. http://www.microsoft.com/SharePoint/. [11] Thomas Bchner, Florian Matthes and Christian Neubert,

    Functional Analysis of Enterprise 2.0 Tools: A Services Catalog, in Lecture Notes of Communications in Computer and Information Science (CCIS), 2010, pp. 351-363. Springer.

    [12] Florian Rosenberg, Christian Platzer and Schahram Dustdar, Bootstrapping performance and dependability attributes of web services, in Proceedings of the IEEE International Conference on Web Services (ICWS06), Washington, DC, USA, 2006, pp. 205-212. IEEE.

    [13] Joel C. SharePoint 2010 Pricing Explained. Oct. 1, 2012. [Blog entry]. Available: http://www.pinnacleofindiana.com/ blog/post/2012/10/01/sharepoint-2010-pricing-explained.aspx [Accessed: Jan. 10, 2012].

    [14] Philip Wicklund, Microsoft SharePoint 2010: Deploying Cloud based Solutions, Oct. 2011.

    [15] Liferay. http://www.liferay.com/. [16] NIST. http://www.nist.gov/. [17] Peter Mell and Timothy Grance (2011, Sep.). The NIST

    Definition of Cloud Computing, [Online]. Available: http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf [Accessed: Nov. 18, 2011].

    [18] David Banks, Jhon S. Erickson and Michael Rhodes, Toward Cloud-based Collaboration Services, in Proceedings of the 1st conference on Hot topics in cloud computing, San Diego, CA, USA, 2009. ACM.

    I. IntroductionII. ECM Platforms ClassificationIII. ECM Platforms EvaluationA. Project management provided technologiesB. Business Process ManagementC. Access rights management and collaborative toolsD. Synthesis

    IV. Sharepoint Online AssessmentA. Microsoft Office 365B. SharePoint Online customizationC. Experimental study

    V. Conclusion and future workReferences

Recommended

View more >