Configuring BEA Tuxedo ATMI for Windows 2000

e-docs > Tuxedo > Using Tuxedo ATMI on Windows > Configuring BEA Tuxedo ATMI for Windows 2000

Using Tuxedo ATMI on Windows

Configuring BEA Tuxedo ATMI for Windows 2000

The following sections describe how to configure BEA Tuxedo ATMI on a Windows 2000 server system:

Introducing the BEA Administration Program

In addition to the BEA Tuxedo Administration Console, the BEA Tuxedo 7.1 or later software for Windows provides a BEA Administration program and two Windows services (Tlisten and BEA procMGR) for configuring the BEA Tuxedo system on a Windows 2000 system. Only if the installation included BEA Tuxedo server components will these additional administration tools be installed on the Windows 2000 system.

Note: The BEA Tuxedo Administration Console offers extensive online help: instructions for all the administrative tasks that can be performed through the console, plus reference information for all configuration tool folders. For information about how to use the BEA Tuxedo Administration Console, see BEA Tuxedo Administration Console Online Help.

Invoking the BEA Administration Program

With BEA Tuxedo release 7.1 or later software installed on your Windows 2000 system, perform the following steps to access the BEA Administration program:

Choose Start —> Settings —> Control Panel to launch the Control Panel.
Figure 2-1 Microsoft Windows Control Panel
In the Control Panel, double-click the BEA Administration icon to launch the BEA Administration window.
Figure 2-2 BEA Administration Window with Machines Page Displayed

You can use the BEA Administration window to perform the following tasks:

Accessing Other Machines on a Network

The Machines page of the BEA Administration window enables you, as the BEA Tuxedo system administrator, to access any machine (where you have login privileges) on the Microsoft Windows Network running Microsoft Windows 2000. You can then set environment variables remotely; determine the location of BEA Tuxedo event logging; add, remove, stop, or start tlisten services; and tune IPC resources.

To access a remote machine, locate and click the machine's icon on the network tree. If you know the name of a remote machine, but do not know its work group, perform the following steps to select it:

In the lower right-hand corner of the Machines page, click Select to display the Enter Machine Name dialog box.
In the Enter Machine Name dialog box, enter the name of the remote machine (for example, \\intrepid) and click OK.

At this point, all subsequent actions performed on other pages (Environment, Logging, Listener, and IPC Resources) in the BEA Administration window will take place on the selected machine (intrepid in this example).

Setting and Modifying Environment Variables

The Environment page enables you to view, set, or modify BEA Tuxedo environment variables on your Windows 2000 system.

Figure 2-3 BEA Administration Window with Environment Page Displayed

To add, modify, or delete environment variables using the Environment page, follow these steps.

To add a variable, enter its name in the Variable field and its value in the Value field, and then click Set.
To modify a variable, select the variable, enter its new value in the Value field, and then click Set.
To delete a variable, select the variable you want to delete and then click Delete.
Click OK or Apply to write your changes to the Windows 2000 Registry.

Directing BEA Tuxedo Messages to the Windows 2000 Event Log

The Logging page enables you to direct BEA Tuxedo system messages to the Event Log on your Windows 2000 system, to the traditional user log (ULOG) disk file, or both.

Figure 2-4 BEA Administration Window with Logging Page Displayed

You may select the Event Log option, the traditional user log (ULOG) Disk File option, or both. No setup is required for the Event Log.

Setting Up a ULOG

If you want to set up the traditional user log (ULOG) messages, perform the following steps to select a storage directory:

On the Logging page, click the arrow to the right of the Directory field to display a drop-down list of directories.
Select the name of the directory in which you want ULOG messages to be stored.
In the Prefix field, type a prefix for the name of the log file. The default prefix is ULOG, and the default file name is ULOG.mmddyy, where mmddyy is the month, day and year that the log file was created.
To save your selections to the Windows 2000 Registry, click OK or Apply.

Viewing Windows 2000 Event Log Entries

To view Windows 2000 Event Log entries, follow these steps:

From the Windows 2000 desktop, select Start —> Programs —> Administrative Tools —> Event Viewer to display a list of all the events that have occurred since the application booted.
Figure 2-5 Event Viewer Window
On the menu bar (across the top of the Event Viewer window), click Log to display a drop-down Log menu.
From the drop-down Log menu, choose Application. As a result of this selection, only application-specific events are listed in the Event Viewer window.
Double-click the entry for the event for which you want more information. The Windows 2000 Event Detail window appears, with information about the event you have specified.
Figure 2-6 Event Detail Window

This window provides the following information:

Date—date on which the event occurred.
Time—time at which the event occurred.
User—person using the software at the time the event occurred.
Computer—machine on which the event occurred.
Event ID—number under which the message is listed in System Messages.
Source—section of System Messages in which the event is described and an appropriate action is recommended.
Type—purpose of the message; specifically, whether the message is intended to provide information, a warning, or notification of an error.
Description—brief summary of the event.

Viewing ULOG Entries

A ULOG is a text file. You can use any text editor to open a ULOG and view its contents.

Configuring tlisten Processes to Start Automatically

The Listener page enables you to view, create, or modify Tlisten services on your Windows 2000 system.

Figure 2-7 BEA Administration Window with Listener Page Displayed

