Note: For detailed information about distributing Oracle Tuxedo CORBA applications across a network, refer to the Scaling, Distributing, and Tuning CORBA Applications guide.Figure 10‑1 illustrates the basic parts of an application distributed across three machines.Figure 10‑1 Sample of a Distributed ApplicationA distributed application is implemented on a network defined in the NETWORK (and optionally NETGROUPS) section(s) of the configuration file. It frequently uses data-dependent routing, defined in the ROUTING section of the configuration file. A critical part of the design of a distributed application is the arrangement between server groups, processes, transaction manager servers (TMSs), and resource managers (RMs).To set up a distributed application over a network, the application administrator must work with the network administrator. In most instances, the application administrator writes the configuration file for a distributed application (defining parameters in the RESOURCES, MACHINES, GROUPS, SERVICES, and ROUTING sections), and the network administrator or MIS representative writes or contributes to the networking sections.
• “Managing the Network in a Distributed Application” in Administering an Oracle Tuxedo Application at Run Time
• Coordination of autonomous actions—autonomous actions are actions that involve multiple server groups and/or multiple resource manager interfaces. The Oracle Tuxedo system enables you to coordinate autonomous actions among separate applications as a single logical unit of work.
• Resilience—when one of many machines fails, the remaining machines continue to operate. Similarly, when one server in a server group fails, the remaining servers continue the work.
• Scalability—application load or capacity can be increased by:
•
•
•
•