+

Search Tips   |   Advanced Search

Install Application Client by using the installation wizard


This page describes how to install the Application Client for WAS using the installation wizard provided on WAS CD-ROM. This guided, manual procedure is an alternative to using a silent installation based on a pre-configured option response file.

Before starting this task, read the information in Install Application Client for WAS.

To perform a silent installation of the Application Client, see the topic Install Application Client for WAS silently.

Guidelines for installing WAS components on the Microsoft® Windows Vistaoperating system:

The installation wizard does not upgrade or remove previous Application Clients installation automatically.

 

  1. Start the installation wizard

    • Use the Launchpad GUI.

      The free download Application Client installation is not packaged with the Launchpad program. To start the installation wizard for the download Application Client installation, use the install command.

      1. Start the launchpad. For information about the considerations and procedure for starting the launchpad, see the topic "Using the launchpad to start the installation".

      2. On the launchpad, click Launch the installation wizard for Application Client for WAS.

    • Use the install command.

      When you install application clients, the current working directory must be the directory where the installer binary program is located. This placement is important because the resolution of the class files location is done in the current working directory. Failing to use the correct working directory can cause ISMP errors that stop the installation.

      1. On the command line, change directory to the directory where the installer binary program is located.

        • To install from a product installation: cd /APP_ROOT/AppClient

        • To install from WAS CD: cd CD_mount_point/AppClient

        • To install from a free download Application Client installation: cd /download_dir/AppClient

      2. Enter the install command:

        • [AIX] [Linux] [HP-UX] [Solaris]

          ./install

        • (Windows) install.exe

    • Run the install.exe for the Application Client.

      Use the Launchpad GUI to begin installing a Websphere Application Server V7.0 component is not supported on a machine that is running the Microsoft Windows Vista operating system. If the Launchpad starts automatically when the installation media is inserted in a machine running the Windows Vista operating system, cancel the Launchpad. To install the Application Client on a machine running the Windows Vista operating system, perform the following actions:

      1. Go to the Application Client component directory.

        • To install from a product installation: cd /APP_ROOT/AppClient

        • To install from WAS CD: cd CD_mount_point/AppClient

      2. Run the install.exe program, using the administrator account created when the Windows Vista operating system was installed.

        • The Windows Vista operating system detects that install.exe is an installation program, and presents you with an elevation prompt for Administrator privileges. Click Allow to proceed.

        • When the Windows Vista operating system is asked to run a program that requires elevated (Administrator) privileges, it first tells the user whether or not the publisher of the program is recognized. For certain Websphere Application Server programs, for example, an operating-system dialog might appear that states "An unidentified program wants access to the computer." Examine the program details; and if it is the Websphere Application Server program that you intend to run, click Allow to proceed.

    The Welcome panel of the installation wizard is displayed.

  2. Click Next.

  3. Accept the licence agreement. If we agree to the license agreement, select the radio button beside the I accept the terms in the license agreement message then click Next to continue. The installation wizard checks the system for prerequisites.

  4. Verify the prerequisites are installed.

    • If we see a success message on the wizard panel, click Next to continue.

    • If we see a warning message on the wizard panel, click Cancel to exit the installation wizard, then install the prerequisites before restarting the installation wizard.

    Application Client may be fully functional even if some prerequisites are not installed on the system, however it is recommended you update the system to the required level.

    When completing a custom installation in GUI mode, we have installable options such as Applet Client Samples and StandAlone Thin Client Resource Adapters. If we select any of the available options and need to go backwards on the install panels (for instance, to reread the license agreement), the installable options panel disappears when continuing through the installation panels. To access these panels again, restart the installation wizard.

  5. Specify a destination directory.

    1. If we do not want to use the default destination directory, specify a different target directory. The Product installation location field must contain a valid target directory for you to continue with the installation.

    2. Verify there is adequate space available in the target directory.

    3. Click Next to continue.

  6. Choose either a typical or custom installation.

    • Typical

      1. Select this choice to install only the Java EE and Java thin application clients, samples and IBM Developer Kit, Java 2 Technology Edition.

      2. Click Next to continue with the next step.

    • Custom Java EE and Thin Client

      1. Select this choice to install the stand-alone Thin Clients and Resource Adapters, Applet client, ActiveX to EJB bridge, and samples for the different types of clients. This choice also installs the Java EE and Java thin application clients, samples and IBM Developer Kit, Java 2 Technology Edition.

      2. Click Next

      3. Select the features to install.

        • Select the Developer Kit feature to use any of the utilities that it provides, such as the javaccompiler, the jarutility, or the jarsigner utility. The Java 2 Development Kit that IBM provides has two components, Java 2 Runtime Environment (JRE) and a complete Software Developer Kit (SDK). The JRE sub feature is selected by default for the Custom Java EE and Thin Client installation feature. The SDK component is optional; however, install the SDK component to compile the sample.

      4. Click Next to continue with the next step.

        • If we select the ActiveX to EJB Bridge feature, then the following message might be displayed in a dialog box: Do you want to add Java runtime to the system path and make it the default JRE? If we answer Yes, then the Java run time is added to the beginning of the system path. If we answer No, then the ActiveX to EJB Bridge does not function from the Active Server Pages (ASP), unless you add the Java run time to the path. To add the Java run time later, see the topic ActiveX application clients or reinstall the Application Client.

        • If we select the Applet client feature, then the following message might be displayed: An existing JDK or JRE has been detected on the computer. You chose to install the Applet Client, which will overwrite the registry entries for this JDK or JRE. Do you want to continue and install the Applet Client? If we select Yes, the installation overrides the registry on the machine. If we select No, the Applet client feature is not installed, and we are directed to the back feature dialog box.

    • (Windows) Custom Pluggable Client (Deprecated)

      Installation of the pluggable client is deprecated. Instead, use the stand-alone Thin Client for EJBs, which is installed through the Custom Java EE and Thin Client > Stand-alone Thin Clients and Resource Adapters feature.

    • [AIX] [Linux] [HP-UX] [Solaris]

      Custom

      1. Select this choice to customize the installation of client features on non-Windows platforms.

      2. Select the Developer Kit feature to use any of the utilities that it provides, such as the javaccompiler, the jarutility, or the jarsigner utility. The Java 2 Development Kit that IBM provides has two components, Java 2 Runtime Environment (JRE) and a complete Software Developer Kit (SDK). The JRE sub feature is selected by default for the Custom Java EE and Thin Client installation feature. The SDK component is optional; however, install the SDK component to compile the sample.

      3. Click Next to continue with the next step.

  7. Enter the host name and port number of the WAS you want to connect to.

    These details are for Java EE and Java thin application clients that use the Application Client as their runtime environment.

    The default bootstrap port number is 2809.

    Click Next to continue.

  8. Review the summary information

    • To install WAS code, click Next

    • To change choices that you made on earlier panels, click Back.

  9. After the Application Client installation has finished, verify success.

    • If a Success message is displayed on the Completion panel, click Finishto exit the wizard.

    • If we want more information, or the installation failed, examine the APP_ROOT/logs/install/log.txt file for installation status.The installer program records the following indicators of success in the logs:

      • INSTCONFSUCCESS indicates that the installation is successful and that no further log analysis is required.

      • INSTCONFFAILED indicates an installation failure from which we cannot retry or recover without reinstalling.

      The installation wizard records installation events in the installation log files. Examine messages that the installation program displays. If the Application Client for WAS does not install successfully, read the messages to identify why the installation failed. Correct the problems identified and try installing WAS again.

    Tip: If logged in as non-root or non-admin user, you may not get a successful installation. When the installer runs, a log file is created in the home directory. If the installation fails, an attempt is made to move the log to the APP_ROOT directory; however, without the necessary permission to move the file to the APP_ROOT directory, the attempt to move fails and the log remains in the home directory.

    Look for the following log files in the user_home/waslogs directory:

    • log.txt

    • trace.txt.gz

    • trace.xml.gz

 

Results

You successfully installed the Application Client for WAS and the features you selected.

 

Next steps

Use the installation verification utility to verify a successful installation. If the installation is not successful, fix the error as indicated in the installation error message. For example, if we do not have enough disk space, make more space available, then reinstall the Application Client.