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
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.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.
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.
Although
it is not supported or recommended, you can install this product as
a non-root user on a UNIX operating system. However, you must use
a user ID that is part of the administrator group on Windows platforms.
It is recommended that you have 350 MB of temporary disk
space available before beginning the installation.
![[Windows]](../../windows.gif)
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.
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.0.x.x when installing Application
Client Version 6.0.x Fix Packs. Using a later Application Client version
will create problems if, in the future, you install a later Application
Client version on the same machine.
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.
Important: If the installation fails, set PATH to blank and
re-install.