Alfresco Migration Services

Name: Shoeb SargurohDate: 14/07/2010

Alfresco Migration ServicesWebinar Agenda

● An introduction to Alfresco Migration Services

● Wasaaiq expertise in Alfresco

● Demonstration of Alfresco Migrations Services ● 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 SharePointEMC/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● 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 ● Use of owExIm, EntropySoft ETL, OneWindow components for Migration

Wasaaiq – Migration Methodology

DCTM/

MOSS

Active

Dormant/

Offline

Content

Entropy

Soft ETL

Alfresco

Live

Production

Content

OwPackage

/ Acp

owExim

App

Beta

version

OneWindow

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 doneo unified API : method names are the same whatever the remote application iso 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 :o Alfrescoo EMC Documentum Content Server o IBM FileNET P8o IBM Content Managero IBM DB2 Content Manager On Demando IBM Websphere Portal PDMo Interwoven Worksite NT o Open Text LiveLink o OpenText edocs (Hummingbird DM)o Oracle Stellent UCM

Xerox Docushare

� Records Management :o IBM FileNet RMo HP Trim Contexto Hummingbird RMo Symantec Enterprise Vault

� Messaging systems :o Lotus Noteso Microsoft Exchange

� Generic systems :o Xerox Docushare

� Web Content Management Systems :o Interwoven Teamsiteo Vignette

� Collaboration frameworks :o EMC CenterStageo EMC Documentum eRoomo Lotus Quickplaceo Lotus QuickRo Microsoft SharePoint

� Generic systems :o JCRo CMISo File serverso FTPo Webdav

� Labs :o Iron Mountaino GoogleDocso SalesForceo IBM Lotus Web Content Managemento OpenText Artesia

8

EntropySoft products - connectors (3/3)

Client application

� 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 Documentumo getNode() for Alfresco

9

Alfresco

connector

Documentum

connector

Documentum Alfresco

getNode(id

)

getObject(id)

Client application

getItem(id) getItem(id)

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� 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) methodo Content Hub loops on all connectors and calls the search(SQL) method on each one of themo 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)

Client application

getItem("Documentum",

id)

getItem("Alfresco", id)

ContentHub

� In the schema below, you can see that a client application only needs to interact with a single

component : the Content Hub.

1111

Alfresco

connector

Documentum

connector

Documentum Alfresco

getNode(id

)

getObject(id)

ContentHub

getItem(id) getItem(id)

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 themo 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)

1616

EntropySoft products - The big picture (3/3)

171717

Wasaaiq - owExIm

● Offline Package Viewer

● On Demand Content Reconciliation

Other Uses

Used for Transmittals● 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%● 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>