Installing Liberty on distributed operating systems by using the command line
You can install WebSphere® Application Server Liberty Core by using the Installation Manager command line.
Before you begin
Prepare the system onto which you want to install WebSphere Application Server Liberty Core as described in Installing Installation Manager and preparing to install Liberty.
About this task
To install Version 8.5.5.4 and later of
Liberty, you must have IBM® Installation Manager Version 1.6.2
or later.
Procedure
- Optional: If the repository requires a user name and password, create credential-storage and
master-password files to access this repository. Tip: When you create 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, 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 offering repository is available.
imcl.exe listAvailablePackages -repositories source_repository
You see one or more levels of the offering../imcl listAvailablePackages -repositories source_repository
- Use the imcl command to install the offering.
imcl.exe install com.ibm.websphere.liberty.v85_offering_version,optional_feature_ID -repositories source_repository -installationDirectory installation_directory -sharedResourcesDirectory shared_directory -preferences preference_key=value -properties property_key=value -secureStorageFile storage_file -masterPasswordFile master_password_file -acceptLicense
./imcl install com.ibm.websphere.liberty.v85_offering_version,optional_feature_ID -repositories source_repository -installationDirectory installation_directory -sharedResourcesDirectory shared_directory -preferences preference_key=value -properties property_key=value -secureStorageFile storage_file -masterPasswordFile master_password_file -acceptLicense
Tips:- The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or offering_name/lafiles subdirectory of the installation image or repository for this offering.
- The first time that you install a package by using the Installation Manager, you can specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. It is also used as a staging area for the product payload during installation operations. By default, this content is cached so that it can be used for rollback. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.
- 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.5.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.
- You can add a list of features that are separated by commas:
- Embeddable EJB container and JPA client (embeddablecontainer)
This option installs the embeddable EJB container and JPA client.
The embeddable EJB container is a Java™ Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition (SE) environment. You can run enterprise beans by 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.
The JPA client can be used with the embeddable EJB container to provide Java Persistence API capability in a Java SE environment.
Notes:- If no features are specified, the default feature (embeddablecontainer)
is installed.
Beginning with Version 8.5.5.4, the extprogmodels feature is no longer available. Instead, install the extendedPackage-1.0 addon, or install the individual features that you need from the Liberty Repository. See the following topics for more information:
- To ensure that your installation process completes for systems that do not have internet access
specify the -properties user.feature="" parameter on the Installation Manager
command line. If you do not specify this parameter, the installation process attempts to access the
internet and an error occurs.
Verify that firewalls are configured to allow the Installation Manager to access the internet, or that the local Installation Manager repository can be accessed. If the problem persists, then the repository server might be unavailable. To continue the installation without additional assets, specify the user.feature="" and user.addon="" parameters.ERROR: Unable to connect to the IBM WebSphere Liberty repository or local Installation Manager repository.
You can receive a NullPointerException when you apply fix pack V8.5.5.5 for WebSphere Application Server Liberty. The error can occur when you download the WebSphere Application Server Liberty fix pack compressed files and use them, at the downloaded directory location, to install or update Liberty. You can work around this Version 8.5.5.5 error condition by taking the following steps:
- Extract the WebSphere Application Server Liberty fix pack compressed file to a temporary directory.
- Use the temporary directory as the Installation Manager repositories to install or update Liberty.
unzip 8.5.5-WS-LIBERTYPROFILE-OS390-FP0000005.zip to /tmp/fp8555 # ./imcl install com.ibm.websphere.liberty.v85_8.5.5005.20150305_2214 -installationDirectory /SERVICE/usr/lpp/zWebSphere/Liberty/V8R5 -repositories /tmp/fp8555 -acceptLicense
- Embeddable EJB container and JPA client (embeddablecontainer)
You can specify additional assets to install from the Liberty Repository. For a list of Liberty Repository assets, see the downloads page on WASdev.net. If you want to install additional assets, specify the following properties on the command line. You can specify the short name or symbolic name. Note that the feature short names, such as FeatureA, are separated by double commas in the following example:
-properties user.feature=FeatureA,,FeatureB,,FeatureC,user.accept.license=true
For Version 8.5.5.5 and later, user.accept.license=true is not required.
The following example installs the Extended Programming Models on the user.addon parameter, and the Portlet Container feature on the user.feature parameter.
imcl install com.ibm.websphere.liberty.ND.v85 -properties user.accept.license=true,user.addon=extendedPackage-1.0,user.feature=portlet-2.0 -installationDirectory D:\IBM\Liberty -acceptLicense -repositories D:\IBM\LibertyRepo -sharedResourcesDirectory D:\IBM\IMShared -showProgress
You can also install assets from instances of the Liberty Asset Repository Service or local directory-based repositories. For more information about these asset repositories, see Installing assets using Installation Manager. Add the repository on the -repositories parameter. The repositories are accessed in the order that they are specified. By default, the Liberty Repository is the last of the repositories that are accessed during installation. To disable access to the Liberty Repository, on the -properties parameter, set the user.useLibertyRepository option to false.
imcl install com.ibm.websphere.liberty.v85 -properties user.useLibertyRepository=false,user.addon=extendedPackage-1.0,user.feature=portlet-2.0 -installationDirectory D:\IBM\Liberty -acceptLicense -repositories D:\IBM\LibertyProductRepo,https://your_onprem_asset_repo_url,D:\IBM\LocalAssetRepo,D:\IBM\LocalAssetRepo2.zip -sharedResourcesDirectory D:\IBM\IMShared -showProgress
To learn more about the Liberty Repository and the assets it contains, see Liberty Repository.
- Installation Manager can save earlier versions of a package to roll back to if you experience
issues later. When Installation Manager rolls back a package to a previous version, the current
versions of the files are uninstalled and the earlier versions are reinstalled. If you choose not to
save the files for rollback, you can prevent the files from being saved by using the following
preference in your command
specification:
-preference com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts=False
For more information on setting your Installation Manager preferences, see IBM Installation Manager documentation.
Tip: Even if you choose not to preserve files locally for rollback, you can still roll back to any previously installed level by accessing the appropriate offering repository. - You can use the cic.selector.arch property key and related value to specify the
architecture to install, 32 bit or 64 bit.Here is an example of specifying a 32-bit architecture:
-properties cic.selector.arch=x86
If you do not specify anything for this key, you get a correct match for your system. For a 64-bit system, the installation defaults to a 64-bit installation.
Your choice here applies to all packages that are installed in the package group. For information about the supported values for the cic.selector.key keys, see the Values for cic.selector.key table in the Installation Manager documentation.
- The program might write important post-installation instructions to standard output.
For more information on using the imcl command to install the offering, see the IBM Installation Manager documentation.


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