Use this page to install an application (EAR file) or module (JAR or WAR file).
To view this administrative console page, click Applications > Install New Application.
Follow the steps on this page to install an application or module. You must complete, at minimum, the first step; you must complete some or all of the later steps, depending on whether you are installing an application, EJB module, or Web module.
Use Local path if the browser and application files are on the same machine (whether or not the server is on that machine, too).
Use Server path if the application file resides on any node in the current cell context. Only .ear, .jar, or .war files are shown during the browsing.
During application installation, application files are typically uploaded from a client machine running the browser to the server machine running the administrative console, where they are deployed. In such cases, the Web browser running the administrative console is used to select EAR, WAR, or JAR modules to upload to the server machine.
In some cases, however, the application files reside on the file system of any of the nodes in a cell. To have the application server install these files, use the Server path option.
You can also use this option to specify an application file already residing on the machine running the application server. For example, the field value on Windows NT might be C:\WebSphere\AppServer\installableApps\test.ear. If you are installing a stand-alone WAR module, then you also must specify the context root.
This field is used only to install a stand-alone WAR file. The context root is combined with the defined servlet mapping (from the WAR file) to compose the full URL that users type to access the servlet. For example, if the context root is /gettingstarted and the servlet mapping is MySession, then the URL is http://host:port/gettingstarted/MySession.
By choosing this option, you can directly jump to the Summary step and install the application if none of the steps have a red asterisk (*) next to them. A red asterisk denotes that the step has incomplete data and requires a valid value. On the Summary panel, verify the cell, node and server on which the application is installed.
Generate Default Bindings must be selected in order to use any of the other options on the panel.
Bindings are generated as follows:
Generate Default Bindings is similar to the scripting options -usedefaultbindings and -nousedefaultbindings.
The default strategy suffices for most applications or at least for most bindings in most applications. However, it does not work if:
In such cases, you can alter the behavior with an XML document (a custom strategy). Use the Specific bindings file field to specify a custom strategy and see the field's help for examples.
Prefixes is similar to the scripting option -defaultbinding.ejbjndi.prefix.
If this check box is checked, the existing bindings are overridden by the generated ones.
Override is similar to the scripting option -defaultbinding.force.
If the Default Bindings for EJB 1.1 CMPs radio button is selected, specify the JNDI name for the default data source to be used with the container-managed persistence (CMP) 1.1 beans. Also specify the user ID and password for this default data source.
Default Bindings for EJB 1.1 CMPs is similar to the scripting option -defaultbinding.datasource.jndi.
If Default DataSource for 2.0 CMP Beans is selected, specify the JNDI name for the default data source to be used with the 2.0 CMP beans. Also specify the resource authorization.
Virtual Host is similar to the scripting option -defaultbinding.virtual.host.
Alter the behavior of the default binding with an XML document (custom strategy). Custom strategies extend the default strategy so you only need to customize those areas where the default strategy is insufficient. That is, you only need to describe how you want to change the bindings generated by the default strategy; you do not have to define bindings for the entire application.
Specific bindings file is similar to the scripting option -defaultbinding.strategy.file.
Brief examples of how to override various aspects of the default bindings generator follow:
Controlling an EJB JNDI name
<?xml version="1.0"?> <!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd"> <dfltbndngs> <module-bindings> <ejb-jar-binding> <jar-name>helloEjb.jar</jar-name> <!-- this name must match the module name in the .ear file --> <ejb-bindings> <ejb-binding> <ejb-name>HelloEjb</ejb-name> <!-- this must match the <ejb-name> entry in the EJB jar DD --> <jndi-name>com/acme/ejb/HelloHome</jndi-name> </ejb-binding> </ejb-bindings> </ejb-jar-binding> </module-bindings> </dfltbndngs>
Setting the connection factory binding for an EJB JAR file
<!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd"> <dfltbndngs> <module-bindings> <ejb-jar-binding> <jar-name>yourEjb20.jar</jar-name> <connection-factory> <jndi-name>eis/jdbc/YourData_CMP</jndi-name> <res-auth>Container</res-auth> </connection-factory> </ejb-jar-binding> </module-bindings> </dfltbndngs>
Setting the connection factory binding for an EJB file
<?xml version="1.0"> <!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd"> <dfltbndngs> <module-bindings> <ejb-jar-binding> <jar-name>yourEjb20.jar</jar-name> <ejb-bindings> <ejb-binding> <ejb-name>YourCmp20</ejb-name> <!-- this matches the ejb-name tag in the DD --> <connection-factory> <jndi-name>eis/jdbc/YourData_CMP</jndi-name> <res-auth>PerConnFact</res-auth> </connection-factory> </ejb-binding> </ejb-bindings> </ejb-jar-binding> </module-bindings> </dfltbndngs>
Overriding a Resource Ref Binding from a WAR, EJB JAR file, or J2EE client JAR file
Example code for overriding a Resource Ref Binding from a WAR file follows. Use similar code to override a Resource Ref Binding from an enterprise bean (EJB) JAR file or a J2EE client JAR file.
<?xml version="1.0"?> <!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd"> <dfltbndngs> <module-bindings> <war-binding> <jar-name>hello.war</jar-name> <resource-ref-bindings> <resource-ref-binding> <!-- the following must match the resource-ref in the DD --> <resource-ref-name>jdbc/MyDataSrc</resource-ref-name> <jndi-name>war/override/dataSource</jndi-name> </resource-ref-binding> </resource-ref-bindings> </war-binding> </module-bindings> </dfltbndngs>
Overriding MDB JMS listener ports
<?xml version="1.0"?> <!DOCTYPE dfltbndngs SYSTEM "dfltbndngs.dtd"> <dfltbndngs> <module-bindings> <ejb-jar-binding> <jar-name>YourEjbJar.jar</jar-name> <ejb-bindings> <ejb-binding> <ejb-name>YourMDB</ejb-name> <listener-port>yourMdbListPort</listener-port> </ejb-binding> </ejb-bindings> </ejb-jar-binding> </module-bindings> </dfltbndngs>
When updating an application, you must specify the bindings to be used. The options include the following: