You can install WebSphere® Application
Server WebSphere Application
Server Liberty Network
Deployment using
the Installation Manager command line.
Before you begin
Important: Before installing WebSphere Application Server Liberty Network
Deployment, you
must read the license agreement that you can find with the product
files. Signify your acceptance of the license agreement by specifying -acceptLicense in
the command as described in this topic.
Prepare the system
onto which you want to install WebSphere Application
Server Liberty Network
Deployment as
described in Installing Installation Manager and preparing to install Liberty.
Procedure
- Optional: If the repository requires a username
and password, create credential-storage and master-password files
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 Information Center.
For more information on using the
-keyring and
-password options
to store credentials in a keyring file, see the
Installation Manager Version 1.5 Information Center.
- 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
./imcl listAvailablePackages -repositories source_repository
You
should see one or more levels of the offering.
- Use the imcl command to install the
offering.
imcl.exe install com.ibm.websphere.liberty.ND.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.ND.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 using 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 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.
- Extended Programming Models (extprogmodels)
The
Extended Programming Models feature provides a rich set of programming
models such as Web Services, JMS (including Message-Driven Beans),
and Mongo 2.0.
Notes: - If no features are specified, the default features (embeddablecontainer and extprogmodels)
are installed. To install only
the feature that you want, specify that feature explicitly.
You can add a list of additional features
that are separated by commas: Choose from the following additional
features:
- Portlet Serving: provides the Portlet serving
or URL addressability functionality for JSR 168 and JSR 286 compliant
portlets. This feature allows you to invoke a portlet under a defined
URL from a browser.
- Portlet Container: provides a runtime environment
for JSR 168 and JSR 286 compliant portlets.
- Web Cache Monitor: provides monitoring
of the distributed map cache, with simple cache statistics, cache
entries, and cache policy information for Servlet cache instances.
- 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 version 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
to
this:For more information on setting your Installation Manager
preferences, see the IBM® Installation
Manager Information Center.
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 will 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 Information Center.
- 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 Information Center.