Technical data

7 Deploying Applications
7-8 Administration Guide
-Dweblogic.ProductionModeEnabled=true
If auto-deployment is enabled for the target WebLogic Server domain, when an
application is copied into the
/config/domain_name/applications directory of
the WebLogic Administration Server, the Administration Server detects the presence
of the new application and deploys it automatically (if the Administration Server is
running). (The subdirectory
domain_name is the name of the WebLogic Server
domain that was used when starting the Administration Server.) If WebLogic Server
is not running when you copy the application to the
/applications directory, the
application is deployed the next time the WebLogic Server is started.
Note that applications already in the
/config/domain_name/applications
directory will be deployed automatically even when production mode is enabled. It is
not advisable to store applications or files in the directory
/config/domain_name/applications when switching to production mode.
If you use the Administration Console to make any changes to the configuration of an
application that is auto-deployed, those changes are not stored persistently, that is, no
changes are made to the configuration defined in the
config.xml for the active
domain. If you make changes to the configuration of an application that is
auto-deployed, those changes will be gone if you restart the Administration Server.
Enabling or Disabling Auto-Deployment
By default, auto-deployment is enabled.
To determine whether you have auto-deployment enabled, invoke the Administration
Console and go to the domain applications settings page
(domain_name
→Configuration→Applications) for the domain. This page allows you
to enable or disable auto-deployment and to set the interval (in milliseconds) at which
the WebLogic Server checks for new applications in the
/applications
subdirectory. By default, the Administration Server checks every three seconds for
changes in the
/applications directory when auto-deployment is enabled.