A customer has a development environment that uses the autodeployment feature. The customer claims the application is not redeployed even if the new version is copied to an application subdirectory…

Question

Options

• ACheck if archive file in the compressed version has a new REDEPLOY file.
• BIf server was started in the Development Mode.
• CIf the application includes an EJB 3 module.
• DYou change JVM from HotSpot to JRockit.
• EIf the domain is a singleserver domain.

• A
  5% (3)
• B
  83% (55)
• C
  11% (7)
• D
  2% (1)

Explanation

Autodeployment is intended for use with a single server target in a development environment. * If autodeployment is enabled, when an application is copied into the \autodeploy directory of the Administration Server, the Administration Server detects the presence of the new application and deploys it automatically (if the Administration Server is running). If WebLogic Server is not running when you copy the application to the \autodeploy directory, the application is deployed the next time the WebLogic Server Administration Server is started. Autodeployment deploys only to the Administration Server. * Limitations of AutoDeployment Autodeployed applications are very convenient in a development environment, but there are some limitations: There is no configuration in config.xml for an autodeployed application. Therefore, in the Administration Console, there are no notes or target pages associated with an autodeployed application because there is no backing configuration for that information. You cannot associate an autodeployed application with a deployment plan since autodeployed applications do not support any configuration operations which would be reflected in a deployment plan. You cannot set up security policies or roles for autodeployed applications. You cannot undeploy or redeploy autodeployed applications using WebLogic Server tools.

No community discussion yet for this question.