BEA Logo BEA WebLogic Enterprise Release 5.0

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

   e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary

 

   WLE Doc Home   |   BEA WebLogic Enterprise Installation Guide   |   Previous   |   Next   |   Contents   |   Index

WLE Installation on UNIX Systems

This chapter discusses the following topics:

Platforms Supported

The platforms listed in Table 4-1 are supported.

Table 4-1 Supported Platforms

Vendor

Operating System

Release/Version

HP

HP-UX

11.00 32-bit plus patches B.11.00.B0315

Sun

Solaris

2.6 and 7.0 (UltraSPARC)

For the hardware and software requirements for these operating systems, see WLE Platform Data Sheets.

Installing the WLE Software on UNIX Systems

This section describes how to install the WLE software on UNIX systems.

Preinstallation Considerations

This section describes some important tasks that you should perform before starting the WLE installation.

Backing Up Files

If you are installing WLE software on a system that already has M3 or WLE software installed, there are some files that you may want to back up prior to the installation, and then restore them after the installation is complete. This is because some files that you may have modified for your M3 or WLE software are overwritten when the WLE software is installed.

To avoid having to modify these files again, proceed as follows:

  1. If you are installing one or more of the WLE server software components, back up the RM file to a temporary location. This file is located in the M3DIR/udataobj or WLEDIR/udataobj directory.

  2. If you are installing the BEA Administration Console, back up the webgui.ini file to a temporary location. This file is located in the M3DIR/udataobj/webgui or WLEDIR/udataobj/webgui directory.

  3. After the installation is complete, restore these files to their original locations.

Stopping WLE or BEA TUXEDO Applications and Related Services

Before beginning the installation, make sure no BEA TUXEDO or WLE client or server applications are running. For information about the tmshutdown command, see Starting and Shutting Down Applications in the Administration section of the WebLogic Enterprise online documentation.

Checking That Your Account Has the Required Privileges

On most systems, you need superuser privileges to mount the software CD. The account that you log on to to perform the installation must have administrative privileges.

UNIX Installation Procedure

It takes approximately 10 minutes to install the software.

Warning: If you are re-installing the WLE 5.0 software on your system, and you also already installed the optional WLE Security Service software (56-bit or 128-bit) on your system, you must:

To install the WLE software on a UNIX operating system, perform the following steps:

  1. Log on to the system with administrative privileges.

  2. Insert the WLE CD into the reader.

  3. Mount the CD as a file system. For platform-specific instructions on how to do this, see WLE Platform Data Sheets. On most systems, you need superuser privileges to perform the mount. Note: If your system does not have a directly connected CD reader, you can mount the CD on a remote system, share (export) the CD file system, and then mount the remote file system. For detailed instructions for each platform, see WLE Platform Data Sheets. Alternatively, you can mount the CD on a remote system, copy the contents of the CD directory for your platform to the system in which you plan to install the WLE software, and continue with the remainder of the installation procedure.

  4. Use the cd command to change your working directory to the root of the WLE 5.0 software CD.

  5. Run the ls command in the root directory to check the CD's contents. If all the files are in lowercase characters, begin the installation by entering:

    sh install.sh .

    If all the files are in uppercase characters, begin the installation by entering:

    sh INSTALL.SH

  6. The following platform choices are displayed:

    1) HP-UX v11.0

    2) Sun Solaris v2.6

    3) Sun Solaris 7

    Install which platform's files? [01- 3, q to quit, l for list]:

    Enter the number 1 to install the WLE 5.0 software on an HP-UX system; or enter 2 to install the WLE 5.0 software on a Solaris 2.6 system; or enter 3 to install the WLE 5.0 software on a Solaris 7.0 system; or enter the letter l to display the list again.

  7. The remaining prompts in this chapter show a sample WLE 5.0 installation on a Solaris 2.6 system. For example, a confirmation prompt is displayed:

    ** You have chosen to install software for **

    BEA WebLogic Enterprise Release 5.0

    This directory contains the BEA WLE Installation Software for
    Sun Solaris 2.6 on Sun SPARC.

    Is this correct? [y,n,q]:

  8. Enter y to accept the selection; or enter n to reject the selection and return to the list of platforms; or enter q to quit the installation.

  9. An informational messages and the initial component selection menu are displayed:

    To terminate the installation at any time
    press the interrupt key,
    typically <del>, <break>, or <ctrl+c>.

    The following components are available:

    1 servers BEA WebLogic Enterprise Servers

    2 clients BEA WebLogic Enterprise Clients

    3 admcon BEA Administration Console

    Select the one you wish to install [?,??,q]:

    The server and client components have packages that you can select for a more specific installation. Enter the number 1 to display all the WLE server packages; or enter 2 to display all the WLE client packages; or enter 3 to display the Administration Console component; or enter a single question mark (?) to display a brief help message; or enter two question marks (??) to redisplay the menu; or enter q to quit the installation.

  10. If you entered the number 1 in the initial component selection menu to view the list of WLE server packages, the following menu is displayed:

    The following packages are available:

    1 wletsrv BEA WebLogic Enterprise TUXEDO Server

    2 wlecsrv BEA WebLogic Enterprise CORBA C++ Server

    3 wlejsrv BEA WebLogic Enterprise CORBA Java Server

    4 wlej2ee BEA WebLogic Enterprise J2EE Server

    Select the package(s) you wish to install (or 'all' to install
    all packages) (default: all) [?,??,q]:

    Select the server package or packages you want to install. Separate multiple server packages with a comma. Or enter all , the default option, to install all packages.

    Note: You cannot select a particular server package and then a particular client package. When you select a particular server package or set of server packages, only those server packages are installed. The client packages and the Administration Console component are not installed. If you subsequently wanted to install particular clients or the Administration Console on the system, you could run the installation procedure again to select and install those items.

    Note: The BEA TUXEDO server software is always installed as a base component for any of the other WLE servers. The CORBA Java and J2EE server components are always installed together, even if you only select one of those items.

    If instead you entered 2 in the initial component selection menu to view the list of WLE client packages, the following menu is displayed:

    The following packages are available:

    1 wletcli BEA /WS Client

    2 wleccli BEA C++ Client

    3 wlejcli BEA Java Client

    4 wlercli BEA RMI Client

    Select the package(s) you wish to install (or 'all' to install
    all packages) (default: all) [?,??,q]:

    Note: The BEA Java Client is the CORBA Java client; it does not include RMI. The BEA /WS Client is the BEA TUXEDO /WS client.

    Select the client package or packages you want to install. Separate multiple client packages with a comma. Or enter all , the default option, to install all the client packages.

    If, instead, you entered 3 in the initial component selection menu, the following menu is displayed:

    The following packages are available:

    1 admcon BEA Administration Console

    Select the package(s) you wish to install (or 'all' to install
    all packages) (default: all) [?,??,q]:

    Enter the number 1 or the word all if you want to install the Administration Console.

  11. The installation procedure displays the name of the component you are installing, and lists copyright information. For example, if you selected 1 in the initial component selection menu, and then selected 3, CORBA Java Servers, the procedure displays the following:

    BEA WebLogic Enterprise CORBA Java Server
    (sparc) Release 5.0
    Copyright (c) 1999 BEA Systems, Inc.
    All Rights Reserved.
    BEA and WebLogic are trademarks of BEA Systems, Inc.

    SSLplus is a trademark of Certicom Corporation, 1999.
    BSAFE is a trademark of RSA Data Security, Inc., 1999.

  12. Enter the target directory for the selected software. The following prompt is displayed:

    Directory where WebLogic Enterprise files are to be installed [?,q]:

    For example, you could enter the /usr/local/wledir directory.

    Most server components can be installed in any directory whose file system has enough disk space to accommodate them. There may be one or more server components that have to be installed over an existing WLE server component.

    When you enter the directory name, the installation program verifies it by using the following criteria:

  13. The file system for the target directory is checked for available space. For example:

    Determining if sufficient space is available ...
    272989 blocks are required
    16118268 blocks are available to /usr/local/wledir

    Using /usr/local/wledir as the WebLogic Enterprise base directory

    If enough disk space is available, the installation continues. If there is insufficient disk space, the installation returns to the prompt asking for the name of a directory.

  14. If you entered 3 or all in the initial component selection menu, indicating that the installation would include the Administration Console, you are asked to choose between the following:

  15. Again, you have a choice. If you accept the default, the following prompt is displayed:

    Creating /usr/local/wledir/udataobj/webgui/java

    Using /usr/local/wledir/udataobj/webgui/java as the BEA Administration Console document tree

    Directory where BEA Administration Console CGI programs are to
    be installed (default: /usr/local/wledir/udataobj/webgui/cgi-bin) [?,q]:

    Press the Enter key to accept the default locations, if desired.

  16. If you accept the default, the following prompt is displayed:

    Creating /usr/local/wledir/udataobj/webgui/cgi-bin

    Using /usr/local/wledir/udataobj/webgui/cgi-bin as the BEA Administration Console CGI directory

    Web server client prefix for CGI directory. /cgi-bin is a good choice for most web servers. (default: /cgi-bin) [?,q]:

    Press the Enter key to accept the default locations, if desired.

  17. If you accept the default, the following prompt is displayed:

    Using /cgi-bin as the BEA Administration Console CGI prefix

  18. At this point, the installation program proceeds to install the WLE files.

  19. After the installation of the WLE files is completed, the following text and prompt is displayed:

    ... finished

    .
    .
    .

    Changing file permissions...
    ... finished

    Processing default license file...
    ... finished

    Install tlisten password? [y/n]:

  20. If you want to specify a tlisten password, enter y ; otherwise, enter n . For information about the tlisten password and instructions for setting it, see the section Selecting an Administrative Password. If you enter y , the following prompt is displayed:

    Please enter the tlisten password:

  21. Enter the tlisten password. The following prompt is displayed:

    Please verify the password:

  22. Enter the tlisten password again. The following prompt is displayed:

    tlistpwd: INFO: Password appended to file "/usr/local/wledir/udataobj/tlisten.pw".

    Verifying installation...
    ... Installation successful!

    If your license file is accessible, you may install it now.
    Install license file? [y/n]:

  23. If you want to install the WLE software license now, enter y ; otherwise, enter n and install the license later. If you enter y , the following prompt is displayed:

    To terminate the license update at any time
    press the interrupt key,
    typically <del>, <break>, or <ctrl+c>.

    Directory containing source license text file [?,q]:

  24. Insert the license diskette, which is shipped in the WLE software box, in the diskette reader on your machine, mount the disk (if necessary), copy the lic.txt file to a system directory, and enter the location of the lic.txt file at the prompt. For example, if you copy the lic.txt file to /usr , enter /usr . The following prompt is displayed:

    Using /usr/lic.txt to copy license information.

    Updating /usr/local/wledir/udataobj/lic.txt with license information.

    Please don't forget to fill out and send in your registration card

  25. After the installation is completed, unmount the CD file system and remove the CD from the reader. For platform-specific instructions for unmounting the CD, see WLE Platform Data Sheets.

