Installing Application Client for WebSphere Application Server

This topic describes how to install the Application Client for WebSphere Application Server using the installation image on the product CD-ROM.

Before you begin

[AIX HP-UX Linux Solaris Windows] [iSeries] New or updated for this feature pack Attention: If you are installing the Web Services Client feature pack, see Installing the Feature Pack for Web Services Client or Installing the Feature Pack for Web Services Client silently.
[z/OS] New or updated for this feature pack Attention: If you are installing the Web Services Client feature pack, see Installing the Feature Pack for Web Services Client.
Running client applications that communicate with a WebSphere Application Server requires that elements of the Application Server are installed on the system on which the client applications run. However, if the system does not have the Application Server installed, you can install Application Client, which provides a stand-alone client run-time environment for your client applications. See the Supported Prerequisites page for more information on supported product platforms.
[iSeries] The i5/OS Application Client supports the following types of client:
  • Java thin client
  • J2EE application client
  • Web services thin client

The steps that follow provide enough detail to guide you through preparing for, choosing, and installing the variety of options and features provided. To prepare for installation and to make yourself familiar with installation options, complete the steps in this topic and read the related topics, before you start to use the installation tools.

[AIX] [Linux] [HP-UX] [Solaris] As a general rule, if you launch an installation and there is a problem such as not having enough temporary space or not having the right packages on your Linux or UNIX systems, then cancel the installation, and make the required changes. Restart the installation to initiate your changes.

[AIX] [Linux] [HP-UX] [Solaris] [Windows] You can install this product by a non-root user on a UNIX operating system and non-administrator user on a Windows operating system. However, the following functions are not enabled on Windows if the product is installed by a non-administrator user:
  • ActiveX to EJB bridge
  • Applet Client
  • Launching Java Web Start from browser

It is recommended that you have 350 MB of temporary disk space available before beginning the installation.

[AIX HP-UX Linux Solaris Windows] [z/OS] The installation wizard does not upgrade or remove previous Application Client installations automatically. You can install a Version 6.1 Application Client with previously installed Application Clients, if those previously installed versions are lower than Version 6.0. In addition, only one instance of the Version 6.1 Application Client can be installed on the same system.

[Windows] For example, if Version 5 Application Clients are installed under the C:\WebSphere\AppClient directory, you cannot choose the same location for your Version 6.x Application Clients installation.
[AIX HP-UX Linux Solaris Windows] [z/OS] Important: For Application Clients to coexist, there is a limitation that Applet client and ActiveX client on Windows cannot coexist with Version 5.0.x and Version 4.x clients. For example, the Applet client feature in Version 6.x cannot coexist with the Applet client feature in any previous release. This coexistence is not available because the installation of Applet client feature in Version 6.x sets the browser default Java Virtual Machine (JVM) using the Java Runtime Environment (JRE) from the Version 6.x installation, which is Java Runtime Environment Version 1.4.2. Similarly, the ActiveX to EJB Bridge feature in Version 6.x sets the Windows system path to use the JRE from the Version 6.x installation.
Important: If you are logged in as a root user and attempt to uninstall an instance of Application Client that a non-root user installed, the Windows registry will be wiped clean for the Application Client instance that the root user installed. If you need to uninstall an instance of Application Client that a non-root user has installed, be sure that you are logged in as the non-root user.
Attention: Make sure that you use IBM Update Installer (UPDI) Version 6.1.x.x when installing Application Client Version 6.1.x Fix Packs. Using a Version 6.0.x Application Client, or an Application Server version that is later than 6.1.x, will create problems if, in the future, you install a later Application Client version on the same machine.

