| 
      
           
         | 
        
           
         | 
        
           
         | 
        
           
         | 
      
If you are new to the Oracle Tuxedo systems, make sure you are familiar with the concepts discussed in the Introducing the Oracle Tuxedo System, Setting Up an Oracle Tuxedo Application, Administering an Oracle Tuxedo Application at Run Time, and Using the Oracle Tuxedo Domains Component, which are on the online documentation CD, before using the Oracle Administration Console.
 • For additional information about IPC parameters and other system tunables, see Installing the Oracle Tuxedo System.The Oracle Administration Console is automatically installed when you install the Oracle Tuxedo software. For more information, see Installing the Oracle Tuxedo System.Make sure that the TUXDIR environment variable is set to the directory in which you installed Oracle Tuxedo software. For UNIX systems, if you installed Oracle Tuxedo in the default directory, set TUXDIR to /usr/local/TUXDIR. Don’t forget to export TUXDIR if you are using a UNIX system. For Windows 2000 systems, if you installed Oracle Tuxedo in the default directory, it is automatically set to TUXDIR=c:\TUXn (where n represents the release of Oracle Tuxedo being installed).
 • tuxwsvr—a Web server provided with the Oracle Tuxedo system software. You are not required to use this server and can use your own commercial Web server.
 • wlisten—a server required to administer the Oracle Administration Console. It must be run on the master machine in a multi-machine configuration. This machine must be able to support a Java capable browser.To start tuxwsvr on a UNIX system, enter the following command:To start tuxwsvr on a Windows 2000 system, enter the following command at a command prompt:The Oracle Tuxedo installation procedure creates the tuxwsvr.ini file. Usually, you do not need to edit this file—except under certain circumstances. For example, you may decide to move your Java files to a non-default directory. In that case, you would need to edit the pathnames in the initialization file appropriately. For details, refer to the tuxwsvr(1) reference page in the Oracle Tuxedo Command Reference.Before starting wlisten, check the webgui.ini file to verify that the default values assigned to the parameters during installation are appropriate; otherwise, make the appropriate changes. For example, on a machine called “popeye,” the default port assigned to wlisten is 4003. To run wlisten with port 6060, edit the NADDR parameter as follows:Depending on your system, webgui.ini is located in the following locations:Windows 2000 systems: %TUXDIR%\udataobj\webgui\UNIX systems: $TUXDIR/udataobj/webgui/For details about other parameters in the webgui.ini file, refer to the wlisten(1) reference page in the Oracle Tuxedo Command Reference.To start the wlisten process, enter the following command:Some features of the Administration Console, such as the level of encryption used for communication between the Administration Console applet and the Administration Console server, are configured by settings in the webgui.ini file. For more information, refer to Appendix A, “Configuring the Oracle Tuxedo Administration Console”.
 •
 •
 Note: If you are using a commercial browser on the default port (8080), you can use something like the following URL:
http://gumby:8080/webguitop.htmlFigure 1‑1 shows the Administration Console splash screen, including the button that starts the Administration Console, which is located at the bottom of the entry page.Figure 1‑1 Oracle Administration Console Entry Page
 4. Enter your login name and password in the appropriate fields, and click LOGIN. The password must be one of the entries in the tlisten.pw file, which is located in the udataobj directory where Oracle Tuxedo is installed.Figure 1‑2 illustrates the Administration Console main window that displays after you complete your login.Figure 1‑2 Oracle Administration Console Main Window
 Table 1‑1 shows the accessing information about the Oracle Administration Console Main Window. The main window does not display and the Connect Failed error message is displayed.
 1.
 2. If wlisten is not running, open the webgui.ini file, and in the line
NADDR=//<machine_name>:4003
replace the port number (4003) with a valid port number.
 3.
 4. Check that the tuxwsvr process is running at the port as described in the URL.
 5. Verify the password. It must match one of the entries in the tlisten.pw file in the $TUXDIR/udataobj directory.You have successfully started the Oracle Administration Console. Now you can start setting up a single-machine domain environment for the simpapp sample application provided with your Oracle Tuxedo software.This tutorial provides a step-by-step procedure for using the Oracle Administration Console to configure a single-machine domain for either a Oracle Tuxedo ATMI or CORBA environment.The tutorial includes the simpapp sample application, which is provided with your Oracle Tuxedo software.
 Note: To learn more about the simpapp domain, refer to the appropriate README file in one of the following Oracle Tuxedo sample application directories:
 • ATMI: $TUXDIR/samples/atmi/simpapp
 • CORBA: $TUXDIR/samples/corba/simpapp
 1. Create a new directory called simpapp:
 2. Change to the simpapp directory:
 • Set TUXDIR to your Oracle Tuxedo installation directory
 •
 •
 •
 Note: If you are running the HP-UX operating system (OS), set SHLIB_PATH; if you are running the AIX OS, set LIBPATH, instead of LD_LIBRARY_PATH.
 • Set TUXDIR to the Oracle Tuxedo installation directory
 •
 •
 Note: You can also use the setenv.cmd script in the %TUXDIR%\samples\atmi\simpapp directory to automatically set the simpapp environment variables.
 4. For Windows 2000, make sure you have installed MS Visual C++ 6.0 so that the PATH variable includes msdev\bin and the LIB variable includes msdev\lib.
 5.
 Note: In this tutorial, the name of the machine is machine1 and the port assigned to the Web server is 8080. You can use 8080 for the port if you have not already used it for another Web server.
 12. If the wlisten process starts, skip to the next step.
 Note: If the wlisten process does not start, edit the line, NADDR=//machine1:4003
in the $TUXDIR/udataobj/webgui/webgui.ini file by replacing the port number (4003) with a valid port number. Then run wlisten again.http://machine1:8080/webguitop.html
 Note: If you are using a Web server on the default port (8080), you can use the following URL: http://machine1/webguitop.html
 15. Scroll to the bottom of the window and click the Click Here to Run the Oracle Administration Console button.
 16. Enter your login name and the tlisten password after the appropriate prompts, then click on the LOGIN button. As shown in Figure 1‑2, “Oracle Administration Console Main Window,” on page 1‑7, the Oracle Administration Console main window is displayed in your browser.For a complete description of the main window, refer to the section “A Tour of the Main Window” on page 2‑1
 2. Figure 1‑3 Create New Object WindowAs shown in the following figure, the tree view area of the main window displays the newly created simpapp domain.To add GROUP1 to the simpapp domain, follow these steps:
 1. Expand the tree by clicking on the plus sign (+) in front of the simpapp domain name. The tree view displays the listings for the Machines and Service Defaults folders.
 2. Expand the Machines folder to display the inactive SITE1 machine.
 3. Expand the SITE1 machine to display the administrative objects under its control, as shown in the following figure.To add the simpserv server to GROUP1, follow these steps:To activate the simpapp domain, follow these steps:To run simpapp, follow these steps:
 1. Expand the Servers folder. The Tree will display the simpserv server in an active state.
 3. If simpcl runs successfully, it will display the following output:
 4. Select the simpserv server from the tree. Notice that the Configuration Tool is updated with the current parameters for the simpserv server.You have successfully configured and run simpapp through the Oracle Administration Console. Now you can start setting up your environment for your own application domain.