[AIX HP-UX Linux Solaris Windows]

Installing the feature pack on distributed operating systems silently

You can use Installation Manager to install this feature pack silently.

Before you begin

Notes:
  • [Linux] [Fix Pack 9 or later] On the Asianux Server 3 operating system, use IBM® Installation Manager for WebSphere® Version 1.3.4.1 or later to install feature packs for WebSphere Application Server Version 7.0.
  • [Fix Pack 11 or later] You must use IBM Installation Manager Version 1.4.0 or later to install, modify, or uninstall a feature pack on WebSphere Application Server Version 7.0 Fix Pack 11 or later. For more information, see the support documentation for IBM Installation Manager.

Perform the following actions before you install the feature pack.

Detailed preinstallation steps:
  1. Prepare your systems: On each of the systems onto which you want to install the feature pack, perform the following actions:
    1. Install WebSphere Application Server:
      Install one of the following products if you have not done so already:
      • IBM WebSphere Application Server Version 7.0
      • IBM WebSphere Application Server Trial Version 7.0
      • IBM WebSphere Application Server - Express Version 7.0
      • IBM WebSphere Application Server - Express Trial Version 7.0
      • IBM WebSphere Application Server Developers Edition Version 7.0
      • IBM WebSphere Application Server Network Deployment Version 7.0
    2. Install the required product updates:
      Download and install the required fix packs and recommended interim fixes if you have not done so already.
      1. Download and install the latest version of the WebSphere Update Installer.

        For further information, go to the WebSphere Application Server Support Download Web site.

      2. Download both of the following fix packs from the WebSphere Application Server Support Download Web site:
        • [Feature Pack for OSGi Applications and JPA 2.0 Fix Pack 1 or later] IBM WebSphere Application Server Version 7.0 Fix Pack 9 or later
        • [Feature Pack for OSGi Applications and JPA 2.0 Fix Pack 1 or later] Java SDK 1.6.0 SR7 Cumulative Fix for WebSphere Application Server Version 7.0 Fix Pack 9 or later
        Note: The WebSphere Application Server and SDK fix packs must be at the same level.
      3. Download any interim fixes that are recommended for the feature pack from the WebSphere Application Server Support Download Web site.
      4. Use the Update Installer to install the fix packs and any recommended interim fixes.
    3. Install Installation Manager, and optionally configure the product repositories:
      Perform one of the following procedures:
      • If you want to use the Installation Manager that is preconfigured with the repositories for this feature pack, perform the following actions:
        1. Download the necessary compressed files from the Web to your system.
          There are three options for downloading and installing the preconfigured Installation Manager and the feature pack.
          • Download a file from the Passport Advantage® site, and use web-based or local installation

            Licensed customers can download and unpack a compressed file containing the preconfigured Installation Manager as well as the necessary product repositories. You can then install Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from either the web-based repositories or the unpacked local product repositories.

          • Download a file from the Installation Manager Download Web site, and use web-based installation

            You can download and unpack a compressed file containing the Installation Manager appropriate for your operating system from the IBM Installation Manager Download Web site. You can then install Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the web-based repositories.

          • Download files from both the Installation Manager Download Web site and the Feature Pack for OSGi Applications and Java Persistence API 2.0 Web site, and use local installation

            You can download and unpack a compressed file containing the Installation Manager appropriate for your operating system from the IBM Installation Manager Download Web site and download the compressed file containing the base-product importation and feature pack product repositories from the Feature Pack for OSGi Applications and Java Persistence API 2.0 Web site. You can then install Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the unpacked local product repositories.

          Notes:
          • The feature pack version of Installation Manager is preconfigured to use both the local repositories that are included in the download and the remote repositories.
            Note: If you move the local repositories that are included in the download, you must reconfigure the location of the repositories in Installation Manager.
          • Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files.
          • If you use local repositories, you can leave in the remote repositories as well because they will provide post-shipment service updates when you are connected to the Web.
          Supported configurations Supported configurations: The generally available (GA) version of the Feature Pack for OSGi Applications and Java Persistence API 2.0, Version 1.0, downloadable files contain repositories for importing existing installations of WebSphere Application Server Versions 7.0.0.0 through 7.0 Fix Pack 9 into Installation Manager. When a fix pack later than 7.0 Fix Pack 9 is applied to your existing WebSphere Application Server 7.0 installation, an import will not detect the correct fix-pack level using the original downloaded repositories. The web-based service repositories are updated regularly to contain later importation definitions. If you have an existing WebSphere Application Server installation that is later than Version 7.0 Fix Pack 9, you must ensure that you are connected to the web-based repositories. Alternatively, you can download an updated version of the local import repository to use when you are not connected to the Web. You can use one of the following methods:
          • Web-based repository:

            If you want to use a web-based repository, then you do not need to download a file. Instead, add the following URL to your Installation Manager repository list:

            http://public.dhe.ibm.com/software/websphere/repositories
          • Local repository:

            If you want to use a local repository, then you must download an updated version of the local import repository. After you download the file and uncompress it, add the location of the uncompressed files to the Installation Manager repository list. You can download an updated version of the 7.0 local import repository at the following URL:

            ftp://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip
          sptcfg
        2. Unpack the compressed file containing Installation Manager into a temporary folder such as IM_temp.
        3. Run one of the following commands in the temporary folder to install Installation Manager:
          • [Windows] Administrative installation: install.exe
          • [Windows] Non-administrative installation: userinst.exe
          • [AIX] [HP-UX] [Linux] [Solaris] Administrative installation: ./install
          • [AIX] [HP-UX] [Linux] [Solaris] Non-administrative installation: ./userinst

          The installer opens an Install Packages window.

        4. Make sure that the Installation Manager package is selected, and click Next.
        5. Accept the terms in the license agreements, and click Next.

          The program creates the directory for your installation.

        6. Click Next.
        7. Review the summary information, and click Install.
          • If the installation is successful, the program displays a message indicating that installation is successful.
          • If the installation is not successful, click View Log File to troubleshoot the problem.
        8. Configure each local repository in Installation Manager if you are using local feature pack, importation, and service repositories to install the feature pack.
          1. Unpack the compressed file containing the repository to a directory on your system.
          2. Add the local repository to your Installation Manager preferences.
            1. In the top menu, click File > Preferences.
            2. Select Repositories.
            3. Perform the following actions:
              1. Click Add Repository.
              2. Enter the path to the repository.config file in the local directory into which you unpacked the repository files.
                For example:
                • [Windows] C:\repositories\was70\jpa_and_import_repositories
                • [Windows] C:\repositories\was70\jpa_1001_fp_repository
                • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/jpa_and_import_repositories/local-repositories
                • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/jpa_1001_fp_repository
              3. Click OK.
            4. Deselect any locations listed in the Repositories window that you will not be using.
            5. Click Apply.
            6. Click OK.
            7. Click File > Exit to close Installation Manager.
      • If you already have a version of Installation Manager installed on your system and you want to use it to install and maintain the feature pack, perform the following actions:
        1. Download the necessary compressed files from the Web to your system.
          There are three options for downloading and installing the feature pack.
          • Download a file from the Passport Advantage site, and use web-based or local installation

            Licensed customers can download and unpack a compressed file containing the necessary product repositories. You can then use Installation Manager to import WebSphere Application Server Version 7.0 as well as to install the feature pack from either the web-based repositories or the unpacked local product repositories.

          • Use web-based installation

            You can use your existing Installation Manager to import WebSphere Application Server Version 7.0 and to install the feature pack from the web-based repositories.

          • Download files from the Feature Pack for OSGi Applications and Java Persistence API 2.0 Web site, and use local installation

            You can download the compressed file containing the base-product importation and feature pack product repositories from the Feature Pack for OSGi Applications and Java Persistence API 2.0 Web site. You can then use your existing Installation Manager to import WebSphere Application Server Version 7.0 and to install the feature pack from the unpacked local product repositories.

          Notes:
          • Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files.
          • If you use local repositories, you can leave in the remote repositories as well because they will provide post-shipment service updates when you are connected to the Web.
          Supported configurations Supported configurations: The generally available (GA) version of the Feature Pack for OSGi Applications and Java Persistence API 2.0, Version 1.0, downloadable files contain repositories for importing existing installations of WebSphere Application Server Versions 7.0.0.0 through 7.0 Fix Pack 9 into Installation Manager. When a fix pack later than 7.0 Fix Pack 9 is applied to your existing WebSphere Application Server 7.0 installation, an import will not detect the correct fix-pack level using the original downloaded repositories. The web-based service repositories are updated regularly to contain later importation definitions. If you have an existing WebSphere Application Server installation that is later than Version 7.0 Fix Pack 9, you must ensure that you are connected to the web-based repositories. Alternatively, you can download an updated version of the local import repository to use when you are not connected to the Web. You can use one of the following methods:
          • Web-based repository:

            If you want to use a web-based repository, then you do not need to download a file. Instead, add the following URL to your Installation Manager repository list:

            http://public.dhe.ibm.com/software/websphere/repositories
          • Local repository:

            If you want to use a local repository, then you must download an updated version of the local import repository. After you download the file and uncompress it, add the location of the uncompressed files to the Installation Manager repository list. You can download an updated version of the 7.0 local import repository at the following URL:

            ftp://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip
          sptcfg
        2. If you are using the web-based repositories, add them to your Installation Manager preferences.
          1. In the top menu, click File > Preferences.
          2. Select Repositories.
          3. Perform the following actions:
            1. Click Add Repository.
            2. Enter the URL for the following product repository:
              https://www.ibm.com/software/rational/repositorymanager/repositories/websphere
            3. Click OK.
            4. Click Add Repository.
            5. Enter the URL for the following service repository:
              http://public.dhe.ibm.com/software/websphere/repositories
            6. Click OK.
          4. Deselect any locations listed in the Repositories window that you will not be using.
          5. Click Apply.
          6. Click OK.
          7. Click File > Exit to close Installation Manager.
        3. Configure each local repository in Installation Manager if you are using local feature pack, importation, and service repositories to install the feature pack.
          1. Unpack the compressed file containing the repository to a directory on your system.
          2. Add the local repository to your Installation Manager preferences.
            1. In the top menu, click File > Preferences.
            2. Select Repositories.
            3. Perform the following actions:
              1. Click Add Repository.
              2. Enter the path to the repository.config file in the local directory into which you unpacked the repository files.
                For example:
                • [Windows] C:\repositories\was70\jpa_and_import_repositories
                • [Windows] C:\repositories\was70\jpa_1001_fp_repository
                • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/jpa_and_import_repositories
                • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/jpa_1001_fp_repository
              3. Click OK.
            4. Deselect any locations listed in the Repositories window that you will not be using.
            5. Click Apply.
            6. Click OK.
            7. Click File > Exit to close Installation Manager.
  2. Record a response file to import WebSphere Application Server: On one of your systems, perform the following actions to record a response file that will import existing installations of WebSphere Application Server Version 7.0.0.x:
    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:
      • [Windows] Administrator or non-administrator:
        IBMIM.exe 
          -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\import_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./IBMIM 
          -skipInstall /var/temp/imRegistry 
          -record /var/temp/import_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./IBMIM 
          -skipInstall user_home/var/temp/imRegistry 
          -record user_home/var/temp/import_response_file.xml
      Tip: When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:
      • No files are actually installed, and this speeds up the recording.
      • If you use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording the response file. When you start Installation Manager again without the -skipInstall parameter, you then can use your response file to import 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 Information Center.

    3. Add the appropriate repositories to your Installation Manager preferences.
      1. In the top 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://www.ibm.com/software/rational/repositorymanager/repositories/websphere
            • http://public.dhe.ibm.com/software/websphere/repositories
          • Local repositories:
            • [Windows] C:\repositories\was70\osgijpa2_and_import_repositories
            • [Windows] C:\repositories\was70\osgijpa2__fp_repository
            • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/osgijpa2_and_import_repositories
            • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/osgijpa2__fp_repository
        3. Click OK.
      4. Click Apply.
      5. Click OK.
    4. Click Import, or click File > Open > Import Packages in the top menu.
      Notes:
      • If you did not configure your Installation Manager preferences to include the appropriate repository as described earlier in this procedure, the Import button or Import Packages option does not appear. Add the repository and restart Installation Manager.
      • If you are prompted to authenticate, use the IBM ID and password that you registered with on the Web site.
    5. In the Installation Directory field, perform one of the following actions and then click Next.
      • Enter the path to an existing WebSphere Application Server Version 7.0.0.x installation.
        For example:
        • [AIX] /usr/IBM/WebSphere/AppServer
        • [HP-UX] [Linux] [Solaris] /opt/IBM/WebSphere/AppServer
        • [Windows] C:\Program Files\IBM\WebSphere\AppServer
      • Select the path to an existing WebSphere Application Server Version 7.0.0.x installation from the drop-down list.
      • Click Browse to find an existing WebSphere Application Server Version 7.0.0.x installation.
    6. If a panel displays requesting a shared resources directory, perform the following actions:
      1. In the Shared Resources Directory field, perform one of the following actions:
        • Accept the default directory.
        • Enter the path to a shared resources directory.
        • Click Browse to find an existing directory to use for the shared resources.
      2. Click Next.
    7. Click Import to have Installation Manager add that installation into its inventory of installed packages.
      A bar shows progress.
      • If the import process is successful, the program displays a message indicating that installation is successful.
      • If the import process is not successful, click View Log File to troubleshoot the problem.
    8. Click Finish.
    9. Click File > Exit to close Installation Manager.
    10. If you are using an authenticated remote repository, create a keyring file for silent 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:
        • [Windows] Administrator or non-administrator:
          IBMIM.exe 
            -skipInstall "C:\temp\imRegistry" 
            -keyring C:\IM\im.keyring 
            -record C:\temp\keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM 
            -skipInstall /var/temp/imRegistry 
            -keyring /var/IM/im.keyring 
            -record /var/temp/keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] 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 your 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 Information Center.

  3. Use the response files that you created to import WebSphere Application Server silently: .
    1. Use the keyring response file that you created to install the keyring silently:
      • If you are using Installation Manager 1.4.2 or earlier, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse subdirectory in the directory where you installed Installation Manager, and install the keyring silently.
        For example:
        • [Windows] Administrator or non-administrator:
          IBMIMc.exe --launcher.ini silent-install.ini 
            -input C:\temp\keyring_response_file.xml 
            -log C:\temp\keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input /var/temp/keyring_response_file.xml 
            -log /var/temp/keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input user_home/var/temp/keyring_response_file.xml 
            -log user_home/var/temp/keyring_log.xml
      • If you are using Installation Manager 1.4.3 or later, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring silently.
        For example:
        • [Windows] Administrator or non-administrator:
          imcl.exe -acceptLicense 
            input C:\temp\keyring_response_file.xml 
            -log C:\temp\keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./imcl -acceptLicense 
            input /var/temp/keyring_response_file.xml 
            -log /var/temp/keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./imcl -acceptLicense 
            input user_home/var/temp/keyring_response_file.xml 
            -log user_home/var/temp/keyring_log.xml
    2. Use the importation response file that you created to import WebSphere Application Server silently:
      • If you are using Installation Manager 1.4.2 or earlier, go to a command line on each of the systems on which you want to import the product, change to the eclipse subdirectory in the directory where you installed Installation Manager, and import the product silently.
        For example:
        • [Windows] Administrator or non-administrator:
          IBMIMc.exe --launcher.ini silent-install.ini 
            -input C:\temp\import_response_file.xml 
            -log C:\temp\import_log.xml 
            -keyring C:\IM\im.keyring 
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input /var/temp/import_response_file.xml 
            -log /var/temp/import_log.xml 
            -keyring /var/IM/im.keyring 
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input user_home/var/temp/import_response_file.xml 
            -log user_home/var/temp/import_log.xml 
            -keyring user_home/var/IM/im.keyring 
      • If you are using Installation Manager 1.4.3 or later, go to a command line on each of the systems on which you want to import the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and import the product silently.
        For example:
        • [Windows] Administrator or non-administrator:
          imcl.exe -acceptLicense 
            -input C:\temp\import_response_file.xml 
            -log C:\temp\import_log.xml 
            -keyring C:\IM\im.keyring 
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./imcl -acceptLicense 
            -input /var/temp/import_response_file.xml 
            -log /var/temp/import_log.xml 
            -keyring /var/IM/im.keyring 
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./imcl -acceptLicense 
            -input user_home/var/temp/import_response_file.xml 
            -log user_home/var/temp/import_log.xml 
            -keyring user_home/var/IM/im.keyring

      For more information, read the IBM Installation Manager Information Center.

