Enabling Scalability: Using BEA Tuxedo Domains


	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

Domains extends the BEA 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 the user. Domains makes this possible through a highly asynchronous multitasking gateway that processes service requests to and from remote domains.

Multiple-domains Environment

Features of BEA Tuxedo Domains

BEA Tuxedo Domains provides the following features:

Aliasing capability-An administrator can map the service names used by a remote application to the service names used by a local application, allowing easy integration of applications that use different naming schemes.
Availability-Multiple network addresses can be defined for a remote domain. An administrator can specify a backup domain for a set of services.
Scalability and modular growth- Application programmers can structure their applications for modularity, isolation of failures, and independent growth. Interoperation with other TP applications can be achieved easily by adding a description of the interfaces (that is, services) between a remote application and the Domains configuration.
Security-The access control list (ACL) facility restricts access to local services from a particular set of remote domains. The security feature also provides a structuring capability for defining different views of the exported services available to remote domains.
Transparency and independence-Applications are completely unaware of service distribution. Client application programmers need not know the implementation changes made to a service, the location of a service, or network addresses. A service can be available on the same machine as a client, on another machine in the local domain, or on a remote domain.