This chapter lists the features of the BEA TUXEDO Workstation product. It also shows how Workstation alters the existing boundaries of the BEA TUXEDO system, its added features, and the location of Workstation components.
In prior releases, BEA TUXEDO system applications were capable of distributing services across networks of UNIX-based processors. However, all the processors, servers, services, and transactions of the application, and the bridge processes that connect the nodes had to be defined in a configuration file used by the BEA TUXEDO boot process to start the application. Such an application might be diagrammed as shown in Figure 1-1.
Client processes (shown as Native Clients in Figure 1-1) are invoked by users logged in directly on a node where a bulletin board for their application exists under the control of a BBL. They are considered to be within the administrative domain of the application.
Workstation extends the availability of a native BEA TUXEDO application, like the one shown above, to clients resident on workstations. With the Workstation feature, workstations are not required to be within the administrative domain of the application. The Workstation instead, defines an environment where clients can access services of an application through a surrogate handler process. A BEA TUXEDO application using Workstation might be diagrammed as shown in Figure 1-2.
On the workstation, the programming environment is one that works under the operating system of the machine. A Local Area Network provides connectivity to the administrative domain of the application. Therefore, workstations can be UNIX-based as well as non-UNIX based (MS Windows, for example). This gives greater flexibility in the choices of hardware and software platforms on which to deliver the services of your BEA TUXEDO system applications.
The function of Workstation is to provide access to BEA TUXEDO system applications from a network of workstations. The BEA TUXEDO system accomplishes this by providing the same application programming interface (API) for Workstation clients that is available for native-site clients.
Note:
Existing native-site client programs can usually be moved to Workstation sites without modification beyond a recompile.
A potential benefit of Workstation is an increase in an application's performance. Before the Workstation feature, the native processor executed all the client code as well as the server and BEA TUXEDO code. With Workstation, the CPU cycles formerly needed by clients are now available to servers and the BEA TUXEDO system. The client CPU cycles are now furnished by the Workstation processors. The following features are being introduced as part of Workstation:
Overview of the BEA TUXEDO Workstation Product
Product Perspective of BEA TUXEDO Workstation
Figure 1-1 BEA TUXEDO Application without the Workstation Feature
Figure 1-2 BEA TUXEDO Application with the Workstation Feature
Features of BEA TUXEDO Workstation
tmadmin
(1) can monitor statistics of the work load and status of clients.
These features are described in the BEA TUXEDO Programmer's Guide and Administering the BEA TUXEDO System, as well as in Section 1 of the BEA TUXEDO Reference Manual.
Formerly, all of the BEA TUXEDO system software was installed on all of the machines of an application. Now we need to distinguish between software for the BEA TUXEDO system administrative domain, software for the development environment, and platform-specific software needed only at runtime for specific Workstation clients.
The complete release must be installed on the principal server machine. Newer BEA TUXEDO system releases include changes to existing commands and libraries to support the client naming and authentication features. Also included in the recent releases are the workstation listener and workstation handler. The listener and handler must be installed on the machine running the highest level BEA TUXEDO release.
The Workstation can be installed as a step in the installation of the complete BEA TUXEDO system or it can be added at a later time. If you install everything at one time, consult the procedures in the BEA TUXEDO Installation Guide. If you install it separately, refer to the installation instructions in the box containing your software.
The exact nature of the Workstation client development software differs according to the platform for which it is intended, but in all cases the directory structure (under What Goes Where?
For the Administrative Domain
For the Workstation Client Development Environment
$TUXDIR
, the root BEA TUXEDO system directory) is as follows.
include
include
files such as atmi.h
.
bin
buildclt
(1).
locale/C
lib
The location of this software also depends on the characteristics of the machines on which your BEA TUXEDO system application runs. In general, you will probably choose to do client development work on a limited number of machines of the type you expect to use for workstations. Executable client programs can then be moved to the machines where they will be used.
To use BEA TUXEDO Workstation, install the package from the CD-ROM. Consult Appendix A of the BEA TUXEDO Installation Guide for specific information about installing BEA TUXEDO on your platform(s).