Both tuxwsvr and
wlisten listen on distinct network ports waiting for requests to arrive. They know nothing about each other. Therefore, the GUI needs two network ports to operate. These are different from the network ports that are configured in the
UBBCONFIG file for the Bridges and
tlisten processes.
The tuxadm CGI program mentioned above reads the
ini file, and merges it with an HTML template file, generating the applet HTML on the fly. The template file, delivered with the Oracle Tuxedo software, resides in:
To run tuxwsvr, use the following command line:
tuxwsvr -l //machine:port -i ini-file
You may have to replace /dev/tcp with the pathname of the correct device name for the network device. This device will be the same one that you used for
tlisten, and that you specify for the
BRIDGE parameter in the
UBBCONFIG file. The string
machine:port is based on the standard DNS naming convention used by Oracle Tuxedo. Web servers usually run at port 80. However, because you must be root in order to use that port, we recommend selecting a different one, for example:
|
Note:
|
This is not the port number that you saw in the applet element shown previously. That port number was the one given to WLISTEN, not TUXWSVR. We haven’t discussed WLISTEN yet .
|
The ini-file contains the directory mappings for the Web server.
HTML /java TUXDIR/udataobj/webgui/java
HTML /TUXDIR/udataobj/webgui
|
Note:
|
TUXDIR should be replaced by the full path to the Oracle Tuxedo root directory, e.g., /usr/tuxedo. Do not put the word TUXDIR in the ini file.
|
The above file maps this to the Oracle Tuxedo bin directory, where
tuxadm resides. In a secure environment, you would not do this; you would copy
tuxadm somewhere else (or you might need it to be a shell script that sets
LD_LIBRARY_PATH and executes the real
tuxadm). It also helps to have
TUXDIR set in the environment before running
tuxwsvr.
The APPLET element has an attribute called CODEBASE which, as you can see from above, is
/java. When the Web browser attempts to retrieve the applet from the Web server using the path
/java/bea/tuxadm/TuxApplet.class, the above
ini file remaps that to the following:
The mapping of / to
udataobj/webgui is used to map the top-level Web page,
webguitop.html. (Because the
java directory is right under the
webgui directory, the mapping of
/java in the
tuxwsvr.ini file is not strictly needed. We have put it there for illustration purposes, in case you want to move your Java files elsewhere.)
The Web server’s ini file can contain multiple CGI and HTML lines, and they are processed in sequential order until a match is reached.
BASE means the URL prefix that a Web browser uses to retrieve a document. The
CODEBASE for the Java code is
/java, but the server directory for the Java code is
/usr/tuxedo/udataobj/webgui/java.
The next step is to set up the webgui.ini file, which is used by
tuxadm and
wlisten.
tuxadm will look in
$TUXDIR/udataobj/webgui/webgui.ini if it is not given the
INIFILE parameter (more on this later).
wlisten requires the
ini file path on the command line (more later). (If you have installed Oracle Tuxedo using the installation utility, you probably have a usable
webgui.ini file already.)
|
Note:
|
This is a different ini file from the one described for the Web Server. Listing A-2 shows what your ini file might look like:
|
|
•
|
TUXDIR is where Oracle Tuxedo is installed.
|
|
•
|
NADDR is the network address that you will use for wlisten, in the standard Oracle Tuxedo syntax (DNS, 0x, . . . or another provider-specific form).
|
|
•
|
DEVICE is the device filename for the TCP/IP device (not needed on some systems that use sockets, such as HP and IBM).
|
|
•
|
ENCRYPTBITS is 0, 40, 56, or 128. This parameter specifies the strength of encryption used in communication between the GUI applet and the Administration Console server. The default is 128-bit.
|
|
•
|
CODEBASE is the path of the directory in which the Java code can be found (i.e., the aliased path recognized by the Web server, not the physical path on the machine).
|
|
•
|
DOCBASE is where the Oracle Tuxedo help files will be found.
|
|
•
|
INIFILE is the path of this file (the real path, not the aliased path).
|
|
•
|
TEMPLATE is where the HTML template file that tuxadm uses to deliver the applet.
|
The DOMAIN list is optional, especially if you are using the GUI to create your domains from scratch.
DOMAIN=domain_name;tuxconfig-path
The value of tuxconfig-path is the real path, not the aliased path.
Before running wlisten, you need to set the FML32 environment variables so that the programs can find the Oracle Tuxedo MIB field tables. Set the following variables as shown:
wlisten can operate in either of two security modes:
Authentication is done based on the tlisten password file. If there is a file of passwords called
tlisten.pw, in either
$TUXDIR/udataobj or
$APPDIR/.adm, then the user is required to enter a username and password when the applet starts. The password must match one of the passwords in the password file, or authentication fails. The username is passed to
tpinit when the GUI gateway program,
wgated, connects to Oracle Tuxedo.
The installation script places a file called webguitop.html in the directory used by the Web Server for its general HTML files. The bottom of this file has a Submit FORM, which generates the URL to run
tuxadm (the CGI program).
where INIFILE is set to the place where you have put your GUI
ini file.
The tuxdir-path is the absolute path of the Oracle Tuxedo root directory on the server machine. The
inifile-path is the absolute path of the
ini file for the wlisten (not the Web server).
INIFILE should match the
INIFILE parameter within the
ini file. You can leave out the entire
&INIFILE= . . . if the
INIFILE is in the default location of
$TUXDIR/udataobj/webgui/webgui.ini.
<PARAM NAME="
HOST"
VALUE="lcuw99">
This HOST parameter is undocumented, so do not look for it anywhere.
