Online Transaction Processing: Using the Core BEA Tuxedo System


	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

The BEA Tuxedo system is a development platform that enables you to create applications that mix and match hardware platforms, databases, and operating systems to fit your business needs. The BEA Tuxedo system provides a foundation for client/server architecture, request/response and conversational communications interfaces, transaction support, and administration for a distributed application.

The BEA Tuxedo system provides all the features and benefits of a high-end Online Transaction Processing (OLTP) system, including scalability, high performance, mission-critical reliability, and standards support.

Architecture of a Basic BEA Tuxedo System

As shown in this illustration, the BEA Tuxedo system contains the following parts.

Architectural Part
Description

External interface layer

This layer consists of interfaces between the user and the system. It includes both tools for application development, such as Simple Network Management Protocol (SNMP) agents, and tools for administration, such as the BEA Administration Console. The BEA Administration Console and SNMP agents can interact with standard management consoles. Thus a user can manage a BEA Tuxedo system and a network configuration from one console. In addition, application architects and developers can build their own administrative tools or application- or market-specific tools on top of the MIB.

MIB (Management Information Base)

The Management Information Base (MIB) is an interface that enables users to program and administer a BEA Tuxedo system easily.MIB operations enable you to perform all management tasks (monitor, configure, tune, and so on). The MIB allows you to perform one task to one object at a time or to build tool kits with which you can batch tasks and/or objects. (For information regarding the different parts of the MIB, see Available BEA Tuxedo System MIBs.)

Administration Console

A Web-based graphical user interface for managing BEA Tuxedo applications. The interface allows you to enter and modify data in the MIB. The BEA Administration Console makes these tools available through a Web browser. The server-side components of the BEA Administration Console reside on one of the machines in your BEA Tuxedo domain. To use the Console, you must enter the URL of the server and download a set of Java applets, which implement the Console. The Console enables any user with a supported browser to administer the BEA Tuxedo system.

ATMI (Application to Transaction Monitor Interface)

The interface between an application program and the BEA Tuxedo system. The ATMI and the BEA Tuxedo system implement the X/Open DTP model of transaction processing. An abstract environment, the ATMI supports location transparency and hides the details of implementation. As a result, programmers are free to configure and deploy BEA Tuxedo applications without modifying the application code.

BEA Tuxedo Services (administrative services and application processing 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, and compression, and reliable queueing, The administrative services include: distributed transaction processing, security management, service naming, distributed application administration, centralized application configuration, dynamic reconfiguration, and domains partitioning.

Resource Manager

A software product in which data is stored and available for retrieval through application-based queries. The resource manager (RM) interacts with the BEA Tuxedo system and implements the XA standard interfaces. The most common example of a resource manager is a database. Resource managers provide transaction capabilities and permanence of actions; they are the entities accessed and controlled within a global transaction.

Architectural Part	Description
External interface layer	This layer consists of interfaces between the user and the system. It includes both tools for application development, such as Simple Network Management Protocol (SNMP) agents, and tools for administration, such as the BEA Administration Console. The BEA Administration Console and SNMP agents can interact with standard management consoles. Thus a user can manage a BEA Tuxedo system and a network configuration from one console. In addition, application architects and developers can build their own administrative tools or application- or market-specific tools on top of the MIB.
MIB (Management Information Base)	The Management Information Base (MIB) is an interface that enables users to program and administer a BEA Tuxedo system easily.MIB operations enable you to perform all management tasks (monitor, configure, tune, and so on). The MIB allows you to perform one task to one object at a time or to build tool kits with which you can batch tasks and/or objects. (For information regarding the different parts of the MIB, see Available BEA Tuxedo System MIBs.)
Administration Console	A Web-based graphical user interface for managing BEA Tuxedo applications. The interface allows you to enter and modify data in the MIB. The BEA Administration Console makes these tools available through a Web browser. The server-side components of the BEA Administration Console reside on one of the machines in your BEA Tuxedo domain. To use the Console, you must enter the URL of the server and download a set of Java applets, which implement the Console. The Console enables any user with a supported browser to administer the BEA Tuxedo system.
ATMI (Application to Transaction Monitor Interface)	The interface between an application program and the BEA Tuxedo system. The ATMI and the BEA Tuxedo system implement the X/Open DTP model of transaction processing. An abstract environment, the ATMI supports location transparency and hides the details of implementation. As a result, programmers are free to configure and deploy BEA Tuxedo applications without modifying the application code.
BEA Tuxedo Services (administrative services and application processing 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, and compression, and reliable queueing, The administrative services include: distributed transaction processing, security management, service naming, distributed application administration, centralized application configuration, dynamic reconfiguration, and domains partitioning.
Resource Manager	A software product in which data is stored and available for retrieval through application-based queries. The resource manager (RM) interacts with the BEA Tuxedo system and implements the XA standard interfaces. The most common example of a resource manager is a database. Resource managers provide transaction capabilities and permanence of actions; they are the entities accessed and controlled within a global transaction.