Datasheet 
Download 
Resources 
Quotation
Buy online 
Support 
Print Page 
Email Page 
t:: +44-(0)1684-576343
f:: +44-(0)700-6020779 enquiries@purplerage.com
PeerLink Server is part of PeerCollaboration Enterprise. PeerLink is an enterprise application that creates a fully collaborative environment across both LAN and WAN networks. It ensures the same data exists on all participating servers regardless of where changes occur, even on NetApp filers. The result is users are prevented from accessing files that are already in use on another server in the environment.
A file collaboration session consists of two or more participating servers, and a folder hierarchy called the Watch Set, located on each server which will be kept synchronised by propagating file locks and modifications to all participating servers in real-time.
PeerLink Server is made up of three elements which together form the fully collaborative environment that is PeerLink.
- PeerLink Hub -
this is the central component of the PeerLink framework. All PeerLink solutions are installed, configured and started at the Hub.
- PeerLink Broker - makes up the central messaging system that supports PeerLink applications. The Broker provides the core communication facility that connects the Hub and Agents in a PeerLink collaboration environment.
- PeerLink Agent - is a lightweight component that is installed on a networked host that enables it to participate in a PeerLink collaboration environment.
Using PeerLink
After installing and configuring a PeerLink file collaboration session the following occurs:Step 1: Session Start
At the start of a file collaboration session, PeerLink requests to scan each participating server’s "Watch Set" (the collection of folders being monitored and controlled) for file content. The scans are performed at the agents and results are dispatched back to the hub for merging and file conflict resolution. Transfers are then issued to the agents to synchronise their servers’ folders. Once complete, the agents are directed to start detecting access and change events on their respective servers.
Step 2: File Lock
Files will be opened by users during the course of a file collaboration session. When a file is loaded into an application to be modified, the PeerLink Agent detects the event and notifies the PeerLink Hub of the activity. The Hub then issues a lock event for each of the remaining (target) analogous files across the session. Only one (1) source instance is allowed for any given opened file in a session. Note: If a file is opened in read-only mode, or if the application that opens the file does not acquire a read-write lock on the file (e.g. NotePad, WordPad, etc.), the lock will not be propagated to the target hosts.
Step 3: File Transfer
When an opened source file is closed with modifications, a synchronising transfer request is issued. The session first acquires a lock on the source file to facilitate a stable transfer. The locks on the target copies are preserved during the lock transition at the source. The revised source content is propagated to the target instances and the locks are released. Transfers are conducted among participating Agents and coordinated through the Hub.