About this task

Perform this procedure to install the feature pack silently.

Tip: These instructions describe how you can use Installation Manager to create two separate response files for importing an existing WebSphere Application Server Version 7.0 base-product installation and installing the feature pack. You could combine these two operations into one recording session and therefore produce one response file that performs both operations silently. In other words, you could launch Installation Manager in record mode, import your existing installation, then install the feature pack. You could then use the response file that you created to perform both operations silently with one invocation. The sample response file at the end of this article is already an example of such a file.

Procedure

  1. Stop all servers on the WebSphere Application Server installations that are being upgraded.
  2. Record a response file to install the feature pack: On one of your systems, perform the following actions to record a response file that will install the feature pack.
    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:
      • [Windows] Administrator or non-administrator:
        IBMIM.exe 
          -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./IBMIM 
          -skipInstall /var/temp/imRegistry 
          -record /var/temp/install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./IBMIM 
          -skipInstall user_home/var/temp/imRegistry 
          -record user_home/var/temp/install_response_file.xml
      Tip: When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:
      • No files are actually installed, and this speeds up the recording.
      • If you use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording the response file. When you start Installation Manager again without the -skipInstall parameter, you then can use your 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 Information Center.

    3. Add the appropriate repositories to your Installation Manager preferences.
      1. In the top 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://www.ibm.com/software/rational/repositorymanager/repositories/websphere
            • http://public.dhe.ibm.com/software/websphere/repositories
          • Local repositories:
            • [Windows] C:\repositories\was70\osgijpa2_and_import_repositories
            • [Windows] C:\repositories\was70\osgijpa2_1001_fp_repository
            • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/osgijpa2_and_import_repositories
            • [AIX] [HP-UX] [Linux] [Solaris] /var/repositories/was70/osgijpa2_1001_fp_repository
        3. Click OK.
      4. Click Apply.
      5. Click OK.
    4. Click Install.
      Note: If you 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 appropriate actions.
      1. Select IBM WebSphere Application Server V7 Feature Pack for OSGi Applications and Java Persistence API 2.0 and the appropriate version.

        If you already have the feature pack installed on a WebSphere Application Server installation on your system, a message displays indicating that the feature pack is already installed. To install the feature pack on a WebSphere Application Server installation where it is not yet installed, click Continue.

      2. Click Next.
    6. Accept the terms in the license agreements, and click Next.
    7. If multiple import operations were performed, select the appropriate installation.
    8. Click Next.
    9. Optional: Clear the OSGi Applications or Java Persistence API 2.0 checkbox if you do not want to install one of the features.
      Notes:
      • The features are selected by default.
      • You must select at least one of the features.
      • After you install a feature, you must use the manageprofiles command or the Profile Management Tool to augment an existing profile or create a new profile when this installation is finished to enable the functionality provided by the feature.
    10. Click Next.
    11. Review the summary information, and click Install.
    12. Click Finish.
    13. Click File > Exit to close Installation Manager.
    14. Optional: If you are using an authenticated remote repository, create a keyring file for silent 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:
        • [Windows] Administrator or non-administrator:
          IBMIM.exe 
            -skipInstall "C:\temp\imRegistry" 
            -keyring C:\IM\im.keyring 
            -record C:\temp\keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM 
            -skipInstall /var/temp/imRegistry 
            -keyring /var/IM/im.keyring 
            -record /var/temp/keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] 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 your 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 Information Center.

  3. Use the response files to install the feature pack silently:
    1. Optional: Use the keyring response file that you created to install the keyring silently:
      • If you are using Installation Manager 1.4.2 or earlier, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse subdirectory in the directory where you installed Installation Manager, and install the keyring silently.
        For example:
        • [Windows] Administrator or non-administrator:
          IBMIMc.exe --launcher.ini silent-install.ini 
            -input C:\temp\keyring_response_file.xml 
            -log C:\temp\keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input /var/temp/keyring_response_file.xml 
            -log /var/temp/keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input user_home/var/temp/keyring_response_file.xml 
            -log user_home/var/temp/keyring_log.xml
      • If you are using Installation Manager 1.4.3 or later, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring silently.
        For example:
        • [Windows] Administrator or non-administrator:
          imcl.exe -acceptLicense 
            input C:\temp\keyring_response_file.xml 
            -log C:\temp\keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./imcl -acceptLicense 
            input /var/temp/keyring_response_file.xml 
            -log /var/temp/keyring_log.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./imcl -acceptLicense 
            input user_home/var/temp/keyring_response_file.xml 
            -log user_home/var/temp/keyring_log.xml

      For more information on keyring files, read the IBM Installation Manager Information Center.

    2. Use the installation response file that you created to install the feature pack silently:
      • If you are using Installation Manager 1.4.2 or earlier, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse subdirectory in the directory where you installed Installation Manager, and install the feature pack silently.
        For example:
        • [Windows] Administrator or non-administrator:
          IBMIMc.exe --launcher.ini silent-install.ini 
            -input C:\temp\install_response_file.xml 
            -log C:\temp\install_log.xml 
            -keyring C:\IM\im.keyring
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input /var/temp/install_response_file.xml 
            -log /var/temp/install_log.xml 
            -keyring /var/IM/im.keyring
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM --launcher.ini silent-install.ini 
            -input user_home/var/temp/install_response_file.xml 
            -log user_home/var/temp/install_log.xml 
            -keyring user_home/var/IM/im.keyring
      • If you are using Installation Manager 1.4.3 or later, go to a command line on each of the systems on which you want to install the feature pack, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the feature pack silently.
        For example:
        • [Windows] 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
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./imcl -acceptLicense 
            input /var/temp/install_response_file.xml 
            -log /var/temp/install_log.xml 
            -keyring /var/IM/im.keyring
        • [AIX] [HP-UX] [Linux] [Solaris] 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
      Note: The program might write important post-installation instructions to standard output.

      Read the IBM Installation Manager Information Center for more information.

