1z0-599 Oracle WebLogic Server 12c Essentials Questions and Answers

You can configure a JDBC TLOG store to persist transaction logs to a database, which provides the following benefits:

* Leverages replication and HA characteristics of the underlying database.

* Simplifies disaster recovery by allowing the easy synchronization of the state of the database and TLOGs.

* Improved Transaction Recovery service migration as the transaction logs to do not need to be migrated (copied) to a new location.

* You can configure a JDBC TLOG store to persist transaction logs to a database, which allows you to leverage replication and HA characteristics of the underlying database, simplify disaster recovery, and improve Transaction Recovery service migration.

incorrect:

not B: Read-only, One-phase Commit Optimization requires Oracle DB 11.1.0.7.3PSU or above.

Using JNDI, a JMS client can obtain access to a JMS provider by first looking up a ConnectionFactory. The ConnectionFactory is used to create JMS connections, which can then be used for sending and receiving messages. Destination objects, which represent virtual channels (topics and queues) in JMS, are also obtained via JNDI and are used by the JMS client. The directory service can be configured by the system administrator to provide JMS administered objects so that the JMS clients don't need to use proprietary code to access a JMS provider.

Note:

* The Java Naming and Directory Interface (JNDI) is part of the Java platform, providing applications based on Java technology with a unified interface to multiple naming and directory services.

B: WLST enables you to create a new domain or update an existing domain without connecting to a running WebLogic Server (that is, using WLST offline)—supporting the same functionality as the Configuration Wizard.

E: With WLST you can

Creating a Domain (Offline)

Updating an Existing Domain (Offline)

Creating a Domain Template (Offline)

Exporting Diagnostic Data (Offline)

Stepping Through a Sample Script: Creating a Domain Using WLST Offline

The JRockit JVM is included in all Oracle WebLogic products – Oracle WebLogic Server Standard Edition, Oracle WebLogic Enterprise Edition, WebLogic Suite, and Oracle WebLogic Application Grid. JRockit will also be used across the Oracle Fusion Middleware and Oracle Applications product families, with the certification process happening over the coming months. For current status, see the certification matrices available from Oracle Metalink.

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: 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 the Diagnostic Volume attribute 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 to Medium:

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.

WAN HTTP Session State Replication

Resources in a wide area network (WAN) are frequently spread across separate geographical regions. In addition to requiring network traffic to cross long distances, these resources are often separated by multiple routers and other network bottle necks. Network communication in a WAN generally has higher latency and slower interconnect.

Slower network performance within a WAN makes it difficult to use a synchronous replication mechanism like the one used within a MAN. WebLogic Server provides failover across clusters in WAN by using an asynchronous data replication scheme.

Note:

HTTP Session State Replication

Weblogic Server uses two methods for replicating HTTP session state across clusters:

in-memory replication

* Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

* JDBC-based persistence

In JDBC-based persistence, WebLogic Server maintains the HTTP session state of a servlet or JSP using file-based or JDBC-based persistence.

JDBC-based persistence is also used for HTTP session state replication within a Wide Area Network (WAN). 

Similar to the configuration information, WebLogic Server runtime MBeans are arranged in a hierarchical data structure. When connected to an Administration Server, you access the runtime MBean hierarchy by entering the serverRuntime or the domainRuntime command. The serverRuntime command places WLST at the root of the server runtime management objects, ServerRuntimeMBean; the domainRuntime command, at the root of the domain-wide runtime management objects, DomainRuntimeMBean.