Glossary

1 Glossary

1.1 A

This section describes glossary information about alphabet A.

Parent topic: Glossary

1.1.1 abort

Terminate a transaction in such a way that the values assigned to all protected resources, such as database records, are unchanged from the beginning of the transaction.

Parent topic: A

1.1.2 absolute OID

(CORBA) An object identifier (OID) that specifies a unique path to a managed object from the root of the OID tree.

See Also:

object identifier (OID).

Parent topic: A

1.1.3 Abstract Syntax Notation One (ASN.1)

A formal notation used to define data types and encode data values. A language that describes the data structures that make up an abstract syntax. ITU-T (formerly CCITT) specification X.409 is equivalent to ASN.1. ASN.1 Distinguished Encoding Rules (DER) object identifiers are used in public key interface (PKI) security programming.

Parent topic: A

1.1.4 access control list (ACL)

An Oracle Tuxedo security feature that controls client access to services, objects, and methods by means of lists of clients that are authorized to receive specific services or invoke specific objects and methods. When ACL security is being used, the Oracle Tuxedo system checks the appropriate list whenever a client requests a service, to determine whether the client is authorized to access the service.

Parent topic: A

1.1.5 Access Decision object

(CORBA) The object in the security infrastructure of a CORBA application that enforces the checking of authorized access before a request to the target object is delivered.

Parent topic: A

1.1.6 access machine

The processor within the administrative domain of an application at which a client first accesses the system. For a native client, this is the processor on which it is running. For a Workstation client, this is the site at which it contacts the application.

Parent topic: A

1.1.7 ACID properties

The essential characteristics of transaction processing systems include the following:

Atomicity, which requires that all changes made by a transaction to a database are made permanent, or else all are nullified.
Consistency, which defines the success of a transaction as the transformation of a database from one valid state to another.
Isolation, which requires that changes made by a transaction to a database must not be visible to other operations until the transaction completes its work.
Durability, which guarantees that changes made by a transaction to a database survive future system or media failures.

Parent topic: A

1.1.8 ACL

See Also:

access control list (ACL).

Parent topic: A

An Oracle Tuxedo server that is either processing a service request or is available to do so.

Parent topic: A

1.1.14 ADE

See Also:

A component of a network management system that exchanges data about managed objects with a manager at a network management workstation. At a manager’s request, agents provide a software interface to, and gather data about, managed resources.
In a two-phase commit syncpointing sequence (LU6.2 or MRO), a task that receives syncpoint requests from an initiator (a task that initiates syncpointing activity).

See Also:

An interactive Java program that can be run via a Web page displayed by a Java-capable browser. An applet enhances the Web page’s display or enables the user to complete a task.

Parent topic: A

1.1.31 application

A business program, built around the Oracle Tuxedo system, that is defined and controlled by a single Oracle Tuxedo configuration file, and that is administered as a single entity. Such an application may comprise one or more clients (local or remote), one or more servers, and one or more machines. At a minimum, an Oracle Tuxedo application includes one machine, one server, and one client. Also referred to as an Oracle Tuxedo domain.

Multiple Oracle Tuxedo applications can communicate with each other through a domain gateway group.

Note:

In this context, the term business program is defined as a set of one or more programs that work together. Similarly, in conversation the term application is often used loosely: it may refer to a standalone program or to a set of programs that work together to accomplish a particular business objective.

See Also:

A hardware and software platform (for example, SPARC/Solaris, Intel Pentium/Windows NT, or Intel Pentium/Linux).
The structure and interrelationship of components in a system or in an environment.

Parent topic: A

1.1.46 ASN.1

See Also:

Abstract Syntax Notation One (ASN.1).

Parent topic: A

1.1.47 asymmetric algorithm

An encryption algorithm that has two keys: a public key and a private key. The public key can be distributed openly while the private key is kept secret. Asymmetric algorithms may be capable of a number of operations, including encryption, digital signatures, and key agreements.

Parent topic: A

1.1.48 asymmetric outbound IIOP

Note:

(CORBA) The process of associating a name with an application object or a naming context object. Also used to describe the process of connecting a client application to an application object.

Parent topic: B

1.2.6 bitmap

In temporary storage, a control block used by intrapartition transient data to show the VSAM control intervals that have been used and are available. It is updated whenever a control interval or track is assigned to or released from a destination.

Parent topic: B

1.2.7 blocking

The process of combining two or more records into one block.

(CORBA) An application-level component that can be used in combinations that may not be defined ahead of time. A business object is independent of any single application and represents a recognizable, everyday-life entity, such as a document processor. A business object is a self-contained deliverable that has a user interface and a state, and that can cooperate with other separately developed business objects to perform a desired task.

See Also:

object.

Parent topic: B

1.2.18 byte

A sequence of eight adjacent bits that are operated on as a unit.

Parent topic: B

1.3 C

This section describes glossary information about alphabet C.

Parent topic: Glossary

1.3.1 C++

An object-oriented programming language developed at AT&T Bell Laboratories in the early 1980s. C++ is a “hybrid” language based on the non-object-oriented C language.

Parent topic: C

1.3.2 cache

A subset of memory that contains copies of the frequently accessed parts of a larger memory.

Parent topic: C

1.3.3 callback method

A method that is implemented by application code and that is invoked by system code when needed to perform a specific function. Callback methods are never intended to be invoked directly by application code.

See Also:

application code and metadata interface.

Parent topic: C

1.3.4 Callbacks Wrapper object

(CORBA) An object implemented to support callbacks on CORBA joint client/server applications using the Oracle Wrapper Callbacks API.

Parent topic: C

1.3.5 CARRAY buffer

A data structure that is an array of characters any of which can be the null character. The interpretation of the array is entirely application dependent.

Parent topic: C

1.3.6 catalog

See Also:

message catalog.

server application.

Parent topic: C

1.3.19 Client Data Caching design pattern

(CORBA) The design pattern that provides increased performance for client applications by caching server application data on the machine on which the client application resides, thereby avoiding repeated remote calls to retrieve data.

See Also:

design pattern.

Parent topic: C

A software infrastructure in which developers cannot remove and replace software components easily in a plug-and-play fashion.

Parent topic: C

1.3.25 CMIP

See Also:

Common Management Interface Protocol (CMIP).

Parent topic: C

1.3.26 columnar object

A MIB leaf object—that is, a MIB object that does not have any objects below it in the OID tree—which can have zero or more instances. A columnar object represents one column in a table.

Parent topic: C

1.3.27 COM

See Also:

Component Object Model (COM).

Parent topic: C

1.3.28 COM view

(CORBA) A representation of an object that conforms to the Component Object Model (COM) standards, including implementations of all necessary interfaces.

See Also:

Component Object Model (COM).

Parent topic: C

1.3.29 command-line interface

A style of user interface that allows user interaction by entering commands at a system prompt.

Parent topic: C

1.3.30 commit

