Using Oracle Tuxedo ATMI on Windows Server 2003

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:

•	Windows Considerations

•	Configuration Issues

•	Specifying Machine Type and User ID Numbers

•	Using Network Drives

•	Using the bankapp Driver

•	Starting Oracle Tuxedo ATMI Applications Automatically

Windows Considerations

Keep in mind the following general considerations when using Oracle Tuxedo ATMI on a Windows system:

•	When you specify pathnames, use a back slash (\), not a forward slash (/) to delimit file and directory names. Use a drive letter (such as C:) for all fully qualified paths.

•	You do not need to specify the .exe suffix for executable files. The suffix is always implied for Oracle Tuxedo ATMI for Windows.

•	Filenames follow Windows naming conventions. For instance, names ending in .dll identify dynamically-linked libraries; names ending in .lib identify statically linked and imported libraries; names ending in .cmd identify command scripts.

•	All Oracle Tuxedo system executables, command scripts, and dynamically-linked libraries are located in %TUXDIR%\bin. Statically-linked libraries are located in %TUXDIR%\lib.

Configuration Issues

Keep in mind the following configuration issues when setting up the Oracle Tuxedo ATMI software on a Windows Server 2003 system:

•	Server names are case sensitive.

•	The names of Windows Server 2003 machines specified in Oracle Tuxedo ATMI application files should always be spelled in uppercase.

•	The OPENINFO string in the Oracle Tuxedo configuration file (UBBCONFIG) must be presented in the following format:

OPENINFO="resource managers:resource(s)"

For example:

OPENINFO="TUXEDO\SQL:APPDIR1\bankdl3;bankdb;readwrite"

Note:

The first separator in the preceding string is a colon; subsequent separators are semicolons.

Specifying Machine Type and User ID Numbers

In the MACHINES section of the configuration file, include the following three entries:

•	TYPE="WinNT"

•

UID=0

•

GID=0

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.

Using Network Drives

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:

•	The network drive must be connected as Administrator.

•	The administrator must use the same password on the local and remote systems.

•	In the tuxipc service startup options, the ENTRY option must have Administrator set for Log On As This Account. The password must be the same as the administrator’s so that the tuxipc service has full administrator access rights.

Allocating and Releasing Memory Buffers

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 malloc() and free(), see the documentation delivered with your operating system.

Using the bankapp Driver

The 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.

Starting Oracle Tuxedo ATMI Applications Automatically

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 srvany.wri and rktools.hlp.

To ensure proper operation of Oracle Tuxedo ATMI programs that start automatically when booting up, you must set the Oracle Tuxedo system environment variables %TUXDIR% and %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” on page 2‑4.

See Also

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:

•	Setting Up an Oracle Tuxedo Application

•	Administering an Oracle Tuxedo Application at Run Time

•	Using the Oracle Tuxedo ATMI Workstation Component

•	Oracle Tuxedo Command Reference

•	Oracle Tuxedo ATMI C Function Reference

•	Oracle Tuxedo ATMI COBOL Function Reference

•	Oracle Tuxedo ATMI FML Function Reference

•	Oracle Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference