PrepAway - Latest Free Exam Questions & Answers

What can the administrator do to identify the cause of the installation failure?

The installation of WebSphere Application Server did not complete successfully, and a system
administrator needs to troubleshoot the installation.

What can the administrator do to identify the cause of the installation failure?

PrepAway - Latest Free Exam Questions & Answers

A.
Run the installer command with the appropriate command line options.

B.
Check the files under the Agent data location of IBM Installation Manager.

C.
Check the files under the logs directory of IBM Installation Manager installation directory.

D.
Check the log.txt under <WebSphere Application Server install directory><log directory>.

24 Comments on “What can the administrator do to identify the cause of the installation failure?

    1. certhunt says:

      WebSphere® Application Server Version 7 and earlier had an installation verification utility, the installver command, that would verify checksums of installed files against a bill of materials that was shipped with the product. In WebSphere Application Server Version 8.0 and later, where the installation is based on the Installation Manager rather than on InstallShield MultiPlatform (ISMP), the installver command is replaced by the verification capabilities of the Installation Manager.




      0



      0
  1. Testtaker says:

    Beware guyz, The question is about identifying the cause of the installation failure and not verifying whether it is correctly installed or not. So if we are using A method,can we verify which caused the failure??




    0



    0
  2. certhunt says:

    To verify installation of the product, you can use Installation Manager to find the product in the list of installed packages.
    Perform one of the following actions:
    Change the directory to the eclipse/tools subdirectory of the Installation Manager binaries location and run this command:

    ./imcl listInstalledPackages

    If you used the Installation Manager -log option during installation, you can verify that the resulting log file does not contain any errors.
    If you used the following command to install the product silently for example:

    ./imcl -acceptLicense
    input /var/temp/install_response_file.xml
    -log /var/temp/install_log.xml
    -keyring /var/IM/im.keyring

    and the installation was successful, the install_log.xml file should contain something like this:




    1



    0
  3. Charles says:

    The answer is D. A is only for package verification but D can check the failure details. The challenge is, D’s log name is incorrect. There is no log named log.txt. However, D is more appropriate than A.




    0



    0
  4. rajesh says:

    My answer is D

    as the question says “installation of WebSphere Application Server did not complete successfully” means it was partly success which you can see in the logs directory of the same websphere as “INSTCONFFAILED”




    0



    0
  5. xtonehari says:

    As per the WAS 8.5 Admin and Config Guide:

    To examine the logs manually, locate the Installation Manager logs directory. The default
    location for this directory varies according to the operating system:
    Windows: C:\ProgramData\IBM\Installation Manager\logs
    UNIX: /var/ibm/InstallationManager/logs

    Based on the above information, the answer is C.

    Check the files under the logs directory of IBM Installation Manager installation directory.




    0



    0
  6. Wasser says:

    D refers to a log file which is unlikely to exist if the installation failed – starting point should be the IBMIM logs. I agree A could be interpreted as the correct answer – assuming “appropriate command line options” refers to “imcl viewlog” to review the installation log. This would be a roundabout way of inspecting the logs in the IBMIM default logs directory so answer C would seem the most appropriate.




    0



    0

Leave a Reply