Install and uninstall applications

 

Overview

Use the administrative console to install and uninstall enterprise applications on the application servers.

You can also use the wsadmin tool to install and uninstall applications. For more information about wsadmin, see The wsadmin administrative tool.

 

Install applications

To install an application, follow these steps:

  1. Start the 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 the workstation, select Local path.

    • If the application is stored on a node in the WAS 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 the application is located in the installableApps directory of the default WAS instance on the iSeries, you would specify:

      /QIBM/UserData/WebAS5/Base/default/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: WAS reads the deployment descriptor of the 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, specify several general options that determine how WAS installs the application.

    1. To precompile JSP files as part of the installation, select Pre-compile JSP. Otherwise, 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 directory...

      /QIBM/UserData/WebAS5/Base/instance/installedapps/node

      Use the default value.

    3. Specify whether the application should be enabled for distribution. The effect of this option varies depending on which edition of the product you are using. It is recommended you leave this option enabled.

      • WebSphere Application Server: When this option is enabled, the application binaries are expanded to the target location (by default, the installedApps directory) when the configuration is saved. If you disable this option, then ensure that the application binaries are expanded in the appropriate location. If you disable this option and later uninstall the application, the binaries are not deleted.

      • WebSphere Application Server Network Deployment: When this option is enabled, the application is distributed automatically to other nodes on the cell. If you disable this option, then ensure that the application binaries are expanded appropriately in the destination directories of all nodes where the application is expected to run.

    4. 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. Use the default setting.

    5. To generate the deployment code for any enterprise beans that are contained in the application during installation, select Deploy EJBs. You must select this option in these cases:

      • The EAR file was assembled with the Application Assembly (AAT) tool and you did not invoke the Generate code for deployment command.

      • The EAR file was not assembled with the AAT tool.

      • The EAR file was assembled with versions of the AAT tool previous to Version 5.

      Selecting this option may cause the installation program to run for several minutes.

    6. Specify a name for the application. Application names must be unique within a cell.

    7. By default, WAS 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 wsadmin administrative tool to administer the enterprise application. To not use this capability, deselect this option>

    8. To enable class reloading when application files are updated, select Enable class reloading. If you enable class reloading, you can update the application and apply the changes without restarting the application server. In addition, WAS 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 reloading be turned off, or that the reload interval be large.

    9. 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. Provide options to perform the EJB Deploy

    If you selected Deploy EJBs on the Provide options to perform the installation panel, specify options for the deployment process. On this panel, specify extra classpath, rmic options, database types, and database schema names to be used while running the deployment operation tool.

  10. Provide JNDI Names for Beans

    If the application uses EJB modules, specify a JNDI name for each enterprise bean in every EJB module. You must specify a JNDI name for every enterprise bean defined in the application. The JNDI name specified for each enterprise bean during assembly is displayed and used by default.

  11. Provide default datasource mapping for modules containing 1.x entity beans

    If the application uses EJB modules that contain Container Managed Persistence (CMP) beans that are based on the EJB 1.x specification, specify a JNDI name for the default data source for the EJB modules. The JNDI name specified for the data source is displayed and used by default. If data sources are specified for individual CMP beans, this step is optional.

  12. Map datasources for all 1.x CMP

    If the application has CMP beans that are based on the EJB 1.x specification, specify a JNDI name for data sources to be used for each of the 1.x CMP beans. If a data source is specified for the EJB module that contains the CMP beans, this step is optional. However, if a data source is specified for neither the CMP beans nor the EJB module, the installation wizard displays a validation error and cancels the installation when you click Finish.

  13. Map EJB references to beans

    If the application defines EJB references, specify JNDI names for enterprise beans that represent the logical names specified in EJB references. You must bind all of the EJB references to an EJB file before you click Finish.

  14. Map resource references to resources

    If the 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 the WAS configuration.

  15. Map virtual hosts for web modules

    If the application contains Web modules, 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: Do not select the admin_host virtual host unless you are deploying the administrative console application or other administrative application. The admin_host is a special virtual host whose host and port aliases are not exposed and are not accessible from an external HTTP server WebSphere plugin for serving requests.

  16. Map modules to application servers

    Select a target server or a cluster for each module from the Clusters and Servers list. To specify the same target server or cluster for multiple modules, select the checkbox for each module that you want to specify and click Apply.

  17. Map security roles to users/groups

    If the application has security roles defined in its deployment descriptor, 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.

  18. 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.

  19. Ensure all unprotected 1.x methods have the correct level of protection

    If the application contains EJB 1.x CMP beans that do not have method permissions defined for some of the EJB methods, you can leave such methods unprotected or specify Deny All Access.

  20. Provide Listener Ports for messaging beans

    If the application contains message driven enterprise beans, provide a listener port name for every message driven bean. If you do not specify a name for each bean, the installation wizard displays a validation error when you click Finish.

  21. Provide default datasource mapping for modules containing 2.0 entity beans

    If the application uses EJB modules that contain CMP beans that are based on the EJB 2.0 specification, specify a JNDI name for the default data source for the EJB modules. If data sources are specified for individual CMP beans, this step is optional.

  22. Map datasources for all 2.0 CMP

    If the application has CMP beans that are based on the EJB 2.0 specification, specify a JNDI name for data sources to be used for each of the 1.x CMP beans. If a data source is specified for the EJB module that contains the CMP beans, this step is optional. However, if a data source is specified for neither the CMP beans nor the EJB module, the installation wizard displays a validation error and cancels the installation when you click Finish.

  23. Ensure all unprotected 2.0 methods have the correct level of protection

    If the application contains EJB 2.0 CMP beans that do not have method permissions defined in the deployment descriptors for some of the EJB methods, specify one of these options:

    • Assign a specific role to the unprotected methods.

    • Add the methods to the exclude list. These methods are marked as uncallable.

    • Mark the methods as unchecked. No authorization check is performed prior to these methods' invocation.

  24. Mapping Resource Environment References to Resources

    If the 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.

  25. Replacing RunAs System to RunAs Roles

    If the application defines Run-As Identity as System Identity, you can optionally change it to Run-As role and specify a user name and password for the RunAs role specified. Selecting System Identity implies that the invocation is done using the WAS security server ID and should be used with caution.

  26. Specify the isolation level for Oracle type provider

    If the application has resource references that map to resources that have an Oracle database doing back-end processing, specify or correct the isolation level to be used for such resources when used by the application. Oracle databases support ReadCommitted and Serializable isolation levels only.

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

  28. Click Finish.

  29. Associate any necessary shared libraries with the application. For information on shared libraries, see Administer shared libraries.

  30. Save the configuration. The application is registered with the administrative configuration and application files are copied to the target directory.

    • For a WAS instance, application files are copied to the destination directory when you save the configuration.

    • For a WAS Network Deployment instance, application files are copied to remote nodes when you synchronize configuration changes.

 

Uninstall applications

To uninstall an application, follow these steps:

  1. Start the 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.

 

See also