Example: Installing an EAR file using the default bindings

 

+

Search Tips   |   Advanced Search

 

If application bindings were not specified for all enterprise beans or resources in an enterprise application during application development or assembly, we can select to generate default bindings. After application installation, we can modify the bindings as needed using the admin console.

This page assumes that the application can run on a Web server.

This page describes how to install a simple .ear file using the default bindings. We can follow the steps to install any application, including applications provided with WAS in the samples or installableApps subdirectory.

1. Click...

   Applications | New Application | New Enterprise Application

2. On the first Preparing for application install page, specify the full path name of the EAR file.

   1. For Path to the new application, specify the full path name of the .ear file. For this example, the base file name is my_appl.ear and the file resides on a server at C:\sample_apps.

      Optionally, select Remote file system and click Browse. On the Browse Remote Filesystems page, select the node that runs on the server which holds my_appl.ear and the EAR file name.

      Click C:\sample_apps\my_appl.ear and then OK.

   2. Click Next.

3. On the second Preparing for application install page, choose to generate default bindings.

   1. Expand Choose to generate default bindings and mappings.

   2. Select Generate default bindings.

      Use the default bindings causes any incomplete bindings in the application to be filled in with default values. WAS ND v7.0 does not change existing bindings. By choosing this option, we can skip many of the steps of the application installation wizard and go directly to the Summary step.

   3. Click Next.

4. If application security warnings are displayed, read the warnings and click Continue.

5. On the Install New Application page, click the step number for Map modules to servers, and verify the cell, node, and server onto which the application files will install.

   1. From the Clusters and servers list, select the server onto which the application files will install.

   2. Select all of the application modules.

   3. Click Next.

   On the Map modules to servers page, we can map modules to other servers such as Web servers. If we want a Web server to serve the application, use the Ctrl key to select an appserver or cluster and the Web server together in order to have the plug-in configuration file plugin-cfg.xml for that Web server generated based on the applications which are routed through it.

6. On the Install New Application page, click the step number beside Summary, the last step.

7. On the Summary panel, click Finish.

 

Next steps

Examine the application installation progress messages. If the application installs successfully, save the admin configuration. We can now see the name of the application in the list of deployed applications on the Enterprise applications page accessed by clicking...

Applications | Application Types | WebSphere enterprise apps

If the application does not install successfully, read the messages to identify why the installation failed. Correct problems with the application as needed and try installing the application again. If the application has a Web module, try opening a browser on the application.

1. Point a Web browser at the URL for the deployed application.

   The URL typically has the format...

   http://host_name:9060/Web_module_name

   Examine the performance of the application.

If the application does not perform as desired, edit the application configuration, then save and test it again.

Application bindings

 

Related tasks

Install enterprise application files with the console
Map modules to servers
Install enterprise application files

 

Related

Prepare for application installation settings
Prepare for application installation binding settings