Example

[Windows] The following is an example of a response file for silently importing an existing installation of WebSphere Application Server Version 7.0.0.x and installing the feature pack using Installation Manager 1.4.2 or earlier.
<?xml version="1.0" encoding="UTF-8"?>

<!-- ##### Copyright ######################################################
# Licensed Materials - Property of IBM
# 5724-H88, 5724-J08, 5724-I63, 5724-H89 (c) Copyright IBM Corp. 2010. 
# All Rights Reserved. US Government Users Restricted Rights-Use, duplication 
# or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
####################################################################### -->
   
<!-- ##### Frequently Asked Questions #####################################
# The latest information about using Installation Manager is 
# located in the online Information Center. There you can find 
# information about the commands and attributes used in 
# silent installation response files.
# 
#     Installation Manager Information Center can be found at:
#     http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp
# 
# Question 1. How do I record a response file using Installation Manager?
# Answer 1. Start Installation Manager from the command line with the
# record parameter and it will generate a response file containing actions 
# it performed, repositories it used, and its preferences settings. 
# Optionally use the -skipInstall parameter if you do not want the product
# to be installed to the machine. Specify a new agentDataLocation location 
# value when doing a new installation. Do not use an existing 
# agentDataLocation for an installation because it might damage the 
# installation data and prevent you from modifying, updating, rolling back, 
# or uninstalling the installed packages.
#
# Windows: IBMIM -record <responseFile> -skipInstall <agentDataLocation>
# Linux or UNIX: ./IBMIM -record <responseFile> -skipInstall <agentDataLocation>
# 
# For example:
#   Windows = IBMIM.exe -record c:\temp\responsefiles\FEP.install.xml
#     -skipInstall c:\temp\skipInstall\WebSphere_Feature_Pack
#   Linux or UNIX = ./IBMIM -record /home/user/responsefiles/FEP.install.xml
#     -skipInstall c:\temp\skipInstall\WebSphere_Feature_Pack
# 
# Question 2. How do I run Installation Manager silently?
# Answer 2. Create a silent installation response file and submit it to 
# Installation Manager on the command line:
#
#   Windows = IBMIMc.exe -silent -input <path and file name of response file>
#   Linux or UNIX = ./IBMIM -silent -input <path and file name of response file>
# 
# For example: 
#   Windows = IBMIMc.exe -silent -input c:\temp\responsefile\FEP.install.xml
#   Linux or UNIX = ./IBMIM -silent -input /home/user/responsefile/FEP.install.xml
# 
# Note that Windows uses IBMIMc.exe, whereas Linux and UNIX uses IBMIM.exe.
# Do not use the command IBMIM.exe on Windows systems for silent installations.
# Do not use the command IBMIMc.exe on Linux and UNIX operating systems.
#
# Question 3. How do I store and pass credentials to repositories that 
# require authentication?
# Answer 3. Installation Manager uses a key ring file to store encrypted
# credentials for authenticating with repositories. Follow this two-step
# process for creating and using a key ring file with Installation Manager.
# 
# First, create a key ring file with your credentials by starting 
# Installation Manager from the command line with the keyring parameter.
# Use the optional password parameter to password protect your file.
# 
#   Windows = IBMIM.exe -keyring <path and file name> -password <password>
#   Linux or UNIX = ./IBMIM.exe -keyring <path and file name> -password <password>
# 
# Installation Manager will start in graphical mode. Verify that the 
# repositories to which you need to authenticate are included in the 
# preferences, File / Preferences / Repositories. If they are not 
# listed, then click Add Repositories to add the URL or UNC path.
# Installation Manager will prompt for your credentials. If the repository 
# is already in the list, then any attempt to access the repository location, 
# such as clicking the Test Connections button, will also prompt for your
# credentials. Enter the correct credential and check the Save password 
# checkbox. The credentials are saved to the key ring file you specified. 
# 
# Second, when you start a silent installation, provide Installation 
# Manager with the location of the key ring file and the password if
# the file is protected. For example:
#
#   Windows = IBMIMc.exe -silent -input <path and file name of response file>
#      -keyring <path and name of key ring file> -password <password>
#   Linux / UNIX = ./IBMIM -silent -input <path and file name of response file> 
#      -keyring <path and name of key ring file> -password <password>
#
####################################################################### -->

