Terminology

<< Click to Display Table of Contents >>

Navigation:  Peer Management Center Help > Getting Started >

Terminology

Introduction

Before getting started, it is important to have a good understanding of key concepts and terminology used throughout this help system.

Terms

File Access Event

An event that is triggered from the opening or closing of a file.

File Change Event

A event that causes a file to be changed in some way, for example, file modify, file delete, file rename, file attribute change.

File Collaboration Job

A specific instance of a Peerlet that can be created, saved, modified, and run. A Peerlet represents a type of job.

In the case of File Collaboration, a File Collaboration job represents a single configurable File Collaboration Session. The two terms may be used interchangeably throughout the interface and this document.

File Collaboration Session

A communication session made up of two or more hosts, each with a designated root of folders and files that are to be shared or collaborated on. A collaboration session coordinates the primary functions of file locking and synchronization.

File Lock Conflict

A file collaboration condition that exists when two users open a file at the same time and both hold exclusive locks on the file.

Heartbeat

A communication mechanism used between the Peer Management Center and all connected Peer Agents to ensure that Peer Agents are alive and responsive. Heartbeats share information about the Peer Agent host server with the Peer Management Center, aid in verifying when a Peer Agents is no longer available, and signal when a disconnected Peer Agent has reconnected. All heartbeat information is sent through the Peer Management Broker.

Job

For File Collaboration, a job is a grouping of two or more participating hosts, each with a designated set of folders and files that are to be shared or collaborated on. A File Collaboration job coordinates the primary functions of file locking and synchronization.

For Cloud Sync, a job is a single participating host with a designated set of folders and files that are to be replicated to a cloud storage device.

Initial Synchronization Process

The background process that occurs at the start of a file collaboration session, where the directory watch set is recursively scanned on all participating hosts, file conflict resolution is performed, and any files that require updating are synchronized with the most current copy of the file.

Participating Host

The Management Agent of a file server that is taking part in a file collaboration session or a Cloud Sync job.

Peer Agent (or Agent)

A lightweight, distributed component that is used to perform operations on the host on which it is running. A Peer Management Center environment will typically contain several Peer Agents, one per participating networked host. Peer Agents invoke the distributed portions of a Peerlet, and will often run near resources of interest, such as collaborated files. The Peer Agent is designed to be purposed across the entire Peer Management Center solution suite, and will normally be directed to perform functions with messages received from Peerlets through the Peer Management Broker.

Peer Management Center

The focal software component where Peerlets are installed, configured and ran. The Peer Management Center can host Peerlets of various types and is where the components of a centralized solution function. The Peer Agent is invoked by Peerlets, distributing components with messages sent through the Peer Management Broker.

The Peer Management Center runs as three parts:  a Windows Service that is set to run all the time, along with a rich client application and a web server component that both connect to the primary service for configuration and monitoring.

Peer Management Broker

The central messaging system of the Peerlet framework. The Peer Management Broker serves to connect the Peer Management Center and the Peer Agents, forming a Peer Management Center "network" that can be cast over local or wide-area networks via TCP/IP.  A Peer Management Center environment will deploy one or more Peer Management Brokers.

Peerlet

A solution built for the Peer Management Center framework. A Peerlet is a distributed application containing various parts, some of which function at a focal point called the Peer Management Center and others invoked at remote points designated as Peer Agents.

Peerlet Editor

A container within the user interface of the Peer Management Center that shows runtime and configuration information for a single file collaboration job. A Peerlet Editor is represented by a single tab, typically in the large center section of the Peer Management Center's interface. The editor itself consists of multiple sub-tabs, with various runtime and configuration information dispersed amongst the sub-tabs. For more information, see Runtime Job Views.

Editors for multiple file collaboration jobs can be opened in several different editor tabs, allowing for quick movement between jobs.

The Peerlet Editor area of the Peer Management Center is referred to as the File Collaboration Runtime view throughout this document.

Quarantined File

A file that has been removed from a file collaboration session as a result of a file lock conflict that could not be resolved. This file will remain quarantined until the user manually removes it from quarantine.

Source Host

The Management Agent of a file server where a file access or change event originated from.

Target Host

One or more Management Agents of file servers where file access and change events will be propagated to.

Views

Individual sections of the Peer Management Center's user interface, each providing unique information and control.

Examples: Main View, Jobs View, Peer Agent Summary View, Alerts View, Job Alerts View.

Watch Set

The configured root folder and all subfolders on a file server that are being scanned and/or monitored by a File Collaboration or Cloud Sync job.