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   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Setting Up a BEA Tuxedo Application

An administrator's job can be viewed as two broadly defined tasks:

• Setup tasks-all the tasks required to prepare your system before booting your application

• Run-time administration-any tasks performed on an application that has been booted

Setup Tasks

During the setup phase, an administrator is responsible for the planning, design, installation, security, and configuration of the BEA Tuxedo system. The following table describes the required and optional tasks during the setup phase.

Setup Task	Required	Optional
Collect information from designers, programmers, and business users of the application	X
Set up the hardware and software, and install the BEA Tuxedo system and the application (installation)	X
Set up the BEA Tuxedo system parameters that govern how the application uses components (configuration)	X
Configure transactions for domains, machines, groups, interfaces, services, and other required components (configuration)	X
Select and implement security methods for protecting the application and data	X
Set up distributed applications with routing tools		X
Set up networked applications		X
Configure local and remote domains		X
Set up Workstation clients: add environment tables and a Workstation Listener, and modify the machine configuration		X
Create an application queue space and modify the configuration to support queued messages		X

Run-time Tasks

With your BEA Tuxedo system installed and your TUXCONFIG file loaded, you are ready to boot your application. When your application is launched, you must start monitoring its activities for problems-both actual and potential. The following table describes the required and optional tasks during the run-time phase.

Run-Time Task	Required	Optional
Start up and shut down an application	X
Manage buffers	X
Administer the security of your application	X
Monitor the activities, problems, and performance of your application	X
Manage transactions		X
Manage networked applications		X
Manage remote Workstation clients		X
Subscribe to events		X
Use queued messaging		X
Identify and resolve problems as they occur (troubleshoot)		X
Reassign primary responsibility for your application from the MASTER machine to an alternate (BACKUP) machine (migration) when problems occur on the MASTER (migration)		X
Change system parameters and the selection of services to meet evolving needs (dynamic modification)		X
Refine your application to reflect additional components, such as new machines or servers (dynamic reconfiguration)		X

During run time, you may need to respond quickly to potential problems or evolving requirements of an application. To help you perform these functions, you have a choice of three tools: the BEA Administration Console, the command-line interface, and the AdminAPI. The following chart describes some of the circumstances in which your intervention may be needed.

To	You May Want To
Maximize performance	Add load balancing or set priorities for interfaces and services
Fix problems that may develop on the MASTER machine	Replace it with a designated BACKUP machine
Change processing and resource usage requirements	Add machines, servers, clients, interfaces, services, and so on

See Also

• Planning the Design of Your Application

• Tools to Help You Administer Your Application