Under Specify the EAR, WAR or JAR
module to upload and install:
- Ensure that Application name refers
to the application to be updated.
- Under Update options,
select the installed application, module, or file that you want to update.
The online help Preparing
for application update settings provides detailed information on the
options. Briefly, the options are as follows:
- Full application
- Replaces the installed (old) application with the updated (new) application
on the server. If you select Full application,
specify the path for the new .ear file. The path provides
the location of the new .ear file before installation.
- Single module
- Adds a new module to, or replaces a module in, the installed application.
Specify the path for the new Web module (.war),
EJB module (.jar), or resource adapter module (.rar).
The path provides the location of the new module before installation.
To replace a module, the value for Relative
path to module (or module URI) must match the path of the module
to be updated in the installed application.
To
add a new module to the installed application, the value for Relative
path to module must not match the path of a module in the
installed application. The value specifies the desired path for the new module.
If you are installing a standalone Web module, specify
a value for Context root.
- Single file
- Adds a new file to, or replaces a file in, the installed application.
Specify the path for the new file. The path provides the location of the new
file before installation.
To replace a file, the value for Relative
path to file must match the path of the file to be updated in
the installed application.
To add a new file to the installed application,
the value for Relative path to file must not match
the path of a file in the installed application. The value specifies the desired
path for the new file.
The relative path to a file from the root of
the application is the concatenation of the module path and the file path
within the module. For example, if the file is com/mycompany/abc.class within
the module foo.jar, then the relative file path is foo.jar/com/mycompany/abc.class.
- Partial application
- Updates multiple files of an installed application by uploading a compressed
file. Depending on the contents of the compressed file, a single use of this
option can replace files in, add new files to, and delete files from the installed
application. Each entry in the compressed file is treated as a single file
and the path of the file from the root of the compressed file is treated as
the relative path of the file in the installed application.
Specify a valid
compressed file format such as .zip or .gzip.
The path provides the location of the compressed file before installation.
This option unzips the compressed file into the installed application directory.
To
replace a file, a file in the compressed file must have the same relative
path as the file to be updated in the installed application.
To add
a new file to the installed application, a file in the compressed file must
have a different relative path than the files in the installed application.
To
remove a file from the installed application, specify metadata in the compressed
file using a file named META-INF/ibm-partialapp-delete.props at
any archive scope. The ibm-partialapp-delete.props file
must be an ASCII file that lists files to be deleted in that archive with
one entry for each line. The entry can contain a string pattern such as a
regular expression that identifies multiple files. The file paths for the
files to be deleted must be relative to the archive path that has the META-INF/ibm-partialapp-delete.props file.
Refer to Preparing for
application update settings for more information.
After you select an option, specify a path.
Use Local file system if the browser and application
files are on the same machine (whether or not the server is on that machine,
too). Use Remote file system if the application file
resides on any node in the current cell context. Only .ear, .jar,
or .war files are shown during the browsing.
You
can browse the entire file system of a node if the node agent or deployment
manager is running on that selected node.
During application updating, application files
typically are uploaded from a client machine running the browser to the server
machine running the administrative console, where they are deployed. In such
cases, use the Web browser running the administrative console 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 Remote
file system option.
Also use the Remote file
system option to specify an application file already residing
on the machine running the application server.
For
example, the field value on a Windows machine might be C:\WebSphere\AppServer\installableApps\test.ear.
For example,
the field value on a Windows machine might be C:\WebSphere\AppServer\installableApps\test.ear.
If you are installing a standalone Web module, then specify the context root
as well.
After the application file is transferred, the Remote
file system value shows the path of the temporary location on
the deployment manager or server
machine.