A customer stores environmental settings in the deployment descriptors of an application.
Whenever they promote the application version from testing to the production environment, they
need to open the archive and modify the deployment descriptor. This process is against their
security policy.
What approach should you recommend to leverage WebLogic features such that they do not have
to modify the application archive for different environments?
A.
Keep environmental data in the global settings of domain and the application can read it from
the domain where it runs.
B.
Keep environmental data in Deployment Plan XML files. It allows you to change parameters in
the deployment descriptor without opening the archive file.
C.
Keep environmental data in the database because it is the most effective way of parametrizing
the environment.
D.
Keep archive in exploded format so the customer does not have to open the archive files.
E.
Eliminate all environmental settings from the application. There should not to be any
environmental settings in the application.
Explanation:
WebLogic Server uses the standard J2EE web.xml deployment descriptor for
defining a Web Application. Some applications also require the WebLogic-specific deployment
descriptor, weblogic.xml. You use these deployment descriptors to define components and
operating parameters for a Web Application. Deployment descriptors are standard text files,
formatted using XML notation. You package them in the Web Application.
Reference: Overview of Web Application Deployment Descriptors