IBM Support

PM36760: INSTALLER SHOULD GIVE MORE INFORMATIVE MESSAGE ON PROMPT

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Install script is too silent. Common issues such as bad file
    permissions in image (no execute permission on java), no X11
    display, or error in install process before installer creates
    the product target directory can not be seen.  This typically
    creates a PMR because clients are not educated about the
    "-is:javaconsole" parameter and "waslogs" location. We should
    write a message to the console (or stderr) which suggests
    using the "-is:javaconsole" parameter and also suggests where
    to find logs
    

Local fix

  • Prompt message when installation is failed, tell customer
    where to find logs, if no log file is found, then try
    installation again with  parameter "-is:javaconsole". Add new
    parameter "-noOutput" if customer does not want any output on
    console.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Installation     *
    *                  Factory and Update Installer                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Install script is too silent. Common    *
    *                      issues, no X11 display, or error in     *
    *                      install process before installer        *
    *                      creates the product target directory    *
    *                      can not be seen by customer.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When installation finishes, the install.sh/install.exe will
    not check the return code of install process or inform you of
    the install result.
    

Problem conclusion

  • We now put out a prompt message when installation is failed. We
    tell you to find the log from the waslogs/updilogs folder under
    the current user home. If no log file is found, then we tell
    you to try installation again with parameter
    "-is:javaconsole".  We also Added a new parameter "-noOutput"
    if you do not want any output.
    
    The fix for this APAR is currently targeted for inclusion in
    Installation Factory 7.0.0.19 and Update Installer 7.0.0.19.
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM36760

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-11

  • Closed date

    2011-05-16

  • Last modified date

    2011-05-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021