Switch to alfresco with wasaaiq [compatibility mode]
Upcoming SlideShare
Loading in...5

Switch to alfresco with wasaaiq [compatibility mode]



Presentation by Wasaaiq, an Alfresco partner in the Middle East, outlining how to Switch to Alfresco

Presentation by Wasaaiq, an Alfresco partner in the Middle East, outlining how to Switch to Alfresco



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Switch to alfresco with wasaaiq [compatibility mode] Switch to alfresco with wasaaiq [compatibility mode] Presentation Transcript

  • Alfresco Migration Services Name: Shoeb Sarguroh Date: 14/07/2010
  • Alfresco Migration Services Webinar Agenda ● An introduction to Alfresco Migration Services ● Wasaaiq expertise in Alfresco ● Demonstration of Alfresco Migrations Services ● Q&A session
  • Content Migration Made Easy ● Demand to simplify legacy & proprietary ECM system replacement ● Alfresco packaged migration services ● Initially available for organizations migrating from EMC/Documentum & Microsoft SharePoint ● Experienced ECM system integrators to deliver Alfresco Migration Services ● Free-of-charge workshop to discuss & scope your organization’s migration to Alfresco
  • Reduce Cost of Legacy or Proprietary ECM Benefits of Switching to Alfresco ● Significant budget savings on proprietary ECM maintenance fees ● Fund Alfresco subscription out of OPEX budget ● Maintain business as usual for business users ● Additional functionality and next-generation interoperability Future-Proof Platform ● Open Standards & Architecture ● CMIS Compliant Repository ● Avoid Vendor Lock-in
  • Wasaaiq ● Over a decade of ECM experience. ● Specialise in Documentum/Alfresco Migration ● Previous experience include implementing Documentum based solutions ● Use of owExIm, EntropySoft ETL, OneWindow components for Migration
  • Wasaaiq – Migration Methodology Entropy DCTM/ Active Soft ETL MOSS Live Dormant/ Production Offline Content Content Alfresco OwPackage / Acp OneWindow Beta version owExim App On Demand
  • EntropySoft products - connectors (1/3) EntropySoft connectors are stand-alone jar files that can connect to more than 35 content repositories and that expose the same API. Content repositories (ie : content management systems) usually expose a public API so that external client applications can interact with them. This can create interoperability problems since each API is different : o different protocols : SOAP, REST, proprietary, RMI… o different method names : getDocument(), retrieveDocument(), getById()… o different metadata names, permission models, error messages… Main advantages of EntropySoft connectors : o easy integration : just add the jar file to your classpath and you’re done o unified API : method names are the same whatever the remote application is o unified metadata names, permission model, error messages… Connectors can be directly embedded in an application, or remotely accessed using webservices or RMI. A connector follows the adapter UML design pattern. 7
  • EntropySoft products - connectors (2/3) Content Management Systems : Records Management : o Alfresco o IBM FileNet RM o EMC Documentum Content Server o HP Trim Context o IBM FileNET P8 o Hummingbird RM o IBM Content Manager o Symantec Enterprise Vault o IBM DB2 Content Manager On Demand o IBM Websphere Portal PDM Messaging systems : o Interwoven Worksite NT o Lotus Notes o Open Text LiveLink o Microsoft Exchange o OpenText edocs (Hummingbird DM) o Oracle Stellent UCM o Xerox Docushare Generic systems : o JCR o CMIS Web Content Management Systems : o File servers o Interwoven Teamsite o FTP o Vignette o Webdav Collaboration frameworks : Labs : o EMC CenterStage o Iron Mountain o EMC Documentum eRoom o GoogleDocs o Lotus Quickplace o SalesForce o Lotus QuickR o IBM Lotus Web Content Management o Microsoft SharePoint o OpenText Artesia 8
  • EntropySoft products - connectors (3/3) In the schema shown below, a client application is using two Entropysoft connectors. To retrieve an item, the client application calls the same getItem() method on both connectors. Internally, the connector connects to the target DMS and calls the native API : o getObject() for Documentum o getNode() for Alfresco Client application getItem(id) getItem(id) Documentum Alfresco connector connector getObject(id) getNode(id ) Documentum Alfresco 9
  • EntropySoft products - Content Hub (1/4) Content Hub (or Content Federation Server) is the EntropySoft middleware that provides a unique point of access to many content repositories. Behind the scene, Content Hub is using the EntropySoft connectors to access the content repositories. Connectors can be easily plugged and unplugged in Content Hub (like a network cable can be plugged and unplugged in a network hub). A client application connects to Content Hub using web services : Content Hub exposes the same API as all EntropySoft connectors . For example, Content Hub can be used to run a federated search on all content repositories : o client connects to Content Hub and calls the search(SQL) method o Content Hub loops on all connectors and calls the search(SQL) method on each one of them o Content Hub aggregates the result and send it back to the client Content Hub follows the facade UML design pattern. 10
  • EntropySoft products - Content Hub (2/4) In the schema below, you can see that a client application only needs to interact with a single component : the Content Hub. Client application getItem("Documentum", getItem("Alfresco", id) id) ContentHub getItem(id) getItem(id) Documentum Alfresco connector connector getObject(id) getNode(id ) Documentum Alfresco 11
  • EntropySoft products - Content Hub (3/4) Content Hub is also hosting the jobs developped in Content ETL (see next chapter) and is used to start/stop/monitor them. Content Hub is shipped with a web front end called « webTop » that can be used to : o administrate Content Hub (create users, plug and unplug connectors…) o visually browse content repositories and interact with them o start, stop and monitor jobs. • Behind the scene, webTop uses the Content Hub web services. 12
  • EntropySoft products - Content Hub (4/4) 13
  • EntropySoft products - Content ETL Content ETL is a visual development environment for jobs. A job is mainly used to move documents from a source repository to a target repository (in the context of a migration for example). Content ETL is actually a set of Eclipse plugins : most Java developers will feel « at home » when using it. Content ETL uses Content Hub for all interactions with content repositories. Once a job is designed, it can be deployed and executed in Content Hub. Most webTop visual features are available in Content ETL, so you never need to switch between the two applications. 14
  • EntropySoft products - The big picture (1/3) 15
  • EntropySoft products - The big picture (2/3) 16
  • EntropySoft products - The big picture (3/3) 17
  • Wasaaiq - owExIm ● Offline Package Viewer ● On Demand Content Reconciliation Other Uses ● Used for Transmittals ● Allows vendors/ 3rd party to access content without ECM access ● Bulk Loading ● Submittals
  • owExIm
  • One Window Components ● Configurable Layer ● Predefined models for Projects, Correspondences, Regulatory, Engineering and non-engineering content ● XML based configuration – saves from customization! ● Reduces development cost by upto 40% ● AutoFile, Auto Number Confguration ● CMIS enabled (not yet)
  • Demo ● Quick Demo
  • Q&A ● Questions?
  • More information ● More information <insert local url for> http://www.alfresco.com/services/migration/ ● Request a free workshop http://www.alfresco.com/services/migration/#request-a-call ● <insert partner contact info in here>