Setting Up a BEA Tuxedo Application

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Administrative Tasks and Tools

This topic includes the following sections:


Tasks an Administrator Performs

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

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
Collect information from designers, programmers, and business users of the application
Set up the hardware and software, and install the BEA Tuxedo system and the application (installation)
Set up the BEA Tuxedo system parameters that govern how the application uses components (configuration)
Configure transactions for domains, machines, groups, interfaces, services, and other required components (configuration)
Select and implement security methods for protecting the application and data
For CORBA environments, configure an Internet Inter-ORB Protocol (IIOP) Listener/Handler and modify the machine configuration
Set up distributed applications with routing tools: factory-based routing for CORBA environments and data-dependent routing for ATMI environments
Set up networked applications
Configure local and remote domains
Set up Workstation clients: add environment tables and a workstation listener, and modify the machine configuration
Create an application queue space and modify the configuration to support queued messages

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
Start up and shut down an application
Manage buffers
Administer the security of your application
Monitor the activities, problems, and performance of your application
For ATMI environments, manage transactions
For CORBA environments, manage interfaces
Manage networked applications
Manage remote Workstation clients
Subscribe to events
Use queued messaging
Identify and resolve problems as they occur (troubleshoot)
Reassign primary responsibility for your application from the MASTER machine to an alternate (BACKUP) machine (migration) when problems occur on the MASTER (migration)
Change system parameters and the selection of services to meet evolving needs (dynamic modification)
Refine your application to reflect additional components, such as new machines or servers (dynamic reconfiguration)

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 Tuxedo Administration Console, the command-line interface, and the AdminAPI. The following chart describes some of the circumstances in which your intervention may be needed.

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

See Also

Differences Between the BEA Tuxedo ATMI and CORBA Environments

For the BEA Tuxedo CORBA environment, the BEA Tuxedo administration facilities support the administration of applications running within the context of the Object Request Broker (ORB) and the TP Framework.

The UBBCONFIG configuration file for BEA Tuxedo CORBA environments supports the configuration of client and server applications, as follows:

Overall, the administration tasks for the BEA Tuxedo CORBA and ATMI environments are similar. There are a few principal differences between the environments, however, as follows:

Note: The Management Information Base (MIB) defines the set of classes through which the fundamental aspects of an application can be configured and managed. The MIB classes provide an administrative programming interface to the BEA Tuxedo CORBA and ATMI environments.


Planning the Design of Your Application

An administrator needs to know a customer's business requirements and how the software will be used. Once these needs are understood, administrators can work with their system designers and application developers to make sure that the application's configuration can support its requirements.

Answers to the following preliminary questions may help in planning the design of your application.

  1. How many machines will be used? ____________________
  2. Will client applications reside on machines that are remote from the server applications? _______________________
  3. For ATMI, which services will your application offer? ____________________________________________________________________________________________________________________________
  4. For CORBA, which interfaces will your client or server application use? __________________________________________________________________________________________________________________________
  5. What resource managers (database) will the application use and where will they be located? __________________________________________________________________________________________________________________________
  6. What "open" strings will the resource managers need? ____________________________________________________________________________________________________________________________
  7. What setup information will be needed for an RDBMS? __________________________________________________________________________________________________________________________________________________________________________________________
  8. Will transactions be distributed? ________________
  9. Will the application use global transactions? ________________
  10. What buffer types will be used? ____________________________________________________________
  11. Will data be distributed across machines? _________________________________________________________
  12. To which external domains will the application export services? From which external domains will the application import services? ____________________________________________________________________________________________________________________________________________________________________________________________
  13. Will factory-based or data-dependent routing be used in your application? _________________________________________________________
  14. What are the names of the CORBA interfaces or ATMI services? _________________________________________________________________________________________________________________________
  15. In what order of priority should the interfaces or services be available? _________________________________________________________________________________________________________________________
  16. What are the reliability requirements? Will redundant listener and handler ports be needed? Will replicated server applications be needed? ____________________________________________________________________________________________________________________________
  17. For CORBA environments, will the domain need an Interface Repository (IR) database? If so, will the domain benefit from having IR replicas, and how many IR server applications should be defined? ____________________________________________________________________________________________________________________________
  18. Are there any conversational services? What resource managers do they access? What buffer types do they use? _____________________________________________________________________________________________________________________

See Also


Tools to Help You Administer Your Application

The BEA Tuxedo system gives you a choice of several methods for performing the same set of administrative tasks for either BEA Tuxedo ATMI or CORBA environments. Whether you are more comfortable using a graphical user interface or entering commands at a shell prompt, you will be able to find a comfortable method of doing your job as the administrator of a BEA Tuxedo application. The following figure illustrates the tools you can use to write the configuration file and administer your BEA Tuxedo application during run time.

Figure 1-1 Administration Tools

Administration Tools

See Also

  Back to Top       Previous  Next