(n.) The primary connectivity mechanism of a distributed system. All systems that have connectivity to an intermediate system on the backbone are connected to each other. A backbone does not prevent you from setting up systems to bypass the backbone for reasons of cost, performance, or security.
(n.) In the context of Java Enterprise System Messaging Server, an email server whose only function is to store and retrieve email messages. Also called a message store server.
(n.) A JavaBeans component that corresponds to a JSP page that includes JavaServer Faces components. The backing bean defines properties for the components on the page and methods that perform processing for the component. This processing includes event handling, validation, and processing associated with navigation.
(n.) The removal of a software change (a patch, for example), which results in returning the system to its previous state.
(v.) To copy the contents of folders from the message store to a backup device. See also restore.
(n.) A repository for data, typically a file system or database. A backup store can be monitored by a background thread (sweeper thread) to remove unwanted entries.
(n.) A text string displayed by a service such as IMAP when a client first connects to it.
(base distinguished name) (n.) An entry in the DIT. A search operation can be performed on the entry identified by the base DN, the entries that are immediately subordinate to the base DN, or to the entry and all entries below the base DN in the DIT.
(n.) An authentication mechanism in which a Web server authenticates an entity by means of a user name and password obtained using the Web application's built-in authentication mechanism.
(n.) The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean. The data access logic is typically provided by a developer using JavaTM Database Connectivity (JDBCTM) software or other data access technologies. See also container-managed persistence.
(n.) Transaction demarcation for an enterprise bean that is controlled programmatically by the developer. See also container-managed transaction.
(Berkeley database) (n.) A transactional database store intended for high-concurrency read-write workloads and for applications that require transactions and recoverability. Java Enterprise System Messaging Server uses Berkeley databases for numerous purposes.
(n.) See unparsed entity.
(bind distinguished name) (n.) Distinguished name used to authenticate to a Java Enterprise System Directory Server in the bind request.
(1) (v.) For XML files, generating the code needed to process a well-defined portion of XML data.
(2) (v.) For JavaServer Faces technology, wiring UI components to back-end data sources such as backing bean properties.
(n.) In the context of access control, the bind rule specifies the credentials and conditions that a particular user or client must satisfy in order to get access to directory information.
(binary large object) (n.) A data type used to store and retrieve complex object fields. BLOBs are binary or serializable objects, such as pictures, that translate into large byte arrays, which are then serialized into container-managed persistence fields.
(n.) One part of an email message. Although headers and envelopes must follow a standard format, the body of the message has a content determined by the sender. The body can contain text, graphics, or multimedia. Structured bodies follow the MIME standard.
(n.) The Message Queue entity that manages Java Message Service (JMS) API message routing, delivery, persistence, security, and logging. Provides an interface that allows an administrator to monitor and tune performance and resource use.
(n.) Within Java Enterprise System Portal Server, refers to looking through the categorical divisions of the resources in a Search database.
(n.) The XML file that contains one or more asant targets. A target is a set of Apache Ant tasks you want to be executed. When starting asant, you can select which targets you want to have executed. When no target is given, the project's default target is executed. See also asant.
(n.) A hardware or software construct with limited or no dependencies on shared services. A specific configuration that provides optimum performance and horizontal scalability.
(n.) The code that implements the essential functionality of an application rather than data integration or presentation logic. In EJB technology, this logic is implemented by the methods of an enterprise bean.
(n.) A method of an enterprise bean that implements the business logic or rules of an application.
An application component or component assembly that performs business logic on behalf of multiple clients (and is therefore a multi-threaded process). A business service can also be an assembly of distributed components encapsulated as a web service, or it can be a standalone server.