During the BEA Tuxedo installation, the installer program installed a Tlisten service on your Windows 2000 system. Each time you boot your system, the Tlisten service starts a tlisten process on port 3050 of your machine. The password associated with the tlisten process is the one you entered during the installation.

A tlisten process must be started on each machine of a networked BEA Tuxedo application before the BEA Tuxedo system and application servers can boot. You use the tlisten process to perform administrative actions across multiple machines. To learn more about tlisten processes, see tlisten(1)in BEA Tuxedo Command Reference.

To add, remove, stop, or start Tlisten services using the Listener page, follow these steps.

To add a Tlisten service, enter a port number in the Port Number field and then click Add. (Generally, you need one tlisten process for each BEA Tuxedo application running on your machine.)
To remove a Tlisten service, select the Tlisten service you want to delete and then click Remove.
To stop a Tlisten service that has been started, select the Tlisten service you want to stop and then click Stop.
To start a Tlisten service that has been stopped, select the Tlisten service you want to start and then click Start.
Click OK or Apply to write your changes to the Windows 2000 Registry.

Besides viewing and controlling Tlisten services using the Listener page, you can click Start —> Programs —> Administrative Tools —> Services to launch the Services window and then view and control Tlisten services via the Services window.

Configuring IPC Resources to Maximize System Performance

The IPC Resources page enables you to configure the interprocess communication (IPC) resources on your Windows 2000 system to maximize BEA Tuxedo performance.

Figure 2-8 BEA Administration Window with IPC Resources Page Displayed

During the BEA Tuxedo installation, the installer program installed a BEA ProcMGR service on your Windows 2000 system. Each time you boot your system, the BEA ProcMGR service configures the IPC resources on your machine to whatever values you set on the IPC Resources page. The values shown in the preceding display are the default IPC values set by the installer program.

On most machines, BEA ProcMGR runs as installed; however, you can use the IPC Resources page to tune the IPC resources and maximize performance. To determine the minimum IPC Resource values required for a BEA Tuxedo application, see the following table and Checking IPC Requirements in Installing the BEA Tuxedo System. The following table maps the names of the IPC Resources on a Windows 2000 system to the traditional names on a UNIX system.

Table 2-1 IPC Resource Name Mappings Between Windows and UNIX Systems

Windows 2000 Name	Traditional UNIX Name
Maximum Allowed Message Size	MSGMAX
Maximum Number of Message Headers	No matching name
Maximum Message Queue Size	MSGMNB
Maximum Number of Message Queues	MSGMNI
Size of Message Segment	MSGSSZ
Number of Message Segments	MSGSEG
Maximum Number of Processes Using IPC	NPROC
Maximum Number of Semaphores	SEMMNS
Maximum Number of Semaphore Sets	SEMMNI
Maximum Number of Semaphore Undo Structures	SEMMNU
Maximum Number of Processes Per Shared Segment	No matching name
Number of Shared Memory Segments	SHMMNI

To modify IPC Resource values using the IPC Resources page, follow these steps:

In the "Current Resource: Default box," click the Use Default IPC Settings check box to clear it. An insert box appears in the Current Resource: Default box.
Click the insert box, enter the name of your Windows 2000 machine, and press Enter.
Click the fields next to the IPC resources you want to change and enter the desired values.
Click OK or Apply to write your changes to the Windows 2000 Registry.
Stop and restart the BEA ProcMGR service to put your changes into effect: click Start —> Programs —> Administrative Tools —> Services to launch the Services window and then stop and restart the BEA ProcMGR via the Services window.

When interpreting the Maximum Number of Processes Using IPC parameter on the IPC Resources page, keep the following information in mind:

You must count any multicontexted BEA Tuxedo ATMI client multiple times. Your total should match the number of application associations (contexts) that can be outstanding concurrently.
You must count any multicontexted BEA Tuxedo ATMI server multiple times. Your total should match the number of contexts calculated by adding 1 to the value of MAXDISPATCHTHREADS in the target application's configuration (UBBCONFIG) file, where 1 represents the main dispatcher thread.

You can view the performance of a running BEA Tuxedo application on the Windows 2000 Performance Monitor. Choose Start —> Programs —> Administration Tools —> Performance Monitor to launch the Performance Monitor window.

Figure 2-9 Performance Monitor

Reviewing the Windows 2000 Registry Content

The Windows 2000 Registry is the repository for all hardware, software, and application configuration settings for the Windows 2000 system. During the BEA Tuxedo installation, the installer program writes general installation information as well as IPC Resource values to the Registry. The structure of the Registry relevant to BEA Tuxedo is as follows.

HKEY_LOCAL_MACHINE\Software\BEA Systems\Tuxedo\8.1\...

Developer
Environment
Security

To view this structure, choose Start —> Run to launch the Run dialog box, enter regEdt32, and click OK to launch the Registry Editor window.

Developer Key

The Developer key stores product information, including the major and minor version numbers of the release, and user and company names.

Environment Key

The Environment key stores the locations referenced by the BEA Tuxedo environment variables set on your Windows 2000 system. It also stores other values such as IPC resource settings.

Security Key

The Security key holds the access permissions for BEA Tuxedo processes and services. The following permissions are mandatory:

Any user who runs tlisten(1) must have read access permissions.
The account under which the BEA ProcMGR service is running must have read access permissions.

BEA recommends that the Administrator have full control permissions.