+

Search Tips   |   Advanced Search

(dist)

Install the Application Client using response files

We can install the Application Client using Installation Manager response files.


Install Installation Manager on each of the systems onto which to install the product.

Use Installation Manager, we can work with response files to install the Application Client in a variety of ways. We can record a response file using the GUI as described in the following procedure, or we can generate a new response file by hand or by taking an example and modifying it.

  1. Optional: Record a response file to install the Application Client: On one of the systems, perform the following actions to record a response file that will install the Application Client.

    1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.

    2. Start Installation Manager from the command line using the -record option.

      For example:

      • Administrator or non-administrator:

          IBMIM.exe -skipInstall "C:\temp\imRegistry" -record C:\temp\install_response_file.xml


      • Administrator:

          ./IBMIM -skipInstall /var/temp/imRegistry -record /var/temp/install_response_file.xml


      • Non-administrator:

          ./IBMIM -skipInstall user_home/var/temp/imRegistry -record user_home/var/temp/install_response_file.xml

      When you record a new response file, we can specify the -skipInstall parameter. Using this parameter has the following benefits:

      • No files are actually installed, and this speeds up the recording.

      • If we use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording. When you start Installation Manager again without the -skipInstall parameter, you then can use the response file to install against the real installation registry.

        The -skipInstall operation should not be used on the actual agent data location used by Installation Manager. This is unsupported. Use a clean writable location, and re-use that location for future recording sessions.

      For more information, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

    3. Add the appropriate repositories to the Installation Manager preferences.

      1. In the menu, click File > Preferences.

      2. Select Repositories.

      3. Perform the following actions for each repository:

        1. Click Add Repository.

        2. Enter the path to the repository.config file in the remote web-based repository or the local directory into which you unpacked the repository files.

          For example:

          • Remote repositories:

              https://downloads.mycorp.com:8080/WAS_85_repository

            or

              http://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85

          • Local repositories:

            • C:\repositories\appclient\local-repositories

            • /var/repositories/appclient/local-repositories

        3. Click OK.

      4. Click Apply.

      5. Click OK.

    4. Click Install.

      If we are prompted to authenticate, use the IBM ID and password that you registered with on the program website.

      Installation Manager searches its defined repositories for available packages.

    5. Perform the following actions.

      1. Select Application Client for IBM WebSphere Application Server and the appropriate version.

        If we are installing the ILAN version of this product, select Application Client for IBM WebSphere Application Server (ILAN).

        If we already have the Application Client installed on the system, a message displays indicating that the Application Client is already installed. For a given Installation Manager, we can install only one Application Client.

      2. Click Next.

    6. Accept the terms in the license agreements, and click Next.

    7. Installation root directory for the Application Client binaries, which are also referred to as the core product files or system files.

      The panel also displays the shared resources directory and disk-space information.

      Restrictions:

      • Delete the default target location and leaving an installation-directory field empty prevents you from continuing.

      • Do not use symbolic links as the destination directory.

        Symbolic links are not supported.

      • Do not use a semicolon in the directory name.

        The Application Client cannot install properly if the target directory includes a semicolon.

        A semicolon is the character used to construct the class path on Windows systems.

      • The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.

    8. Click Next.

    9. Select any features to install.

      Choose from the following optional features:

      • IBM Developer Kit, Java 2 Technology Edition

        This option installs the IBM Developer Kit, Java 2 Technology Edition.

        This feature includes a development kit and a runtime-environment package. The runtime-environment package is always installed with the Java EE and Java thin application client feature even if this feature is not installed.

        • Java 2 Runtime Environment

          This option installs the Java 2 runtime environment.

          This feature includes the Java 2 runtime environment of IBM Developer Kit, Java 2 Technology Edition.

        • Developer Kit

          This option installs the developer kit.

          This feature includes the developer kit of IBM Developer Kit, Java 2 Technology Edition.

      • Samples

        This option installs executable and source-code examples of programming in both Java EE and non-Java EE client environments.

      • Standalone Thin Clients, Resource Adapters, and Embeddable Containers

        IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, we can use the embeddable EJB container to run enterprise beans outside the application server.

        • Standalone thin clients and resource adapters

          This option installs the runtime for standalone thin clients.

        • Embeddable EJB container

          This option installs the embeddable EJB container.

          The embeddable EJB container is a Java Archive (JAR) file that we can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. We can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

      We can run the Installation Manager later to modify this installation and add or remove features.

    10. Click Next.

    11. Enter the host name and port number of the Websphere Application Server to which to connect.

    12. Click Next.

    13. Review the summary information, and click Install.

      • If the installation is successful, the program displays a message indicating that installation is successful.

        The program might also display important post-installation instructions as well.

      • If the installation is not successful, click View Log File to troubleshoot the problem.

    14. Click Finish.

    15. Click File > Exit to close Installation Manager.

    16. Optional: For an authenticated remote repository, create a keyring file for installation.

      1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.

      2. Start Installation Manager from the command line using the -record option.

        For example:

        • Administrator or non-administrator:

            IBMIM.exe -skipInstall "C:\temp\imRegistry" -keyring C:\IM\im.keyring -record C:\temp\keyring_response_file.xml


        • Administrator:

            ./IBMIM -skipInstall /var/temp/imRegistry -keyring /var/IM/im.keyring -record /var/temp/keyring_response_file.xml


        • Non-administrator:

            ./IBMIM -skipInstall user_home/var/temp/imRegistry -keyring user_home/var/IM/im.keyring -record user_home/var/temp/keyring_response_file.xml

      3. When a window opens that requests the credentials for the authenticated remote repository, enter the correct credentials and save them.

      4. Click File > Exit to close Installation Manager.

        For more information, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

      Start in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

      In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager prior to version 1.7. Update Installation Manager to version 1.7 or higher and then recreate and replace any secure storage files created with earlier versions.

      There is no migration path from keyring files to storage files because of the differences in the file structures. Create a storage file to replace a keyring file. For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.

  2. Use the response files to install the Application Client:

    1. Optional: Use the response file to install the keyring: Go to a command line on each of the systems on which to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring.

      For example:

      • Administrator or non-administrator:

          imcl.exe -acceptLicense input C:\temp\keyring_response_file.xml -log C:\temp\keyring_log.xml


      • Administrator:

          ./imcl -acceptLicense input /var/temp/keyring_response_file.xml -log /var/temp/keyring_log.xml


      • Non-administrator:

          ./imcl -acceptLicense input user_home/var/temp/keyring_response_file.xml -log user_home/var/temp/keyring_log.xml

    2. Use the response file to install the product : Go to a command line on each of the systems on which to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the product.

      For example:

      • Administrator or non-administrator:

          imcl.exe -acceptLicense input C:\temp\install_response_file.xml -log C:\temp\install_log.xml -keyring C:\IM\im.keyring


      • Administrator:

          ./imcl -acceptLicense input /var/temp/install_response_file.xml -log /var/temp/install_log.xml -keyring /var/IM/im.keyring


      • Non-administrator:

          ./imcl -acceptLicense input user_home/var/temp/install_response_file.xml -log user_home/var/temp/install_log.xml -keyring user_home/var/IM/im.keyring

      • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation image or repository for this product.

      • The program might write important post-installation instructions to standard output.

      Read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center for more information.


