|
Term
|
Definition
|
|
Community
|
A community is a set of peers, together with the
role that each peer has within that community, and network routing information
that specifies how packages are sent to members of the community.
|
|
Community Manager
|
A community manager is one of the Everserve roles.
A community manager can modify the definition of the community. It can
add or remove peers and can change the roles or routing information
of all peers within a community. This role is responsible for the propagation
of digital certificates for all peers.
|
|
Package
|
A term to describe the execution and contents of
a package specification. It can be any file, application, or script
that is replicated to community peers using Everserve.
|
|
Package Delivery
|
Package delivery is the process of sending package
instances from a publisher to a set of targets. Delivery is initiated
only by peers with a publisher role and recipients can be an explicit
list of peers or an entire community. Only targets execute the contents
of the package. Packages are digitally signed by the sender and result
in receipts sent back to the sender from the target peers that receive
it.
|
|
Package Specification
|
A package specification is an XML file containing
a set Everserve attributes. It contains any number of file, directory
and command "spec" attributes associated with the replication
of commands and scripts or filesystem objects.
|
|
Peer
|
A member of a community that is named and assigned
one role by the community manager.
|
|
Publisher
|
A publisher is the only peer role that can initiate
package delivery to a set of Everserve peers. After targets open the
package, the publisher accepts return results from package execution
in the form of receipts that are stored in a database.
|
|
Relay
|
A relay is a peer that receives a package from either
a publisher or another relay, and sends the package to a set of peers
in the community as designated by the community manager..
|
| Receipts |
A package return receipt (or more simply, a receipt) contains
the results of opening and executing the contents of an Everserve package.
This includes the standard output, standard error, and return code of
comand attributes along with the results of file and directory replication
operations. Return receipts are sent by targets to the publisher that
issued the deliver command. |
|
Roles
|
A peer may have one role within the context of a
community. The roles are: community manager, publisher, relay, and target.
|
|
Scripts
|
An Everserve script is one that will be executed
on a system running Everserve. Everserve scripts may be intrinsic scripts
or shell scripts. An intrinsic script contains Everserve commands that
are issued through the Everserve interactive shell or on the command
line beginning with "everserve." Shell scripts are executed
by the shell environment of the target system when sent as part of a
package. Thus, shell scripts are operating system dependent whereas
execution of intrinsic scripts depends on the Everserve role assigned
to the peer.
|
Seed File |
A file in zip format created by the Community Manager in
the server directory following execution of the "create community"
command. This contain all the information needed to enable an Everserve
peer into a community, especially the definitions of the publishers, and
community manager peers.. |
|
Target
|
A target is a peer named by the community manager
and successfully joined to the community. It is enabled to receive Everserve
packages. When a target receives a package, it opens the package, executes
the commands and scripts, and sends a receipt back to the community's
publisher.
|
|
Transport
|
The means by which Everserve systems communicate
with each other. This typically refers to the OpenJMS software package
that is bundled with Everserve and RMI (Java's Remote Method Invocation
protocol).
|
