Sun Java Enterprise System Glossary

T

 

 

tag

(n.) In XML documents, a piece of text that describes a unit of data or an element. The tag is distinguishable as markup, as opposed to data, because it is surrounded by angle brackets (< and >). To treat such markup syntax as data, you use an entity reference or a CDATA section.

takeover

See failover.

target

(1) (n.) In the context of access control, the target identifies the directory information to which a particular ACI applies.

(2) (n.) In the Application Server, a target is a server instance to which an application deployment or configuration change applies.

(3) (n.) In Apache Ant, a target is a set of tasks you want to be executed. See also asant, build file.

target entries

(n.) The entries within the scope of a CoS.

task

(n.) In Calendar Express on the client side, a component of a calendar that specifies something to be done. On the server side, a task is also called a todo.

taxonomy

(n.) A system of categories for the resources in the Java Enterprise System Portal Server Search Engine.

telnet proxy

(n.) An application that sits between the telnet client and telnet server and acts as an intelligent relay.

template

(n.) A set of formatting instructions that apply to the nodes selected by an XPath expression.

template entry

See cooperating server.

timeout

(n.) A specified time after which the server should give up trying to finish a service routine that appears to be hung.

time zone

(n.) A geographical region that uses the same time. There are 25 hourly time zones from -12 through +12 (GMT is 0). Each time zone is measured relative to GMT. Most time zones have localized designations in three-letter abbreviations. The Calendar Server also identifies time zones using a time zone ID (TZID) such as America/Los_Angeles or Asia/Calcutta.

TLS

(Transport Layer Security) (n.) A protocol that provides encryption and certification at the transport layer so that data can flow through a secure channel without requiring significant changes to the client and server applications. The standard for SSL, a public key-based protocol.

todo

(n.) On the server side, a component of a calendar that specifies something to be done. In Calendar Express on the client side, a todo is called a task.

tool provider

(n.) An organization or software vendor that provides tools used for the development, packaging, and deployment of J2EE applications.

top

(n.) (UNIX only) A program on some UNIX systems that shows the current state of system resource usage.

topic

(n.) An object created by an administrator to implement the publish and subscribe delivery model. A topic can be viewed as a node in a content hierarchy that is responsible for gathering and distributing messages addressed to it. By using a topic as an intermediary, message publishers are kept separate from message subscribers.

top-level administrator

(n.) A user who has administrative privileges to create, modify, and delete mail users, mail lists, family accounts, and domains in an entire Messaging Server namespace by using the Delegated Administrator for Messaging and Collaboration GUI or CLIs. By default, this user can act as a message store administrator for all messaging servers in the topology.

top-level domain authority

(n.) The highest category of host name classification, usually signifying either the type of organization the domain is (for example, .com is a company and .edu is an educational institution) or the country of its origin (for example, .us is the United States, .jp is Japan, .au is Australia, and .fi is Finland).

topology

(1) (n.) The way a directory tree is divided among physical servers and how these servers link with one another.

(2) (n.) An arrangement of machines, Application Server instances, and HADB nodes, and the communication flow among them. See server instance, HADB node.

transaction

(1) (n.) A set of database commands that succeed or fail as a group. All the commands involved must succeed for the entire transaction to succeed.

(2) (n.) An atomic unit of work that modifies data. A transaction encloses one or more program statements, all of which complete with either a commit or a rollback. Transactions enable multiple users to access the same data store concurrently.

transaction attribute

(n.) A value specified in an enterprise bean's deployment descriptor that is used by the EJB container to control the transaction scope when the enterprise bean's methods are invoked. A transaction attribute can have the following values: Required, RequiresNew, Supports, NotSupported, Mandatory, or Never.

transaction context

(n.) A transaction’s scope, either local or global. See transaction context

transaction isolation level

(n.) The degree to which the intermediate state of the data being modified by a transaction is visible to other concurrent transactions and data being modified by other transactions is visible to it.

transaction manager

(n.) Provides the services and management functions required to support transaction demarcation, transactional resource management, synchronization, and transaction context propagation. Normally uses the XA protocol. See also global transaction.

transaction recovery

(n.) Automatic or manual recovery of distributed transactions.

transience

(n.) A protocol that releases a resource when it is not being used. Opposite of persistence.

transient failure

(n.) An error condition that occurs during message handling. The remote MTA is unable to handle the message when the message is delivered but might be able to handle the message later. The local MTA returns the message to the queue and schedules the message for retransmission at a later time.

Transport Layer Security

(TLS) (n.) The standardized form of SSL. See also secure socket layer.

transport protocols

(n.) Protocols which provide the means to transfer messages between MTAs, for example SMTP and X.400.

trust database

(n.) A security file that contains the public and private keys. Also referred to as the key-pair file.

trusted provider

(n.) One of a group of service providers and identity providers in a circle of trust. Users can transact and communicate with trusted providers in a secure environment.