![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Installing enterprise application files by adding them to a monitored directory
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.
避免困難: 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.gotchaAbout this task
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.
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
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.
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.
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.

作業主題