BEA Tuxedo Architecture Overview


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Using the BEA Tuxedo TOP END Domain Gateway \| Local Topics \| Previous Topic \| Next Topic \| Contents

The BEA Tuxedo system uses the concept of a domain to define a collection of nodes (or machines) involved in an administratively autonomous application. A system administrator uses two files, UBBCONFIG and DMCONFIG, to configure a BEA Tuxedo domain.

A distributed-domain configuration consists of one or more business applications running on multiple machines. Although it contains multiple machines, this type of configuration is considered a single domain because it is administered centrally as a single entity. The following diagram shows the basic parts of a configuration distributed across multiple machines.

BEA Tuxedo Distributed Configuration

The primary components of a distributed configuration are:

Client applications—executable programs that may request services through the BEA Tuxedo system.
Server applications—executable programs that offer named services through the BEA Tuxedo system.
ATMI—the application programming interface (API) for the BEA Tuxedo system.
BEA Tuxedo Services—services and/or capabilities common to the BEA Tuxedo system infrastructure for developing and administering applications. The application processing services available to developers include: transactions, messaging paradigms, type validation, load balancing, data-dependent routing, service prioritization, data encoding, marshalling, compression, and reliable queuing. The administrative services include: distributed transaction processing, security management, service naming, distributed application administration, centralized application configuration, dynamic reconfiguration, and domains partitioning.
Bulletin Board—a shared memory segment that holds configuration and dynamic information for the system. It is available to all BEA Tuxedo processes.
Bulletin Board Liaison (BBL)—a BEA Tuxedo administrative process that monitors the data stored in the bulletin board and any changes made to it.
Distinguished Bulletin Board Liaison (DBBL)—a process dedicated to making sure that the BBL server on each machine is alive and functioning correctly. This server runs on the master machine of a domain and communicates directly with all administration facilities.
Bridges—BEA Tuxedo supplied servers that send and receive service requests between machines, and route them to local servers.

A multiple-domain configuration consists of two or more domains that communicate with each other through a gateway process in each domain. This gateway process provides bidirectional transaction control, and administrative tools that allow the configuration of the information required for interoperability of the local application with other domains. This configuration information includes the identification of a set of exported services, imported services, addressing, and access control. For an illustration of a multiple-domain configuration, see What Is a Multiple-domain Configuration? in Introducing BEA Tuxedo ATMI.