1z0-599 Exam Dumps - Oracle WebLogic Server 12c Essentials

Using the Domain Template Builder to Create Domain Templates

To create a domain, start the Configuration Wizard and choose a domain configuration template.

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.

Note:

* In managing multiple servers, Node Manager uses multiple configuration files and outputs log files to multiple directories.

* nodemanager.domains

This file contains mappings between the names of domains managed by Node Manager and their corresponding directories.

* Node Manager in the WebLogic Server Environment

Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

Note:

* Rolling Upgrade is the process of upgrading a running WebLogic Server cluster with a patch, maintenance pack, or minor release without shutting down the entire cluster or domain. During the rolling upgrade of a cluster, each server in the cluster is individually upgraded and restarted while the other servers in the cluster continue to host your application.

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

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.

The WebLogic Server Management Pack EE greatly improves application

performance by providing unique functionality to automatically detect performance

bottlenecks; quickly diagnose these performance problems, and identify their root

cause. Key application performance management features of the pack include the

following:

* (A) Manage multiple farms and WebLogic Domains centrally

* Monitor Oracle Coherence Cluster – including all nodes within a cluster, all

caches, services, connection managers and connections

* Monitor middleware availability and performance out-of-box; track such data

historically, and receive notifications of potential problems

* Obtain real-time, in-depth JVM diagnostics without instrumentation overhead

* Trace transactions across containers as well as to the database

* (E) Analyze call paths and dependencies via graphical, architecture views

* (E) Automatically discover and model dependencies between Java components,

frameworks, and web services

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.