Oracle 1z0-599 Dumps

B.   

modifying the configuration of an offline domain

E.   

creating and extending domains

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
Reference: Creating and Configuring WebLogic Domains Using WLST Offline

D.   

wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:

wls-maven-plugin—Delivered in WebLogic Server 12c, provides enhanced
functionality to install, start and stop servers, create domains, execute WLST
scripts, and compile and deploy applications.
Reference: Developing Applications for Oracle WebLogic Server, Using the WebLogic
Development Maven Plug-In

E.   

It provides improved performance by associating a database connection with an HTTP
session.

Session Affinity Policy
Web applications where a user session has back-to-back online transaction processing
(OLTP) have better performance when repeated operations against the same set of
records are processed by the same RAC instance. Business applications such as online
shopping and online banking are typical examples of this pattern.
A GridLink data source uses the Session Affinity policy to ensure all the data base
operations for a web session, including transactions, are directed to the same Oracle RAC
instance of a RAC cluster.
Note:
The context is stored in the HTTP session. It is up to the application how windows (within a
browser or across browsers) are mapped to HTTP sessions.
Note 2:
* GridLink Affinity
WebLogic Server GridLink affinity policies are designed to improve application performance
by maximizing RAC cluster utilization. A GridLink data source monitors RAC load balancing
advisories (LBAs) using the AffEnabled attribute to determine if RAC affinity is enabled for
a RAC cluster. The first connection request is load balanced using Runtime Connection
Load-Balancing (RCLB) and is assigned an Affinity context. All subsequent connection
requests are routed to the same Oracle RAC instance using the Affinity context of the first
connection until the session ends or the transaction completes

Reference; Configuring and Managing JDBC Data Sources for Oracle Weblogic server 12c,
Using GridLink Data Sources

A.   

JMS Queue

JMS queue
A staging area that contains messages that have been sent and are waiting to be read.
Note that, contrary to what the name queue suggests, messages don't have to be delivered
in the order sent. A JMS queue only guarantees that each message is processed only
once.
Incorrect:
Not B: (Only one queue required)
* A distributed destination is a set of destinations (queues or topics) that are accessible as
a single, logical destination to a client. A distributed destination has the following
characteristics:
It is referenced by its own JNDI name.
Members of the set are usually distributed across multiple servers within a cluster, with
each destination member belonging to a separate JMS server.
* A distributed queue is a set of physical JMS queue members. As such, a distributed
queue can be used to create a QueueSender, QueueReceiver, and a QueueBrowser. The
fact that a distributed queue represents multiple physical queues is mostly transparent to
your application.
Not Topic:
JMS topic
A distribution mechanism for publishing messages that are delivered to multiple
subscribers.

B.   

Configure a WebLogic Cluster for Distributed JMS.

C.   

Update the client application that is creating the JMS messages to use Unit of Order.

D.   

 Enable XA Transactions on the JMS Connection Factory used by the client application.

C: Message Unit-of-Order is a WebLogic Server value-added feature that enables a standalone
message producer, or a group of producers acting as one, to group messages into a
single unit with respect to the processing order. This single unit is called a Unit-of-Order
and requires that all messages from that unit be processed sequentially in the order they
were created.
D Transactions required for parallel processing.
Incorrect:
A: Many applications need an even more restricted notion of a group than provided by the
Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic
JMS provides the Unit-of-Work (UOW) Message Groups, which allows applications to send
JMS messages, identifying some of them as a group and allowing a JMS consumer to
process them as such. For example, an JMS producer can designate a set of messages
that need to be delivered to a single client without interruption, so that the messages can
be processed as a unit. Further, the client will not be blocked waiting for the completion of
one unit when there is another unit that is already complete.
Note:
* WebLogic JMS defines two default connection factories, which you can look up using the
following JNDI names:
weblogic.jms.ConnectionFactory
weblogic.jms.XAConnectionFactory
Reference: Using Message Unit-of-Order

B.   

Based on available examples of Filtering Classloader entries, try to modify get the
proper entries.

Note:
* The FilteringClassLoader provides a mechanism for you to configure deployment
descriptors to explicitly specify that certain packages should always be loaded from the
application, rather than being loaded by the system classloader. This allows you to use
alternate versions of applications such as Xerces and Ant.
* To configure the FilteringClassLoader to specify a certain package is loaded from an
application, add a prefer-application-packages descriptor element to the weblogicapplication.
xml which details the list of packages to be loaded from the application. The
following example specifies that org.apache.log4j.* and antlr.* packages are loaded from
the application, not the system classloader:
<prefer-application-packages>
<package-name>org.apache.log4j.*</package-name>
<package-name>antlr.*</package-name>
</prefer-application-packages>
Reference: Understanding WebLogic Server Application Classloading

A.   

Search information in logs across multiple domains

C.   

Move transaction logs to a highly available database.

D.   

Move JMS persistent stores to a highly available database.

A.   

There may be a bottleneck in the application that additional hardware would not solve.

C.   

Adding hardware at the application layer may place additional load on an already
overloaded database, network appliance, or storage system.

B.   

coherence.jar

C.   

active-cache-1.0.jar

D.   

coherence-web-spi.war

B, D: In addition to the coherence.jar file, Coherence provides a deployable shared library,
coherence-web-spi.war, that contains a native plug-in to WebLogic Server's HTTP Session
Management interface. Coherence also provides the active-cache-1.0.jar file which
contains the classes that allow WebLogic Server to interact with Coherence.
C: The active-cache-1.0.jar is included in the WebLogic Server installation.
Reference: Oracle Coherence Tutorial for Oracle Coherence