You can use the Installation Manager GUI to install and remove a product
feature.
Before you begin
Make sure that your Installation Manager preferences point to the appropriate web-based or local
repositories containing the product.
About this task
Note: Like other Installation Manager operations, you can also modify features 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 documentation.
Procedure
- Stop all servers and applications on the WebSphere® Application Server 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 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.
- EJBDeploy tool for pre-EJB 3.0 modules
This option installs the EJBDeploy tool for pre-EJB 3.0
modules.
Before you deploy applications on the server, you must run the EJBDeploy tool on
applications that contain EJB modules that are based on specifications before EJB 3.0 that are not
in a Java EE 7 application. Running the EJBDeploy tool generates deployment code for enterprise
beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer
required because WebSphere Application Server uses a new feature that is called JITDeploy, which
automatically generates code when the application starts. EJB modules in a Java EE 7 application
uses JITDeploy even if they are based on specifications before EJB 3.0.
Tip: Unexpected errors might occur if applications that are provided with IBM
WebSphere Application Server, such as the samples,
require the optional EJBDeploy tool for pre-EJB 3.0 modules but the feature is not installed. If you
deploy and use applications that might require pre-EJB 3.0 modules, include the optional EJBDeploy
feature in all WebSphere Application Server
installations that will be used by servers running the pre-EJB 3.0 applications.
- Stand-alone thin clients, resource adapters, and embeddable containers
IBM thin clients and resource adapters provide a set of clients and resource
adapters for various technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An
embeddable container runs in a stand-alone Java™ Platform,
Standard Edition (Java SE) environment. For example, you can use the embeddable EJB container to run
enterprise beans outside the application server.
- Stand-alone thin clients and resource adapters
This option installs the IBM stand-alone thin clients and resource adapters.
IBM thin clients provide a set of clients for various technologies, such as
JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM
resource adapters provide the resource adapters for JMS.
- Embeddable EJB container
This option installs the embeddable EJB container.
The
embeddable EJB container is a Java Archive (JAR) file that you
can use to run enterprise beans in a stand-alone Java 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 specification and is primarily used for
unit testing enterprise beans business logic.
- Sample applications
This option installs the sample applications for learning and
demonstration environments.
The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.
- 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 to close Installation Manager.
Examples
- Modifying features:
In the following list, the optional feature offering names
are enclosed in parentheses:
- EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)
Before you deploy applications on the server, you must run the EJBDeploy tool on applications
that contain EJB modules that are based on specifications before EJB 3.0 that are not in a Java EE 7
application. Running the EJBDeploy tool generates deployment code for enterprise beans in the
application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required
because WebSphere Application Server uses a new feature that is called JITDeploy, which
automatically generates code when the application starts. EJB modules in a Java EE 7 application
uses JITDeploy even if they are based on specifications before EJB 3.0.
- Stand-alone thin clients, resource adapters, and embeddable containers
- Stand-alone thin clients and resource adapters (thinclient)
- Embeddable EJB container (embeddablecontainer)
- Sample applications (samples)
![[Windows]](../images/windows.gif)
Here is an example of a response file for modifying the features 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.ND.v90" />
</server>
<install modify='true'>
<offering id='com.ibm.websphere.ND.v90'
profile='IBM WebSphere Application Server V9.0'
features='samples'/>
</install>
<uninstall modify='true'>
<offering id='com.ibm.websphere.ND.v90'
profile='IBM WebSphere Application Server V9.0'
features='thinclient,ejbdeploy,embeddablecontainer'/>
</uninstall>
<profile id='IBM WebSphere Application Server V9.0'
installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
<data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='en'/>
</profile>
</agent-input>
![[Windows]](../images/windows.gif)
Here is an example of using the
imcl command to modify the
features in an
installation:
imcl.exe modify com.ibm.websphere.ND.v90
-addFeatures samples
-removeFeatures thinclient,ejbdeploy,embeddablecontainer
-repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v90
-installationDirectory C:\Program Files\IBM\WebSphere\AppServer
-secureStorageFile C:\IM\credential.store -masterPasswordFile C:\IM\master_password.txt
- Modifying languages:
To change the installed languages, use the -properties argument with the
cic.selector.nl property in the imcl command to specify the
languages that you want in your installation.
![[Windows]](../images/windows.gif)
For
example:
imcl.exe modify com.ibm.websphere.ND.v90_9.0.0.20160503_0200
-repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v90
-installationDirectory C:\Program Files\IBM\WebSphere\AppServer
-properties cic.selector.nl=en,,hu,,ko,,pl,,es
-secureStorageFile C:\IM\credential.store -masterPasswordFile C:\IM\master_password.txt
English,
Hungarian, Korean, Polish and Spanish would be installed after using this example. If you started
with an installation with English only, this would add the other languages. If you started with an
installation with more languages, the other languages would be removed.
To find out which
languages are installed, use listInstallationDirectories with the imcl command
and specify either -long, or -verbose. ![[Windows]](../images/windows.gif)
For
example:
imcl.exe listInstallationDirectories -long