Note:

* It is recommended that you shutdown WebLogic Server instances through the Administration

Console.

* If automatic server migration is enabled, the servers are required to contact the cluster leader and

renew their leases periodically. Servers will shut themselves down if they are unable to renew their

leases. The failed servers will then be automatically migrated to the machines in the majority

partition.

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

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-599/page_27_img_1.jpg

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

The Clone WebLogic Domain option launches a wizard that enables you to clone a WebLogic Domain

from an existing reference domain that is already discovered with Cloud Control. It allows you to

clone the Middleware Home and its binaries, and the domain configuration.

* If you selected the Cloning a WebLogic Domain option, the Middleware Provisioning: Domain

Configuration page appears. This page contains a set of links to several pages where you can enter

the properties that are most likely to be reconfigured like domain name, listen addresses for the

administration server and managed servers, Node Manager/Machine configuration, and JDBC data

sources.

Note:

* Apache Maven is a software tool for building and managing Java-based projects. WebLogic Server

provides support for Maven through the provisioning of plug-ins that enable you to perform various

operations on WebLogic Server from within a Maven environment.

* Continuous Integration is a software engineering practice which attempts to improve quality and

reduce time to deliver software by applying small, frequent quality control efforts. It is characterized

by these key practices:

Use of a version control system

All developers commit to the ‘HEAD’ (main code line) every day

The product is built on every commit

The build must be automated and fast

Automated deployment to a production-like environment

Automated testing

Results of all builds are published (so everyone can see who broke the build)

Deliverables are easily available (for developers, testers, other stakeholders)

Note:

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-599/page_6_img_1.jpg

The WebLogic Server JDBC subsystem has supported Oracle RAC since WLS

version 8.1 SP5, originally developed for Oracle9i RAC. This support is based on a

particular type of data source configuration, called a multi data source. A multi data

source is a data source abstraction over one or more individual data sources. It

serves JDBC connections from each of the member data sources according to a

specified policy2. A RAC multi data source configuration requires that each

member data source obtain connections to a particular RAC instance, as illustrated

in the following diagram of a three-node RAC cluster configuration.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-599/page_22_img_2.jpg

Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application Clusters(RAC)

Note:

* Persistent messages are saved in the persistent store on the sending side until they are successfully

forwarded to and acknowledged by the receiving side.

Incorrect:

Not A: New or enhanced WebLogic 12c features include

JAVA EE 6 support all kinds of JEE6 specifications

Not C: 12c do include a new Maven plug-in

Not D: For 1.6 adapters, you can embed metadata annotations in the resource adapter class files to

specify deployment information, eliminating the need to create the ra.xml file manually.

http://my-java-planet.blogspot.com/2014/04/which-weblogic-optimization-allows-one.html

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