Skip navigation.

Administration Console Online Help

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

BEA Administration Console Product Overview

The BEA Administration Console supports high performance client-server applications. It is a powerful, intuitive solution that lets you configure and manage your company's BEA Tuxedo applications.

Based on Java and Web technology, the BEA Administration Console lets you operate your BEA Tuxedo domains from virtually anywhere—even from home, given security authorization.

This topic includes the following sections:

 


Administration Through the Web

The BEA Administration Console is a Java-based applet that you can download into your Internet browser and use to remotely manage BEA Tuxedo system applications.

The BEA Administration Console simplifies many of the system administration tasks required for managing multiple-tier systems. It lets you monitor system events, manage system resources, create and configure administration objects, and view system statistics.

As system administrator, your tasks include planning, implementing, setting up, and maintaining the operation of an application built on the BEA Tuxedo system. Your application might be as simple as a single client and server operating entirely on one machine, or it might be more complex due to one of the following circumstances:

Where to Get More Information

If you are new to the BEA Tuxedo systems, make sure you are familiar with the concepts discussed in the Introducing the BEA Tuxedo System, Setting Up a BEA Tuxedo Application, Administering a BEA Tuxedo Application at Run Time, and Using the BEA Tuxedo Domains Component, which are on the online documentation CD, before using the BEA Administration Console.

To work with the BEA Tuxedo system resources provided through the BEA Administration Console, you should become familiar with the BEA Tuxedo system online documentation. For additional reading recommendations, see the introductory chapter, About This Online Help.

 


System Requirements

This section lists the hardware, operating system resources, and browser you must provide to support the BEA Administration Console.

Hardware Requirements

To run the BEA Administration Console, you need a color display device that meets the following requirements:

Operating System Requirements

Given the broad outlines of an application design, you must verify the availability of operating system resources needed to support your application. Operating system resources include:

For additional information about IPC parameters and other system tunables, see Installing the BEA Tuxedo System.

Browser Requirements

Although any Java capable Web browser might be able to run the Administration Console, at this time BEA supports only the following browsers:

 


Installation

The BEA Administration Console is automatically installed when you install the BEA Tuxedo software. For more information, see Installing the BEA Tuxedo System.

 


Setting Up Your Environment for the BEA Administration Console

Make sure that the TUXDIR environment variable is set to the directory in which you installed BEA Tuxedo software. For UNIX systems, if you installed BEA 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 BEA Tuxedo in the default directory, it is automatically set to TUXDIR=c:\TUXn (where n represents the release of BEA Tuxedo being installed).

To run the BEA Administration Console, you need to set up two servers:

Starting tuxwsvr

To start tuxwsvr on a UNIX system, enter the following command:

tuxwsvr -l //machine:port -i $TUXDIR/udataobj/tuxwsvr.ini

To start tuxwsvr on a Windows 2000 system, enter the following command at a command prompt:

tuxwsvr -l //machine:port -i %TUXDIR%\udataobj\tuxwsvr.ini

The BEA 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 BEA Tuxedo Command Reference.

Starting wlisten

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:

NADDR=//popeye:6060

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 BEA Tuxedo Command Reference.

To start the wlisten process, enter the following command:

wlisten

 


Configuring the Administration Console

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 BEA Tuxedo Administration Console.

 


Starting the BEA Administration Console

To start the BEA Administration Console, follow these steps:

  1. Start a Web browser.
  2. Enter the following URL (uniform resource locator):
  3. http://<machine_name>:<port>/webguitop.html

    Use of this URL depends on the following assumptions:

    The BEA Administration Console entry page is displayed, including warranty and license notices.

MEF(Issue): Need new screen shot for Taurus.

Figure 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 BEA Administration Console Entry Page