Complete a transaction so that changes are recorded and stable. Protected resources are released.
The declaration or process of making a transaction’s updates and messages visible to other transactions. When a transaction commits, all its effects become public and durable. After commitment, the effects of a transaction cannot be reversed automatically.

Parent topic: C

1.3.31 Common Management Interface Protocol (CMIP)

An protocol for network management defined by ISO standards.

Parent topic: C

1.3.32 Common Object Request Broker Architecture

See Also:

CORBA.

Parent topic: C

1.3.33 compact disc-read only memory (CD-ROM)

A disk from which data is read optically by laser and on which the data cannot be modified except under special conditions.

Parent topic: C

1.3.34 component

Part of an application.

Parent topic: C

1.3.35 Component Object Model (COM)

(CORBA) A collection of services that let software components interoperate in a networked environment.

See Also:

Parent topic: C

1.3.45 conversation

A dialog over a connection.

Parent topic: C

1.3.46 conversational

Communication characterized by one or more messages exchanged by a requestor and a server such that the server remains dedicated to the communication until the termination of the exchange.

Parent topic: C

1.3.47 conversational communication

See Also:

conversational.

Parent topic: C

1.3.48 conversational server

A server that offers services that require a connection to have a conversation with the requester. The conversation follows an application-established protocol. A conversational service must conform to the startup and termination rules of Oracle Tuxedo system services.

Parent topic: C

1.3.49 conversational service

A service routine that is invoked by means of conversational communication from a client program. When the connection is established and the service is invoked, the client and service exchange data in a manner specific to the application. When the service returns, the connection ends.

Parent topic: C

1.3.50 CORBA

(CORBA) Common Object Request Broker Architecture. A multivendor standard published by the Object Management Group for distributed object-oriented computing.

Parent topic: C

1.3.51 CORBA callback object

(CORBA) A CORBA object supplied as a parameter in a client application's invocation on a target object. The target object can make invocations on the callback object either during the execution of the target object or at some later time (even after the invocation on the target object has been completed). A callback object might be located inside or outside an Oracle Tuxedo domain.

See Also:

client application, CORBA object, and Oracle Tuxedo domain.

Parent topic: C

1.3.52 CORBA client stub

When using CORBA objects, a file created by the IDL compiler when you compile an application's OMG IDL statements. The client stub contains code that is generated during the client application build process. The client stub maps OMG IDL operation definitions for an object type to the methods in the server application that the Oracle Tuxedo domain calls when it invokes a request. The code is used to send the request to the CORBA server application.

When using OMG IDL, a C++ or Java programming language class created by the compiler and used transparently by the client ORB during object invocation. The remote object reference held by the client points to the client stub. This stub is specific to the IDL interface from which it was generated, and contains the information needed for the client to invoke a method on the CORBA object defined in the IDL interface.

Note:

metadata interface, OMG IDL, skeleton, and Oracle Tuxedo domain.

Parent topic: C

(CORBA) A client application that invokes operations defined in OMG IDL statements to talk to CORBA server applications. Relative to the CORBA domain to which the server applications belong, a client application is either native (that is, local) or remote. Remote and native client applications are the same. Their requests are handled differently and transparently, depending on whether or not the applications are collocated on a machine that is running in the CORBA domain. CORBA native client applications are always collocated on a machine in the CORBA domain.

Parent topic: C

1.3.57 CORBA object

(CORBA) An entity that complies with the CORBA standard upon which operations are performed. An object is defined by its interface.

See Also:

interface, object, and operation.

Parent topic: C

1.3.58 CORBA ORB

(CORBA) Any Object Request Broker (ORB) that complies with the CORBA standard. A CORBA ORB is a communications intermediary between client and server applications that are distributed across a network. The ORB used in Oracle Tuxedo applications is a CORBA ORB.

See Also:

conversation.

Parent topic: C

1.3.59 CORBA remote client application

(CORBA) A client application that invokes operations defined in OMG IDL statements to talk to remote CORBA server applications using IIOP. Remote and native client applications are the same. Their requests are handled differently and transparently, depending on whether or not the applications are collocated on a machine that is running in the CORBA domain. CORBA remote client applications are typically not located on a machine that is running in the CORBA domain.

Parent topic: C

1.3.60 CORBA server application

(CORBA) A program that performs a task requested of it by a client application and that is written to be used with the Oracle Tuxedo CORBA software.

See Also:

local factory.

Parent topic: C

1.3.61 CORBA TP framework

(CORBA) Run-time library of default implementations that the CORBA server application build procedure links to the server application executable image. The Transaction Processing (TP) Framework consists of a set of convenience functions that make it easy for you to write code that does the following:

Initializes the server application and executes startup and shutdown routines.
Ties the server application to CORBA domain resources.
Manages objects, bringing them into memory when needed, flushing them from memory when no longer needed, and managing reading and writing of data for persistent objects.
Performs object housekeeping.

See Also:

CORBA domain and CORBA server application.

Parent topic: C

1.3.62 CORBAfacilities

(CORBA) The adopted OMG Common Facilities. Common Facilities provide horizontal end-user-oriented frameworks that are applicable to most applications, and are defined in OMG IDL.

See Also:

OMG IDL.

The API for the Oracle TOP END system.

Parent topic: C

1.3.73 current context

(ATMI) Clients may initialize to multiple contexts; however, at any given time, in any particular thread, only one of these contexts may be the current context.

(CORBA) A special type of ORB object that is used to communicate between a user application and a specialized built-in service.

The sending and receiving of DDE messages between a client application and a server application.

Parent topic: D

1.4.14 deadlock

Unresolved contention for the use of a resource.
An error condition in which processing cannot continue because each of the two elements of the process is waiting for an action or a response from the other.

Parent topic: D

1.4.15 decoding

The conversion of encoded data back to the native format.

See Also:

encoding.

Parent topic: D

1.4.16 decryption

The process of restoring encrypted data to its original form.

Parent topic: D

1.4.17 decryption private key

An algorithm that reverses the work of the encryption algorithm.

Parent topic: D

1.4.18 default

The value assumed by a program if a value is not supplied by the user.

Parent topic: D

1.4.19 default context

An Oracle Tuxedo application association that is referenced by subsequent ATMI calls if tpsetctxt() is not called. The default context may differ from thread to thread. This term is often used interchangeably with application context.

See Also:

application context.

Parent topic: D

1.4.20 deferred synchronous communication

A form of asynchronous communication in which one piece of software can send a message to another piece of software, and then continue to work and retrieve the reply to the message at some later time.

Parent topic: D

1.4.21 deployment

The process of placing an application in a distributed environment and making the application available for use. Deployment can include such tasks as installation, configuration, and administration of various parts of the application.

Parent topic: D

1.4.22 DES

See Also:

Data Encryption Standard (DES).

Parent topic: D

1.4.23 design document

