|
|
As the administrator of your organization's computing applications, you are responsible for setting up and running a system that is critical to your corporate mission. You must plan how to maximize the performance and reliability of your WLE or BEA TUXEDO system, and then make it happen.
This chapter discusses the following topics:
You are the person responsible for configuring and booting an application and then keeping it running smoothly. Your job can be viewed in two phases:
The Administrator's Job
Most of the work you do during this phase is necessary only once. The exception to this rule is the configuration work: the WLE or BEA TUXEDO system allows you to reconfigure your application whenever necessary to maximize performance and reliability.
The remainder of this chapter lists the specific tasks you need to do during each phase.
During the this phase, you must do the following tasks:
:
The Groundwork Phase
Depending on your application, you may also need to set up the following:
:
Note:
This guide provides instructions for all the tasks shown in this table, except installation. For installation instructions, see the Installation Guide.
During the this phase, you must do the following tasks:
The Operational Phase
Log the activities, problems, and performance of your application and analyze the results regularly.
|
|
Depending on your application, you may also have to do the following:
Redefine your application to reflect the addition of a component, such as a new machine or server.
|
For the WLE system, the existing BEA TUXEDO administration facilities have been extended to support the administration of applications running within the context of the WLE Object Request Broker (ORB) and the WLE TP Framework.
The UBBCONFIG
configuration file for WLE systems includes the following enhancements to support the configuration of WLE client and server applications:
Differences Between the WLE and BEA TUXEDO Systems
However, WLE systems use a different communications protocol to connect remote and foreign clients to WLE server applications. The protocol is the standard Internet Inter-ORB Protocol (IIOP). Instead of the BEA TUXEDO Workstation Handler (WSH) process and Workstation Listener (WSL) process, the WLE system calls its gateway processes the IIOP Server Handler (ISH) and the IIOP Server Listener (ISL). This results in a slight syntax difference, ISL instead of WSL , in the SERVERS section of each application's UBBCONFIG configuration file.
In the BEA TUXEDO system, you can examine any FML field used for a service invocation to determine the data-dependent routing criteria. In WLE systems, the system designer must personally communicate to you the routing criteria of CORBA interfaces. For WLE systems, there is no service request message data or associated buffer information available for routing. This occurs because WLE routing is performed at the factory, not on a method invocation on the target CORBA object.
Details on these differences and exceptions are provided in subsequent chapters of this document.
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 WLE or BEA TUXEDO system. At the beginning of this chapter, we summarized your job responsibilities in two phases. For software descriptions and procedures that help you perform your work, refer to the appropriate documentation, as follows:
The BEA TUXEDO Reference Manual includes, in the TM_MIB
(5) section, reference material about the T_INTERFACE
MIB class, T_IFQUEUE
MIB class, and T_FACTORY
MIB class. Those MIB classes were added for WLE.
An online version of the BEA TUXEDO Reference Manual is available on the Online Documentation CD. On the CD, click the Reference button from the main menu. Next, click the hyperlink "BEA TUXEDO Manuals." On the BEA TUXEDO home page, click the hyperlink "Reference Manual: Section 5."
Also see the descriptions of the T_DOMAIN
MIB class, T_MACHINE
MIB class, T_SERVER
MIB class, T_TRANSACTION
MIB class, and T_ROUTING
MIB class. Those MIB classes were enhanced for WLE.
Roadmap for Your Responsibilities
As an administrator, you need to work with your system designers and application designers to understand how the administrative configuration of your application can support the requirements for it. In addition, you need to know the requirements of your customer: the business unit using the new software.
Before you can start configuring your system, you need answers to questions about the design of your application and about the server applications developed from that design, as defined in the following section.
The following questions may help you start the planning process:
How many machines will be used?
Will client applications reside on machines that are remote from the server applications?
Which CORBA interfaces will your WLE client or server application use?
What resource managers will the application use and where will they be located?
What "open" strings will the resource managers need?
What setup information will be needed for a database resource manager?
Will transactions be distributed?
What buffer types will be used?
Will data be distributed across machines?
Will factory-based routing be used in your WLE application?
Will data-dependent routing be used in your BEA TUXEDO application?
Planning Your Configuration
Questions About the Design
What are the reliability requirements? Will redundant listener and handler ports be needed? Will replicated server applications be needed?
The following questions may help you focus on the issues related to your server application that need to be resolved in your plan:
What are the names of the WLE interfaces or BEA TUXEDO services?
Are there any conversational services (BEA TUXEDO system)?
What resource managers do they access?
What buffer types do they use?
As you start putting together a configuration plan, you will discover more questions to which you need answers.
Questions About Server Applications
|
Copyright © 1999 BEA Systems, Inc. All rights reserved.
|