InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.1: Administering applications (overview) >
6.6.1.1: Administering enterprise applications with the Java administrative console >
6.6.1.1.1: Installing enterprise applications and modules with the Java administrative console

6.6.1.1.1: Installing enterprise applications and modules with the Java administrative console

To install an enterprise application into an application server runtime, use the Application Installation Task Wizard. Access it by clicking Console -> Wizards -> Install Enterprise Application on the console menu bar.

Using the Application Installation wizard

You use the Application Installation wizard to install an application (EAR file) or module (JAR or WAR file). It leads you through some or all of the following tasks, depending on whether you are working with an application, EJB module, or Web module:

Please take the term "EJBs" in the console to refer to "enterprise beans."

  Users and groups defined in the application EAR file will be removed during application installation if they do not exist in the specified system registry.

  Note that if the EAR file or EJB module that you are installing contains method permissions, you will be prompted whether to deny all access to unprotected methods. If you select to deny access, the method permission for all methods in all enterprise beans in the application will be set to DenyAllRole.

Specifying the application or module

On the Specifying the Application or Module panel:

  1. Select to work with either an application or a standalone module.
  2. Specify the application or module path, the application name and, for modules, the context root for the web module.

    View properties reference for:

  3. Click Next.

Mapping users to roles

For assistance with this task, see the associated instructions.

When finished, click Next.

Mapping RunAs roles to users

On the Mapping EJB RunAs Roles to Users panel:

  1. Select a RunAs role from the table and click Select.
  2. Enter the name of a user. The user must exist in the user registry and be a member of the role to which the RunAs role is being assigned.
  3. Enter the password for the user in the Password field.
  4. Repeat steps 1 and 4 for each role that needs to be mapped.
  5. Click Next.

Binding EJBs to JNDI names

On the Bind EJB to JNDI Name panel:

  1. Select an EJB from the table and click Edit JNDI Name.
  2. Select a JNDI name for the EJB.

    View properties reference for:

  3. Repeat steps 1 and 2 for each EJB that needs binding to a JNDI name.
  4. Click Next.

Mapping EJB references to EJBs

On the Mapping EJB references to EJB panel:

  1. Select an EJB reference from the table and click Select EJB.
  2. Select an EJB and provide its JNDI name.

    View properties reference for:

  3. Repeat steps 1 and 2 for each EJB reference that needs to be mapped.
  4. Click Next.

Mapping resource references to resources

On the Mapping Resource References to Resources panel:

  1. Select a resource reference from the table and click Select Resource.
  2. Select a resource.

    View properties reference for:

  3. Repeat steps 1 and 2 for each resource reference that needs to be mapped.
  4. Click Next.

Specifying the default datasource for EJBModule

On the Specifying the Default Datasource for EJBModule panel:

  1. Select one or more EJB modules from the table and click Select DataSource. To select multiple modules, press the Ctrl key and click the modules.
  2. Select a datasource.

    View properties reference for:

  3. Repeat steps 1 and 2 for EJB modules that need a datasource.
  4. Click Next.

Specifying datasources for CMP beans

On the Specifying Datasources for Individual CMP Beans panel:

  1. If your Container Managed Persistence (CMP) beans need datasources, select one or more CMP beans from the table and click Select DataSource. To select multiple CMP beans, press the Ctrl key and click the beans.
  2. Select a datasource.

    View properties reference for:

  3. Repeat steps 1 and 2 for CMP beans that need a datasource.
  4. Click Next.

Specifying virtual hosts for WAR modules

On the Specifying the Virtual Hosts for WAR Modules panel:

  1. Select one or more web modules from the table and click Select Virtual Host. To select multiple modules, press the Ctrl key and click the modules.
  2. Select a virtual host.

    View properties reference for:

  3. Repeat steps 1 and 2 for web modules that need a virtual host.
  4. Click Next.

Selecting the target application server

On the Selecting the Application Server panel:

  1. Select one or more modules from the table and click Select Server. To select multiple modules, press the Ctrl key and click the modules.
  2. Select an application server or server group.

    View properties reference for:

  3. Repeat steps 1 and 2 for modules that need an application server or server group.
  4. Click Next.

Completing the application or module installation

The Completing the Application Installation Wizard panel lists the node onto which the application will be installed and indicates whether you must copy one or more files to a specific directory.

To have the wizard create a new application with the values you specified, click Finish. If the wizard encounters an error, a message will display explaining why an application could not be created.

To change any values specified, click Back to return to the appropriate panel(s), make any needed changes, and then click Finish on this panel.

Go to previous article: Administering enterprise applications with the Java administrative console Go to next article: Viewing deployment descriptors of enterprise applications with the Java administrative console

 

 
Go to previous article: Administering enterprise applications with the Java administrative console Go to next article: Viewing deployment descriptors of enterprise applications with the Java administrative console