PQ73124: Instructions & code for installing WAS 4.0 InfoCenter don't work for an untailored Linux system

APAR status
Closed as documentation error.

Error description
Here are the steps that I had to use to install the WAS V 4
InfoCenter

- Retrieved the installation file from IBM WebSphere Application
  Server support web site, using the following steps:

  1. Opened the WAS support web page
     
http://www.ibm.com/software/webservers/appserv/support.html

  2. In the "Other documents" section, clicked on the
     "InfoCenter for V 4.0 and V5.0" link

  3. Scrolled down to the "Version 4 InfoCenters - downloads"
     section

  4. Reviewed the information on the "Instructions" web page by
     clicking on the "HTML" link

  5. Selected the appropriate version, and language (e.g.,
     Advanced Edition and English).

  6. Specified where the file should be saved.

  7. Renamed the JAR file, removing the .zip extention
     (infocenter_local_module.jar.zip became
     infocenter_local_module.jar)

  8. Opened a command prompt, logged in as root

  9. Set up the environment to use the WebSphere version of java
    # cd /opt/WebSphere/AppServer/bin
    # . ./setupCmdLine.sh

 10. Verified java version to be executed
    # which java
    /opt/WebSphere/AppServer/java/bin/java
    # java -version
    java was not found in /opt/WebSphere/AppServer/java/bin/exe

 11. Corrected the environment so java can execute correctly
    # echo $JAVA_HOME
    /opt/WebSphere/AppServer/java
    # echo $WAS_HOME
    /opt/WebSphere/AppServer
    # cd $WAS_HOME
    ##########
    # The following locates, and tries to execute each
    # occurrance of java that is found under the WebSphere
    # directory structure.
    #---------
    # I manually added the lines of hyphes to visually separate
    # the command output
    ##########
    # find . -type f -name java -print -exec {} -version {} \;
    ------------------------------------------------------------
    ./java/jre/bin/java
    java version "1.3.1"
    Java(TM) 2 Runtime Environment, Standard Edition
     (build 1.3.1)
    Classic VM (build 1.3.1, J2RE 1.3.1 IBM build
     cxia32131-20030329 (JIT enabled: jitc))
    ------------------------------------------------------------
    ./java/jre/bin/exe/java
    Unable to find xhpi, path used libjava.so/libxhpi.so
    Could not create the Java virtual machine.
    ------------------------------------------------------------
    ./java/bin/java
    java was not found in /opt/WebSphere/AppServer/java/bin/exe
    ------------------------------------------------------------
    ./java_bu/jre/bin/exe/java
    Unable to find xhpi, path used libjava.so/libxhpi.so
    Could not create the Java virtual machine.
    ------------------------------------------------------------
    ./java_bu/jre/bin/java
    java version "1.3.1"
    Java(TM) 2 Runtime Environment, Standard Edition
     (build 1.3.1)
    Classic VM (build 1.3.1, J2RE 1.3.1 IBM build
     cxia32131w-20021107 ORB130 (JIT enabled: jitc))
    ------------------------------------------------------------
    # export JAVA_EXE=$WAS_HOME/java/jre/bin/java
    # $JAVA_HOME -version
    java version "1.3.1"
    Java(TM) 2 Runtime Environment, Standard Edition
     (build 1.3.1)
    Classic VM (build 1.3.1, J2RE 1.3.1 IBM build
     cxia32131-20030329 (JIT enabled: jitc))
    ------------------------------------------------------------
 12. Changed directory to where JAR file is located
    # cd $WAS_HOME/temp
    # ls infocenter*jar
    infocenter_en_wasa.jar

 13. Invoked java, and specified the file to be processed
    # $JAVA_EXE -jar infocenter_locale_module.jar
      i.e.,
    # $JAVA_EXE -jar infocenter_en_wasa.jar

 14. Read the information, and entered "Accept" when prompted
     for the acceptance of the licensing terms.

...

 15. Changed directory to:

    # cd $WAS_HOME/../locale/InfoCenter/moduleID_temp
      i.e.,
    # cd $WAS_HOME/../en/InfoCenter/wasa_temp

 16. Made the InstallUnix.sh shell script executable
    # chmod a+x InstallUnix.sh

 17. Edited the InstallUnix.sh shell script to access the
     correct java executable:
    # vi InstallUnix.sh
    ##########
    # 1. Since I do not have /bin/ksh on my system, I changed
    #    the first line of the script from "#!/bin/ksh" to
    #    "#!/bin/sh"
    ##########
    :s /ksh/sh/
    ##########
    # 2. Changed all lines that start with "java" to "$JAVA_EXE"
    ##########
Local fix
:s / java/$JAVA_EXE/
    ##########
    # 3. Save the changes
    ##########
    :x

 18. Executed the InstallUnix.sh shell script
    ./InstallUnix.sh

...
LOCAL FIX:
See problem description
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server customers who   *
*                 attempt to download and install the V4       *
*                 InfoCenter on a Linux platform. This         *
*                 problem might also affect installation of    *
*                 the V4 InfoCenter on UNIX-based platforms.   *
****************************************************************
* PROBLEM DESCRIPTION: The setupCmdLine.sh script does not     *
*                      properly set the JAVA_HOME variable     *
*                      for the command window:                 *
*                                                              *
*                      # .  $WAS_HOME/bin/setupCmdLine.sh      *
*                                                              *
*                      The customer must locate Java and       *
*                      then figure out how to edit the         *
*                      InfoCenter installation script,         *
*                      InstallUnix.sh,  to install the         *
*                      InfoCenter successfully.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Because the setupCmdLine.sh script does not properly set the
JAVA_HOME environment variable, the customer must locate a
working Java, set the JAVA_HOME environment variable or
another environment variable to use the Java they find, change
the permissions on the <InstallUnix.sh file, and edit
the file to change the shell and the Java pointer:

1. # export
JAVA_EXE=/usr/WebSphere/AppServer/bin/java/jre/bin/java
2. # chmod a+x InstallUnix.sh
3. # vi InstallUnix.sh
   A. Change /bin/ksh to /bin/sh on the first line:
            :s /ksh/sh/
   B. Change lines that start with "java" to  "$JAVA_EXE":
            :%s /^java/$JAVA_EXE/
   C. Save the changes:
            :x
4. Run the InstallUnix script again:
# ./InstallUnix.sh
Problem conclusion
Close this APAR as a documentation change.
The information will appear in the external site after
05/23/2003.
Temporary fix Comments
APAR information
APAR number PQ73124
Reported component name WEBSPHERE AE LI
Reported component ID 5630A2207
Reported release 400
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-11
Closed date 2003-04-30
Last modified date 2004-06-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ73124
IBM Group: Software Group
Modified date: Jun 2, 2004