|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||
Describes the tasks performed by an administrator, and the tools that the BEA
Tuxedo system provides to assist with the administration of an application. Describes the purpose of each section of the configuration file.
Describes how to write the configuration file for any type of BEA Tuxedo application: single machine, distributed, multi-domain, multithreaded, and/or multicontexted. Defines global transactions, explains the benefits of using transactions and offers a sample situation that illustrates these benefits, and describes how the BEA Tuxedo system supports transactions. Defines the use of transactions in a BEA Tuxedo environment. Provides instructions
on how to modify the configuration file to use transactions, as well as modify the domains configuration
file to support transactions. Also includes a sample distributed application that uses transactions. Discusses the characteristics and benefits of distributed applications and data-dependent routing. A distributed application example is provided.
Describes how to set up the configuration file to support a distributed application. Also describes how to set up the domains configuration file to
support routing.
Describes how to write a configuration file to support a distributed application. Defines and illustrates a workstation client, and provides a sample application with four workstation clients.
Defines global transactions, explains the benefits of using transactions and offers a sample situation that illustrates these benefits, and describes how the BEA Tuxedo system supports transactions.
Provides the procedures for booting and stopping an application.
Describes various methods of monitoring your application: the BEA Administration Console, command-line utilities, the MIB, and log files.
Explains how to use the BEA Administration Console, command line utilities, or the MIB to dynamically modify your running application. Describes how to add a machine,
server, or group, change application-wide or server-specific parameters, change
application passwords, suspend or resume services or servers, advertise or
unadvertise services or servers, and change the timeout value of a service.
Describes how to schedule data over parallel data circuits; how and when to use data compression over networks; how to balance
network loads; and how to use data encryption. Discusses the benefits of using the EventBroker and describes the tasks that it performs. Also describes the differences between
application-defined and system-defined events. Illustrates how the EventBroker works and the various
event notifications. Describes how to publish a list of subscription information, configuring servers, setting the polling interval, subscribing to
an event, selecting a notification method, and canceling a subscription. Describes how to switch master and backup machines, how to migrate a group of servers,
how to cancel a migration, and how to move transaction logs to a backup machine. Discusses how to maximize application resources,
when to use MSSQ sets, how to enable load balancing,
and how to assign priorities to services. Also explains how to bundle services into servers and set application
parameters, determine IPC requirements, and measure system traffic.
Includes such topics as distinguishing between types of failures, responding to unsolicited broadcast messages, monitoring system files,
restoring failed machines, and repairing partitioned networks.
Describes the tools and procedures for building a multiple-domain configuration. Summarizes the
types of domain gateways supported by the BEA Tuxedo system, including the
functionality and message services provided by each type. A sample application in which domain gateways are used is also
provided.
Discusses the advantages of building a multiple-domain application. Provides
a sample based on two configuration files that are included. Also provides instructions
for configuring a Domains environment, as well as performing optional tasks
such as compressing data between domains, setting up security in domains,
configuring connections between domains, and configuring failover and failback. Provides instructions for run-time administration of a Domains application,
including managing transactions in Domains. |
|||||||||||||||
|
|