<!-- ##### License Agreement ##############################################
# By changing the acceptLicense attribute in this response file to true, 
# you agree that you reviewed and agree to the terms of the IBM 
# International Program License Agreement accompanying this program. 
# If you do not agree to these terms, do not change the value or otherwise 
# download, install, copy, access, or use the program and promptly return 
# the program and proof of entitlement to the party from whom you acquired 
# it to obtain a refund of the amount you paid.
#  
# Valid values for acceptLicense:
#      true = Accepts the license and product installation will occur.
#      false = Declines the license and product installation will not occur.
# 
# The clean and temporary attributes specify the repositories and other
# preferences Installation Manager uses and whether those settings
# should persist after the installation finishes.
# 
# Valid values for clean:
#      true = only use the repositories and other preferences that are 
#           specified in the response file.
#      false = use the repositories and other preferences that are specified 
#           in the response file and Installation Manager.
# 
# Valid values for temporary:
#      true = repositories and other preferences specified in the response
#           file do not persist in Installation Manager.
#      false = repositories and other preferences specified in the response
#           file persist in Installation Manager.
# 
####################################################################### -->   

<agent-input acceptLicense='false' clean='true' temporary='true'>


<!-- ##### Repositories ###################################################
# Repositories are locations that Installation Manager queries for 
# installable packages. Repositories can be local (on the machine
# with Installation Manager) or remote (on a corporate intranet or 
# hosted elsewhere on the internet). 
# 
# If the machine using this response file has access to the internet, 
# then include the IBM WebSphere Live Update Repositories in the list 
# of repository locations. 
# 
# If the machine using this response file cannot access the internet, 
# then comment out the IBM WebSphere Live Update Repositories and 
# specify the URL or UNC path to any intranet repositories and 
# directory paths to local repositories to use.
# 
####################################################################### -->	
<server>
     <!-- ##### IBM WebSphere Live Update Repositories ####################
     # These repositories contain WebSphere Application Server Feature Packs, 
     # updates for those feature packs, and import repositories for 
     # WebSphere Application Server version 7.
     # 
     # To use the secure repository (https), you must have an IBM ID, 
     # which can be obtained by registering at: http://www.ibm.com/account
     # 
     # And, you must use a key ring file with your response file.
     ################################################################## -->
	 
    <repository location='http://public.dhe.ibm.com/software/websphere/repositories'/>
    <repository location='https://www.ibm.com/software/rational/repositorymanager/repositories/websphere'/>
	
     <!-- ##### Custom Repositories #######################################
     # Uncomment and update the repository location keys below 
     # to specify URLs or UNC paths to any intranet repositories 
     # and directory paths to local repositories to use.
     ################################################################## -->
	 
    <!--<repository location='/home/user/repositories/ariesjpa_and_import_repositories/local-repositories'/> -->
		
		
    <!-- ############################################################
    # Uncomment and update this line when using a local repository
    # containing WebSphere Application Server Feature Pack for OSGi Applicaitons and 
    # Java Persistence API 2.0 fixpacks.
    ############################################################# -->
    <!-- <repository location=''/>	-->
		
