A.

Per Machine

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.
Reference: Overview of WebLogic Server Domains

B.

You need to install and configure only one instance of Node Manager for all products,
regardless of the WebLogic version number.

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

Description of Figure 2-1 follows
Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

A.

JDBC

-DserverType={"wls" | "wlx"}
Specifies the Server Type, which determines the set of services that are started in the
server runtime.
The default is "wls", which starts all WebLogic Server services, including EJB, JMS,
Connector, Clustering, Deployment, and Management.
The "wlx" option starts a server instance that excludes the following services, making for a
lighter weight runtime footprint:
* (not D) Enterprise JavaBeans (EJB)
* (not B, not E) Java EE Connecter Architecture (JCA)
* (not C) Java Message Service (JMS)
Reference: Oracle Fusion Middleware Command Reference for Oracle WebLogic Server ,
Options for Configuring Deployment Attributes

A.

Search information in logs across multiple domains

A.

Stop and start Managed Servers using the Node Manager.

B.

Stop and start Coherence Servers using the Node Manager.

D.

Create and target JDBC connection pools.

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.

D.

weblogic-application.xml

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.
Reference: weblogic.xml Deployment Descriptor Elements

A.

JMS Server

B.

JMS Module

E.

Persistent Store

The major components of the WebLogic JMS Server architecture, as
illustrated in the figure below.
* (A) JMS servers that can host a defined set of modules and any associated persistent
storage that reside on a WebLogic Server instance.
* (B) JMS modules contains configuration resources (such as queues, topics, and
connections factories) and are defined by XML documents that conform to the weblogicjmsmd.
xsd schema.
* Client JMS applications that either produce messages to destinations or consume
messages from destinations.
* JNDI (Java Naming and Directory Interface), which provides a resource lookup facility.
JMS resources such as connection factories and destinations are configured with a JNDI
name. The runtime implementations of these resources are then bound into JNDI using the
given names.
* (E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent
message data.
The following figure illustrates the WebLogic JMS architecture

Understanding WebLogic JMS

E.

serverRuntime ()

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.
Reference: WebLogic Scripting Tool, Browsing Runtime MBeans