Install and uninstall applications with the WebSphere administrative console

You can use the WebSphere administrative console to install and uninstall enterprise applications on your application server.

• Install applications with the administrative console
• Uninstall applications with the administrative console

Install applications with the administrative console

To install an application, follow these steps:

1. Start the WebSphere administrative console.

2. Expand Applications and click Install New Application.

3. Specify the path of the application that you want to install.

   • If the application is stored on your workstation, select Local path.
   • If the application is stored on a node in your WebSphere Application Server - Express cell, select Server path. For a server path, specify the fully qualified path of the application. For example, if the EAR file myApp.ear for your application is located in the installableApps directory of the myAppSvr instance, specify:

     /QIBM/UserData/WebASE/ASE5/myAppSvr/installableApps/myApp.ear

     Note: When using the Server path option, the QEJBSVR user profile must have *RX authority to the EAR or WAR file and the directory where the file is located.

4. If the application is a WAR module, specify the context root.

5. Click Next.

6. Specify options for bindings and mappings.

7. Click Next.

   Note: WebSphere Application Server - Express reads the deployment descriptor of your application before it displays the next page. It uses the information from the deployment descriptor to determine which information you need to provide before you install the application. As a result, you may not see all of the panels described here.

8. Provide options to perform the installation
   On this panel, you can specify several general options that determine how WebSphere Application Server - Express installs your application.

   1. If you want WebSphere Application Server - Express to precompile JavaServer Pages (JSP) files as part of the installation, select Pre-compile JSP. If you do not select this option, JSPs are compiled the first time they are accessed.
   2. Specify the directory where you want to install the application EAR file. By default, the application is installed in the /QIBM/UserData/WebASE/ASE5/instance/installedApps/node directory, where instance is the name of your instance and node is the name of the node for your instance. It is recommended that you use the default value.
   3. Specify where the application configuration used during runtime comes from. If this option is not selected, configurations specified during application installation, and stored in the configuration files, are used. If this option is selected, the configuration specified during installation is ignored, and the settings in the original application are used. The default is not to use the binary configuration. It is recommended that you use the default setting.
   4. Specify a name for the application. Application names must be unique within a cell.

      Note: Because WebSphere Application Server - Express does not support enterprise beans, the Deploy EJBs option does not apply. Ignore this option.

   5. By default, WebSphere Application Server - Express creates MBeans for various resources (such as servlets or JSP files) within an application when the application is started. These MBeans allow you to use the the HTTP Server Adminisration interface and the wsadmin administrative tool to manage your application. It is recommended that you use the HTTP Server Administration interface to manage applications. If you do not want to use this capability, deselect this option.
   6. To enable class reloading when application files are updated, select Enable class reloading. If you enable class reloading, you can update your application and apply the changes without restarting the application server. In addition, WebSphere Application Server - Express periodically scans the application for updates. It may be convenient to have reloading turned on in a development environment. In a production environment, it is suggested that you disable class reloading, or that you specify a long reload interval.
   7. If you enable class reloading, you can also specify the reload interval (in seconds). This value specifies how often the application server scans the application's file system for updated files. The default value is specified by the reload interval attribute in the IBM extension (META-INF/ibm-application-ext.xmi) file of the EAR file or the IBM extension file for each Web module in the EAR file.

9. Map resource references to resources
   If your application defines resource references, specify JNDI names for the resources that represent the logical names defined in resource references. You must bind all of the resource references to a resource before you click Finish. The resources are defined in your WebSphere Application Server - Express configuration.

10. Map virtual hosts for web modules
    If your application contains Web modules, you must map each Web module to a virtual host. Select a virtual host to map to a Web module defined in the application. The port number specified in the virtual host definition is used in the URL that is used to access objects such as servlets and JSP files in the Web module.

    Note: You should never select the admin_host virtual host. This is a special virtual host used by the WebSphere administrative console application.

11. Map security roles to users/groups
    If the application has security roles defined in its deployment descriptor, you can specify users and groups to map to each role. Select the checkbox beside Role to select all of the roles or select individual roles. You can map predefined users such as Everyone or All Authenticated to each role. To select specific users or groups from the user registry:

    1. Select a role and click Lookup users or Lookup groups.
    2. On the Lookup users/groups panel, enter search criteria to view a list of users or groups from the user registry.
    3. Select one or more users or groups from the results displayed.
    4. Click OK to map the selected users or groups to the selected role or roles.

12. Map RunAs roles to user
    If the application's deployment descriptor defines one or more RunAs roles, specify the RunAs user name and password for every RunAs role. RunAs roles are used by enterprise beans that must run as a particular role while interacting with another enterprise bean. Select the checkbox for the role or roles that you want to configure. After you select a role, enter values for the user name and password, then click Apply.

13. Mapping Resource Environment References to Resources
    If your application contains resource environment references, specify JNDI names of resources that map to the logical names defined by the references. If each resource environment reference does not have a resource associated with it, the installation wizard displays a validation error when you click Finish.

14. Replacing RunAs System to RunAs Roles
    If your application defines RunAs Identity as System Identity, you can optionally change it to RunAs role and specify a user name and password for the RunAs role specified. Selecting System Identity implies that the invocation is done using the WebSphere Application Server - Express security server ID and should be used with caution.

15. On the Summary panel, verify that the installation settings are correct. For the Cell/Node/Server item, click Click here to verify the settings.

16. Click Finish.

17. Save the configuration. The application is registered with the administrative configuration and application files are copied to the target directory when you save the configuration.

Uninstall applications with the administrative console

To uninstall an application with the administrative console, follow these steps:

1. Start the WebSphere administrative console.
2. Expand Applications and click Enterprise applications.
3. Select the check box for the application or applications that you want to remove.
4. Click Uninstall.
5. Save the configuration.