You can use Installation Manager to install and remove WebSphere® Application Server
Liberty Network
Deployment features.
Before you begin
Make sure that your Installation Manager preferences are
pointing to the appropriate web-based or local repositories containing WebSphere Application Server
Liberty Network
Deployment.
About this task
Perform this procedure to use the Installation Manager
GUI to install or remove a feature.
Note: Like other Installation
Manager operations, you can also invoke a modification using one of
the following procedures:
- Using a silent response file
You can record this response file
using the GUI and Installation Manager's record mode, or you can manually
create or modify a response file to suit your needs.
- Using the imcl command-line tool
Go to the IBM® Installation
Manager Information Center for more information.
Procedure
- Stop all servers and applications on the WebSphere Application Server Liberty Network
Deployment installation
that is being modified.
- Start Installation Manager.
- Click Modify.
- Select the package group to modify.
- Click Next.
Note: If
you are prompted to authenticate, use the IBM ID and password that you registered with
on the program website.
- Expand IBM WebSphere Application Server
Liberty Network
Deployment.
- Check the appropriate checkbox to install a feature, or
clear the appropriate checkbox to remove a feature if you already
have it installed.
- 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.
- 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.
- Review the summary information, and click Modify.
- If the modification is successful, the program displays a message
indicating that installation is successful.
- If the modification is not successful, click View Log
File to troubleshoot the problem.
- Click Finish.
- Click File > Exit to close Installation
Manager.
Examples
- Modifying features:
In the following list, the optional feature offering names
are enclosed in parentheses:
- Embeddable EJB container and JPA client (embeddablecontainer)
- Extended Programming Models (extprogmodels)

Here is an example of a response file
for modifying (adding) a feature in an installation:
<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' temporary='true'>
<server>
<repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.ND.v85'/>
</server>
<install modify='true'>
<offering id='com.ibm.websphere.liberty.ND.v85'
profile='WebSphere Liberty V8.5'
features='embeddablecontainer,extprogmodels'/>
</install>
<profile id='WebSphere Liberty V8.5'
installLocation='C:\Program Files\IBM\WebSphere\Liberty'>
</profile>
</agent-input>

Here is an example of using
the
imcl command to add features in an installation:
imcl.exe modify com.ibm.websphere.liberty.ND.v85
-addFeatures embeddablecontainer,extprogmodels
-repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.ND.v85
-installationDirectory C:\Program Files\IBM\WebSphere\Liberty
-secureStorageFile C:\credential.store -masterPasswordFile C:\master_password_file.txt
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.

Here is an example of using the
imcl command
to remove a feature from an installation:
imcl.exe modify com.ibm.websphere.liberty.ND.v85
-removeFeatures embeddablecontainer
-repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.liberty.ND.v85
-installationDirectory C:\Program Files\IBM\WebSphere\Liberty
-secureStorageFile C:\credential.store -masterPasswordFile C:\master_password_file.txt