The document written by the system integrator that explains the overall design of the application or the framework to be built.

Parent topic: D

1.4.24 design pattern

A document that encapsulates, in a structured format, solutions to design problems. Design patterns are guides to good design practices.

Parent topic: D

1.4.25 desktop client

(CORBA) A CORBA client application that operates on a Microsoft desktop platform, such as Windows XP. Desktop client applications use the Component Object Model (COM) and communicate with the Oracle Tuxedo domain.

See Also:

Component Object Model (COM), conversation, and application.

Parent topic: D

A disk, disk drive, or group of disks or drives on an IBM machine.

Parent topic: D

1.4.32 Distinguished Bulletin Board Liaison (DBBL)

An Oracle Tuxedo administrative process that runs on the MASTER node of the application and communicates with BBLs to coordinate updates to the bulletin board.

Parent topic: D

1.4.33 Distinguished Name (DN)

(CORBA) A distinguished name (DN) is an entry in the Directory Information Tree (DIT) that uniquely identifies an object in an X.500 directory.

See Also:

The file that describes the relationship between the local domain (the domain in which the DMCONFIG file resides) and remote domains (any other domains). There is one DMCONFIG file per domain. The DMCONFIG file contains domain information for Oracle Tuxedo domains.

See Also:

Domains.

Parent topic: D

1.4.43 domain gateway

A highly asynchronous multitasking server provided by the Oracle Tuxedo system to process service requests to and from remote domains. The gateway makes access to services on a remote domain (and service requests from a remote domain) transparent to both the application programmer and the user.

Parent topic: D

1.4.44 domain gateway group

See Also:

gateway group.

Parent topic: D

1.4.45 Domains

An Oracle Tuxedo system component that provides a framework for interoperability among multiple domains. The framework consists of the following:

An extended client/server model that hides the heterogeneity of different computers and application programs, as well as the location of application programs.
A centralized administration system that allows application administrators to control all cooperating machines as a single application.

Parent topic: D

1.4.46 Domains-level failback

The restoration of message traffic to a primary remote domain. The TDomain gateway always tries to use the primary domain or the highest-level alternate remote domain defined for a service. When these domains become unavailable (due to circuit failure or other reasons), the gateway transfers message traffic to a lower-priority alternate remote domain, and periodically checks the availability of the primary remote domain and the highest-level alternate remote domain. When possible, the gateway restores message traffic to the primary remote domain or the highest-level remote domain.

See Also:

domain gateway and TDomain gateway.

Parent topic: D

1.4.47 Domains-level failover

The transfer of message traffic to an alternate remote domain when a primary remote domain fails.

See Also:

remote domain.

Parent topic: D

1.4.48 dotted-decimal notation

A convention for expressing IP addresses, consisting of a series of four decimal numbers (0-255), separated by periods. Example: 123.205.23.99.

Parent topic: D

1.4.49 DPI subagent

See Also:

Distributed Program Interface (DPI).

Parent topic: D

A type of argument for which a method can allocate or extend the existing storage.

The practice of buying and selling goods and services over the Internet.

Parent topic: E

1.5.2 encoding

The conversion of architecture-specific data into a format that can be transmitted between different architectures, such as XDR encoding.

Parent topic: E

1.5.3 encryption

The process of algorithmically scrambling data to prevent (or hinder) unauthorized disclosure, while still preserving access to the original data by authorized users. To read an encrypted file, a recipient must have access to a secret key or password that enables the recipient to decrypt it. Unencrypted data is called plaintext; encrypted data is referred to as ciphertext.

See Also:

ciphertext and plaintext.

Parent topic: E

1.5.4 encryption key pair

An encryption key pair consists of the public key used to encrypt information and a private key used to decipher the information.

Parent topic: E

1.5.5 environmental object

(CORBA) Any support object that provides independence from the underlying environment (for example, independence from the operating system). The Bootstrap object is an environmental object.

See Also:

(CORBA) An event that occurs during program execution that prevents the program from continuing normally (usually an error). C++ supports exceptions with the try, catch, and throw keywords. There are two categories of exceptions: system and user-defined.

In C++, system exceptions inherit from CORBA::System_Exception and user-defined exceptions inherit from CORBA::User_Exception.

Parent topic: E

1.5.12 extensibility

The ease with which a system adapts to meet new requirements. Extensibility also includes the ability to add or change a function or data (data type, file format, database schema, or information model) without:

Requiring changes to existing functions, data, and interfaces.
Introducing unwanted side effects, such as degradation of performance, reliability, maintainability, portability, and so on.

Parent topic: E

1.5.13 Exterior Gateway Protocol (EGP)

A protocol used to advertise the set of networks that can be reached within an autonomous system. EGP enables this information to be shared with other autonomous systems.

Parent topic: E

1.5.14 External Data Representation (XDR)

A canonical data format defined by Sun Microsystems and used to transfer data between heterogeneous hardware nodes.

Parent topic: E

1.6 F

This section describes glossary information about alphabet F.

Parent topic: Glossary

1.6.1 factory

(CORBA)

Any distributed CORBA object that returns an object reference to other distributed CORBA objects. A factory is located in a server application.
An interface used by a client to obtain an object reference to a CORBA object. Object references to factories are obtained by the client using an object reference to a Factory Finder interface. The Factory Finder interface is advertised by the system and is made available to the client as part of client bootstrap processing.

See Also:

CORBA object, object reference, and application.

Parent topic: F

1.6.2 factory-based routing

(CORBA) A feature of the Oracle Tuxedo software that permits the routing of requests on a CORBA object reference to a specific server group based on criteria supplied at the time the object reference is created by a factory.

See Also:

factoryand object reference.

Parent topic: F

1.6.3 factory finder

(CORBA) A CORBA object that locates the factories that an application needs. Both client applications and server applications can use a factory finder. A factory finder object provides an implementation of the CORBAservices COSLifeCycle.FactoryFinder interface, as well as the Oracle Tobj.FactoryFinder interface.

See Also:

factory, local factory, object, client application, and server application.

factory_finder.ini file

(CORBA) The FactoryFinder configuration file for domains. This file is parsed by the TMFFNAME service when it is started as a Master NameManager. The file contains information used by NameManagers to control the import and the export of object references for factory objects with other domains.

See Also:

domain, factory, and object reference.

Parent topic: F

1.6.4 failback

Restoration of message traffic to a higher-priority circuit. The BRIDGE process always tries to use the highest-priority circuit defined for the node; when traffic is flowing on a lower-priority circuit, whether due to circuit failure or just non-availability, the BRIDGE periodically checks higher-priority circuits to find one that is usable. When a higher priority circuit becomes available again, the data flow is returned to it. This mechanism is called failback.

Parent topic: F

1.6.5 failover

(ATMI and CORBA) Seamless transfer of message traffic to a lower-priority circuit on the occasion of the failure of a higher-priority circuit. Some operating system and hardware bundles transparently detect a problem on one network card and replace it with another. When this replacement is done quickly, application-level TCP virtual circuits have no indication that a fault has occurred.

