You can use the Installation Manager GUI to install WebSphere® Application Server
Liberty Network
Deployment.
Procedure
- Start Installation Manager.
- 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.
- Perform the following actions.
- Select IBM WebSphere Application Server
Liberty Network
Deployment and
the appropriate version.
Note: If you are installing the
trial version of this product, select the appropriate trial edition
and the appropriate version.
If you already have the WebSphere Application Server
Liberty Network
Deployment offering
installed on your system in the installation location, a message displays
indicating that the product is already installed. To create another
installation of the offering in another location, click Continue.
Tip: If the Search service repositories during installation
and updates option is selected on the Installation Manager Repository
preference page and you are connected to the Internet, you can click Check
for Other Versions and Extensions to search for updates in the
default update repositories for the selected packages. In this case,
you do not need to add the specific service-repository URL to the
Installation Manager Repository preference page.
- 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.
- Click Next.
Note: Installation Manager might prompt you to update to the
latest level of Installation Manager when it connects to the repository.
Update to the newer version before you continue if you are prompted
to do so. Read the
IBM Installation
Manager Information Center for information about automatic
updates.
- Accept the terms in the license agreements, and click Next.
- Specify the installation root directory for the product
binaries, which are also referred to as the core product files or
system files.
The panel also displays the shared resources
directory and disk-space information.
Note: 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. Consider setting your
rollback preferences to save these files as described in
Installing Installation Manager and preparing to install Liberty.
Use your largest drive for this installation. You cannot change the
directory location until after you uninstall all packages.
If
you are installing on a 64-bit system, use the bit-selection option
to select the bitness of the installed Java™ libraries.
If you are installing on a 32-bit system, this option is not available.
When installing on a 64-bit system, you must select either the 32-bit
or 64-bit option. This choice will determine the architecture bitness
of the installation profile group. All extension offerings to WebSphere Application Server
Liberty Network
Deployment will
be installed under the same profile group and have the same architecture
bitness. For example, WebSphere SDK Java Technology Edition Version
7.0 for Liberty is an extension offering to WebSphere Application Server Liberty Network
Deployment and
its installation will use a 32-bit or 64-bit JDK depending on your
choice here.
Restrictions: - Deleting the default target location and leaving an installation-directory
field empty prevents you from continuing.
- Do not use symbolic links as the destination directory.
Symbolic
links are not supported.
- Do not use a semicolon in the directory name.
WebSphere Application Server Liberty Network
Deployment cannot
install properly if the target directory includes a semicolon.
A semicolon is the character used to construct
the class path on Windows systems.
- Click Next.
- Select the features that you want to install.
Choose
from the following features:
- IBM WebSphere Application Server Liberty Network
Deployment
- Embeddable EJB container and JPA client
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.
Tip: You can run the Installation Manager later to modify this
installation and add or remove this feature.
- Extended Programming Models
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.
- Click Next.
Select the additional features that
you want to install. 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.
- Click Next.
- Review the summary information, and click Install.
- Click Finish.
- Click File > Exit to close Installation
Manager.