B: Java EE Enterprise Web Services is supported.

E: New or enhanced WebLogic 12c features include

JAVA EE 6 support all kinds of JEE6 specifications are implemented like :

JSF 2.0,Java Servlets 3.0 JPA 2.0 and EJB 3.1.

Managed Beans 1.0

F: WebLogic 12c also supports supports Java SE 7 (and Java SE 6).

Java language optimizations and Internationalization

Client and server support

SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security

Converged Java VM:JRockit and HotSpot are incorporated with the best features from both. Oracle’s Publisher Seminar 2011 during OOW

Incorrect:

not C:

Follow the on-screen instructions to access the table of WebLogic Server installers.

After accessing the installer table, click the  File1  link for the Generic Package or OS-specific Package installer, as appropriate for your operating environment. For example, if your operating system is Linux x86, click the  File1  link under the  Linux (32-bit JVM)  column, on the  Oracle WebLogic Server 12 c R1 + Oracle Coherence  row.

C:

* A WebLogic Messaging Bridge communicates with the configured source and target bridge destinations. For each mapping of a source destination to a target destination, you must configure a messaging bridge instance. Each messaging bridge instance defines the source and target destination for the mapping, a message filtering selector, a QOS, transaction semantics, and various reconnection parameters.

Note:

* In your JMS Foreign Server configuration:

/ Specify oracle.jms.AQjmsInitialContextFactory as the JNDI Initial Context Factory.

/ Configure the JDBC data sources needed for your application environment.

Load Balancing for JMS

WebLogic Server JMS supports server affinity for distributed JMS destinations and client connections. (B, not A)

By default, a WebLogic Server cluster uses the round-robin method to load balance objects. To use a load balancing algorithm that provides server affinity for JMS objects (not D), you must configure the desired method for the cluster as a whole.

By default, JMS messages never expire. When applications send messages to queues or topics with durable subscribers, WebLogic must retain the message until it is consumed. This is fine in most point-to-point messaging applications because consumers are constantly consuming messages. Any message sent to a queue will typically be consumed in a relatively short period of time. If the consumers get disconnected, they will usually reconnect as soon as possible and start processing any messages that might have built up in the queue.

D: For durable subscribers to a topic, this is not necessarily true. The messaging system is forced to retain any message that has not been consumed by a durable subscriber, regardless of whether that durable subscriber will ever return. In this case, WebLogic is at the mercy of the durable subscriber to unsubscribe when it no longer wishes to receive the messages. If the durable subscriber logic is flawed in such a way that the subscribers do not unsubscribe properly, the messaging system will start to fill up with messages that may never be delivered. This calls for real caution in using durable subscribers. Fortunately, there is another way to help deal with this problem. Message expiration can be set at the connection factory level. Using a connection factory’s default time-to-live attribute, we can specify the number of milliseconds that WebLogic should retain an undelivered message after it is sent.

WebLogic GridLink Data Sources supports transaction-based affinity.

Note:

* Rolling Upgrade is the process of upgrading a running WebLogic Server cluster with a patch, maintenance pack, or minor release without shutting down the entire cluster or domain. During the rolling upgrade of a cluster, each server in the cluster is individually upgraded and restarted while the other servers in the cluster continue to host your application.