What Is a Multiple-domain Configuration?


	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 \| Introducing BEA Tuxedo ATMI \| Local Topics \| Previous Topic \| Next Topic \| Contents

A multiple-domain configuration consists of two or more domains that communicate with each other. Each domain may be either a single-machine configuration or a multiple-machine configuration. Inter-domain communication is achieved through a highly asynchronous multitasking gateway that processes outgoing and incoming service requests to or from all domains. Multiple BEA Tuxedo domains can be connected, allowing clients in one domain transparent access to services physically located in remote domains. Each domain can share services and data, but is administered separately.

The BEA Tuxedo system provides different types of gateways to accommodate various network transport protocols. Following are the different types of Domains gateways:

The BEA Tuxedo Domains (TDomains) gateway provides interoperability between two or more BEA Tuxedo applications through a specially designed TP protocol that flows over network transport protocols such as TCP/IP.
The BEA eLink OSI TP gateways provides interoperability between BEA Tuxedo applications and other transaction processing applications that use the OSI TP standard. OSI TP is a protocol for distributed transaction processing defined by the International Standards Organization (ISO).
The BEA eLink Adadpter for Mainframe SNA gateway provides interoperability between clients and servers in a BEA Tuxedo domain and clients and servers in an MVS/CICS or MVS/IMS environment in remote SNA domains. It also connects a local BEA Tuxedo domain to multiple SNA networks.
The BEA eLink Adapter for Mainframe TCP for CICS is a gateway connectivity feature that makes it possible for non-transactional tasks within BEA Tuxedo regions to access services provided by CICS application programs and vice-versa. It enables a BEA Tuxedo domain to communicate via the TCP/IP network transport protocol to a CICS environment.
The BEA eLink Adapter for Mainframe TCP for IMS is a gateway connectivity feature that provides transparent communications between client and server transactions in an IMS system and a BEA Tuxedo domain, a CICS system, or another IMS system.
The TOP END Domain Gateway (TEDG) provides interoperability between BEA TOP END systems and BEA Tuxedo domains.

The basic parts of a multiple-domain configuration are illustrated in the following diagram.

Multiple-domain Configuration

Parts of a Multiple-domain Configuration

Multiple-domain Part

Description

Bridges

BEA Tuxedo system-supplied servers within a domain that send and receive service requests between machines, and route requests to local servers (literally, to local server queues).

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.)

Distinguished Bulletin Board Liaison (DBBL)

Ensures that the BBL servers on each machine are alive and functioning correctly. This server runs on the Master machine of an application and communicates directly with any administration facility.

Domains tools: DMADM, GWADM, GWTDOMAIN, dmloadcf, dmunloadcf, and DMCONFIG

DMADM—the Domains administrative server.
GWADM—the gateway group administrative server that registers with the DMADM server to obtain configuration information used by the gateway group.
GWTDOMAIN—the gateway process that provides connectivity to remote gateway processes (for TDomains).
dmloadcf—translates the DMCONFIG file to a binary BDMCONFIG configuration file.
dmunloadcf—translates the BDMCONFIG configuration. file from the binary representation into ASCII.
DMCONFIG—the Domains configuration file.

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 processes running on remote sites).

ULOG (User Log)

A file in which error messages are stored.

Multiple-domain Part	Description
Bridges	BEA Tuxedo system-supplied servers within a domain that send and receive service requests between machines, and route requests to local servers (literally, to local server queues).
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.)
Distinguished Bulletin Board Liaison (DBBL)	Ensures that the BBL servers on each machine are alive and functioning correctly. This server runs on the Master machine of an application and communicates directly with any administration facility.
Domains tools: DMADM, GWADM, GWTDOMAIN, dmloadcf, dmunloadcf, and DMCONFIG	DMADM—the Domains administrative server. GWADM—the gateway group administrative server that registers with the DMADM server to obtain configuration information used by the gateway group. GWTDOMAIN—the gateway process that provides connectivity to remote gateway processes (for TDomains). dmloadcf—translates the DMCONFIG file to a binary BDMCONFIG configuration file. dmunloadcf—translates the BDMCONFIG configuration. file from the binary representation into ASCII. DMCONFIG—the Domains configuration file.
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 processes running on remote sites).
ULOG (User Log)	A file in which error messages are stored.