Chapter 4 . BEA Administration Console Startup

This chapter discusses the following topics:

• System Requirements

• Setting Up Your Environment

• Starting the BEA Administration Console

System Requirements

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

Platforms Supported

The BEA Administration Console runs on all server platforms that support the BEA M3 version 2.2 software. For a complete list of supported platforms, see the section "Supported Platforms" on page A-1.

Hardware Requirements

In addition to the hardware and software requirements for installing M3 client and server software on your particular platform (see Appendix A, "Platform Data Sheets"), the BEA Administration Console requires a color display device with the following capabilities:

• Resolution: 800 by 600 dpi or more is required; 1024 by 768 or more is recommended.

• Colors: 256 colors or more is recommended.

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:

• System shared resources (IPC), which control the maximum message size and maximum queue length, among other things

• Resources governed by kernel parameters

For information about setting Microsoft Windows NT IPC parameters, see the section "Maximizing System Performance" on page 5-9.

For information about setting UNIX system IPC parameters, see the section "Verifying IPC Requirements" on page 5-18.

For more information about system tuning parameters for a particular platform, see Appendix A, "Platform Data Sheets."

Browser Requirements

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

• Netscape Navigator 4.05 Gold

• Microsoft Internet Explorer 4.0

For up-to-date information about other supported Web browsers, see the M3 Release Notes on the Customer Support section of the BEA Web site:

http://www.beasys.com/

Setting Up Your Environment

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

• tuxwsvr
  A Web server provided with the M3 system software. (You are not required to use this server; you may, if you prefer, use your own commercial Web server.)

  wlisten

  A server required to administer the BEA Administration Console. It should be run on the master machine.

  Note: You can use any machine that supports a Java capable browser for performing M3 system administration through the BEA Administration Console.

Starting tuxwsvr

To start tuxwsvr on UXIX systems, enter:

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

To start tuxwsvr on Microsoft Windows NT systems:

1. Open an MS-DOS window.

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

During installation, the tuxwsvr.ini file is created. Usually, you do not need to edit this file. Under certain circumstances, however, you may want to edit this file. For example, you may decide, after installation, to move your Java files to a nondefault directory. In that case, you would need to edit the pathnames in the initialization file appropriately. For details, see the tuxwsvr(1) reference page in the BEA TUXEDO Reference.

Starting wlisten

To start wlisten, proceed as follows:

1. Before starting wlisten, check the webgui.ini file (located in M3DIR\udataobj\webgui for Microsoft Windows NT systems and in M3DIR/udataobj/webgui for UNIX systems) to make sure that the default values assigned to the parameters during installation are appropriate. Otherwise, make the appropriate changes.

2. 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 line in the webgui.ini file, as follows:

   NADDR=//popeye:6060

   For details about other parameters in the webgui.ini file, see the wlisten(1) reference page in the BEA TUXEDO Reference.

3. Start the wlisten process:

   $ wlisten

To start the BEA Administration Console, proceed as follows:

1. Start the browser.

2. Enter the following URL:

   http://<machine_name>:<port>/webguitop.html

   Use of this URL depends on the following assumptions:

   • You are using tuxwsvr with the file tuxwsvr.ini.

   • The webgui.ini file is in the default location, M3DIR/udataobj/webgui.

     Note: If you are using a commercial browser on the default port (8080), you can use something like the following URL:
     
http://ctomsn:8080/webguitop.html

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

   

3. To start the BEA Administration Console, click the prompt at the bottom of the screen. The Login window is displayed.

   

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 in the M3DIR/udataobj directory. The main window of the BEA Administration Console is displayed.

   

   Note: Refer to Table 4-1 for instructions for accessing additional information about the BEA Administration Console main window.

   Table 4-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	See "Tutorial" section in the BEA Administration Console online help.
   The main window is displayed and you want to read a description of it	See Chapter 2, "A Tour of the Main Window," in the BEA Administration Console Online Help.
   The main window does not display and the Connect Failed error message is displayed	1. Enter 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=//lcsol1:4003", replace the port number (4003) with a valid port number. 3. Enter wlisten again: $ wlisten -i \ M3DIR/udataobj/webgui/webgui.ini 4. Check that the tuwsvr 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 M3DIR/udataobj directory. 6. Return to step 1 above.

5. Click the Deact button to start the deactivate process and pop up the Progress of Deactivate (Entire Domain).

6. When you see the confirmation message "Deactivation has completed successfully," click the Dismiss button to close the dialog box.

7. To exit the BEA Administration Console, click Domain->Exit.

You may now start setting up your environment for your own application domain.