Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop Client applications > Develop client applications

Install, updating, rolling back, and uninstalling the Application Client for IBM WAS

IBM Installation Manager is a common installer for many IBM software products that you use to install, update, roll back, and uninstall the Application Client for IBM WAS.

New feature: Application Client for IBM WAS is now installed by Installation Manager rather than by the programs based on InstallShield MultiPlatform (ISMP) that are used to install and uninstall previous versions.New feature:

Before you start to use the installation tools, prepare for choosing and installing the variety of options and features provided by the Application Client. Read through all the steps in this article and read the related topics before installing the Application Client:

IBM recommends that we have 350 MB of temporary disk space available before starting the installation.

Restrictions:

• (Solaris) The Installation Manager GUI is not supported on Solaris 10 x64 systems. Perform the following actions to install or uninstall the product on these systems:

  • Use the Installation Manager GUI on a supported system to record a response file that will allow you to install or uninstall the product.
  • Edit the recorded response file if necessary.

  • Use the response file to install or uninstall the product on your system.

• For any Linux system that is enabled for Security Enhanced Linux (SELinux), such as Red Hat Enterprise Linux Version 5 or SUSE Linux Enterprise Server v11, identify the Java shared libraries in the Installation Manager v1.4.3 or earlier installation image to the system. Also, identify the Java shared libraries in the Installation Manager v1.4.3 or earlier installation after it has been installed. For example:

  chcon -R -t texrel_shlib_t ${IM_Image}/jre_5.0.3.sr8a_20080811b/jre/bin
  chcon -R -t texrel_shlib_t ${IM_Install_root}/eclipse/jre_5.0.3.sr8a_20080811b/jre/bin
  

• Application Client for WAS ships only with the 32-bit WAS.

• Installation Manager console mode, which is included in Installation Manager v1.4.3 and later, does not work with WAS v8.0 offerings.

The Application Client provides resources and clients to aid development of client applications for use with WAS. The Application Client is a source for the clients (as runtime frameworks) for client applications, either to run on the Application Client machine or to be distributed with client applications that are to run on other machines.

To assemble some types of client applications, install the client that provides the framework for the client application. Instead of installing WAS, you can install the Application Client feature, which provides the same resources and clients to aid development of client applications.

Similarly, running some types of client applications for use with WAS requires that the associated client is deployed with the client application. For client applications that only need a small fraction of the Application Client, you can install the Application Client onto a convenient machine, such as the machine used to develop the client application, then package the client application with only the clients that it needs. For example, this means that a standalone client application is deployed on only the required fraction of the clients provided with the Application Client.

Procedure

• Install the Application Client using the GUI
• Install the Application Client using response files
• Install and uninstall features in the Application Client
• Install fix packs on the Application Client using the GUI
• Uninstall fix packs from the Application Client using the GUI
• Uninstall the Application Client using the GUI
• Uninstall the Application Client using response files

Results

Notes on logging and tracing:

• An easy way to view the logs is to open Installation Manager and go to File > View Log. An individual log file can be opened by selecting it in the table and then clicking the Open log file icon.
• Logs are located in the logs directory of Installation Manager's application data location. For example:
  • (Windows) Administrative installation:

    C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs
    

  • (Windows) Non-administrative installation:

    C:\Documents and Settings\user_name\Application Data\IBM\Installation Manager\logs
    

  • (AIX) (Solaris) Administrative installation:

    /var/ibm/InstallationManager/logs
    

  • (AIX) (Solaris) Non-administrative installation:

    user_home/var/ibm/InstallationManager/logs
    

• The main log files are time-stamped XML files in the logs directory, and they can be viewed using any standard web browser.
• The log.properties file in the logs directory specifies the level of logging or tracing that Installation Manager uses.

  To turn on tracing, for example, create a log.properties file with the following content:

  com.ibm.ws=DEBUG
  com.ibm.cic.agent.core.Engine=DEBUG
  global=DEBUG
  

  Restart Installation Manager as necessary, and Installation Manager outputs traces.

Notes on troubleshooting:

• By default, some HP-UX systems are configured to not use DNS to resolve host names. This could result in Installation Manager not being able to connect to an external repository.

  You can ping the repository, but nslookup does not return anything.

  Work with the system administrator to configure your machine to use DNS, or use the IP address of the repository.

• In some cases, you might need to bypass existing checking mechanisms in Installation Manager.
  • On some network file systems, disk space might not be reported correctly at times; and you might need to bypass disk-space checking and proceed with your installation.

    To disable disk-space checking, specify the following system property in the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager:

    cic.override.disk.space=sizeunit
    

    where size is a positive integer and unit is blank for bytes, k for kilo, m for megabytes, or g for gigabytes. For example:

    cic.override.disk.space=120 (120 bytes)
    cic.override.disk.space=130k (130 kilobytes)
    cic.override.disk.space=140m (140 megabytes)
    cic.override.disk.space=150g (150 gigabytes)
    cic.override.disk.space=true
    

    Installation Manager will report a disk-space size of Long.MAX_VALUE. Instead of displaying a very large amount of available disk space, N/A is displayed.

  • To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager.

  If use any of these bypass methods, contact IBM Support for assistance in developing a solution that does not involve bypassing the Installation Manager checking mechanisms.

• For more information on using Installation Manager, read the IBM Installation Manager v1.4 Information Center.

  Read the release notes to learn more about the latest version of Installation Manager. To access the release notes, complete the following task:

  • (Windows) Click Start > Programs > IBM Installation Manager > Release Notes.
  • (AIX) (Solaris) Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.

Related

Install the Application Client using the GUI
Install the Application Client using response files
Install and uninstall features in the Application Client
Install fix packs on the Application Client using the GUI
Uninstall fix packs from the Application Client using the GUI
Uninstall the Application Client using the GUI
Uninstall the Application Client using response files

+

Search Tips   |   Advanced Search