![]() |
![]() |
![]() |
![]() |
![]() |
•
• As indicated in the following figure, middleware consists of software services that exist between a client or server application and the operating system and network services on a system node in the network.Figure 1‑1 Use of MiddlewareRelease 4.0 introduced the ATMI API and transaction processing. Release 5.0 introduced the Domains component, which provided for the federation of Tuxedo applications and inter-application transaction processing. Release 7.1 introduced a security plug-in architecture, which allowed for the installation of third-party security systems.Release 7.1 also introduced multithreading and multicontexting—ATMI functions that enabled programmers to write multithreaded and/or multicontexted application clients and servers—and XML buffer support—the ability to use extensible markup language (XML) typed buffers to exchange XML data within and between ATMI applications. In release 7.1, the Oracle Jolt product was bundled with Oracle Tuxedo for the first time.Release 8.0 introduced the Oracle CORBA API and CORBA Object Transaction Monitor (OTM) capability. The CORBA OTM combined the advantages of a CORBA-compliant programming model with the proven power and reliability of the Oracle Tuxedo core technology infrastructure.Changes the behavior of the ON_STARTUP type connection policy of the Tuxedo domain gateway process to allow customers to selectively establish connections on a per remote domain basis.In addition, both the Oracle Jolt product and the Oracle SNMP Agent product are bundled with Oracle Tuxedo 8.1. For details about the new features and enhancements offered by Oracle Tuxedo 8.1, see the Oracle Tuxedo Release Notes.
• In addition, both the Oracle Jolt product and the Oracle SNMP Agent product are bundled with Oracle Tuxedo 9.0. For details about the new features and enhancements offered by Oracle Tuxedo 9.0, see the Oracle Tuxedo Release Notes and the What’s New link on the Oracle Tuxedo Documentation page.Supports clustering of machines that utilize replicated Oracle database services accessing the same Oracle database. For more information, see Using Tuxedo with Oracle Real Application Clusters (RAC) in Setting Up an Oracle Tuxedo Application.A facilitating tool that helps to efficiently develop Tuxedo .NET Workstation Client applications leveraging the benefit of Microsoft’s .NET Framework. For more information, see Creating Tuxedo .NET Workstation Client Applications in Using the Tuxedo .NET Workstation Client .Oracle TSAM provides comprehensive monitoring and reporting for Oracle Tuxedo system and applications. It includes two components: Oracle TSAM Agent and Oracle TSAM Manager.This feature provides support for SSL encryption over all network links in Tuxedo where LLE encryption is available. For more in formation, see Introducing ATMI Security, in “Using Security in ATMI Applications.”The MQ Adapter provides bi-directional, transactional connectivity to and from WebSphere MQSeries. For more information, see Running the Tuxedo MQ Adapter.Generic AUTHSVR is a new Tuxedo system server (GAUTHSVR) that enables Tuxedo users to be authenticated with LDAP based directory servers without need to write custom code. For more information, see Implementing Single Point Security Administration, in “Using Security in ATMI Applications.”
• Provides Tuxedo TDomain domain gateway features used to defend against DoS attacks, and Tuxedo Domain improved password pair configuration flexibility. For more information, see Introducing ATMI Security in “Using Security in ATMI Applications.”Tuxedo 10.0 PKI plug-in added support for OpenLDAP for X.509 certificate lookup. For more information, see Administering Security,Cert-C PKI Encryption Plug-In Configuration, Configure Certificate Lookup in “Using Security in ATMI Applications.”Release 10g Release 3 (10.3)Release 10gR3 introduced the following new features and enhancements:For more information on using IPv6 with Oracle Tuxedo 10gR3, see Enabling IPv6 in the Oracle Tuxedo Programming Guide.Two new APIs, tpappthrinit(3c) and tpappthrterm(3c) are provided for application-created thread in ATMI server to create and terminate separate Tuxedo context. In context created using tpappthrinit(3c), the application-created server thread can initiate service requests and define transactions.For more information, see Programming a Multithreaded and Multicontexted ATMI Application in the Oracle Tuxedo Administration Guide.
• tlisten password encryptiontlisten.pw file is system-encrypted. To change password, you must use tlistpwd(1).Local domain with a PERSISTENT_DISCONNECT connection policy will neither connect to nor accept connect request from any remote domain.Release 11g Release 1 (11.1.1.1.0)Release 11gR1 introduced the following features and enhancements:When configured, ON_STARTUP domain gateway continuously re-tries to establish connection to remote domain when domain password pair validation fails.If configured in Microsoft Windows, processes booted in an Oracle Tuxedo domain are owned by the user who executed the tmboot command, instead of the user who starts the TUXIPC system service.Release 11g Release 1 (11.1.1.2.0)Release 11gR1 (11.1.1.2.0), the current Oracle Tuxedo product, introduces the following new features and enhancements:Oracle Tuxedo now supports multiple Resource Managers (RMs) in one group, so every group application server has the ability to communicate with multiple RMs in one global transaction. For more information, see the Oracle Tuxedo ATMI COBOL Function Reference, Oracle Tuxedo ATMI C Function Reference, Oracle Tuxedo File Formats, and Data Descriptions, MIBs, and System Processes Reference..Previous Oracle Tuxedo releases have supported views. In Release 11.1.1.2.0 view functionality has been extedned to support nested views. For more information, see Managing Typed Buffers in Programming an Oracle Tuxedo ATMI Application Using C.The Oracle Tuxedo system and ATMI together implement the X/Open distributed transaction processing (DTP) model of online transaction processing (OLTP). The DTP model ensures that work being done throughout a client/server application is atomically completed, meaning that all involved databases are updated properly if the work is successful, or all involved databases are “rolled-back” to their original state if the work fails.
• Internet Protocol Version 6 (IPv6)—The next generation protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 (IPv4)A client/server application separates the calling (client) software and the called (server) software into separate programs. The advantage of a client/server application is that multiple client processes can interface with a single server process, where the processes do not need to run on the same host machine. Thus, clients and servers can run on hardware and software platforms suited to their particular functions. For example, clients can run on inexpensive platforms such as workstations or personal computers, and database management servers can run on platforms specially designed and configured to perform queries.The Oracle Tuxedo system has been ported to most popular client platforms, including Microsoft Windows Server and XP, and a variety of UNIX workstations. The Oracle Tuxedo system has been ported to most popular server platforms, including Microsoft Windows Server, HP-UX, IBM AIX, and Sun Solaris.For a complete list of supported platforms for Oracle Tuxedo 11g Release 1 (11.1.1.2.0), see Oracle Tuxedo 11g Release 1 (11.1.1.2.0) Platform Data Sheets on page A-1 in Installing the Oracle Tuxedo System.ATMI and CORBA applications developed with Oracle Tuxedo are mission-critical, meaning that they are reliable, scalable, secure, and manageable. Applications can grow as the company grows, and they continue running when various parts of the network fail. Applications can expand and contract as the demand requires.For more information about transactions, see Introducing Oracle Tuxedo ATMI and Using CORBA Transactions.For more information about scaling, see “Tuning an Oracle Tuxedo ATMI Application” in Administering an Oracle Tuxedo Application at Run Time and Scaling, Distributing, and Tuning CORBA Applications.Figure 1‑2 Oracle Tuxedo Plug-in Security ArchitectureFor more information on security in ATMI and CORBA applications, see Using Security in ATMI Applications and Using Security in CORBA Applications.For information about security when interoperating with earlier releases of Oracle Tuxedo software or Oracle WebLogic Enterprise, or when interoperating with Oracle WebLogic Server, see Oracle Tuxedo Interoperability.Figure 1‑3 Simplified View of Administration ToolsFor the Oracle Tuxedo Administration Console startup procedure, see “Starting the Oracle Tuxedo Administration Console” in Installing the Oracle Tuxedo System. For information about how to use the Oracle Tuxedo Administration Console, either access Help directly from the console or see Oracle Tuxedo Administration Console Online Help . Also see “Oracle Tuxedo Management Tools” in Introducing Oracle Tuxedo ATMI.Most of the functionality needed for dynamic modification of an Oracle Tuxedo application is provided by the tmadmin and tmconfig commands. Most of the functionality needed for dynamic modification of an Oracle Tuxedo Domains configuration is provided by the dmadmin command. Each of these commands is an interactive meta-command having many subcommands for performing various administrative tasks, including the modification of configuration entries while the system is running.For details about these commands, see reference pages tmadmin(1), tmconfig, wtmconfig(1), and dmadmin(1)in Oracle Tuxedo Command Reference. Also, see “Oracle Tuxedo Management Tools” in Introducing Oracle Tuxedo ATMI.There are MIB interfaces to administer the access control list, disk-based queues, Domains, events, core Tuxedo, and the workstation extension. The following are the corresponding MIB component names: ACL_MIB, APPQ_MIB, DM_MIB, EVENT_MIB, TM_MIB, and WS_MIB. Through the MIB interface, administrators control the application by programmatically querying the Tuxedo bulletin board for the current state of MIB objects, and then effecting administrative changes by either setting and resetting specific MIB values or creating new MIB objects.For details about the Oracle Tuxedo MIBs, see reference pages ACL_MIB(5), APPQ_MIB(5), DM_MIB(5), EVENT_MIB(5), MIB(5), TM_MIB(5), and WS_MIB(5) in Oracle Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference; start with the MIB(5) reference page. Also, see “Oracle Tuxedo Management Tools” in Introducing Oracle Tuxedo ATMI.Figure 1‑4 Oracle Tuxedo Client and Server ComponentsA remote Tuxedo client—ATMI (/WS), Jolt, or CORBA C++—interfaces with a Tuxedo server via a network connection and a pair of Tuxedo gateway processes: Workstation Listener/Handler (WSL/WSH), Jolt Server Listener/Handler (JSL/JSH), or IIOP Listener/Handler (ISL/ISH). A remote Tuxedo client may run on a machine that is not part of the Tuxedo server application (typically a workstation or personal computer), or the remote client may run on a machine that is part of the Tuxedo server application. For the latter case, the local operating system intercepts the messages destined for the network and redirects them to the destination process—the Tuxedo remote client or handler process—running locally.A native Tuxedo client—a native ATMI client or a native CORBA C++ client—is co-located on a machine that is part of the Tuxedo server application and interfaces with a Tuxedo server via the Tuxedo infrastructure using interprocess communication. Native Jolt clients are not supported. These clients can only access a Tuxedo server via a pair of JSL/JSH gateway processes.The following client component software is included in the Oracle Tuxedo 11g Release 1 (11.1.1.2.0) distribution:The following server component software is included in the Oracle Tuxedo 11g Release 1 (11.1.1.2.0) distribution:
* A native Tuxedo ATMI or CORBA C++ client does not use listener or handler gateway processes.For information on how Oracle Tuxedo 11g Release 1 (11.1.1.2.0) interoperates with older releases of Oracle Tuxedo software, Oracle WebLogic Enterprise, and third-party products, or how Oracle Tuxedo 11g Release 1 (11.1.1.2.0) interoperates with Oracle WebLogic Server, see Oracle Tuxedo Interoperability.For more information about remote ATMI clients, see Using the Oracle Tuxedo ATMI Workstation Component.For more information about Jolt, see Using Oracle Jolt and the Oracle Jolt API Javadoc reference information.For details, see Creating CORBA Client Applications.As shown in the figure, a CORBA C++ object can include ATMI calls to Oracle Tuxedo services. For an example, see the Wrapper University sample application, available in the Guide to the CORBA University Sample Applications.Figure 1‑6 Simplified View of an Oracle Tuxedo DomainIn Oracle Tuxedo terminology, a domain is the same as an application—a business application; both terms are used as synonyms throughout the Oracle Tuxedo user documentation. Examples of business applications currently running on Tuxedo are airline and hotel reservation systems, credit authorization systems, stock-brokerage systems, banking systems, and automatic teller machines.For more information about Tuxedo domains, see “Important Oracle Tuxedo Terms and Concepts” on page 2‑1. For information about interconnecting Tuxedo domains, see “Oracle Tuxedo Domains” on page 2‑14.Oracle Jolt extends the functionality of existing Tuxedo ATMI applications to include intranet- and Internet-wide availability. Oracle Jolt also enables Oracle WebLogic Server to invoke Tuxedo ATMI services. For clarification, see “Making Tuxedo Services Web Accessible Through Oracle Jolt” on page 5‑7.