Distributing ATMI Applications Across a Network

This topic includes the following sections:

•	What Is a Distributed ATMI Application?

•	Why Distribute an ATMI Application Across a Network?

Note:

For detailed information about distributing Oracle Tuxedo CORBA applications across a network, refer to the Scaling, Distributing, and Tuning CORBA Applications guide.

What Is a Distributed ATMI Application?

A distributed application consists of one or more local or remote clients that communicate with one or more servers on several machines linked through a network. With this type of application, business operations can be conducted from any geographical location. For example, a corporation may distribute the following types of operations across a large region, or even across international boundaries:

•	Forecasting sales

•	Ordering supplies

•	Manufacturing, shipping, and billing for goods

•	Updating corporate databases

State of the art telecommunications and data networks are making distributed operations of this sort increasingly common. Applications developed to implement this type of strategy allow businesses to reduce costs and enhance their offerings of services to customers around the world.

The Oracle Tuxedo system supports this type of architecture by simplifying the task of managing a distributed application. Whether an application comprises only one computer or thousands of computers working together over a network, all the elements of that application, including clients, servers, and the networks that connect them, are managed through a single Oracle Tuxedo configuration file.

Example of a Distributed Application

Figure 10‑1 illustrates the basic parts of an application distributed across three machines.

Figure 10‑1 Sample of a Distributed Application

Implementing a Distributed Application

A 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.

See Also

•	Creating the Configuration File for a Distributed ATMI Application on page 11‑1

•	Setting Up the Network for a Distributed Application on page 12‑1

•	“Managing the Network in a Distributed Application” in Administering an Oracle Tuxedo Application at Run Time

•	Scaling, Distributing, and Tuning CORBA Applications

Why Distribute an ATMI Application Across a Network?

Distributed applications provide several important benefits. Early business applications were developed to run on one large mainframe computer. Because all computing was performed on a single machine, a failure could bring down an entire system. With the increasing popularity of distributed applications, this threat of system failure is declining.

Another advantage is that by distributing an application, you can group parts of an application logically and position these logical groups in the most effective locations. By creating groups of servers, for example, you can partition a large application into separate, business-specific components of manageable size and optimal location.

A distributed application allows you to do the following:

•	Perform data-dependent partitioning

•	Manage multiple resources

•	Enlarge the client and/or server model

•	Obtain transparent access to Oracle Tuxedo system services

•	Establish multiple server groups

•	Use multiple computers simultaneously to do the work of one application, providing better throughput and response time

•	Provide for replicated resources for increased availability

Features of a Distributed Application

•	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:

•	Placing more servers in a group.

•	Adding machines to an application and redistributing groups across machines.

•	Replicating a server group that resides on one machine, on other machines, and using load balancing.

•	Segmenting a database using data-dependent routing for groups that meet specific criteria.

See Also

•	How to Create the Configuration File for a Multiple-machine (Distributed) Application on page 3‑3.

•	“What Is Load Balancing?” in Introducing Oracle Tuxedo ATMI

•	“What Is Data-Dependent Routing?” in Introducing Oracle Tuxedo ATMI

•	Scaling, Distributing, and Tuning CORBA Applications