Oracle 1z0-599 Oracle WebLogic Server 12c Essentials Exam Practice Test

This document provides a complete reference for the elements in 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.

Use the Administration Console to:

* (A) Configure, start, and stop WebLogic Server instances

* Configure WebLogic Server clusters

* (D) Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS)

* Configure security parameters, including managing users, groups, and roles

* Configure and deploy your applications

* Monitor server and application performance

* View server and domain log files

* View application deployment descriptors

* (F) Edit selected run-time application deployment descriptor elements

* (B) Control (start, stop, and restart) standalone Coherence cache servers

* (B) Create and configure Coherence clusters

Incorrect:

Not C: The separate Domain Template Builder is used for creating Domain Templates.

By default, JMS messages never expire. When applications send messages to queues or topics with durable subscribers, WebLogic must retain the message until it is consumed. This is fine in most point-to-point messaging applications because consumers are constantly consuming messages. Any message sent to a queue will typically be consumed in a relatively short period of time. If the consumers get disconnected, they will usually reconnect as soon as possible and start processing any messages that might have built up in the queue.

D: For durable subscribers to a topic, this is not necessarily true. The messaging system is forced to retain any message that has not been consumed by a durable subscriber, regardless of whether that durable subscriber will ever return. In this case, WebLogic is at the mercy of the durable subscriber to unsubscribe when it no longer wishes to receive the messages. If the durable subscriber logic is flawed in such a way that the subscribers do not unsubscribe properly, the messaging system will start to fill up with messages that may never be delivered. This calls for real caution in using durable subscribers. Fortunately, there is another way to help deal with this problem. Message expiration can be set at the connection factory level. Using a connection factory’s default time-to-live attribute, we can specify the number of milliseconds that WebLogic should retain an undelivered message after it is sent.

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

E: Oracle Enterprise Pack for Eclipse 12c (12.1.1.2.1)

Eclipse Based Enterprise Application Development

Oracle Enterprise Pack for Eclipse (OEPE) 12.1.1.2.1 for Eclipse Juno provides tools that make it easier to develop applications utilizing specific Oracle Fusion Middleware technologies and Oracle Database.

Note:

* Support for IDE’s. WebLogic already supported JDeveloper 11.1.1.5, but will come out with the 11.1.1.6 later on. Also suported are Eclipse and NetBeans 7.1 IDE. The JDeveloper 11.1.1.6 and IntelliJIdea IDE will be supported in a later timeframe.

A, B: With Active GridLink for RAC, WebLogic instances are isolated from RAC configuration changes, and DBAs only need to contend with a single data source rather than multiple data sources.

D: Active GridLink for RAC distributes work based on different backend node capacities, automatically detecting and adapting to overworked nodes and hangs. It enables smart load balancing across RAC nodes. This makes it easier to route traffic around node failures, enhancing availability and performance.

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 gainingaccess to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

The JMS SAF Client feature extends the JMS store-and-forward service introduced

in WebLogic Server 9.0 to standalone JMS clients. Now JMS clients can reliably send

messages to server-side JMS destinations, even when the client cannot reach a

destination (for example, due to a temporary network connection failure). While disconnected from the server, messages sent by a JMS SAF client are stored locally on

the client file system and are forwarded to server-side JMS destinations when the

client reconnects. See Reliably Sending Messages Using the JMS SAF Client.

A: Oracle Smart Update is a standalone Java application that is automatically installed in the Middleware home utils/bsu directory. Smart Update simplifies the process of applying patches to your WebLogic Server installation. When support makes a patch available for an installed version of WebLogic Server, you download the patch from My Oracle Support and then use Oracle Smart Update to apply it to your installation. Smart Update organizes all available updates for you, and has several features that allow a great deal of customizing in the way various patches are applied and managed in your environment.

B: As part of a new Enterprise Manager system, the installation wizard does the following:

* Oracle My Oracle Support Management Plug-In

etc.

C: Applying patch from server start script:

After downloading the patch (jar file) follow the below steps:

- Stop your server.

- Then take the path of the folder which has the CRxxxxxx_xxxmpx.jar file and copy it in the CLASSPATH of setDomainEnv.cmd which is in

(/user_projects/domains//bin/setDomainEnv.cmd)

For example, the script would look something like this:

set CLASSPATH=%PRE_CLASSPATH%;%WEBLOGIC_CLASSPATH%; C:\extra\my_projects\doc\CR\CR218639_920mp3.jar;C:\extra\my_projects\doc \CR\ CR360676_920mp3.jar;C:\extra\my_projects\doc\CR\CR367966_920mp3.jar; C:\extra\my_projects\doc\CR\CR368155_920mp3.jar;C:\extra\my_projects\doc\CR\CR370311_920mp3.jar

- Re-start your server.

- You should see the patch applied in the stdout file.

Note:

* The FilteringClassLoader provides a mechanism for you to configure deployment descriptors to explicitly specify that certain packages should always be loaded from the application, rather than being loaded by the system classloader. This allows you to use alternate versions of applications such as Xerces and Ant.

* To configure the FilteringClassLoader to specify a certain package is loaded from an application, add a prefer-application-packages descriptor element to the weblogic-application.xml which details the list of packages to be loaded from the application. The following example specifies that org.apache.log4j.* and antlr.* packages are loaded from the application, not the system classloader:

org.apache.log4j.*

antlr.*

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.

Use multi-node and clustering to get performance suitable for a product environment.