The following sections describe additional information about using the Oracle Tuxedo ATMI Workstation component on a Windows XP or Windows Server 2003 system:
The Windows instantiation of the Workstation client offers significant benefits to application developers:
The software prerequisites for running the Workstation component on a Windows system are as follows:
You can develop client programs targeted for Windows workstations in the same way that you would develop native client programs within the Oracle Tuxedo system administrative domain. All the ATMI functions are available.
Interoperability between Oracle Tuxedo release 7.1 and later Workstation clients and applications based on pre-7.1 releases of the Oracle Tuxedo system is supported in any of the following situations:
An Oracle Tuxedo release 7.1 or later Workstation client with multiple threads in a single context cannot interoperate with a pre-7.1 release of the Oracle Tuxedo system.
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 Component” in Programming an Oracle Tuxedo ATMI Application Using COBOL.
Use buildclient(1) with the
-w flag to link-edit your client programs.
You can also build Oracle Tuxedo clients without using the
buildclient(1) utility. If you are using Microsoft Visual C++ projects, use the following settings:
In addition, set the
PATH search directories appropriately.
atmi/ws directory contains several different windows platform
.mak files for creating GUI atmi clients. For an example of how these files may be used, see Full C Application in Tutorials for Developing Oracle Tuxedo ATMI Applications.
When you run client programs, your
PATH must includo
The Oracle Tuxedo libraries (DLLs) prior to Oracle 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 Oracle Tuxedo calls (such as ATMI, FML,
userlog(), and so on).
To join an Oracle Tuxedo application, a multithreaded Workstation client must always call tpinit(3c) with the
TPMULTICONTEXTS flag set, even if the client is running in single-context mode.