</server>


<!-- ##### Import IBM WebSphere Application Server version 7 ##############
# Because WebSphere Application Server version 7 is installed using 
# a different installation technology, it has to be imported into 
# Installation Manager before any feature packs can be installed. 
# 
# If the installation of WebSphere Application Server version 7 
# that will be the target of this feature pack installation 
# has not been imported, then you must uncomment the profile command 
# below to register it with Installation Manager and then update the 
# import command with a profile id that matches the id created in the
# profile command. If the specified profile ID exists, you must also 
# change the profile ID. Profile IDs are listed in 'installed.xml' in 
# the 'IBM Installation Manager Application Data' folder.
# 
# If the installation of WebSphere Application Server version 7 
# was imported previously, then registering it with Installation 
# Manager is not required. However, the target installation should 
# be imported again to ensure that the current state of WebSphere 
# Application Server installation matches exactly with what is
# in the list of installed packages.
#
# The installationLocation attribute specifies the directory path to 
# an existing installation of WebSphere Application Server.
# 
# The profile id attribute specifies the package group name assigned 
# to the imported installation of WebSphere Application Server. The 
# example below illustrates a profile id for Network Deployment edition, 
# but the id should be customized for your installation. Profile ids 
# must be unique within the instance of Installation Manager using 
# the response file.
# 
# The eclipseLocation data key should use the same directory path to 
# WebSphere Application Server as the installationLocation attribute.
# 
# Set the user.import.profile data key to true to import 
# the installation of WebSphere Application Server version 7.
# 
# The user.cic.imported data key must be paired with the offering ID
# key that matches the edition of WebSphere Application Server to import. 
# Valid WebSphere Application Server offering ID values are:
#      com.ibm.websphere.EXPRESS.v70
#      com.ibm.websphere.EXPRESSTRIAL.v70
#      com.ibm.websphere.BASE.v70
#      com.ibm.websphere.BASETRIAL.v70
#      com.ibm.websphere.ND.v70
# 
# Other feature packs that were previously installed should be 
# imported as well. Add each existing feature pack that needs to 
# be imported as a new data key in the profile command. 
# Several feature pack offering ID values are:
#      com.ibm.websphere.SCA.v10
#      com.ibm.websphere.XML.v10
#      com.ibm.websphere.CEA.v10
#      com.ibm.websphere.ARIESJPA.v10
# 
# In the import command, the profile attribute must match the 
# profile id for the targeted installation of WebSphere Application 
# Server. If the installation was imported previously, then its
# profile id can be found in the installed.xml file located in 
# the application data location for Installation Manager.
# 
####################################################################### -->