In the Oracle Tuxedo system, data flows over the highest available priority circuit. If all network groups have the same priority, data travels over all networks simultaneously. If all circuits at the current priority fail, data is sent over the next lower priority circuit. This is called “failover.”

(Jolt) A failure prevention mechanism that works as follows. If the current Jolt Relay Adapter (JRAD) fails to respond to a connection request, the Jolt Relay (JRLY) is enabled to connect to another available JRAD. The Jolt client proves a list of JRLY addresses to which the JRAD attempts connection in a round-robin fashion.

Parent topic: F

1.6.6 field

In a record, a specified area used for a particular category of data.
An area within a segment that is the smallest referable unit of data.
Any designated portion of a segment.
A way of addressing a single item of data in a database table.
An area of a window where data displays.

Parent topic: F

1.6.7 Field Manipulation Language (FML)

(ATMI) A set of C language functions for defining and manipulating storage structures called field buffers. Cooperating processes can send and receive data in fielded buffers.

(Jolt) An interface for maintaining buffers with field/value pairs; specifically, the 16-bit version of this interface.

Parent topic: F

1.6.8 field table

(ATMI) A file that consists of FML field names and their identifiers. The field table enables users to refer to fields by logical names rather than by system field identifiers.

Parent topic: F

1.6.9 FML

See Also:

Field Manipulation Language (FML).

Parent topic: F

1.6.10 FML buffer

(ATMI) A buffer of self-describing data items accessed through the field manipulation language API.

Parent topic: F

1.6.11 foreign access path

A physical connection between a native Oracle Tuxedo system node and a foreign node. At least one gateway server must reside on the Oracle Tuxedo node.

Parent topic: F

1.6.12 foreign client application

(CORBA) A client application that is implemented on an ORB that is not a product of Oracle Systems, Inc. Although the client is implemented on a Microsoft product, the ORB is provided by Oracle Systems, Inc.

See Also:

(CORBA) A standard for communication between independent CORBA Object Request Broker (ORB) implementations. GIOP was developed by the Object Management Group (OMG). GIOP is an abstract protocol that forms the basis for specific protocols that map the GIOP standard to individual transport layers. For example, IIOP maps the GIOP standard to the TCP/IP transport layer.

See Also:

CORBA ORB and IIOP.

Parent topic: G

1.7.5 GIOP

See Also:

General Inter-ORB Protocol (GIOP).

Parent topic: G

1.7.6 global transaction

The Oracle Tuxedo system name for a transaction in which multiple servers or multiple resource manager interfaces are used and that is coordinated as an atomic unit of work. A global transaction may be composed of several local transactions, in each of which a single resource manager is accessed.

See Also:

resource manager (RM).

Parent topic: G

1.7.7 Global Transaction Identifier (GTRID)

A data structure, the value of which uniquely identifies a global transaction.

Parent topic: G

1.7.8 graphical user interface (GUI)

A high-level interface that uses windows and menus with graphic symbols instead of typed system commands to provide an interactive environment for a user. The Oracle Administration Console, available through the World Wide Web, enables an authorized user to configure and control an Oracle Tuxedo application.

Parent topic: G

1.7.9 group

A collection of servers or services on a machine, often associated with a resource manager. A group is an administrative unit used for booting, shutting down, and migrating servers and services.

See Also:

MIB group.

Parent topic: G

1.7.10 GUI

See Also:

graphical user interface (GUI).

Parent topic: G

1.8 H

This section describes glossary information about alphabet H.

Parent topic: Glossary

1.8.1 handler

A request that originates on a remote computer. Handlers are registered in the local Oracle Tuxedo bulletin board as client programs.

See Also:

See Also:

Implementation Configuration File (ICF).

Parent topic: I

1.9.2 ident string

See Also:

identification string.

Parent topic: I

1.9.3 identification string

Portions of a file that get expanded by RCS and SNMP Agent utilities to contain file and identification information. If compiled, these strings are placed into object file functions, where the information is made available.

Parent topic: I

IDL interface.

Parent topic: I

1.9.29 Interface Repository

(CORBA) An online database that contains the definitions of the interfaces that determine the CORBA contracts between client and server applications.

See Also:

conversation and IDL interface.

Parent topic: I

1.9.30 internationalization

A mechanism that allows customization of a system’s text messages and data formats into an application’s language and format of choice.

Parent topic: I

1.9.31 International Standards Organization (ISO)

An international organization whose membership includes standards and research groups from various nations. ISO establishes standards for computer network communications and many other technologies.

Parent topic: I

1.9.32 Internet

The world’s largest network, the Internet is based on the TCP/IP protocol suite and is universally accessible.

Parent topic: I

1.9.33 Internet Inter-ORB Protocol (IIOP)

See Also:

IIOP.

Parent topic: I

1.9.34 Internet Protocol Address (IP address)

A numeric value that uniquely identifies a node in a TCP/IP network. IP addresses are usually expressed in dotted decimal notation, a series of four decimal numbers (0-255), separated by periods. Example: 123.205.23.99.

Parent topic: I

1.9.35 interoperability

The ability to exchange requests between entities.

Parent topic: I

1.9.36 Interoperable Object Reference (IOR)

(CORBA) The entity that associates a collection of tagged profiles with object references. An ORB must create an IOR (from an object reference) whenever an object reference is passed across ORBs.

See Also:

CORBA ORB and object reference.

See Also:

Internet Protocol Address (IP address).

Parent topic: I

1.9.41 ISO

See Also:

International Standards Organization (ISO).

Parent topic: I

1.10 J

This section describes glossary information about alphabet J.

Parent topic: Glossary

1.10.1 JAR files (.jar)

(CORBA) Java ARchive files. A file format used for aggregating many files into one file.

See Also:

Java.

Parent topic: J

1.10.2 Java

An object-oriented programming language developed by Sun Microsystems, Inc. A write once, run anywhere programming language.

A subset of the Java Development Kit that is suitable for redistribution and sufficient for end users. The JRE consists of the Java Virtual Machine (JVM), the Java core classes, and supporting files.

Parent topic: J

1.10.7 JDK

See Also:

Java Development Kit (JDK).

Parent topic: J

1.10.8 joint client/server application

An application that executes code that acts as the starter for some business actions, and also executes method code for invocations on objects.

See Also:

(ATMI) Renamed Oracle Tuxedo-JSE Connectivity.

Parent topic: J

1.10.18 Jolt WAS for WebLogic

(ATMI) Renamed Oracle Tuxedo-WebLogic Connectivity.

Parent topic: J

An Oracle Tuxedo server that provides services to access the Jolt Repository storage. It provides support for the Jolt Runtime Environment and minimum editing and query functions.

Note:

