The following sections describe some basic differences between using Oracle Tuxedo ATMI on a UNIX server system and using Oracle Tuxedo ATMI on a Windows Server 2003 system:
Keep in mind the following general considerations when using Oracle Tuxedo ATMI on a Windows system:
C:) for all fully qualified paths.
.exesuffix for executable files. The suffix is always implied for Oracle Tuxedo ATMI for Windows.
.dllidentify dynamically-linked libraries; names ending in
.libidentify statically linked and imported libraries; names ending in
.cmdidentify command scripts.
%TUXDIR%\bin. Statically-linked libraries are located in
Keep in mind the following configuration issues when setting up the Oracle Tuxedo ATMI software on a Windows Server 2003 system:
OPENINFOstring in the Oracle Tuxedo configuration file (
UBBCONFIG) must be presented in the following format:
|Note:||The first separator in the preceding string is a colon; subsequent separators are semicolons.|
MACHINES section of the configuration file, include the following three entries:
|Note:||These entries require different settings on a UNIX system.|
Whenever you create a configuration file for an environment with both UNIX and Windows systems, include these entries in the
MACHINES section for every Windows Server 2003 node in your configuration.
For reliability purposes, Oracle recommend that you do not use network drives. If, however, you try to start an Oracle Tuxedo ATMI application on a Windows Server 2003 machine in which the
TUXCONFIG file resides on a network drive, you must set the following permissions:
tuxipcservice startup options, the
ENTRYoption must have
Log On As This Account. The password must be the same as the administrator’s so that the
tuxipcservice has full administrator access rights.
When allocating and releasing memory buffers on a Windows Server 2003 system, make sure each memory buffer is released from the same heap in which it was allocated. If it is not, a segmentation fault occurs.
For example, a memory buffer that is allocated using
Falloc() must be released using
Ffree(). If a memory buffer allocated with
malloc() is freed using
Ffree(), a segmentation fault occurs. The
free() routine must be used, in the latter case, to free the memory buffer.
For more information about Falloc, Falloc32(3fml)and Ffree, Ffree32(3fml), see Oracle Tuxedo ATMI FML Function Reference. For more information about
free(), see the documentation delivered with your operating system.
bankapp program is a small example application bundled with Oracle Tuxedo ATMI for Windows Server 2003. Besides demonstrating the operation of Oracle Tuxedo ATMI and providing an example of Oracle Tuxedo ATMI application code, the
%APPDIR%\UBB file generated by the
bankapp driver (
driver.exe is located in
%TUXDIR%\APPS\bankapp\2003\driver) can act as a template for configurations for any new applications.
When Oracle Tuxedo ATMI is installed on a Windows Server 2003 server system, it may be useful to configure the machine to start an Oracle Tuxedo ATMI application automatically when booting up your system using the
srvany.exe utility program provided in Microsoft’s Resource Kit for Windows 2003. For configuration instructions, see
To ensure proper operation of Oracle Tuxedo ATMI programs that start automatically when booting up, you must set the Oracle Tuxedo system environment variables
%NLSPATH%. Set these variables using the conventional Windows 2003 method or by using the Oracle Administration program, as explained in Setting and Modifying Environment Variables.
For information about installing Oracle Tuxedo ATMI on a Windows Server 2003 system, see Installing the Oracle Tuxedo System. For more information about the Oracle Tuxedo system, see the following documents: