If application bindings were not specified for all enterprise beans or resources in an
enterprise application during application development or assembly, you can select to generate
default bindings. After application installation, you can modify the bindings as needed using the
administrative console.
Before you begin
The application can run on a web server.
About this task
The steps describe how to install a simple .ear file using the default
bindings. You can follow the steps to install any application, including applications provided in
the Samples section of V8.5 product documentation.
Procedure
- Click in the console navigation tree.
- On the first Preparing for application install page, specify the full path
name of the EAR file.
- 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 in the
sample_apps directory.
For this example, the base file name is my_appl.ear and
the file resides on a server at /home/myuserid/myapps. Thus, enter the fully
qualified path name for the file, /home/myuserid/myapps/my_appl.ear.
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.
![[AIX]](../images/aixlogo.gif)
![[HP-UX]](../images/hpux.gif)
![[Linux]](../images/linux.gif)
![[Solaris]](../images/solaris.gif)
Click sample_apps,
my_appl.ear, and then OK.
Assuming the node is MYISERIES, click
MYISERIES, home, * myuserid,
myapps, my_appl.ear *, and then
OK.
Click C:/,
sample_apps, my_appl.ear, and then
OK.
- Click Next.
- On the second Preparing for application install page, choose to generate
default bindings.
- Expand Choose to generate default bindings and mappings.
- Select Generate default bindings.
Using the default bindings causes any incomplete bindings in the application to be filled in with
default values. The product does not change existing bindings. By choosing this option, you can skip
many of the steps of the application installation wizard and go directly to the
Summary step.
- Click Next.
- If application security warnings are displayed, read the warnings and click
Continue.
- 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.
- From the Clusters and servers list, select the server onto which the
application files will install.
- Select all of the application modules.
- Click Next.
On the Map modules to servers page, you can map modules to other servers
such as web servers. If you want a web server to serve the application, use the
Ctrl key to select an application server 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.
- On the Install New Application page, click the step number for
Summary.
- On the Summary page, click Finish.
What to do next
Examine the application installation progress messages. If the application installs successfully,
save your administrative configuration. You can now see the name of your application in the list of
deployed applications on the Enterprise applications page accessed by clicking in the console navigation tree.
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.
- Point a web browser at the URL for the deployed application.
The URL typically has the format
http://host_name:9060/web_module_name, where
host_name is your valid web server and 9060 is the default port number.
- Examine the performance of the application.
If the application does not perform as desired, edit the application configuration, then save and
test it again.