<!-- <profile 
     installLocation='/home/user/IBM/WebSphere/AppServer' 
        id='IBM WebSphere Application Server - ND'> 
     <data key='eclipseLocation' value='/home/user/IBM/WebSphere/AppServer'/>
     <data key='user.import.profile' value='true'/>
     <data key='user.cic.imported,com.ibm.websphere.ND.v70' value='WAS'/>
     <data key='user.cic.imported,com.ibm.websphere.featurepackID.v10' value='WAS'/>
</profile> -->

<import type='WAS' profile='IBM WebSphere Application Server - ND'/>
	
<!-- ##### Installation Packages ##########################################
# Use the install command to inform Installation Manager of the 
# installation packages to install. 
# 
# The offering ID attribute is required because it specifies the 
# offering to be installed. The offering listed must be present in 
# at least one of the repositories listed earlier. The example 
# command below contains the offering ID for this feature pack. 
# 
# The profile attribute is required and must match the profile ID 
# of the targeted installation of WebSphere Application Server 
# version 7 used earlier.
# 
# The version attribute is optional. If a version number is provided, 
# then the offering will be installed at the version level specified 
# as long as it is available in the repositories. If the version 
# attribute is not provided, then the default behavior is to install 
# the highest version available in the repositories.
# 
# The features attribute is optional. Offerings always have at least
# one feature; a required core feature which is installed regardless 
# of whether it is explicitly specified. If other feature names 
# are provided, then only those features will be installed.
# The default setting is installing all of them together. 
# 
# The possible feature values of WebSphere Application Server Feature 
# Pack for JPA/OSGi could be:
# 'fep.eba.core.feature', 
# 'fep.jpa.core.feature',
# or both. 
# 
# Interim fixes for offerings can also be installed while they
# are being installed by including the offering ID for the interim
# fix and specifying the profile ID.
# 
####################################################################### -->