Tuxedo server TMMETADATA replaces JREPSVR starting with version 12.2.2.

Parent topic: J

1.10.23 JRLY

See Also:

Jolt Relay (JRLY).

Parent topic: J

1.10.24 JSH

See Also:

Jolt Server Handler (JSH).

Parent topic: J

1.10.25 JSL

See Also:

See Also:

Local Area Network (LAN).

Parent topic: L

(ATMI) An existing application, usually based on a relatively old release of the Oracle Tuxedo system that must be modified or wrapped before it can be used by an Oracle Tuxedo domain.

See Also:

domain, Workstation Handler (WSH), and wrapper.

Parent topic: L

1.12.6 Life Cycle Service

See Also:

CORBAservices Life Cycle Service.

Parent topic: L

1.12.7 Lightweight Directory Access Protocol

A set of protocols for accessing information directories. These directories can be physically distributed across multiple systems for access by many applications within an enterprise. LDAP is based on the standards contained within the X.500 standard, but is significantly simpler. And unlike X.500, LDAP supports TCP/IP, which is necessary for any type of Internet access. LDAP is an ideal way to publish certificates because it is closely coupled with the X.509 standard for certificates.

See Also:

certificate and X.509.

Parent topic: L

1.12.8 link-level encryption (LLE)

The encryption of messages moving over network links. Encryption is performed just before data is transmitted on the network, and decryption is performed just after data is received.

LLE operates over Workstation client, domain gateway, bridge, and administrative network links. It employs a symmetric key encryption technique (specifically, RC4), which uses the same key for encryption and decryption.

Parent topic: L

1.12.9 link-level failover in Domains

Link-level failover is a mechanism that ensures that an alternate network link becomes active when a primary link fails.

Parent topic: L

1.12.10 listener

See Also:

Workstation Listener (WSL).

Parent topic: L

In data communication, pertaining to devices that are accessed directly (that is, without use of a telecommunication line).

Parent topic: L

1.12.15 local application names

The DDE Listener uses the application name supplied in the DDE Initiate message to determine if the client is looking for a local or a remote DDE application. The syntax for a local DDE application includes only the name of the application. For example, if the client is looking for Microsoft Excel on the local computer, the application name would be EXCEL.

Parent topic: L

1.12.16 Local Area Network (LAN)

A high-speed network that spans a limited distance, such as a building or a cluster of buildings. LANs can be connected to wide area networks (WANs) with bridge devices.

Parent topic: L

1.12.17 local domain

View of an application (that is, a subset of the application’s services) that is available to other domains. Because a local domain is always represented by a domain gateway group, the terms are used interchangeably.

Parent topic: L

1.12.18 local factory

(CORBA) A factory object that exists in the local domain that is made available to remote domains through an Oracle Tuxedo factory finder.

See Also:

1.13.3 managed resource

The physical resource whose attributes are represented by managed objects in a management information base. A managed resource can be a software entity such as an application or queue, or a hardware device, such as an interface card or hub.

Parent topic: M

1.13.4 management framework

A system that provides a unified view of hardware and software resources on distributed systems and enterprise-wide networks to help network or system administrators to manage and control these resources.

Parent topic: M

1.13.5 Management Information Base (MIB)

(ATMI and CORBA) An Oracle Tuxedo system component that provides a complete definition of the classes and their attributes that make up the Oracle Tuxedo system. The Oracle Tuxedo System Management Information Base comprises a generic MIB and a specific MIB for each major component, such as Domains and Workstation. Configuration and administration of the Oracle Tuxedo system can be done programmatically by using the ATMI to set or change the value of an attribute.

See Also:

A formula for sending data and values across applications. Messages may contain statistical or status information about application processes or instructions for the recipient. They consist of a header, containing message ID data, and a body containing user-defined information.

See Also:

(CORBA) In object-oriented programming, a programmed procedure that is defined as part of a class and included in any object of that class. A class (and thus an object) can have more than one method. A method in an object can have access only to the data known to that object, which ensures data integrity among the set of objects in an application. A method can be reused in multiple objects.

See Also:

Callbacks Wrapper object and operation.

Parent topic: M

1.13.21 MIB

See Also:

Parent topic: M

1.13.39 MVS

See Also:

(CORBA) An object that contains a set of name associations in which each name is unique.

See Also:

CORBAservices Naming Service.

Parent topic: N

1.14.6 Naming Service

See Also:

CORBAservices Naming Service.

Parent topic: N

A machine in an Oracle Tuxedo configuration that contains the full complement of Oracle Tuxedo software, and that has access to the same bulletin board as all other native nodes in the configuration (that is, it is part of the administrative domain of the application).

Parent topic: N

1.14.11 network

An interconnected group of nodes.
The assembly of equipment through which connections are made between data stations.
The communication path used to communicate with a server.

See Also:

CORBA object and Remote Method Invocation (RMI).

Parent topic: O

1.15.2 object activation

(CORBA) The process of making a CORBA object ready to accept invocations from client applications. The object needs to have its methods and state available in memory.

When using CORBA objects, the association of an object ID to a servant in the Active Object Map of a POA and the TP Framework. When a CORBA object is activated, the TP Framework reloads the state of the CORBA object from persistent storage and makes the object available to fulfill requests from client applications.

Parent topic: O

(CORBA) An international organization that establishes industry guidelines and object management specifications to provide a common framework for object-oriented application development. The OMG Common Object Request Broker Architecture specifies the CORBA object model.

Parent topic: O

1.15.12 object model

(CORBA) The model that reflects as objects the overall design of an application or system.

Parent topic: O

1.15.13 object reference

(CORBA) An identifier that uniquely specifies an instance of an object within a distributed ORB system.

Parent topic: O

1.15.14 Object Request Broker

See Also:

CORBA ORB.

Parent topic: O

1.15.15 object system

(CORBA) A software system that stores, manipulates, and uses a collection of objects according to a set of system-specific standards. An object system specifies how information is exchanged between objects, and how objects are implemented in accordance to an object model, such as CORBA COM, EJB, and RMI.

See Also:

(CORBA) Object Management Group Interface Definition Language. A definition language specified by the OMG for describing an object's interface (that is, the characteristics and behavior of an object, including the operations that can be performed on the object).

1.15.22 online transaction processing (OLTP)

A form of data processing in which users at terminals or workstations send messages to application programs, which update databases in real time.
The execution of units of work in a performance-critical environment that appears to the user as immediate; real-time; usually having internal recoverability, history-keeping, and consistency-assurance features.

See Also:

object.

Parent topic: O

1.15.29 ORB

See Also:

CORBA ORB.

Parent topic: O

1.15.30 ORBMain module

(CORBA) The main procedure of the Oracle Tuxedo server application process. The Oracle Tuxedo software provides the ORBMain module. You do not modify this module. The server application build procedure automatically builds the ORBMain module into the server application process. The ORBMain module is provided by the buildobjserver command for servers using the TP Framework. Note that joint client/server applications must provide their own main procedure and must use the -P switch on the buildobjclient command.

