|
|
The following sections describe some basic differences between using BEA Tuxedo ATMI on a UNIX server system and using BEA Tuxedo ATMI on a Windows Server 2003 system:
Keep in mind the following general considerations when using BEA Tuxedo ATMI on a Windows system:
C:) for all fully qualified paths..exe suffix for executable files. The suffix is always implied for BEA Tuxedo ATMI for Windows..dll identify dynamically-linked libraries; names ending in .lib identify statically linked and imported libraries; names ending in .cmd identify command scripts.%TUXDIR%\bin. Statically-linked libraries are located in %TUXDIR%\lib.
Keep in mind the following configuration issues when setting up the BEA Tuxedo ATMI software on a Windows Server 2003 system:
OPENINFO string in the BEA Tuxedo configuration file (UBBCONFIG) must be presented in the following format: OPENINFO="resource managers:resource(s)"
OPENINFO="TUXEDO\SQL:APPDIR1\bankdl3;bankdb;readwrite"
| Note: | The first separator in the preceding string is a colon; subsequent separators are semicolons. |
In the 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, BEA recommend that you do not use network drives. If, however, you try to start a BEA 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:
Administrator.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.
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 BEA Tuxedo ATMI FML Function Reference. For more information about malloc() and free(), see the documentation delivered with your operating system.
The bankapp program is a small example application bundled with BEA Tuxedo ATMI for Windows Server 2003. Besides demonstrating the operation of BEA Tuxedo ATMI and providing an example of BEA 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 BEA Tuxedo ATMI is installed on a Windows Server 2003 server system, it may be useful to configure the machine to start a BEA 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 BEA Tuxedo ATMI programs that start automatically when booting up, you must set the BEA Tuxedo system environment variables %TUXDIR% and %NLSPATH%. Set these variables using the conventional Windows 2003 method or by using the BEA Administration program, as explained in Setting and Modifying Environment Variables.
For information about installing BEA Tuxedo ATMI on a Windows Server 2003 system, see Installing the BEA Tuxedo System. For more information about the BEA Tuxedo system, see the following documents:
|