Installing the Product License After You Install the WLE Software

If you elected not to install the product license when you installed the WLE software, you can install the license using the BEA License Utility.

Note: Your product license is on a 3.5-inch diskette that is included in the WLE product box.

To install the license, use the following steps:

  1. Insert the license diskette, which is shipped in the WLE software box, in the disk reader on your machine, mount the disk (if necessary), and copy the lic.txt file to a directory of your choice, but not to the wledir directory or any of its subdirectories.

  2. Change to the bin directory where you installed the WLE software. For example:

    cd /usr/local/wledir/bin

  3. Enter sh ./lic.sh .

    The following prompt is displayed:

    To terminate the license update at any time
    press the interrupt key,
    typically <del>, <break>, or <ctrl+c>.

    Directory containing source license text file [?,q]:

  4. Enter the name of the directory that contains the lic.txt file (for example, /kits/license ). The following prompt is displayed:

    Using /kits/license/lic.txt to copy license information.

    Directory where WebLogic Enterprise files are installed. [?,q]:

  5. Enter /usr/local/wledir or the name of the directory where you installed the WLE software. The following prompt is displayed:

    Updating /usr/local/wledir/udataobj/lic.txt with license information.

Running Simpapp to Verify the WLE Software Installation

To verify that you have successfully installed the WLE client and server software, run the simpapp application. This "simple application" is a WLE client/server application that converts strings to uppercase and lowercase letters.

