BEA Logo BEA Tuxedo Release 7.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   Tuxedo Doc Home   |   Programming   |   Topic List   |   Previous   |   Next   |   Contents

   Using the BEA Tuxedo Workstation Component

Writing Client Programs

You can develop client programs targeted for Windows workstations in the same way that you would develop native client programs within the BEA Tuxedo system administrative domain. All of the ATMI functions are available.

Interoperability Restrictions for Workstation Clients

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:

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.

Building Client Programs

To compile client programs written in C, you can use any compiler that can read Microsoft C import libraries. To compile COBOL source programs that call the ATMI, use the LITLINK option of the COBOL compiler. For details, see COBOL Language Bindings for the Workstation Component in Programming a BEA Tuxedo Application Using COBOL.

Use buildclient(1) with the -w flag to link-edit your client programs.

You can also build BEA Tuxedo clients without using the buildclient(1) utility. If you are using Microsoft Visual C++ projects, use the following settings:

In addition, set the INCLUDE, LIB, and PATH search directories appropriately.

Runtime

When you run client programs, your PATH must include %TUXDIR%\bin.

Limitations

The BEA Tuxedo libraries (DLLs) prior to BEA Tuxedo Release 7.1 are not thread-safe. For applications written using the pre-Release 7.1 DLLs, threads should not be used; otherwise, threaded access is serialized through all BEA Tuxedo calls (such as ATMI, FML, userlog(), and so on).

See Also