What Is a Single-machine Configuration


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| Getting Started \| Topic List \| Previous \| Next \| Contents

Introducing the BEA Tuxedo System

A single-machine configuration consists of one or more local or remote clients that communicate with one or more servers residing on a single machine running one or more business applications. Even though it may include multiple applications, this type of configuration is considered a single domain because it is administered as a single entity. All the managed elements (services, servers, and so on) of all the applications in this configuration are defined in and controlled from one BEA Tuxedo configuration file. The basic parts of a single-machine configuration when installed and running on a single machine are illustrated in the following diagram.

A Single-machine BEA Tuxedo Configuration

Parts of a Single-machine Configuration

Single-machine Part
Description

Bulletin Board (BB)

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 both the data stored in the bulletin board (including any changes made to it) and all application programs.

Clients

Executable programs that periodically request services through the BEA Tuxedo system. (Client programs are normally written by customers.)

Message queues

Communication between clients and servers is performed through operating-system supported, memory-based message queues.

Messaging paradigms

Different models of transferring messages between a client and a server. Examples include request/response mode, conversational mode, events, and unsolicited communication.

Servers

Executable programs that offer named services through the BEA Tuxedo system. (Server programs are normally written by customers.)

Workstation Handler (WSH)

A multi-contexted gateway process on a server that manages service requests from Workstation clients (that is, client processes running on remote sites).

Workstation Listener (WSL)

A server process running on an application site that listens for and distributes connections from Workstation clients (client process running on a remote site).

ULOG (User Log)

A file in which error messages are stored.

Single-machine Part	Description
Bulletin Board (BB)	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 both the data stored in the bulletin board (including any changes made to it) and all application programs.
Clients	Executable programs that periodically request services through the BEA Tuxedo system. (Client programs are normally written by customers.)
Message queues	Communication between clients and servers is performed through operating-system supported, memory-based message queues.
Messaging paradigms	Different models of transferring messages between a client and a server. Examples include request/response mode, conversational mode, events, and unsolicited communication.
Servers	Executable programs that offer named services through the BEA Tuxedo system. (Server programs are normally written by customers.)
Workstation Handler (WSH)	A multi-contexted gateway process on a server that manages service requests from Workstation clients (that is, client processes running on remote sites).
Workstation Listener (WSL)	A server process running on an application site that listens for and distributes connections from Workstation clients (client process running on a remote site).
ULOG (User Log)	A file in which error messages are stored.