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

You can develop client programs targeted for workstations in the same way that you would develop client programs within the BEA Tuxedo system administrative domain (that is, native clients). All of the ATMI and FML functions are available to the Workstation client.

Interoperability between BEA Tuxedo Release 7.1 Workstation clients and applications based on pre-7.1 releases of the BEA Tuxedo system is supported in any of the following situations:

• The client is neither multithreaded nor multicontexted.

• The client is multicontexted.

• The client is multithreaded and each thread is in a different context

A BEA Tuxedo Release 7.1 Workstation client with multiple threads in a single context cannot interoperate with a pre-7.1 release of the BEA Tuxedo system.

You compile and link-edit Workstation client programs using the buildclient(1) command. If you are building a Workstation client on a native node (that is, one on which the complete BEA Tuxedo system is installed), use the -w option to indicate the client should be built using the workstation libraries. Otherwise, on a native node, where both native and workstation libraries are present, the default is to use the native libraries. In this case, using the -w option ensures that the correct libraries for a workstation client are used. On a workstation, where only the workstation libraries are present, it is not necessary to use the -w option.

The following listing shows an example of the buildclient(1) command line on a native node.

TUXDIR=/var/opt/tuxedo CC=ncc; export TUXDIR CC
buildclient -w -o wsclt -f wsclt.c -f "userlib1.a userlib2.a"

The -o option provides a name for your output file. Input files are specified with the -f firstfiles option to indicate that they are link-edited before system libraries. As indicated in the example, you must define the TUXDIR environment variable to ensure that the buildclient command can locate system libraries. CC defaults to cc but can be set to another compiler, as shown in the example.

• Writing Clients in Programming a BEA Tuxedo Application Using C and Programming a BEA Tuxedo Application Using COBOL

• COBOL Language Bindings for the Workstation Component in Programming a BEA Tuxedo Application Using COBOL

• Writing Security Code So Client Programs Can Join the Application in Using BEA Tuxedo Security

• buildclient(1) in BEA Tuxedo Command Reference