Parent topic: O

See client.

Parent topic: O

1.15.38 Oracle Tuxedo domain

An Oracle Tuxedo domain consists of an Oracle Tuxedo application running one or more business applications. A single domain is defined in one configuration file and is administered as a single entity. A domain can be connected to other Oracle Tuxedo domains through the Domains feature.

See Also:

domain, TUXCONFIG file, and UBBCONFIG file.

Parent topic: O

1.15.39 Oracle Tuxedo Domains

An Oracle Tuxedo component that extends the Oracle Tuxedo system client/server model to provide transaction interoperability across TP domains. This extension preserves the client/server model and the ATMI interface by making access to services on a remote domain (and service requests from a remote domain) transparent to both the application programmer and user.

Parent topic: O

1.15.40 Oracle Tuxedo server

A program that performs a task requested of it by a client application.

Parent topic: O

1.15.46 OTS

Note:

CORBAservices Object Transaction Service (OTS).

Parent topic: O

1.15.47 outbound IIOP

(CORBA) A feature of the Oracle Tuxedo software that supports client callbacks. Outbound IIOP adds the outbound half-gateway to the ISL/ISH. The Oracle Tuxedo system supports the following three types of outbound IIOP:

asymmetric outbound IIOP: Outbound IIOP, via a second connection, to joint client/server applications that are not connected to an ISH. This feature of the Oracle Tuxedo software is supported for GIOP 1.0, GIOP 1.1, and GIOP 1.2 client applications, server applications, and joint client/server applications.
bidirectional outbound IIOP: Outbound IIOP to a remote joint client/server application that is connected to an ISH. The outbound callback reuses the same connection initially used by the joint client/server for inbound calls. This feature is supported only for Oracle Tuxedo C++ GIOP 1.2 client applications, server applications, and joint client/server applications.
dual-paired connections outbound IIOP: Outbound IIOP to a remote joint client/server application that is connected to an ISH. Unlike bidirectional outbound IIOP, the outbound callback uses a second connection that is separate from the connection initially used by the joint client/server application for inbound calls. This feature of the Oracle Tuxedo software is supported for GIOP 1.0, GIOP 1.1, and GIOP 1.2 client applications, server applications, and joint client/server applications.

See Also:

process ID (PID).

Parent topic: P

1.16.7 PIDL (Pseudo-IDL)

(CORBA) The interface definition language for describing a CORBA pseudo-object. Each language mapping, including the mapping from IDL to the C++ or Java programming language, describes how pseudo-objects are mapped to language-specific constructs. PIDL mappings may or may not follow the rules that apply to mapping regular CORBA objects.

Parent topic: P

1.16.8 PKCS-7

See Also:

Public-Key Cryptography Standard 7 (PKCS-7).

Parent topic: P

1.16.9 plaintext

In cryptography, text that is not encrypted.

Parent topic: P

(ATMI) For security purposes, an authenticated user.

(CORBA) A user or programmatic entity with the ability to use the resources of a system.

Parent topic: P

1.16.21 Principal Authenticator object

(CORBA) The object that is visible to the application responsible for the creation of Credentials for a given principal. A user or principal that requires authentication, but has not been authenticated, uses the Principal Authenticator object.

See Also:

Parent topic: P

1.16.27 profile

A set of information about a client or a user. The profile provides information the server might require to recognize the client or the user.

Parent topic: P

1.16.28 protocol

A set of rules that govern the format and timing of messages sent and received over a communication link. TCP/IP is an example of a network protocol.
The set of rules followed by two systems to communicate and exchange information.

Parent topic: P

1.16.29 provider

The communications product supplying networking facilities through level 4 of the OSI communications protocol.

Parent topic: P

1.16.30 Pseudo-IDL

See Also:

PIDL (Pseudo-IDL).

Parent topic: P

1.16.31 pseudo-object

(CORBA) An object similar to a CORBA object in that it is described in IDL however, unlike a CORBA object, it cannot be passed using its object reference, nor can it be narrowed or stringified.

The DII interfaces are examples of pseudo-objects, although the DII interfaces are implemented as libraries and are more accurately described in OMG specifications as pseudo-objects with IDL interfaces. The IDL for pseudo-objects is called PIDL, indicating that a pseudo-object is being defined.

See Also:

The act of pushing a structured event into the event channel to make the event available to subscribers.

Parent topic: P

1.17 Q

This section describes glossary information about alphabet Q.

queue

(ATMI) View of an application that is accessed through a local domain gateway group.

Parent topic: R

1.18.15 remote factory

(CORBA) A factory object that exists in a remote domain that is made available to the application through an Oracle Tuxedo factory finder.

See Also:

factory, factory finder, local factory, and CORBA domain.

Parent topic: R

1.18.16 remote file sharing (RFS)

A UNIX system capability that provides access to remote files over a network.

Parent topic: R

1.18.17 remote gateway

The functionality of a specific gateway group within a remote Oracle Tuxedo application.

Parent topic: R

1.18.18 remote joint client/server applications

(CORBA) A CORBA joint client/server application that is located outside an Oracle Tuxedo domain. The remote joint client/server application does not use the Oracle Tuxedo TP Framework and requires more direct interaction between the client application and the ORB. Remote joint client/server applications are built with the buildobjclient command or with the Java client application commands.

See Also:

Parent topic: R

1.18.26 requester

A process that receives messages from clients, converts these messages to a common internal form, determines the appropriate server or servers for the transaction request, and forwards the request to a server.
A generic term for a client or server that is acting as a client.

1.18.34 resource manager instance

A particular instance or occurrence of a resource manager. There may be many occurrences or instances of the same or different resource managers within a global transaction, each managing different data. Each resource manager instance is considered to be autonomous, in full control of local access (for both local and global transactions), administration, and so forth.

Parent topic: R

To terminate a transaction in such a way that all resources updated within a transaction revert to their original (that is, pretransactional) state.

Parent topic: R

1.18.39 rollback

The event that ends a transaction and nullifies or undoes all changes to resources that were specified during that transaction.

Parent topic: R

1.18.40 RPC

See Also:

1.19.4 scope

(ATMI) To use a class to enforce a particular use for an application.

Parent topic: S

1.19.5 Secure Sockets Layer (SSL)

A transport-level technology developed by Netscape for authentication and data encryption between two communicating applications, based on the use of public key technology.

See Also:

authentication.

Parent topic: S

1.19.6 security

The protection of information from unauthorized modification or disclosure and the protection of resources from unauthorized use.

Parent topic: S

1.19.7 SecurityCurrent

(CORBA) The object that provides access to the security features of the system.

Note:

1.19.13 servant factory

(CORBA) A feature of Oracle Tuxedo Java server applications for automatically instantiating servants. Unlike Oracle Tuxedo C++ servers, Java servers do not need to provide a callback for instantiating servants.

