Install a new application

 

Overview

To install an enterprise application, use the administrative console or the wsadmin tool.

When performing install tasks, if you want to back out of your changes, do not simply move move to another page. Rather, click Cancel.

 

  1. Click thru:

    Applications > Install New Application

  2. On the first Preparing for application install page:

    1. Specify the full path name to your *.ear file

      The EAR file can be either on the client (local) machine or on the server machine.

    2. If you are installing a stand-alone WAR file, specify the context root.

    3. Click Next.

  3. On the second Preparing for application install page:

    Select whether to generate default bindings.

    Using the default bindings causes any incomplete bindings in the application to be filled in with default values. Existing bindings are not altered.

  4. Click Next. The Install New Application pages appear.

    • Decide whether to precompile JSP files as a part of installation. The default is not to precompile JSP files.

    • For Directory to Install Application, specify the directory to which the EAR file will be installed. The default is:

      $WAS_HOME/installedApps/cellname

    • For Distribute Application, specify whether WAS expands or deletes application binaries in the installation destination.

      The default is to enable application distribution. As a result, when you save changes in the console, application binaries for newly installed applications are expanded to the directory specified.

      The binaries are also deleted when you uninstall and save changes to the configuration. 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.

    • For Use Binary Configuration, specify whether the appserver uses the binding, extensions, and deployment descriptors located in deployment.xml file (default), or those located in the EAR file.

      The default is not to use the binary configuration.

    • For Deploy EJBs, specify whether the EJBDeploy tool runs during application installation.

      The tool generates code needed to run EJB files. The default is not to run the EJBDeploy tool.

      Enable this setting if the EAR file was assembled using the AAT, and the EJBDeploy tool was not run during assembly or if the EAR file was not assembled using the AAT tool. Enabling this setting might cause the installation program to run for several minutes.

    • For Application Name, name the application.

      Application names must be unique within a cell and cannot contain characters that are not allowed in object names.

    • For Create MBeans for Resources, specify whether to create MBeans for various resources (such as servlets or JSP files) within an application when the application is started.

      The default is to create MBean instances.

    • For Enable class reloading, specify whether to enable class reloading when application files are updated.

      The default is not to enable class reloading.

    • For Reload Interval, specify the number of seconds to scan the application's file system for updated files.

      The default is the value of the reload interval attribute in the IBM extension (META-INF/ibm-application-ext.xmi) file of the EAR file. This setting takes effect only if class reloading is enabled.

      The reload interval specified here overrides the value specified in the IBM extensions for each Web module in the EAR file (which in turn overrides the reload interval specified in the IBM extensions for the application in the EAR file).

  5. If you chose to generate default bindings, proceed to the Summary Panel. Otherwise, complete the following steps:

    • Provide JNDI Names for Beans panel

      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.

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

      Specify a JNDI name for the default data source for the EJB modules.

      The default data source for the EJB modules is optional if data sources are specified for individual CMP beans.

    • Map datasources for all 1.x CMP

      Specify a JNDI name for data sources to be used for CMP beans.

      The data source attribute is optional for individual CMP beans if a default data source is specified for the EJB module that contains CMP beans.

      If neither a default data source for the EJB module nor a data source for individual CMP beans are specified, then a validation error displays after Finish is clicked, and the installation is cancelled.

    • Map EJB references to beans

      Specify JNDI names for enterprise beans that represent the logical names specified in EJB references.

      Each EJB reference defined in the application must be bound to an EJB file before clicking Finish on the Summary Panel.

    • Map resource references to resources

      Specify JNDI names for the resources that represent the logical names defined in resource references.

      Each resource reference defined in the application must be bound to a resource defined in your WAS configuration before clicking on Finish on the Summary Panel.

    • Map virtual hosts for web modules

      Select a virtual host from the list that should 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 artifacts such as servlets and JSP files in the Web module. Each Web module must have a virtual host to which it maps. Not specifying all needed virtual hosts will result in a validation error displaying after you click Finish on the Summary Panel.

    • Map modules to appservers

      For every module select a target server or a cluster from the Clusters and Servers list.

      Place a checkmark in the check box beside Module to select all of the application modules or select individual modules.

    • Map security roles to users/groups

      Specify users and groups that are mapped to each of the security roles.

      Place a checkmark in the check box beside Role to select all of the roles or select individual roles. For each role, you can specify if predefined users such as Everyone or All Authenticated users are mapped to it. 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 shown, enter search criteria to extract a list of users or groups from the user registry.

      3. Select individual users or groups from the results displayed.

      4. Click OK to map the selected users or groups to the role selected on the step "Map security roles to users/groups panel".

    • Map RunAs roles to user

      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. Place a checkmark in the check box beside Role to select all of the roles or select individual roles. After selecting a role, enter values for the user name, password, and verify password and click Apply.

    • If your application contains EJB 1.x CMP beans that do not have method permissions defined for some of the EJB methods, for the step Ensure all unprotected 1.x methods have the correct level of protection", specify if you want to leave such methods unprotected or assign protection with deny all access.

    • Provide Listener Ports for messaging beans

      Provide a listener port name for every message driven bean. If a name is not specified for each bean, then a validation error displays after you click on Finish on the Summary Panel.

    • Provide default datasource mapping for modules containing 2.0 entity beans

      Specify a JNDI name for the default data source and the type of resource authorization to be used for the default data source for the EJB modules.

      The default data source for EJB modules is optional if data sources are specified for individual CMP beans.

    • Map datasources for all 2.0 CMP panel

      For each of the 2.0 CMP beans specify a JNDI name and the type of resource authorization for data sources to be used.

      The data source attribute is optional for individual CMP beans if a default data source is specified for the EJB module that contains CMP beans. If neither a default data source for the EJB module nor a data source for individual CMP beans are specified, then a validation error is shown after you click Finish and installation is cancelled.

    • Ensure all unprotected 2.0 methods have the correct level of protection panel

      Specify whether you want to assign a specific role to the unprotected methods, add the methods to the exclude list, or mark them as unchecked. Methods added to the exclude list are marked as uncallable.

      For methods marked unchecked no authorization check is performed prior to their invocation.

    • Provide options to perform the EJB Deploy panel

      Specify extra classpath, rmic options, database types, and database schema names to be used while running the EJBDeploy tool. The tool is run on the EAR file during installation after you click Finish.

    • Mapping Resource Environment References to Resources

      Specify JNDI names of resources that map to the logical names defined in resource environment references.

      If each resource environment reference does not have a resource associated with it, a validation error is shown after you click Finish.

    • Replacing RunAs System to RunAs Roles

      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 WebSphere Application Server security server ID and should be used with caution as this ID has more privileges.

    • Specify the isolation level for Oracle type provider

      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.

  6. On the Summary Panel, verify the cell, node, and server onto which the application modules will install. Beside the Cell/Node/Server option, click Click here and verify the settings. Then click Finish.

  7. Associate any shared libraries that the application needs to the application.

  8. Click Save on the administrative console taskbar to save the changes to your configuration. The application is registered with the administrative configuration and application files are copied to the target directory, which is $WAS_HOME/installedApps/cellname by default or the directory that you designate. For the single-server (base) installation, application files are copied to the destination directory when you click Save; for the Network Deployment installation, files are copied to remote nodes when the configuration on the deployment manager synchronizes with the configuration on individual nodes.

  9. Test the application. For example, point a Web browser at the URL for the deployed application and examine the performance of the application. If necessary, update the application.