Most Recent Oracle 1Z0-599 Exam Dumps

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.

JMS queue

A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary to what the namequeuesuggests, 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 aQueueSender,QueueReceiver, and aQueueBrowser. 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.

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.

* Built on top of Oracle Coherence (Coherence), Coherence*Web:

/ brings Coherence data grid's data scalability, availability, reliability, and performance to in-memory session management and storage.

/ can be deployed to many mainstream application servers such as Oracle GlassFish Server, Oracle WebLogic Server, IBM WebSphere, Tomcat, and so on

* Coherence*Web enables HTTP session sharing and management across different Web applications, domains, and heterogeneous application servers. Session data can be stored in data caches outside of the application server, thus freeing application server heap space and enabling server restarts without losing session data.

WebLogic Server uses the standard J2EE web.xml deployment descriptor for defining a Web Application. Some applications also require the WebLogic-specific deployment descriptor, weblogic.xml. You use these deployment descriptors to define components and operating parameters for a Web Application. Deployment descriptors are standard text files, formatted using XML notation. You package them in the Web Application.