Parent topic: S

1.19.14 servant pooling

(CORBA) A feature of the Oracle Tuxedo (C++) software that gives your Oracle Tuxedo server application the opportunity to keep a servant in memory after the servant’s association with a specific object ID has been broken.

See Also:

object identifier (OID) and servant.

Parent topic: S

1.19.15 server

A software program that provides a service in a client/server architecture by performing the following steps:

Receives a request from a client (or another serving playing the role of a client) for a particular service.
Dispatches a service routine to fulfill the request.
Sends a response to the original requester, indicating whether the requested service has been performed successfully and conveying the results of the service that has been performed.

See Also:

client.

Parent topic: S

1.19.16 server abstraction

Applications combine their service routines with the Oracle Tuxedo system main() in building a server process. The Oracle Tuxedo system’s main() provides server initialization and termination, and receives incoming requests and dispatches them to service routines. All of this processing is transparent to applications.

Parent topic: S

1.19.17 server application

(CORBA) A program, written for use with the Oracle Tuxedo software, that performs a task requested of it by a client application.

See Also:

local factory.

Parent topic: S

1.19.18 Server Description File

(CORBA) The file within which you assign the default CORBA activation and transaction policies for the interfaces implemented in your Java server application. This XML file also contains a server declaration, which includes the name of the server implementation class and the name of the server descriptor file. You can also identify the Java class files that comprise the server application’s Java ARchive (.jar) file. See JAR files (.jar).

Parent topic: S

1.19.19 server group

See Also:

group.

Parent topic: S

1.19.20 server ID

An identifier for a single server. No two servers can operate at the same time with the same server ID.

Parent topic: S

1.19.21 Server object

(CORBA) The object that performs server application initialization functions, creates one or more servants, and performs server application shutdown and cleanup procedures.

See Also:

A Java replacement for CGI. Servlets are Java classes that are invoked by a Web server in response to HTTP requests. Servlets generate Hypertext Markup Language (HTML) as their output.

1.19.43 SNMP agent

An agent that uses the SNMP protocol to exchange data with a system manager.

Parent topic: S

1.19.44 socket

An endpoint of communication to which a name may be bound. The socket interface is a network access method supported by the Oracle Tuxedo system. The logical end point of a TCP/IP connection. An application accesses a TCP/IP connection through a socket.

Parent topic: S

Structured Query Language. A non-procedural language for defining and accessing relational databases. SQL has become the industry standard database language.

Parent topic: S

1.19.49 standard MIB

A MIB developed as a standard by the Internet community. Examples are MIB I and MIB II.

Parent topic: S

1.19.50 StarLAN

An AT&T LAN product.

Parent topic: S

1.19.51 state

(ATMI) The situation of a conversation from the point of view of one of the participating transactions. The conversation state determines the commands that a transaction can validly issue. The state of each transaction changes dynamically in the course of conversation.

(CORBA) An object ID represented as a string.

See Also:

object identifier (OID).

Parent topic: S

1.19.58 Structured Event

(CORBA) A COS Structured Event as defined by the CORBAservices Notification Service. A Structured Event contains a Fixed header, Variable header, Filterable body parts, and a Remaining body.

Parent topic: S

1.19.59 Structured Query Language

See Also:

1.19.65 synchronization

A coordinated commitment control process between communicating transactions that ensures that all logically related updates to recoverable resources are completed or that all are backed out.

Parent topic: S

1.19.66 synchronous

Pertaining to an event that happens, exists, or arises at precisely the same time as another event.
Pertaining to an operation that occurs regularly or predictably with regard to the occurrence of a specified event in another process; for example, the calling of an input/output routine that receives control at a precoded location in a program.

Parent topic: S

1.19.67 synchronous communication

A method of transmitting data using a timing signal. With this form of communication, when one piece of software sends a message to another piece of software, the originating software must wait until the service provider completes the request before it can continue.

Parent topic: S

1.19.68 synchronous process

A process that cannot be executed independently of other processes. When a request is processed synchronously, the client must wait until the service provider completes the request before continuing.

Parent topic: S

1.19.69 system

Oracle TOP END term that is equivalent to Tuxedo domain.

See Also:

Tuxedo domain.

Parent topic: S

1.19.70 system administration

The preparation of an instance of a system for use in a particular setting or installation.
Changing the system as the installation changes. This term is often used in a way that includes system operations as well.

Parent topic: S

1.19.71 system administrator

See Also:

administrator.

Parent topic: S

1.19.72 system manager

The part of a network management system that requests data from an agent and takes actions based on that data.

Parent topic: S

1.19.73 system operations

Tasks that need to be performed regularly for a system. Examples are backing up and restoring data and logs, monitoring the system for error conditions, and so forth.

Parent topic: S

1.20 T

This section describes glossary information about alphabet T.

An operating system capability that allows a single process to be divided into multiple entities, each of which executes independently while sharing a common address space.

Parent topic: T

1.20.7 thread-per-object concurrency model

(CORBA) A threading model supported by a multithreaded CORBA server application. In the thread-per-object concurrency model, each active object in the server process is associated with a single thread at any one time. Each request for an object establishes an association between a dispatch thread and the object.

See Also:

multithreaded CORBA server application.

Parent topic: T

1.20.8 thread-per-request concurrency model

(CORBA) A server application provided with Oracle Tuxedo software that runs the FactoryFinder and supporting NameManager services that maintain a mapping of application-supplied names to object references.

See Also:

factory finder and object reference.

Parent topic: T

1.20.17 TMIFRSVR

(CORBA) A server application provided with Oracle Tuxedo software for accessing the Interface Repository. The API is a subset of the Interface Repository API defined by CORBA. For a description of the Interface Repository API, see the C++ Programming Reference.

See Also:

application programming interface (API), conversation, and Interface Repository.

Parent topic: T

1.20.18 TMS

See Also:

Transaction Manager Server (TMS).

Parent topic: T

A complete unit of work that transforms a database from one consistent state to another. In DTP, a transaction can include multiple units of work performed on one or more systems.
A logical construct through which applications perform work on shared resources (for example, databases). The work done on behalf of the transaction conforms to the four ACID properties: atomicity, consistency, isolation, and durability.

See Also:

distributed transaction processing (DTP).

Parent topic: T

1.20.26 transaction coordinator

A system software component that provides the infrastructure that guarantees the integrity and consistency of an operation and the data involved in a transaction.

See Also:

transaction manager (TM).

Parent topic: T

1.20.27 TransactionCurrent

(CORBA) An object that is used to manage transactions. The TransactionCurrent object supports all of the methods of the Current object in the CosTransactions module. In addition, the TransactionCurrent object supports APIs to open and close the resource manager.

TransactionCurrent defines the methods that allow a client of the CORBAservices Object Transaction Service (OTS) to explicitly manage the association between threads and transactions. This object also defines methods that simplify the use of the OTS for most applications.

