In WebLogic 10.3.6 and WebLogic 12c on ExaLogic, performance of JMS is further improved through _____ and _____.
D: Elastic message overflow is the ability for WebLogic JMS to take advantage of solid state disks, especially on Exalogic, for paging of JMS messages. This is especially important in spikes of traffic. Access to SSD is much faster than disks or the database, which are used for true persistent storage. This speed of writing and reading enables the system to absorb the spikes in traffic.
A customer wants to improve the availability of a web application and provide more predictable scalability when scaling out the application.
Which Feature of WebLogic should you recommend to help solve this problem?
* 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.
Identify three advantages of Active GridLink for RAC over multidata source.
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.
A customer wants to send JMS messages to a remote WebLogic server from a Java SE application over an unreliable network connection. Which feature of WebLogic JMS will enable the customer to send messages from a Java SE client to a JMS destination that is not always easily reached?
. The JMS SAF Client feature extends the JMS store-and-forward service introduced
in WebLogic Server 9.0 to standalone JMS clients. Now JMS clients can reliably send
messages to server-side JMS destinations, even when the client cannot reach a
destination (for example, due to a temporary network connection failure). While disconnected from the server, messages sent by a JMS SAF client are stored locally on
the client file system and are forwarded to server-side JMS destinations when the
client reconnects. See Reliably Sending Messages Using the JMS SAF Client.
Which two elements of the Java Enterprise Application Archive are required?
* 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.
