Inter-Repository Exchange

[resplin]

Obsolete Pages{{Obsolete}}

The official documentation is at: http://docs.alfresco.com

Design DiscussionsResearch For Future Features

Table of Contents

• 1 Overview


• 2 Type


• 3 Actors


• 4 Executives


• 5 Exceptions

Overview

This is the hand-over of content from one repository to another. The principal actors are the repository that is sending content, the repository that is receiving the content and the administrators who are managing this exchange. There will probably multiple use cases including the push of content from one to many repositories and the pull of content from one repository to another. There are also ancillary use cases around the follow-up actions that can occur to the exchange or the compensation to failure of the exchange.

This use case is about the movement of content from one repository to another. There have been some attempts to solve simple syndication in the form of RSS, but the class of replication required by enterprises and B2B are much more complex. Internal replication of content bases is something that only large organizations have been able to accomplish after a great deal of effort. By establishing a set of web services interfaces, it should be possible for 3rd party developers to simplify this process and provide whole solutions for replications. As the industry consolidates to fewer players, this should be an enabler to allow that to occur.

• Geographic replication � Sharing and synchronizing content bases between two or more geographic sites for the purpose of knowledge sharing or re-use of web content for closer proximity or translation.
  

• B2B replication � Create new classes of content services by allowing the external management of records repositories or shared business processes. Industry clusters such as aerospace or pharmaceutical could share and trade information with collaboration partners with the added security of web services security access without opening up firewalls.
  

• B2B syndication � RSS solves a set of problems for syndicating content, but more complex push and pull of information such information related to commercial transactions or process related information such as specifications or quality certificates requires more sophisticated handling of security, classification and lifecycle.
  

Offline Synchronization - Tools to manage download sets for off-line users that provides both the content and metadata for accessing the content. Synchronize when next connected.

Type

User Goal

Actors

1. System Administrator
   
2. System
   
3. Job Scheduler
   

Executives

1. System Administrator provides authentication credentials for two repositories for logging into a central authentication service.
   
2. System provides a list of content types, a list of repositories, and a list of search criteria to qualify the content to be replicated.
   
3. System Administrator specifies the content type, and search criteria of the source repository.
   
4. System Administrator specifies the target repository to send the content to.
   
5. System submits the transfer request and job schedule to a Job Scheduler.
   
6. Job Scheduler invokes the transfer request at the specified time.
   
7. Job Scheduler provides authentication credentials, source repository, content types, and search criteria for the source content.
   
8. Job Scheduler provides authentication credentials for the target repository.
   
9. System executes the content transfer asynchronously
   
10. System returns the execution status to Job Scheduler
    
11. System succeeds or fails in the transfer.
    

Exceptions