This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.
Installing IBM WebSphere SDK Java Technology Edition Version 7.0 or 7.1 for Liberty using the command line
You can install IBM® WebSphere® SDK Java™ Technology Edition Version 7.0 or 7.1 for Liberty using the Installation Manager command line.
Before you begin
- Prepare your system as described in Installing Installation Manager and preparing to install Liberty.
- Install one the following offerings:
- IBM WebSphere Application Server Liberty
- IBM WebSphere Application Server Liberty Trial
- IBM WebSphere Application Server Liberty Core
- IBM WebSphere Application Server Liberty Core Trial
- IBM WebSphere Application Server Liberty - Express®
- IBM WebSphere Application Server Liberty Network Deployment
- IBM WebSphere Application Server Liberty Network Deployment Trial
- IBM WebSphere Application Server Liberty for Developers
- IBM WebSphere Application Server Liberty for Developers (ILAN)
![[8.5.5.2 or later]](../ng_v8552.gif)
- Download the installation files from the IBM Fix Central website and use a local installation.
- Access the live repositories and use your IBM Software ID for a web-based installation.
Procedure
- Optional: If the repository requires a username and password, create a credential-storage file to access
this repository. Tip: When creating a credential-storage file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.Note: When you use Installation Manager Version 1.6.2 and later, you should use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential-storage file. In versions of Installation Manager earlier than Version 1.6.2, the -keyring and -password options were used to access credentials in a keyring file. These options were deprecated in Version 1.6.2. There is no migration path from keyring files to storage files because of the differences in the file structures. 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 documentation. For more information on using the -keyring and -password options to store credentials in a keyring file, see the Installation Manager Version 1.5 documentation.
- Log on to your system.
- Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
- Verify that the repository is available.
imcl.exe listAvailablePackages -repositories path_to_repository
You should see one or more levels of the offering../imcl listAvailablePackages -repositories path_to_repository
- Use the imcl command to install the offering.
imcl.exe install com.ibm.websphere.liberty.IBMJAVA.v70_offering_version -repositories source_repository -installationDirectory installation_directory -secureStorageFile storage_file -masterPasswordFile master_password_file
imcl.exe install com.ibm.websphere.liberty.IBMJAVA.v71_offering_version -repositories source_repository -installationDirectory installation_directory -secureStorageFile storage_file -masterPasswordFile master_password_file
./imcl install com.ibm.websphere.liberty.IBMJAVA.v70_offering_version -repositories source_repository -installationDirectory installation_directory -secureStorageFile storage_file -masterPasswordFile master_password_file
./imcl install com.ibm.websphere.liberty.IBMJAVA.v71_offering_version -repositories source_repository -installationDirectory installation_directory -secureStorageFile storage_file -masterPasswordFile master_password_file
The value of the -installationDirectory parameter should be the location of an existing Liberty installation. The SDK offering will be installed into the <liberty_home>\java\java_1.7_32 or <liberty_home>\java\java_1.7_64 folder, depending on whether the installation location was configured to be 32-bit or 64-bit when the Liberty offering was initially installed.
Note: The bit architecture that will be installed, 32 bit or 64 bit, will match the bit selection made during the installation of the Liberty offering. For GUI installations of Liberty offerings, this selection is made on the Location panel. For command-line and response-file installations of Liberty offerings, the default can be overridden using the cic.selector.arch property.Tips:- The offering_version, which optionally can be attached to the offering ID
with an underscore, is a specific version of the offering to install
(8.5.0.20110503_0200 for example).
- If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
- If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.
The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:imcl listAvailablePackages -repositories source_repository
- You can also specify none, recommended or all
with the -installFixes argument to indicate which interim fixes you want installed
with the offering.
- If the offering version is not specified, the -installFixes option defaults to all.
- If the offering version is specified, the -installFixes option defaults to none.
- 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.
For more information on using the imcl command, see the IBM Installation Manager Information Center.
- The offering_version, which optionally can be attached to the offering ID
with an underscore, is a specific version of the offering to install
(8.5.0.20110503_0200 for example).
Related tasks:


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=twlp_ins_installation_jdk7_cl
File name: twlp_ins_installation_jdk7_cl.html