How to Pass the Oracle 1z0-599 Exam: Comprehensive Oracle WebLogic Server 12c Essentials Guide and Tips

-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)

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.

Note:

An internal application may be configured to always use a minimum version of the same library. Applications that require no specific version can be configured to use the latest version of the library.

Note:

* Specification-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the specification version of the shared Java EE library. Referencing applications can optionally specify a required Specification-Version for a library; if the exact specification version is not available, deployment of the referencing application fails.

The Specification-Version uses the following format:

Major/minor version format, with version and revision numbers separated by periods (such as "9.0.1.1")

Referencing applications can be configured to require either an exact version of the shared Java EE library, a minimum version, or the latest available version.

* Implementation-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the code implementation version of the shared

Java EE library. You can provide an Implementation-Version only if you have

also defined a Specification-Version.

* Extension-Name (a manifest Attributes for Java EE Libraries)

An optional string value that identifies the name of the shared Java EE library. Referencing applications must use the exact Extension-Name value to use the library.

As a best practice, always specify an Extension-Name value for each library. If you do not specify an extension name, one is derived from the deployment name of the library. Default deployment names are different for archive and exploded archive deployments, and they can be set to arbitrary values in the deployment command.

* After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console.

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

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

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: auto-kill-if-failed

Specifies whether the Node Manager should automatically kill

this server (the managed server) if its health state is failed.

(Interface=weblogic.management.configuration.ServerMBean Attribute=getAutoKillIfFailed)

When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

E: When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.