Note: This section assumes you installed all WLE server components, or one of the CORBA server components. If you installed only the J2EE server component, see the next section, Running a Basic EJB Sample to Verify the WLE J2EE Software Installation, for information about running an EJB sample to verify the installation.

Before running the sample application, see Appendix A, "WLE Platform Data Sheets" for important information about prerequisite software.

To run simpapp , perform the following steps:

  1. Make sure that the directory in which you installed the WLE software is set in the environment variable TUXDIR . For example, if you installed the software in the default directory, enter the following to set the TUXDIR environment variable: TUXDIR=/usr/local/wledir; export TUXDIR

  2. Create a directory under wledir and copy the content of the simpapp directory to it.

    Notes: If you installed all WLE servers or the CORBA C++ server component in the default directory, a C++ simpapp directory is located at usr/local/wledir/samples/corba/simpapp .

    If you installed the CORBA Java server component in the default directory, the simpapp directory is located at usr/local/wledir/samples/corba/simpapp_java.

    If you installed the BEA TUXEDO server component in the default directory, the simpapp directory is located at usr/local/wledir/samples/atmi/simpapp.

  3. Change (cd) to the copy directory.

  4. To change the permissions on all the files to allow full access, enter:
    chmod 777 *

  5. Ensure that make is in your path.

  6. To run simpapp automatically, enter ./runme.ksh . The simpapp application runs and prints the following messages:

Testing simpapp
cleaned up
prepared
built
loaded ubb
booted
ran
shutdown
saved results
PASSED

  1. To run simpapp manually to observe the processes starting and stopping, do the following:

    1. Enter KSH .

    2. Enter . ./results/setenv.ksh .

    3. Enter tmloadcf -y results/ubb .

    4. Enter tmboot -y . The application starts several processes.

    5. Enter ./simple_client . The prompt String? is displayed.

    6. Enter a word in lowercase letters. The application converts the word to uppercase and then to lowercase letters and displays the results.

    7. Enter tmshutdown -y . The application shuts down the processes.

  2. To restore the directory to its original state, enter:

    1. . ./results/setenv.ksh

    2. make -f makefile.mk clean

Running a Basic EJB Sample to Verify the WLE J2EE Software Installation

If you installed only the WLE J2EE server component, you can run a stateless session EJB sample provided by the WLE software to verify the installation.

Before running the sample application, see Appendix A, "WLE Platform Data Sheets" for important information about prerequisite software. For example, on NT systems, you must first download and install the Java 2 SDK version 1.2.2.

This sample demonstrates the usage of stateless session EJBs using a simple stock trader application. This sample demonstrates how the client must maintain any persistent state -- such as the change in the cash account -- across repeated calls to the session EJB. All the logic for the balance is encapsulated in the client, where all the persistence is provided by the container and the logic is maintained in the EJB.

The EJB in this sample provides basic trading methods, such as buying and selling stocks. Because there are no persistent stores involved in this sample, all the stock data are set in the deployment descriptor of the EJB as environment properties. The container supplies the data to the EJB through the JNDI lookup operation.

Main Directory Location

The following directory contains the Java source files and XML-based deployment descriptors:

$TUXDIR/samples/j2ee/ejb/basic/statelessSession

A common build script, runme.cmd , is provided for all the EJB samples and is in the following directory:

$TUXDIR/samples/j2ee/ejb

This rumme.ksh shell script file contains commands to set the environment, boot the server, and execute the client for this sample.

Source Files

The following table lists and describes all the files for this sample application.

File Name

Description

ejb-jar.xml

The XML deployment descriptor file used to help add the bean to the EJB container.

weblogic-ejb-extensions.xml