Example

The following is an example of a response file for installing the Application Client. 

<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean="true" temporary="true">
server
<repository location="http://www.ibm.com/software/repositorymanager/com.ibm.websphere.APPCLIENT.v85" />
</server>
<install modify='false'>
<offering id='com.ibm.websphere.APPCLIENT.v85'    profile='Application Client for IBM WebSphere Application Server V8.5'    features='javaee.thinclient.core.feature,javaruntime,developerkit,embeddablecontainer' installFixes='none'/>
</install>
<profile id='Application Client for IBM WebSphere Application Server V8.5'    installLocation='C:\IBM\WebSphere\AppClient'>
<data key='eclipseLocation' value='C:\IBM\WebSphere\AppClient'/>
<data key='user.import.profile' value='false'/>
<data key='user.select.64bit.image,com.ibm.websphere.APPCLIENT.v85' value='false'/>
<data key='user.appclient.serverHostname' value='localhost'/>
<data key='user.appclient.serverPort' value='2809'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>

In the following list, the optional feature offering names are enclosed in parentheses:

If no features are specified, the required features and those selected by default (javaruntime, developerkit, and embeddablecontainer) are installed. To install only the features we want, specify the list of features explicitly.

See Sample response file: Install the Application Client for IBM WebSphere Application Server for an annotated sample of a response file for performing this procedure.


Related tasks

  • Installing, updating, rolling back, and uninstalling the Application Client for IBM WebSphere Application Server
  • Install the Application Client using the GUI
  • Install the Application Client using the command line
  • Install 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
  • Uninstall the Application Client using the command line