The additivity of each logger ("true" or "false"), determines whether it sends the output from its key to each appender.
A person who maintains the Rhino SLEE, deploys services and resource adaptors and provides access to the web console and command console.
The Apache Ant build tool.
Depending on the configuration, appenders append log messages to files, sockets or the Unix syslogd daemon.
After a transaction commits, saving the results of its operations into a durable form.
The interactive command-line interface use by administrators to issue online management commands to the Rhino SLEE.
A group of Rhino SLEE nodes which are managed as a single system image.
A separate Unix process, with a unique node ID. Multiple nodes can be installed in the same machine, but each node can only be a member of one cluster. A node can execute management commands and SBBs.
Embedded Jetty scenario
Deployment architecture for the web console, running in the Jetty servlet container and It launching using an m-let in the same virtual machine as Rhino.
Associated with every event fired in a JAIN SLEE 1.1, the event context encapsulates information related to the event, such as the event object, activity context, service and address.
Extension deployment descriptor
An OpenCloud-proprietary descriptor included in the deployable unit, which lets you configure many SBB runtime properties.
With Rhino, fault tolerance mans in the event of a failure, the SLEE is continuously available for management operations, each deployed service is continuously available, each service's session is continuously available, and a proportion (>95%) of sessions residing on a failed cluster member will be failed-over to another cluster member.
For Rhino, high availability means that in the event of a failure, the SLEE is continuously available for management operations, each deployed service is continuously available, each service's session is not continuously available, and any session being executed on a cluster member which fails will be destroyed.
The machine running the Rhino SLEE.
A programme of API development initiated by SUN Microsystems in the area of telecommunications. This term was initially an acronym for 'Java APIs for the Intelligent Network' but is now a trademark as the scope of JAIN increased to include non SS7 based networks and protocols
A telecommunications focused application server that adheres to the JAIN SLEE 1.0 (JRS 22) and JAIN SLEE 1.1 (JSR 240) specifications. SLEE is an acronym for 'Service Logic Execution Environment'
JAIN SLEE Developer
A person who writes and compiles components and deployment descriptors according to the JAIN SLEE 1.0 and 1.1 specifications.
A Java keystore (JKS), an in-memory collection of keys and certificates.
A configurable logging component which writes log messages to a medium such as a file or network.
A logging component which sends log messages to a log appender.
Main Working Memory
The mechanism used to hold the runtime state and the working configuration.
The memory database that holds the main working memory.
Management applet — a manageable extension to the Rhino SLEE.
An operational participant of a Rhino SLEE in a cluster.
The ability to survive a system failure.
A notification emitted or delivered to a notification listener.
A callback handler for JMX notifications.
Internal grouping of similar objects for performance.
Optimistic currency control
A model where each unit of transacted state has a version number and a value. When a transaction first accesses a unit of transacted state, the system makes a copy of the committed version number and value, to use for all operations in the transaction.
Typically standard output from the Rhino SLEE execution.
Pessimistic currency control
A model where the resource manager acquires a lock (shared or exclusive, depending on the semantics of the access) as the system first accesses each addressable unit of transacted state.
A Java-sandbox security policy which allocates permissions to codebases.
The PostgreSQL database server.
The group of nodes in a cluster which can process work (the set of nodes which know the authoritative state of the cluster).
A certificate containing an aliased asymmetric private key.
An operating-system process such as the Java VM.
An instance of a profile table.
A schema, which is defined in a profile specification from a deployable unit.
A certificate containing an aliased asymmetric public key.
Lightweight node that does not perform any event processing, nor participates in management-level operations. Intended to be used strictly for determining which parts of the cluster remain in the primary component, in the event of node failure.
An object which has been initialised and is ready to perform work.
A SLEE component that is used for communicating between the SLEE and an external resource.
Resource adaptor entity
A logical instance for a resource adaptor that performs work.
Resource adaptor object
A Java object created from a resource adaptor implementation for the purpose of executing resource adaptor logic.
Resource adaptor type
The common definition of a set of resource adaptors, including the Java interfaces they implement. Typically, an organisation of collaborating SLEE or resource vendors (such as the SLEE expert group) defines RA types. Administrators install them in the SLEE. A resource adaptors then is an implementation of particular RA type.
Resource adaptor-based fault tolerance
Also called "activity fault tolerance", because it applies to activities created by fault-tolerant RAs. All activities that fault-tolerant RAs create are replicated to other nodes in the cluster. If the activity-creating node fails, another cluster member can "adopt" the activity and assume responsibility for processing the events it produces.
A process that manages one or more instances of a transacted resource. For example, a relational database server may serve several relational databases. A resource manager typically supports a one-phase commit, and may or may not support two-phase commit.
Updating a new cluster member with the state of the cluster.
The total set of modules, components and application servers which run on JAIN SLEE.
The configuration of the Rhino SLEE including, but not limited to, the deployable units installed, profile tables, profiles, log levels, trace level, threshold based alarms, Service activation state and so on.
An object instance of an SBB that performs work.
The Java security manager.
Service-based fault tolerance
SBB entities and their state are replicated across all nodes in the cluster, using a replicated version of the main working memory. If a cluster node fails, or a network segmentation occurs, the replicated SBB state is still visible to other nodes.
To sign a jar using the Java jarsigner tool.
A system running on a network which stores the registration of SIP devices, and uses that information to provide the location of the SIP device on an IP network.
Exported binary images of particular profile tables.
A queue of units of work for Rhino to perform, operated by the staging-thread system.
The micro-management of work within the Rhino SLEE. This work is divided up into items, executed by workers. A system-level thread represents each worker.
A pool of threads on which Rhino performs event delivery.
Metrics gathered by the running Rhino SLEE.
Before a transaction commits, saving the results of its operations into a durable form.
Alarms configured by an administrator (to supplement the standard alarms raised by Rhino), to be raised or cleared automatically according to input from Rhino's statistics facility.
A resource that maintains the ACID properties of the transacted programming model when the system performs operations on it. Common examples include: relational databases, object databases and JMS message queues (when used in transacted mode).
An isolated unit of work.
Transaction manager or transaction coordinator
A process that demarcates transaction boundaries in a transacted resource. May coordinate several transacted resources in a single transaction. (A resource manager may or may not include a transaction manager.)
A lightweight thread that monitors the Rhino SLEE for undesirable behaviour.
The HTTP interface to the Rhino SLEE management facility.
What the SLEE does while it is in the RUNNING state: processing activities and events.
The copy of the configuration files that are actually used by the Rhino SLEE codebase.
The deployable units, profiles and resource adaptors configured in the main working memory.
The mechanism used to hold the runtime state and the working configuration.
Something missing? Let us know!
If you would like a reply, please provide valid contact details.