Building 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 \| Using the BEA Tuxedo Domains Component \| Local Topics \| Previous Topic \| Next Topic \| Contents

To build a multiple-domain configuration, you need to consider the following tasks:

Integrate your existing BEA Tuxedo application with other domains
Ensure interoperability across domains
Preserve or restrict access to services across domains
Accept or deny service requests across domains

Domains achieve these tasks through a highly asynchronous, multitasking, multithreaded gateway. A domain gateway (DGW) is a BEA Tuxedo-supplied server that handles requests to remote domains and from remote domains. Any request can be processed within a transaction. The following figure illustrates how one BEA Tuxedo domain communicates with another domain via a domain gateway.

Two-way Communication Through a Gateway

In this illustration, the gateway processes outgoing credit card authorization requests to another domain. The gateway also handles incoming authorization responses.

Domain gateways manage all the communication between domains. The gateway processes include a gateway administrative server (GWADM) that enables run-time administration of the domain gateway group and a Domains administrative server (DMADM) that enables run-time administration of the BEA Tuxedo application-wide Domains configuration information.

Tools to Set Up and Maintain a Multiple-domain Application

The following illustration shows the tools provided by the BEA Tuxedo system for setting up and maintaining a multiple-domain configuration.

Domains Administrative Tools

Domains Administrative Tool

Description

dmadmin(1)

A command that allows you to configure, monitor, and tune domain gateway groups dynamically. Use this command to update the BDMCONFIG file while an application is running. The command acts as a front-end process that translates administrative commands. These commands send requests to the DMADMIN service, a generic administrative service advertised by the DMADM server. DMADMIN invokes functions that validate, retrieve, or update information in the BDMCONFIG file.

DMCONFIG(5)
BDMCONFIG

DMCONFIG is the text version of the configuration file for a multiple-domain configuration; BDMCONFIG is the binary version.

dmloadcf(1) and dmunloadcf(1)

dmloadcf—reads the DMCONFIG file, checks the syntax, and optionally loads a binary BDMCONFIG configuration file.

dmunloadcf—translates the BDMCONFIG configuration file from binary to text format.

DMADM(5)

An administrative server that enables you to manage a Domains configuration at run time. DMADM provides a registration service for gateway groups. This service is requested by GWADM servers as part of their initialization procedure. The registration service downloads the configuration information required by the requesting gateway group. The DMADM server maintains a list of registered gateway groups, and propagates to these groups any changes made to the configuration file (BDMCONFIG).

GWADM(5)

An administrative server that supports run-time administration of a specific gateway group. This server registers with the DMADM server to obtain the configuration information used by the corresponding gateway group. GWADM accepts requests from DMADMIN for run-time statistics or changes in the run-time options of the specified gateway group. Periodically, GWADM sends an "I-am-alive" message to the DMADM server. If no reply is received from DMADM, GWADM registers again. This process ensures the GWADM server always has the current information about the Domains configuration for its group.

GWTDOMAIN(5)

A gateway process that receives and forwards messages from clients and servers in all connected domains (for BEA Tuxedo Domains).

Domains Administrative Tool	Description
dmadmin(1)	A command that allows you to configure, monitor, and tune domain gateway groups dynamically. Use this command to update the BDMCONFIG file while an application is running. The command acts as a front-end process that translates administrative commands. These commands send requests to the DMADMIN service, a generic administrative service advertised by the DMADM server. DMADMIN invokes functions that validate, retrieve, or update information in the BDMCONFIG file.
DMCONFIG(5) BDMCONFIG	DMCONFIG is the text version of the configuration file for a multiple-domain configuration; BDMCONFIG is the binary version.
dmloadcf(1) and dmunloadcf(1)	dmloadcf—reads the DMCONFIG file, checks the syntax, and optionally loads a binary BDMCONFIG configuration file. dmunloadcf—translates the BDMCONFIG configuration file from binary to text format.
DMADM(5)	An administrative server that enables you to manage a Domains configuration at run time. DMADM provides a registration service for gateway groups. This service is requested by GWADM servers as part of their initialization procedure. The registration service downloads the configuration information required by the requesting gateway group. The DMADM server maintains a list of registered gateway groups, and propagates to these groups any changes made to the configuration file (BDMCONFIG).
GWADM(5)	An administrative server that supports run-time administration of a specific gateway group. This server registers with the DMADM server to obtain the configuration information used by the corresponding gateway group. GWADM accepts requests from DMADMIN for run-time statistics or changes in the run-time options of the specified gateway group. Periodically, GWADM sends an "I-am-alive" message to the DMADM server. If no reply is received from DMADM, GWADM registers again. This process ensures the GWADM server always has the current information about the Domains configuration for its group.
GWTDOMAIN(5)	A gateway process that receives and forwards messages from clients and servers in all connected domains (for BEA Tuxedo Domains).

Types of Domain Gateways

The BEA Tuxedo system provides different types of gateways to accommodate various network transport protocols used to communicate with remote domains. Access to remote domains that use the same communication and transaction commitment protocol is provided through a group of gateways that implement the configuration defined for a particular local domain. Following are the different types of domain gateways:

BEA Tuxedo Domains (TDomains) gateway (that is, the GWTDOMAIN 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.
Note: GWTDOMAIN gateways should not be specified as members of an MSSQ set. They should not have a reply queue (REPLYQ=N should be specified). GWTDOMAIN gateways are recommended to be restartable.
BEA eLink OSI TP gateway—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).
BEA eLink Adapter 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 a remote SNA domain. It also supports communication with multiple SNA networks.
BEA eLink Adapter for Mainframe TCP:
- For CICS gateway—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, with a CICS environment.
- For IMS gateway—provides transparent communications between client and server transactions in an IMS system and a BEA Tuxedo domain, a CICS system, or another IMS system.
BEA TOP END Domain Gateway (TEDG)—provides interoperability between TOP END systems and BEA Tuxedo domains.

Functionality Supported by Domain Gateways

Domain gateways support the following functionality:

Administration—gateways can be booted or shut down exactly as any other BEA Tuxedo server. Run-time administration is provided through an administrative server, DMADM. Using DMADM, application administrators can make changes to a domains configuration file, and tune the performance of a gateway group. (The DMADM administrative server should be booted before gateway groups.)
ATMI—gateways can access the programming interface between a domain and the BEA Tuxedo system ensuring access to the following messaging models:
Multidomain Interaction—gateways can communicate with multiple domains.
Multinetwork Support—gateways can communicate with other domains via a variety of network protocols, such as TCP/IP, IPX/SPX, and others. However, a gateway is limited by the capabilities of the networking library to which it is linked. In other words, a gateway typically supports a single type of network protocol.
Transaction Management—application programs can interoperate with other domains within a transaction. The gateway coordinates the commitment or rollback of transactions running across domains.
Typed Buffer Support—gateways can perform encoding and decoding operations for all the types of buffers defined by the application.