Installing IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1 using response files

IBM® WebSphere® SDK Java™ Technology Edition Version 6.0 is no longer in service. Using IBM Installation Manager, you can optionally install IBM WebSphere SDK Java Technology Edition Version 7.0 and 7.1., which are in service until July 2022. For new installations of WebSphere Application Server 8.5.5.11 or later, Java SE 8 is installed by default.

1. Optional: Record a response file to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1: On one of your systems, perform the following actions to record a response file that will install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1.
   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

      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. 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 documentation.

   3. Add the appropriate repositories to your 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

              https://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v70 

              https://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v71 

            • Local repositories:
              • C:\repositories\jdk7\local-repositories
              • /var/repositories/jdk7/local-repositories
         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 SDK Java Technology Edition and the appropriate version, and click Continue.
      2. Select the fixes to install.

         Any recommended fixes are selected by default.

         If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

      3. Click Next.
   6. Select the appropriate WebSphere Application Server installation on which to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1, and click Next.
   7. Click Next.
   8. Review the summary information, and click Install.
      • If the installation is successful, the program displays a message indicating that installation is successful.
        Note: 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.
   9. Click Finish.
   10. Click File > Exit to close Installation Manager.
   11. 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:

          • 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 your credentials for the authenticated remote repository, enter the correct credentials and save them.
       4. Click File > Exit to close Installation Manager.

       Supported configurations:

       Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring 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 before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

       There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the IBM Installation Manager documentation.

2. Use the response files to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1:
   1. Optional: Use the response file to install the keyring: Go to a command line on each of the systems on which you want to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1, 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
          input C:\temp\keyring_response_file.xml 
          -log C:\temp\keyring_log.xml

      • Administrator:

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

      • Non-administrator:

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

   2. Use the response file to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1: Go to a command line on each of the systems on which you want to install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1.
      For example:

      • Administrator or non-administrator:

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

      • Administrator:

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

      • Non-administrator:

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

      Notes:

      • 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.

Example

The following is an example of a response file for installing IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1.

<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean="true" temporary="true">
<server>
<repository location="https://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v70" /> 
</server>
<install modify='false'>
<offering id='com.ibm.websphere.IBMJAVA.v70' 
  profile='IBM WebSphere Application Server V8.5' installFixes='none'/>
</install>
<profile id='IBM WebSphere Application Server V8.5' installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>

<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean="true" temporary="true">
<server>
<repository location="https://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v71" /> 
</server>
<install modify='false'>
<offering id='com.ibm.websphere.IBMJAVA.v71' 
  profile='IBM WebSphere Application Server V8.5' installFixes='none'/>
</install>
<profile id='IBM WebSphere Application Server V8.5' installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>