Preparing for application installation settings
Use this page to specify an application or module to install.
To view this administrative console page, click .
This page is the first Preparing for the application installation page. On this page, specify an application or module to install. You can install an enterprise application archive (EAR file), enterprise bean (EJB) module (JAR file), Session Initiation Protocol (SIP) module (SAR file), or web module (WAR file).
The second Preparing for the application installation page has more installation options, such as to generate default bindings for incomplete existing bindings in your application or module.
Path to the new application
Specifies the fully qualified path to the enterprise application file.
The file can be an .ear, .jar, .sar, or .war file.
During application installation, the product typically uploads application files from a client workstation running the browser to the server running the administrative console, and then deploys the application files on the server. In such cases, use the web browser running the administrative console to select EAR, WAR, SAR, or JAR modules to upload to the server.
Use Local file system when the browser and application files are on the same computer.
- The application file resides on any node in the current cell context. Only .ear, .jar, .sar, or .war files are shown during the browsing.
- The application file resides on the file system of any of the nodes in a cell.
- The application file already resides on the computer running the application server. For example, the field value might be profile_root/installableApps/test.ear.
After the product transfers the application file, the Remote file system value shows the path of the temporary location on the server.