<install modify='false'>
     <offering id='com.ibm.websphere.ARIESJPA.v10' 
	    profile='IBM WebSphere Application Server - ND' 
		features='fep.eba.core.feature,fep.jpa.core.feature'/>

<!-- <offering id='PM12345_FEATUREPACK' 
     profile='IBM WebSphere Application Server - ND'/> -->
</install>
	
<!-- ##### Shared Data Location ###########################################
# Uncomment the preference for eclipseCache to set the shared
# data location the first time you use Installation Manager 
# to do an installation.
# 
# Eclipse cache location can be obtained from the installed.xml file found in 
# Linux/Unix: /var/ibm/InstallationManager
# Windows: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
# from the following property:  
# <property name='cacheLocation' value='C:\Program Files\IBM\AppServer-Shared'/>
#
# Open in a text editor, it has a style sheet which will hide this value if opened in a browser.
# For further information on how to edit preferences, please refer to the public liabrary at:
# http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp?topic=/com.ibm.silentinstall12.doc/topics/r_silent_prefs.html
#
# After the shared data location is set, it cannot be changed
# using a response file or the graphical wizard.
# 
# Ensure that the shared data location is a location that can be written 
# to by all user accounts that are expected to use Installation Manager.
#
####################################################################### -->

<!-- <preference name='com.ibm.cic.common.core.preferences.eclipseCache' 
   value='/home/user/IBM/WebSphere/IMShared'/> -->

<!-- ##### Preferences Settings ###########################################
# Additional preferences for Installation Manager can be specified. 
# These preference correspond to those that are located in the graphical
# interface under File / Preferences. 
# 
# If a preference command is omitted from or commented out of the response 
# file, then Installation Manager uses the preference value that was 
# previously set or the default value for the preference. 
# 
# Preference settings might be added or deprecated in new versions of
# Installation Manager. Consult the online Installation Manager
# Information Center for the latest set of preferences and 
# descriptions about how to use them.
#
# http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp
# 
####################################################################### -->

<!-- 
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
 -->

</agent-input>
Note: If you are using Installation Manager 1.4.3 or later, use -acceptLicense in the command rather than in the response file.

What to do next

You must create a new profile with OSGi Applications or Java Persistence API 2.0 feature functionality or augment an existing profile with the feature in order to use the feature's functionality. In addition, the deployment manager for a feature-enabled managed node must be augmented with the feature.




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: Jan 16, 2013 3:37:33 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=tins_runsilentfp
File name: tins_runsilentfp.html