This chapter discusses the following topics:
This section lists the hardware, operating system resources, and browser you must provide to support the BEA Administration Console.
The BEA Administration Console runs on all server platforms that support the BEA WLE (C++) version 4.2 software. For a complete list of supported platforms, see the section "Supported Platforms" on page A-1.
In addition to the hardware and software requirements for installing WLE client and server software on your particular platform (see Appendix A, "WLE (C++) Platform Data Sheets"), the BEA Administration Console requires a color display device with the following capabilities:
System Requirements
Platforms Supported
Hardware 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:
Operating System Requirements
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-17.
For more information about system tuning parameters for a particular platform, see Appendix A, "WLE (C++) Platform Data Sheets."
Although any Java capable Web browser may be able to run the BEA Administration Console, at this time BEA supports only the following browsers:
For up-to-date information about other supported Web browsers, see the WLE (C++) Release Notes on the Customer Support section of the BEA Web site:
The Release Notes are also included in the WLE 4.2 product box. To run the BEA Administration Console, you need to set up two servers:
Browser Requirements
http://www.beasys.com/
Setting Up Your Environment
tuxwsvr
wlisten
Note:
You can use any machine that supports a Java capable browser for performing WLE system administration through the BEA Administration Console.
To start To start Starting tuxwsvr
tuxwsvr on UXIX systems, enter:
$ tuxwsvr -l //machine:port -i \
${TUXDIR}/udataobj/tuxwsvr.inituxwsvr on Microsoft Windows NT systems:
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.
To start wlisten, proceed as follows:
wlisten, check the webgui.ini file (located in
WLEDIR\udataobj\webgui for Microsoft Windows NT systems and in
WLEDIR/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.
For details about other parameters in the webgui.ini file, see the wlisten(1) reference page in the BEA TUXEDO Reference.
wlisten process:
To start the BEA Administration Console, proceed as follows:
Use of this URL depends on the following assumptions:
tuxwsvr with the file tuxwsvr.ini.
webgui.ini file is in the default location, WLEDIR/udataobj/webgui.
The BEA Administration Console entry page is displayed, including warranty and license notices.


tlisten.pw file in the
WLEDIR/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.
You may now start setting up your environment for your own application domain.