BEA Administration Console Entry Page


 
  1. To start the BEA Administration Console, scroll down to the bottom of the page and click the Click Here to Run the BEA Administration Console button.
  2. The BEA Administration Console Login window is displayed.

    BEA Administration Console Entry Page


     
  3. 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 BEA Tuxedo is installed.
  4. The main BEA Administration Console window is displayed.

    Figure 1-2 illustrates the Administration Console main window that displays after you complete your login.

    Figure 1-2 BEA Administration Console Main Window

    BEA Administration Console Main Window


     


     

    Table 1-1 Accessing Information About the BEA Administration Console Main Window 

    If . . .

    Then . . .

    The main window is displayed and you want to start working with the GUI.

    Refer to the section BEA Administration Console Tutorial on page 1-9.

    The main window is displayed and you want to read a description about it's features.

    Refer to the section A Tour of the Main Window on page 2-1.

    The main window does not display and the Connect Failed error message is displayed.

      1. Use the ps command to verify that the wlisten process is running.

      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. Enter wlisten again:
      $ wlisten -i $TUXDIR/udataobj/webgui/webgui.ini

      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.

      6. Return to step 1 above.


     

You have successfully started the BEA Administration Console. Now you can start setting up a single-machine domain environment for the simpapp sample application provided with your BEA Tuxedo software.

 


Exiting the BEA Administration Console

To exit the BEA Administration Console, select Domain—>Exit from the menu bar. This closes the current domain and exits the BEA Administration Console applet.

 


BEA Administration Console Tutorial

This tutorial provides a step-by-step procedure for using the BEA Administration Console to configure a single-machine domain for either a BEA Tuxedo ATMI or CORBA environment.The tutorial includes the simpapp sample application, which is provided with your BEA Tuxedo software.

Note: To learn more about the simpapp domain, refer to the appropriate README file in one of the following BEA Tuxedo sample application directories:

Step 1: Set Up Your Environment

