The following sections describe how to configure Oracle Tuxedo ATMI on a Windows Server 2003 system:
1. Figure 2‑1 Microsoft Windows Control PanelThe Machines page of the Oracle Administration window enables you, as the Oracle Tuxedo system administrator, to access any machine (where you have login privileges) on the Microsoft Windows Network running Microsoft Windows Server 2003. You can then set environment variables remotely; determine the location of Oracle Tuxedo event logging; add, remove, stop, or start tlisten services; and tune IPC resources.
2. 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 Oracle Administration window will take place on the selected machine (intrepid in this example).The Logging page enables you to direct Oracle Tuxedo system messages to the Event Log on your Windows Server 2003 system, to the traditional user log (ULOG) disk file, or both.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.If you want to set up the traditional user log (ULOG) messages, perform the following steps to select a storage directory:
2. Select the name of the directory in which you want ULOG messages to be stored.
3. 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.
1. From the Windows Server 2003 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 WindowFigure 2‑6 Event Detail Window
• 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.During the Oracle Tuxedo installation, the installer program installed a Tlisten service on your Windows Server 2003 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 Oracle Tuxedo application before the Oracle 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 Oracle Tuxedo Command Reference.
1. 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 Oracle Tuxedo application running on your machine.)
2. 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.On most machines, Oracle 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 an Oracle Tuxedo application, see the following table and “Checking IPC Requirements” in Installing the Oracle Tuxedo System. The following table maps the names of the IPC Resources on a Windows Server 2003 system to the traditional names on a UNIX system.
5. Stop and restart the Oracle 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 Oracle 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 Oracle 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 Oracle Tuxedo application on the Windows Server 2003 Performance Monitor. Choose Start → Programs → Administration Tools → Performance Monitor to launch the Performance Monitor window.Figure 2‑9 Performance Monitor
• To view this structure, choose Start → Run to launch the Run dialog box, enter regEdt32, and click OK to launch the Registry Editor window.
• Any user who runs tlisten(1) must have read access permissions.Oracle recommends that the Administrator have full control permissions.