Parent topic: T

1.20.28 transaction log (TLOG)

The Oracle Tuxedo system log that keeps track of global transactions.

Parent topic: T

1.20.29 transaction manager (TM)

A system software component that manages global transactions on behalf of application programs. A transaction manager coordinates commands from application programs and communication resource managers to start and complete global transactions by communicating with all resource managers that are participating in those transactions. When resource managers fail during global transactions, transaction managers help resource managers decide whether to commit or roll back pending global transactions.

See Also:

transaction coordinator.

Parent topic: T

1.20.30 transaction policy

(CORBA) The policy that determines the TP Framework’s or EJB container’s interaction between the client request (which may be associated with a transaction) and the servant’s transaction context.

Parent topic: T

1.20.31 Transaction Manager Server (TMS)

An Oracle Tuxedo system server process that manages the two-phase commit protocol and recovery for global transactions.

Parent topic: T

1.20.32 transaction processing (TP)

Transaction processing consists of a set of convenient functions that make it easy for you to write code that does the following:

Initialize the server application and execute startup and shutdown routines.
Tie the server application to Oracle Tuxedo domain resources.
Perform housekeeping functions.

Parent topic: T

1.20.33 transaction processing monitor (TP monitor)

A class of products that provide a transaction execution environment on top of conventional operating systems.

Parent topic: T

1.20.34 transaction processing protocols (TP protocols)

A set of standard protocols by which transaction processing managers on heterogeneous systems interoperate.

Parent topic: T

1.20.35 transaction processing service user title (TPSUT)

A value that is used to identify OSI TP endpoints that exist within one application entity.

Parent topic: T

1.20.36 Transaction Service

See Also:

CORBAservices Object Transaction Service (OTS).

Parent topic: T

1.20.37 transactions per second (TPS)

A throughput rating used in conjunction with the standard transactions defined by TPC. Often the rating implies the maximum number of transactions that can be processed by the system in which 90% of the transaction’s response times are less than two seconds.

Parent topic: T

1.20.38 transient object

(CORBA) An object that exists only for the lifetime of the process within which it is created.

See Also:

1.20.44 trap

An SNMP data packet that contains information about an error that occurred with a managed object. Traps are unsolicited event notifications, that is, notifications generated by an agent on its own initiative.

Parent topic: T

1.20.45 TUXCONFIG file

The binary version of the configuration file for an Oracle Tuxedo application. This file is accessed by all Oracle Tuxedo processes for all configuration information.

See Also:

application, client, server, and UBBCONFIG file.

Parent topic: T

1.20.46 Tuxedo

See Also:

Oracle Tuxedo system.

Parent topic: T

1.20.47 Tuxedo domain

See Also:

domain.

Parent topic: T

1.20.48 Tuxedo MIB

A Tuxedo internal data structure for resources. Specifically, it is an Oracle Tuxedo or WebLogic Enterprise framework component that provides a complete definition of the object classes and their attributes that together constitute the Tuxedo or WebLogic Enterprise framework. The total Tuxedo system management information base is organized into a generic MIB and component-specific MIBs for each major component. Configuration and administration of the Tuxedo or WLE framework can be done programmatically.

Parent topic: T

1.20.49 Tuxedo remote client application

See Also:

Parent topic: T

1.21 U

This section describes glossary information about alphabet U.

Parent topic: Glossary

1.21.1 UBBCONFIG file

The ASCII version of the configuration file for an Oracle Tuxedo application. A binary version, referred to in Oracle Tuxedo documentation as the TUXCONFIG file, is generated from the UBBCONFIG file.

See Also:

application, client, server, and TUXCONFIG file.

Parent topic: U

1.21.2 UDP

See Also:

user datagram protocol (UDP).

Parent topic: U

1.21.3 unadvertised

A service is unadvertised when there is no service table entry for it in the Oracle Tuxedo bulletin board.

Parent topic: U

1.21.4 uniprocessor

A computer that has only one CPU.

See Also:

multiprocessor.

1.23 W

This section describes glossary information about alphabet W.

Parent topic: Glossary

1.23.1 WAN

See Also:

Wide Area Network (WAN).

Parent topic: W

1.23.2 Web GUI

See Also:

See Also:

WebLogic Server.

Parent topic: W

1.23.9 worker thread

(CORBA) A thread that is scheduled to execute a request from a client application. The Oracle Tuxedo Java software uses a thread pooling model, where a pool of available worker threads is managed by the software. When the Oracle Tuxedo Java software receives a request from a client application, the software schedules, from the thread pool, an available worker thread to execute the request. When the request is complete, the worker thread returns to the thread pool. A worker thread can serve only one request at a time.

See Also:

thread.

Parent topic: W

1.23.10 Workstation

The component of the Oracle Tuxedo system that allows application clients to be located on sites on which no server-side components of the Oracle Tuxedo system are installed. A Workstation client does not support an administration server, an application server, or a bulletin board. All communication between such a client and the rest of the application takes place over a network.

See Also:

tie class.

Parent topic: W

1.24 X

This section describes glossary information about alphabet X.

Parent topic: Glossary

1.24.1 X.509

A standard that specifies the format of certificates, which provide a way to securely associate a name to a public key, providing strong authentication.

See Also:

See Also:

External Data Representation (XDR).

Parent topic: X

1.24.8 XML

eXtensible Markup Language. A language developed by the World Wide Web Consortium (W3C) and organized by Sun Microsystems, Inc. Used in specifying the Server Descriptor file and the EJB deployment descriptor.

Parent topic: X

1.24.9 X_OCTET buffer

(ATMI) An array of bytes whose structure is defined by an application. X_OCTET is one of three buffers that are defined in the X/Open XATMI standard. It is equivalent to the Oracle Tuxedo CARRAY buffer.

Parent topic: X

1.24.10 X/Open

The X/Open Company, Ltd., an international private consortium of vendors and users working to establish standards for open systems. Oracle Tuxedo products are designed to implement X/Open standards for distributed transaction processing.

Parent topic: X

1.24.11 X/Open Distributed Transaction Processing (DTP) model

The distributed transaction processing model specified in standards developed by the X/Open Company, Ltd. The Oracle Tuxedo architecture is based on these standards. The model defines four components of a DTP system:

Application programs (APs) define the transaction boundaries and perform the actions that make up the transaction (typically database updates).
Resource managers (RMs), such as database management systems, provide access to shared resources.
Communication resource managers (CRMs) allow application programs to communicate with each other.
Transaction managers (TMs) assign unique identifiers (XIDs) to transactions, monitor the progress of transactions, and handle transaction completion or recovery.

Parent topic: X

1.25 Y

Note:

(No terms starting with the letter "Y")

Parent topic: Glossary

1.26 Z

Note:

(No terms starting with the letter "Z")

Parent topic: Glossary