Oracle 1Z0-599 Exam Dumps

Auto-deployment is intended for use with a single server target in a development environment.

Note:

* If auto-deployment 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. Auto-deployment deploys only to the Administration Server.

* Limitations of Auto-Deployment

Auto-deployed applications are very convenient in a development environment, but there are some limitations:

There is no configuration in config.xml for an auto-deployed application. Therefore, in the Administration Console, there are no notes or target pages associated with an auto-deployed application because there is no backing configuration for that information.

You cannot associate an auto-deployed application with a deployment plan since auto-deployed applications do not support any configuration operations which would be reflected in a deployment plan.

You cannot set up security policies or roles for auto-deployed applications.

You cannot undeploy or redeploy auto-deployed applications using WebLogic Server tools.

Reference; Developing Applications for Oracle WebLogic Server 12c, Auto-Deploying Applications in Development Domains

The WebLogic Server-specific deployment descriptor weblogic.xml.

If your Web application does not contain a weblogic.xml deployment descriptor, WebLogic Server automatically selects the default values of the deployment descriptor elements.

Note:

A Web archive (WAR file) contains the files that make up a Web application. A WAR file is deployed as a unit on one or more WebLogic Server instances. A WAR file deployed to WebLogic Server always includes the following files:

* One servlet or Java Server Page (JSP), along with any helper classes.

* An optional web.xml deployment descriptor, which is a Java EE standard XML document that describes the contents of a WAR file.

* A weblogic.xml deployment descriptor, which is an XML document containing WebLogic Server-specific elements for Web applications.

* A WAR file can also include HTML or XML pages and supporting files such as image and multimedia files.

Load Balancing for JMS

WebLogic Server JMS supports server affinity for distributed JMS destinations and client connections. (B, not A)

By default, a WebLogic Server cluster uses the round-robin method to load balance objects. To use a load balancing algorithm that provides server affinity for JMS objects (not D), you must configure the desired method for the cluster as a whole.

C: Spring Console Extension. WebLogic provides an Admin Console extension for Spring to provide administrators with visual tools for monitoring the Spring parts of deployed applications (first navigate to WebLogic Admin Console's Preferences | Extension menu option and and enable spring-console). This Spring console extension is basically a set of pages which are added amongst the normal pages of the standard WebLogic admin console, rather than being a separate console per se. The extension provides a view onto the values of the WebLogic generated Spring MBeans

D: If you have an issue, you use the Oracle Support organisation for help with WebLogic specific problems and any Spring parts to your application are treated just like your own custom code is, from an Oracle Support perspective.

E: WebLogic Injected Spring Beans is a Weblogic feature that is enabled by default.

Note:

* Types of Security Roles: Global Roles and Scoped Roles

There are two types of security roles in WebLogic Server:

/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource

/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.

Incorrect:

Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.