A file containing the WLE extensions to the deployment descriptor DTD.

Client.Java

The Java source code for the client.

TraderBean.java

The Java source code for the stateless session bean. This class contains the business logic method implementations and methods required by the EJB 1.1 specification.

Trader.java

The Java source code for the Remote interface of the TraderBean class.

TraderHome.java

The Java source code for the Home interface of the TraderBean class.

TradeResult.java

An application-specific utility class used to carry a trade execution result between the EJB and the client.

ProcessingErrorException.java

An application-specific exception thrown by the TraderBean class for business methods.

Utility Files

The following table lists and describes the utility files for this sample application. These files are generated based on the WLE installation environment. Because a common build script is provided for all the EJB samples, instructions to build and execute the samples are provided in the section Building the EJB Sample Applications. The runme.ksh file resides in the $TUXDIR/samples/j2ee/ejb directory. The other utility files are in the $TUXDIR%/samples/j2ee/ejb/basic/statelessSession directory.

File

Description

runme.ksh

The UNIX Korn shell script that contains commands to set the environment, boot the server, and execute the client for this sample.

run_client.ksh

The UNIX Korn shell script to run the client on UNIX systems.

setenv.ksh

The UNIX Korn shell script to set the necessary environment variables on UNIX systems.

ubbconfig

The WLE server configuration file to be used on UNIX systems.

ejb_basic_statelessSession.jar

The ejb-jar file that contains the source file classes, the container-specific class files generated by the ejbc command, and the deployment descriptor files. This is the ejb-jar file that is deployed on the WLE server.

Variable Descriptions

HOST

The host name portion of the TCP/IP network address used by the ISL process to accept connections from Java clients. The default value is the name of the local machine.

PORT

The TCP port number at which the ISL process listens for incoming requests; it must be a number between 0 and 65535. The default value is 2468.

IPCKEY

The address of shared memory; it must be a number greater than 32769 unique to this application on this system. The default value is 55432.

JAVA_HOME

The directory path where you installed the Java 2 SDK software. For example:

JAVA_HOME =c:\JDK1.2.2 (on NT)

JAVA_HOME =/usr/local/JDK1.2.1 (on UNIX)

Building the EJB Sample Applications

Use the following steps to build the EJB samples:

  1. Ensure that the directory in which you installed WLE is set in the environment variable TUXDIR . Make sure to set the JAVA_HOME environment variable.

  2. Make a copy of the $TUXDIR/samples/j2ee/ejb directory into a working directory.

  3. Change directory to the working directory.

  4. Change the permissions on all the files to give them write-access. For example:

    prompt>chmod -R +w *

    Change the permission of the runme.ksh file to give it execute permission, as in the following command:

    prompt>chmod +x runme.ksh

  5. Run the JavaServer version of the sample automatically by entering the runme command:

    prompt>. ./runme.ksh basic statelessSession

  6. A number of messages are displayed, along with information about whether the build procedure was successful. The sample is built, the servers are booted, and the client is run once.

After you have executed the runme command, you can run the samples manually if you like. To run the samples manually:

  1. Change the current directory to your work samples directory.

  2. Ensure that your environment is set correctly by entering the following command:

    prompt>. ./setenv.ksh

  3. Boot the server, run the client, and shut down the server by entering the following commands:

    prompt>tmboot -y

    prompt>. ./run_client.ksh

    prompt>tmshutdown -y

To restore the sample application directory to its original state:

  1. Set the directory to the directory containing the sample application.

  2. Enter the following command, where TUXDIR is the directory in which you installed the WLE software:

prompt>. $TUXDIR/samples/j2ee/ejb/clean.ksh

Removing (Uninstalling) the WLE Software from Your System

To remove the software from your system, use the following procedure. This procedure also removes the WLE Security Service software, if present on your system.

  1. Log on as the WLE administrator or superuser.

  2. Make sure that no BEA TUXEDO or WLE client or server applications are running. Use tmshutdown to shut down all WLE applications.

  3. Enter the following command:

    prompt> rm -rf wledir

    where wledir is the WLE base directory.

 

 

Copyright © 1999 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.