Installing and removing features on distributed operating systems

You can use Installation Manager to install and remove a product feature.

Before you begin

Make sure that your Installation Manager preferences are pointing to the appropriate web-based or local repositories containing the product.

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 documentation for more information.

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 prior to EJB 3.0. 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 feature called JITDeploy, which automatically generates code when the application starts.
  
  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.
- Standalone thin clients, resource adapters, and embeddable containers
  IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.
  - Standalone thin clients and resource adapters
    This option installs the IBM standalone thin clients and resource adapters.
    
    IBM thin clients provide a set of clients for a variety of 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 standalone Java Platform, Standard Edition 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.
- 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 (TM) 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 File > Exit to close Installation Manager.

Examples

You can modify features:
In the following list, the optional feature offering names are enclosed in parentheses:
- EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)
- Standalone thin clients, resource adapters, and embeddable containers
  - Standalone thin clients and resource adapters (thinclient)
  - Embeddable EJB container (embeddablecontainer)
- Sample applications (samples)
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="https://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v85" />
</server>
<install modify='true'>
<offering id='com.ibm.websphere.ND.v85' 
  profile='IBM WebSphere Application Server V8.5' 
  features='samples'/>
</install>
<uninstall modify='true'>
<offering id='com.ibm.websphere.ND.v85' 
  profile='IBM WebSphere Application Server V8.5' 
  features='thinclient,ejbdeploy,embeddablecontainer'/>
</uninstall>
<profile id='IBM WebSphere Application Server V8.5' 
  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>
```
Tip: See Sample response file: Modifying IBM WebSphere Application Server Network Deployment for an annotated sample of a response file for performing this procedure.
Here is an example of using the imcl command to modify the features in an installation:
```
imcl.exe modify com.ibm.websphere.ND.v85
  -addFeatures samples
  -removeFeatures thinclient,ejbdeploy,embeddablecontainer
  -repositories https://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v85
  -installationDirectory C:\Program Files\IBM\WebSphere\AppServer
  -keyring C:\keyring_file.keyring -password password
```
Supported configurations:
Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the IBM Installation Manager documentation.
You can modify 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.
For example:
```
imcl.exe modify com.ibm.websphere.ND.v85_8.5.0.20110503_0200
  -repositories https://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v85
  -installationDirectory C:\Program Files\IBM\WebSphere\AppServer
  -properties cic.selector.nl=en,,hu,,ko,,pl,,es 
  -keyring C:\keyring_file.keyring -password password
```
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.
For example:
```
imcl.exe listInstallationDirectories -long
```