To set up your sample application environment, follow these steps:

  1. Create a new directory called simpapp:

    Platform

    Command

    UNIX

    mkdir simpapp

    Windows 2000

    md simpapp

  2. Change to the simpapp directory:
  3. cd simpapp
  4. Depending on the operating system, set and export your environment variables:

    Platform

    Command

    UNIX

    • Set TUXDIR to your BEA Tuxedo installation directory

    • Set TUXCONFIG to the `pwd'/tuxconfig directory (simpapp)

    • Add $TUXDIR/bin to the beginning of PATH

    • Add $TUXDIR/lib to the beginning of LD_LIBRARY_PATH

    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.

    Windows 2000

    • Set TUXDIR to the BEA Tuxedo installation directory

    • Set APPDIR to the current application directory (simpapp)

    • Set TUXCONFIG to the %APPDIR%\TUXCONFIG directory

    Note: You can also use the setenv.cmd script in the %TUXDIR%\samples\atmi\simpapp directory to automatically set the simpapp environment variables.

  5. 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.
  6. Copy the simpapp domain to your current application directory (simpapp):

    Platform

    Command

    UNIX

    ATMI

    cp $TUXDIR/samples/atmi/simpapp/* .

    CORBA

    cp $TUXDIR/samples/corba/simpapp/* .

    Windows 2000

    ATMI

    xcopy %TUXDIR%\samples\atmi\simpapp\*

    CORBA

    xcopy %TUXDIR%\samples\corba\simpapp\*

  7. Change the permissions on all sample application files to allow full access:

    Platform

    Command

    UNIX

    chmod 777 *

    Windows 2000

    attrib -R /S *.*

  8. Depending on the BEA Tuxedo environment, build the client by entering one of the following commands from the current application directory:

    Environment

    Command

    ATMI

    buildclient -o simpcl -f simpcl.c

    CORBA

    buildobjclient -o simple_client -f "simple_c.cpp simplec.cpp"

  9. Depending on the BEA Tuxedo environment, build the server by typing one of the following commands from the current application directory

    Environment

    Command

    ATMI

    buildserver -o simpserv -f simpserv.c -s TOUPPER

    CORBA

    buildobjserver -o simple_server -f "simple_c.cpp simple_s.cpp
    simple_i.cpp simples.cpp"

  10. Start the Web server by entering the following command:
  11. 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.

    Platform

    Command

    UNIX

    tuxwsvr -l //machine1:8080 -i $TUXDIR/udataobj/tuxwsvr.ini

    Windows 2000

    tuxwsvr -l //machine1:8080 -i %TUXDIR%\udataobj\tuxwsvr.ini

  12. If you get the following error message:
  13. Could not establish listening endpoint

    you must use a port number other than 8080. Select a valid number that is not already being used.

  14. Start the wlisten process by typing the following command:
  15. wlisten
  16. If the wlisten process starts, skip to the next step.
  17. 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.

  18. Start the browser. In this example, we are using Netscape Navigator 4.73 on a machine running Windows 2000.
  19. Enter the following URL:
  20. 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

    The initial BEA window is displayed, including the BEA logo and several legal notices.

  21. Scroll to the bottom of the window and click the Click Here to Run the BEA Administration Console button.
  22. After the page reloads, the LOGIN window is displayed.

  23. Enter your login name and the tlisten password after the appropriate prompts, then click on the LOGIN button. As shown in Figure 1-2, BEA Administration Console Main Window, on page 1-7, the BEA 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

Step 2: Create a New Domain

To create a new domain, follow these steps:

  1. From the main window menu bar, select Domain —>New.
  2. BEA Administration Console Main Window


     
  3. On the Create New Object window, enter the values indicated in the appropriate fields, as shown in Figure 1-3.
  4. Figure 1-3 Create New Object Window

    Create New Object Window


     
  5. Leave the remaining fields blank and click Create.
  6. If successful, a window displays the following message:

    The SET operation was successful.
  7. Click OK to close the window.
  8. Note: If you get an error message, enter a different value in the IPC Key field.

    As shown in the following figure, the tree view area of the main window displays the newly created simpapp domain.

    Create New Object Window


     

Step 3: Add GROUP1 to the 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.
  4. Create New Object Window


     
  5. Right-click the Groups folder to display the Quick Menu, and then select New.
  6. When the Create New Object window is displayed, enter the appropriate values shown in the appropriate fields and click Create.
  7. Create New Object Window


     
  8. When the operation has succeeded, click OK to close the confirmation window.

Step 4: Add Server simpserv to GROUP1

To add the simpserv server to GROUP1, follow these steps:

  1. In the tree, expand the Groups folder to view GROUP1.
  2. Expand GROUP1 to display the folders for Servers and Transactions.
  3. Right-click the Servers folder to display the Quick Menu, and then select New to display the Create New Object window.
  4. Create New Object Window


     
  5. Enter the appropriate values as shown in the figure above, and then click Create.
  6. When the operation has succeeded, a confirmation message window is displayed. Click OK to close the window.

Step 5: Activate the simpapp Domain

To activate the simpapp domain, follow these steps:

  1. Click the Activate toolbar button to display the Activate Objects window.
  2. Create New Object Window


     
  3. Click the Activate button. The Progress of Activate (Entire Domain) window is displayed, as shown in the following figure.
  4. Create New Object Window


     
  5. When the "Activation has completed successfully" message displays, click Dismiss to close the window.

Step 6: Run simpapp

To run simpapp, follow these steps:

  1. Expand the Servers folder. The Tree will display the simpserv server in an active state.
  2. From a command prompt, execute the client by entering the following command:
  3. simpcl "hello"
  4. If simpcl runs successfully, it will display the following output:
  5. Returned string is: HELLO
  6. Select the simpserv server from the tree. Notice that the Configuration Tool is updated with the current parameters for the simpserv server.
  7. Click the Deact toolbar button (Deactivate) to display the Deactivate Objects window.
  8. Create New Object Window


     
  9. Select the Force deactivation even if clients remain check box.
  10. Click Deactivate to start the deactivate process and to display the Progress of Deactivate (Entire Domain) window.
  11. When you see the confirmation message, "Deactivation has completed successfully," click Dismiss to close the window.
  12. To exit the BEA Administration Console applet, select Domain—>Exit from the menu bar.

You have successfully configured and run simpapp through the BEA Administration Console. Now you can start setting up your environment for your own application domain.

 

Skip navigation bar  Back to Top Previous Next