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

   Using the BEA Tuxedo Workstation Component

The Workstation component of the BEA Tuxedo system allows application clients to reside on a machine that does not have a full server-side installation, that is, a machine that does not support any administration or application servers. All communication between the client and the application servers takes place over the network.

A Workstation client process can run on a Windows or UNIX platform. The client has access to the ATMI. The networking behind requests is transparent to the user. A Workstation client does not have access to all the capabilities available to a native client. Both types of clients, however, can do the following:

• Send and receive messages

• Begin, end, or commit transactions

• Send and receive unsolicited messages

• Meet application security requirements

• Communicate information about remote clients through the tmadmin(1) command

  Note: A Workstation client communicates with application servers through a Workstation Handler (WSH) process.

Limitations of Workstation Clients

Workstation clients do not have access to all the functionality available to native clients. For example, unlike a native client, a Workstation client cannot join an application as tpsysadm, which means that the client cannot subsequently subscribe to an event that issues a service call.

• Workstation Connectivity: Using BEA Tuxedo Workstation in Introducing the BEA Tuxedo System

• What Are the Workstation Handler and Workstation Listener in Introducing the BEA Tuxedo System

• About Workstation Clients in Setting Up a BEA Tuxedo Application