Procedure

  1. [iSeries] Install WebSphere Application Client from your iSeries server. Installing the product from the CD-ROM drive of your iSeries server requires direct physical access to the server. The local installation requires less time to complete than a remote installation. The local installation reads installation options from a response file.

    See Installing WebSphere Application Client from your iSeries server.

  2. [iSeries] Run the GUI installation tool from a Windows workstation
    [AIX HP-UX Linux Solaris Windows] [Fix Pack 9 or later]
    [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Guidelines for installing WebSphere Application Server components on the Microsoft® Windows Vista™ operating system:
    • Using the Launchpad GUI to begin installing a Websphere Application Server Version 6.1 component is not supported when your are running Websphere Application Server on a machine that contains 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 a Websphere Application Server component on a machine running the Windows Vista operating system, you must perform the following actions:
      1. Go to the individual component directory.
      2. Run the install.exe program that is located in that directory using the administrator account that was created when the Windows Vista operating system was installed.
        • The Windows Vista operating system will detect the fact that install.exe is an installation program, and it will present 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 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 interactive GUI uses an InstallShield interface to prompt you for installation options. Installing the product from a Windows workstation does not require direct physical access to the iSeries server.

    See Installing using a Windows workstation GUI .

  3. [AIX HP-UX Linux Solaris Windows] [z/OS] Install Application Client for WebSphere Application Server using the launchpad.

    [AIX] [Linux] [HP-UX] [Solaris] [Windows] [iSeries] See Install Application Client for WebSphere Application Server using the launchpad.

    [AIX] [Linux] [HP-UX] [Solaris] The launchpad program is available on the root directory of the product CD in the program, launchpad.sh.

    [Windows] The launchpad program is available on the root directory of the product CD in the program launchpad.bat.

    [Windows] [Fix Pack 9 or later]
    [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Guidelines for installing WebSphere Application Server components on the Microsoft® Windows Vista™ operating system:
    • Using the Launchpad GUI to begin installing a Websphere Application Server Version 6.1 component is not supported when your are running Websphere Application Server on a machine that contains 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 a Websphere Application Server component on a machine running the Windows Vista operating system, you must perform the following actions:
      1. Go to the individual component directory.
      2. Run the install.exe program that is located in that directory using the administrator account that was created when the Windows Vista operating system was installed.
        • The Windows Vista operating system will detect the fact that install.exe is an installation program, and it will present 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 your computer." Examine the program details; and if it is the Websphere Application Server program that you intend to run, click Allow to proceed.
    Note: The free download Application Client installation is not packaged with the launchPad program.
    1. Click Launch the installation wizard for Application Client for WebSphere Application Server from the launchpad tool to launch the InstallShield for MultiPlatforms installation wizard. This action launches the installation wizard.
      The Readme documentation to which the launchpad links is the readme.html file in the CD root directory. The readme directory off the root of the CD has more detailed Readme files. The Installation Guide is in the /docs directory of the CD root directory.
      Note: Readme file names are based on product offerings.
      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. For example:
      cd /app_server_root/AppClient
      
      ./install
      or
       cd <CD mount point>/AppClient
      
           ./install
      Failing to use the correct working directory can cause ISMP errors that abort the installation.

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

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

    2. As indicated in the previous example, you can start the installation wizard from the product CD-ROM, using the command line.

      [AIX] [Linux] [HP-UX] [Solaris] Run the ./install command.

      [Windows] Run the Install.exe command.

    3. [AIX HP-UX Linux Solaris Windows] [iSeries] You can also perform a silent installation using the -options responsefile -silent parameter, which causes the installation wizard to read your responses from the options response file, instead of from the interactive graphical user interface. Customize the response file before installing silently. After customizing the file, issue the command to silently install. Silent installation is particularly useful if you install the product often.

      The rest of this procedure assumes that you are using the installation wizard. There are corresponding entries in the response file for every prompt that is described as part of the wizard. Review the description of the response file for more information. Comments in the file describe how to customize its options.

  4. [AIX HP-UX Linux Solaris Windows] [z/OS] Click Next to continue when the Welcome panel is displayed.
    1. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement, and click Next to continue.
  5. [AIX HP-UX Linux Solaris Windows] [z/OS] The installation wizard checks the system for prerequisites. Click Next if you see a success message on the wizard panel. If a warning message is displayed on the panel, click Cancel to exit the installation wizard and install the proper prerequisites to the system. Note: 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.
  6. [AIX HP-UX Linux Solaris Windows] [z/OS] Specify a destination directory. Click Next to continue.
    1. Ensure that there is adequate space available in the target directory.
    2. Specify a target directory for the Application Client product.
    3. Enter the required target directory to proceed to the next panel. Deleting the default target location and leaving an installation directory field empty prevents you from continuing the installation process.
  7. [AIX HP-UX Linux Solaris Windows] [z/OS] Choose a type of installation, and click Next.

    If you use the GUI you can choose a Typical installation type, which installs J2EE and Thin application client, Samples and IBM Developer Kit, Java 2 Technology Edition, or you can choose the custom installation type. For Windows, there are two custom installation types: Custom J2EE/Thin Client and Custom Pluggable Client. For other platforms, there is only one custom installation type.

    [Windows] Custom J2EE/Thin Client

    • If you select the ActiveX to EJB Bridge feature, then the following is 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 back to the feature dialog box.
    • Install the Software 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 Runtime Environment (JRE) and a complete Software Developer Kit (SDK). The JRE sub feature is selected by default for the Custom J2EE/Thin Client installation type. The SDK component is optional; however, you must install the SDK component to compile the sample.
    • Install the Administration Thin Client, if you need a runtime jar that is customized to enable client applications to perform WebSphere administration tasks. The Administration Thin Client is installed into app_server_root/runtimes.
    • Install 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_server_root/runtimes.
    • New or updated for this feature pack 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_server_root/runtimes.

    [Windows] Custom Pluggable Client

    • Install the Pluggable Client samples if you want to make use of the Pluggable Client applications.

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

    • Install the Software 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 Runtime Environment (JRE) and a complete Software Developer Kit (SDK). The JRE sub feature is selected by default for the Custom J2EE/Thin Client installation type. The SDK component is optional; however, you must install the SDK component to compile the sample.
    • Install the Administration Thin Client, if you need a runtime jar that is customized to enable client applications to perform WebSphere administration tasks. The Administration Thin Client is installed into app_server_root/runtimes.
    • Install 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_server_root/runtimes.
    • New or updated for this feature pack 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_server_root/runtimes.
  8. [AIX HP-UX Linux Solaris Windows] [z/OS] (Pluggable Client installation type only) Click Next to accept the detected Sun JRE, or click Browse to select the location of the installed Sun JRE. The Sun Software Development Kit installation location is optional. However, if the installation location is not provided, the installed Samples do not compile.
    • If Sun JRE has not been installed, the installation cannot be continued. Click Cancel to exit the installation. Install the Sun JRE, and restart the Pluggable Custom installation. The Sun JRE panel is displayed with the JRE path detected, and the Pluggable application client installation continues.
  9. [AIX HP-UX Linux Solaris Windows] [z/OS] Enter the host name of the WebSphere Application Server machine. Click Next to continue. The default port number is 2809.
  10. [AIX HP-UX Linux Solaris Windows] [z/OS] Review the summary information, and click Next to install the product code or you might also click Back to change your specifications.
  11. [AIX HP-UX Linux Solaris Windows] [z/OS] Click Finish to exit the wizard, after the Application Client installs.
  12. [AIX HP-UX Linux Solaris Windows] [z/OS] Verify the success of the installer program by examining the Completion panel and the app_server_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 that you cannot retry or recover from 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_server_root directory; however, without the necessary permission to move the file to the app_server_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/waslogs 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, add more space, and reinstall the Application Client.
[This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] Important:

You may notice that the IBM JRE icon is missing in the control panel directory. Copy the <client_home>\java\jre\bin\IBMJavaPlugin150.cpl file into the C:\Windows\System32\ directory. The icon should now display in the control panel.

[Solaris] Important: If the installation fails, set PATH to blank and re-install.



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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tcli_installclient
File name: tcli_installclient.html