You can install an enterprise application file on an application
server by dragging or copying
an enterprise archive (EAR), web application archive (WAR), Java archive (JAR), or Session Initiation
Protocol (SIP) archive (SAR) to a monitored directory. An enterprise
application file must conform to the Java Platform, Enterprise Edition
(Java EE) specification.
Before you begin
Develop and assemble the EAR, JAR, WAR, or SAR file. You
can use a supported assembly tool such as an IBM® Rational® Application
Developer for WebSphere® Software
product to specify bindings and assemble the file.
Installing
an EAR, JAR, WAR, or SAR file by adding it to a monitored directory
does not change existing Java Naming and Directory (JNDI) and other
application bindings. If you must set binding values during deployment,
install the file using the administrative console application installation
wizard, a wsadmin script, or a properties file that sets bindings.
See Installing enterprise
application files by adding properties files to a monitored directory.
By
default, monitored directory deployment is not enabled. Before you
can use monitored directory deployment, you must enable it. See Setting monitored directory deployment
values.
Restriction: Installing an EAR, JAR,
WAR, or SAR file by adding it to a monitored directory is available
only on distributed and z/OS® operating
systems. It is not supported on IBM i operating systems.
Avoid trouble: ![[Updated in August 2011]](../../delta.gif)
Do not use monitored directory deployment in
a production environment where the application must remain continuously
available. Instead, in production environments, use an automated process
that staggers application updates to each application server by first
draining requests from each server, updating the application, and
then restarting the server. For information about this automated process,
see
IBM WebSphere Developer Technical Journal: Maintain continuous
availability while updating WebSphere Application Server enterprise
applications.
![[Updated in August 2011]](../../deltaend.gif)
aug2011
gotcha
About this task
New feature: You can
deploy an EAR, JAR, WAR, or SAR file to an application server by dragging or copying the file to
a monitored directory. For base (stand-alone) application servers,
the monitored directory is the
monitoredDeployableApps/servers/server_name directory
of the application server profile. The product scans a monitored
directory for new applications no more frequently than every five
seconds, by default. After finding a new EAR, JAR, WAR, or SAR file
in a monitored directory, the product installs the file on the application
server and starts the application
or module.
newfeat
After you add an EAR file to a monitored directory,
the product creates a temporary copy of the EAR file in another directory
and installs the file on the server. After you add a JAR, WAR, or
SAR file to a monitored directory, the product creates a temporary
copy of the archive in another directory, wraps the archive in an
EAR file named archive_extension.ear,
and installs the new EAR file. For example, simpleApp.war is
installed as simpleApp_war.ear. The original
archive that you added to the monitored directory is not changed.
You
can update application files the same way. If you later add an updated
EAR, JAR, WAR, or SAR file to the same monitored directory, the product
stops the previously deployed application, installs the updated file
on the application server, and
starts the updated application or module. For example, suppose you
previously deployed my_app.ear by dragging it
to a monitored directory. If you later drag a file named my_app.ear to
the monitored directory, the product replaces the previously deployed
EAR file with the updated EAR file that has the same name. The server must be running for the product to
notice changes to files in its monitored directory.
You can
use a graphical file browser to drag or copy the EAR, JAR, WAR, or
SAR file. Alternatively, you can use operating system commands to
copy a file into a monitored monitoredDeployableApps subdirectory.
Procedure
- Ensure that the application server on which you want to install the enterprise application
file is running.
- Ensure that monitored directory deployment is enabled.
See Setting monitored directory deployment values.
- Browse the file structure of the computer and find the monitored directory.
For
base (stand-alone) application servers, the monitored directory is
under the application server profile. The directory path is:
- app_server_root/profiles/application_server_profile_name/monitoredDeployableApps/servers/server_name
For stand-alone servers, the product creates a monitored
server_name directory
automatically.
- Copy the EAR, JAR, WAR, or SAR file that you want to deploy
to the monitored directory.
Choose a file that is not
already deployed to the target monitored directory, unless you want
to update a currently deployed file.
Results
The product adds a directory having the same name as the
file to the installedApps/cell_name directory
of the profile.
Also, the product writes messages about the
application deployment to the SystemOut.log file
in the app_server_root/logs/server_name directory.
The messages start with the CWLDD message key.
The
messages indicate that the product deployed the application file and
that the application is running.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log, and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
Example
Suppose you want to install the sample DynaCacheEsi.ear file
by copying the EAR file to a monitored directory. You can find the
sample EAR file in the app_server_root/installableApps directory.
Deploying
an EAR file on a stand-alone application server
- Ensure that the application server on which you want to install
the DynaCacheEsi.ear file is running.
To see
if the server is running, you can use the serverStatus -all command.
To start the server, you can use the startServer server_name command.
For example, suppose the stand-alone application server
has a profile name of AppSrv02. Run the
serverStatus command
from a command prompt at the
app_server_root/profiles/AppSrv02/bin directory:
serverStatus -all
If the server is not
running, start the server.
For example, to start
an application server named server1 on AppSrv02, run the
startServer command
from a command prompt at the
app_server_root/profiles/AppSrv02/bin directory:
startServer server1
The
Server server1
open for e-business message indicates that the server is running.
- Locate the monitored directory.
For the stand-alone
AppSrv02 profile, the monitored directory is app_server_root/profiles/AppSrv02/monitoredDeployableApps/servers/server1.
- Copy the DynaCacheEsi.ear file in the app_server_root/installableApps directory
to the monitored directory.
- Verify that the directory for installed applications exists.
- app_server_root/profiles/AppSrv02/installedApps/cell_name/DynaCacheEsi.ear
- Verify that DynaCacheEsi.ear is in the list
of installed enterprise applications and is running.
What to do next
Test the deployed application or module. For example,
point a web browser at the URL for a deployed application and examine
the performance of the application.
If the deployment is not
successful, read messages in the SystemOut.log file,
fix the error condition, and add the application or module to the
monitored directory again.