Free Oracle WebLogic Server 12c Essentials 1Z0-599 Exam Questions

* Built on top of Oracle Coherence (Coherence), Coherence*Web:

/ brings Coherence data grid's data scalability, availability, reliability, and performance to in-memory session management and storage.

/ can be deployed to many mainstream application servers such as Oracle GlassFish Server, Oracle WebLogic Server, IBM WebSphere, Tomcat, and so on

* Coherence*Web enables HTTP session sharing and management across different Web applications, domains, and heterogeneous application servers. Session data can be stored in data caches outside of the application server, thus freeing application server heap space and enabling server restarts without losing session data.

* When you create a data source using the Administration Console, the Administration Console automatically sets the Test Table Name attribute for a data source based on the DBMS that you select. The Test Table Name attribute is used in connection testing which is optionally performed periodically or when you create or reserve a connection, depending on how you configure the testing options. For database tests to succeed, the database user used to create database connections in the data source must have access to the database table. If not, you should either grant access to the user (make this change in the DBMS) or change the Test Table Name attribute to the name of a table to which the user does have access (make this change in the WebLogic Server Administration Console).

* To manually test a connection from a data source, you can use the Test Data Source feature on the JDBC Data Source: Monitoring: Testing page in the Administration Console (see '' Test JDBC data sources'') or the testPool() method in the JDBCDataSourceRuntimMBean. To test a database connection from a data source, Test Reserved Connections must be enabled and Test Table Name must be defined in the data source configuration. Both are defined by default if you create the data source using the Administration Console.

When you test a data source, WebLogic Server reserves a connection, tests it using the query defined in Test Table Name, and then releases the connection.

A Node Manager process is not associated with a specific WebLogic domain but with a

machine. You can use the same Node Manager process to control server instances in

any WebLogic Server domain, as long as the server instances reside on the same

machine as the Node Manager process. Node Manager must run on each computer

that hosts WebLogic Server instances---whether Administration Server or Managed

Server---that you want to control with Node Manager.

* 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.

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.

A: You can enable JFR at runtime to take JRA recordings from the JRockit Management Console. You also have the option of turning off the JFR and recordings at the JRockit JVM level from the java command line using:

$ java -XX:-FlightRecorder

B:

* In most environments, there is little performance impact when the Diagnostic Volume is set to Low and the most performance impact if Diagnostic Volume is set to High. The volume of diagnostic data produced by WebLogic Server needs to be weighed against potential performance loss.

* WLDF provides theDiagnostic Volumeattribute to set the amount of code coverage that is enabled and the amount of data provided in the events that are generated for the covered code

The following code example sets the volume toMedium:

. . .

connect()

edit()

startEdit()

cd('Servers/myserver')

cd('ServerDiagnosticConfig')

cd('myserver')

cmo.setWLDFDiagnosticVolume('Medium')

save()

activate()

D: Integrated with the WebLogic Diagnostic Image and Watch and Notification

system

* Enables capture based on system state, event -- capture during event; no need to replicate

* Watch for stuck thread count, heap size increase, available memory, etc.

* Set up notifications: capture WLDF image

* Diagnostic image capture spurs JFR file generation; JFR file included in diagnostic image

* Includes full JFR data from all event generators

Note:

* WebLogic Diagnostic Framework (WLDF) provides specific integration points with JRockit Mission Control Flight Recorder. WebLogic Server events are propagated to the Flight Recorder for inclusion in a common data set for runtime or post-incident analysis.

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:

* iAS: Oracle Application Server

* Oracle WebLogic Server SmartUpgrade is one several Oracle software tools that can help you upgrade your entire Oracle Application Server or Oracle WebLogic Server environment to Oracle Fusion Middleware 11g.

Oracle Coherence 3.6 is a component of Oracle Fusion Middleware 11g.