Installing Application Client by using the installation wizard

You can install the Application Client for WebSphere® Application Server by using the installation wizard provided on the product CD-ROM. This guided, manual procedure is an alternative to using a silent installation based on a pre-configured option response file.

Before you begin

Before starting this task, read the information in the Installing Application Client for WebSphere Application Server topic.

If you want to silently install the Application Client, refer to the Installing Application Client for WebSphere Application Server silently topic.

About this task

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

Application Client V6.1 and later can be installed together with previously installed Application Client installations if their versions are lower than 6.1. However, only one instance of Application Client V6.1 and later can be installed on the same system. When the installer is launched, it will detect any existing installation of Application Client V6.1 and later and direct the installation flow to the feature panels so that additional features can be added on top of the existing installation.

Procedure

  1. Start the installation wizard
    • [AIX Solaris HP-UX Linux Windows] [z/OS] Use the Launchpad GUI.
      Important: 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 more information, see the topic "Using the launchpad to start the installation".
      2. On the launchpad, click Launch the installation wizard for Application Client for WebSphere Application Server.
    • [AIX Solaris HP-UX Linux Windows] [z/OS] Use the install command.

      When you install Application Client, 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_server_root/AppClient
        • To install from the product 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
    • [Windows Vista] Run the install.exe for the Application Client.

      Using the Launchpad GUI to begin installing a Websphere Application Server Version 7.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, you must complete the following actions:
      1. Go to the Application Client component directory.
        • To install from a product installation: cd /app_server_root/AppClient
        • To install from the product CD: cd CD_mount_point/AppClient
      2. Run the install.exe program, using the administrator account that was 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 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 your 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. [AIX Solaris HP-UX Linux Windows] [z/OS] Click Next.
  3. Accept the licence agreement. If you agree to the license agreement, select I accept the terms in the license agreement then click Next to continue. The installation wizard checks the system for prerequisites.
  4. [AIX Solaris HP-UX Linux Windows] [z/OS] Ensure that the prerequisites are installed.
    • If you see a success message on the wizard panel, click Next to continue.
    • If you see a warning message on the wizard panel, click Cancel to exit the installation wizard, then install the prerequisites before restarting the installation wizard.
    Important: Application Client may be fully functional even if some prerequisites are not installed on the system, however it is recommended you update your system to the required level.
    Attention: If you select any of the available options and need to go backwards on the installation panels (for instance, to reread the license agreement), the installable options panel disappears when continuing through the installation panels. To access these panels again, you must restart the installation wizard.
  5. [AIX Solaris HP-UX Linux Windows] [z/OS] Specify a destination directory.
    1. If you 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. Ensure that there is adequate space available in the target directory.
    3. Click Next to continue.
  6. [AIX Solaris HP-UX Linux Windows] [z/OS] Choose either a typical or custom installation.
    • Typical
      1. Select this choice if you want 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.
    • [Windows] Custom Java EE and Thin Client
      1. Select this choice if you want 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 that you want to install.
        • Select the Developer Kit feature if you need 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, you must install the SDK component to compile the sample.
        • Select the Administration Thin Client, if you need a runtime jar that is customized to enable client applications to undertake WebSphere administration tasks. The Administration Thin Client is installed into app_client_root/runtimes.
        • Select the Web Services Thin Client, if you need a JAX-RPC Web services runtime JAR that is customized to enable JAX-RPC client applications to communicate with the application server through Web Services. The Web Services Thin Client is installed into app_client_root/runtimes.
        • Select the Thin Client for JAX-WS with WebSphere Application Server, if you need a JAX-WS Web services runtime JAR that is customized to enable JAX-WS client applications to communicate with the application server through Web Services. The Thin Client for JAX-WS is installed into app_server_root/runtimes.
      4. Click Next to continue with the next step.
        Attention:
        • If you 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 you answer Yes, then the Java run time is added to the beginning of the system path. If you 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 you select the Applet client feature, then the following message might be displayed: An existing JDK or JRE has been detected on your 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 you select Yes, the installation overrides the registry on your machine. If you select No, the Applet client feature is not installed, and you 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 Enterprise JavaBeans (EJB), 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
      Attention: When completing a custom installation in GUI mode, you have installable options such as Applet Client Samples and StandAlone Thin Client Resource Adapters.
      1. Select this choice if you want to customize the installation of client features on non-Windows platforms.
      2. Select the Developer Kit feature if you need 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, you must install the SDK component to compile the sample.
      3. Select the Administration Thin Client, if you need a runtime jar file that is customized to enable client applications to undertake WebSphere administration tasks. The Administration Thin Client is installed into app_client_root/runtimes.
      4. Select the Web Services Thin Client, if you need a JAX-RPC Web services runtime JAR that is customized to enable client applications to communicate with the application server through Web Services. The Web Services Thin Client is installed into app_client_root/runtimes.
      5. Install the Thin Client for JAX-WS with WebSphere Application Server, if you need a JAX-WS Web services runtime JAR that is customized to enable JAX-WS client applications to communicate with the application server through Web Services. The Thin Client for JAX-WS is installed into app_client_root/runtimes.
      6. Click Next to continue with the next step.
  7. [AIX Solaris HP-UX Linux Windows] [z/OS] Enter the host name and port number of the WebSphere Application Server 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. [AIX Solaris HP-UX Linux Windows] [z/OS] Review the summary information
    • To install the product code, click Next
    • To change choices that you made on earlier panels, click Back.
  9. [AIX Solaris HP-UX Linux Windows] [z/OS] 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 you want more information, or the installation failed, examine the app_client_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 you 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 WebSphere Application Server does not install successfully, read the messages to identify why the installation failed. Correct the problems identified and try installing the product again.

    Tip: If you are 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 your home directory. If the installation fails, an attempt is made to move the log to the app_client_root directory; however, without the necessary permission to move the file to the app_client_root directory, the attempt to move fails and the log remains in your home directory. Look for the following log files in the user_home/cltlogs directory:
    • log.txt
    • trace.txt.gz
    • trace.xml.gz

Results

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

What to do next

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 you do not have enough disk space, make more space available, then reinstall the Application Client.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tcli_installclient_wiz
File name: tcli_installclient_wiz.html