If application bindings were not specified for all enterprise beans
or resources in an 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.
An example of a simple .ear file installation using the default
bindings follows:
- Go to the Preparing
for application install pages.
Click Applications > Install New
Application in the console navigation tree.
- 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 /home/myuserid/myapps.
- 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.
Assuming the node is MYISERIES,
click MYISERIES, home, * myuserid, myapps, my_appl.ear
*, and then OK.
- For How do you want to install the application,
select Show me all installation options and parameters.
- Click Next.
- On the second Preparing for application installation page, select Generate
default bindings and click Next.
Using the default bindings causes
any incomplete bindings in the application to be filled in with default values.
Existing bindings are not changed. By choosing this option, you can skip many
of the steps on the Install New Application page and go directly to the Summary
step.
- If application security warnings are displayed, read the warnings and
click Continue.
- On the Install New Application page, click step 2, Manage modules,
and verify the cell, node, and server onto which the application files will
install.
- On the Manage modules panel,
select the server onto which the application files will install from the Clusters
and Servers list, click Module to select all of the application
modules, and click Next.
On the Manage modules panel,
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 beside Summary,
the last step.
- On the Summary panel, click Finish.
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 Applications > Enterprise Applications 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.