1z0-599 Practice Exam Questions with Answers Oracle WebLogic Server 12c Essentials Certification

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 have to be delivered in the order sent A JMS queue only guarantees that each message is processed only once.

A: Oracle Smart Update is a standalone Java application that is automatically installed in the Middleware home utils/bsu directory. Smart Update simplifies the process of applying patches to your WebLogic Server installation. When support makes a patch available for an installed version of WebLogic Server, you download the patch from My Oracle Support and then use Oracle Smart Update to apply it to your installation. Smart Update organizes all available updates for you, and has several features that allow a great deal of customizing in the way various patches are applied and managed in your environment.

B: As part of a new Enterprise Manager system, the installation wizard does the following:

* Oracle My Oracle Support Management Plug-In

etc.

C: Applying patch from server start script:

After downloading the patch (jar file) follow the below steps:

- Stop your server.

- Then take the path of the folder which has the CRxxxxxx_xxxmpx.jar file and copy it in the CLASSPATH of setDomainEnv.cmd which is in

(/user_projects/domains//bin/setDomainEnv.cmd)

For example, the script would look something like this:

set CLASSPATH=%PRE_CLASSPATH%;%WEBLOGIC_CLASSPATH%; C:\extra\my_projects\doc\CR\CR218639_920mp3.jar;C:\extra\my_projects\doc \CR\ CR360676_920mp3.jar;C:\extra\my_projects\doc\CR\CR367966_920mp3.jar; C:\extra\my_projects\doc\CR\CR368155_920mp3.jar;C:\extra\my_projects\doc\CR\CR370311_920mp3.jar

- Re-start your server.

- You should see the patch applied in the stdout file.

Restrictions on Production Redeployment Updates

WebLogic Server can host a maximum of two different versions of an application at one time.

Note:

* When you redeploy a new version of an application, you cannot change:

An application's deployment targets

An application's security model

A Webapplicationspersistent store settings

To change any of the above features, you must first undeploy the active version of the application.

Incorrect:

* (not A)

Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability*to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application.

* (not C) Not dependant on whether the application is JRockit or Hotspot.

* (not E)

The production redeployment strategy is supported for:

Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).

Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.

All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.

Production redeployment is not supported for:

Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.

Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.

Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.

Using FastSwap Deployment to Minimize Redeployment

Java EE 5 introduces the ability to redefine a class at runtime without dropping its ClassLoader or abandoning existing instances. This allows containers to reload altered classes without disturbing running applications, vastly speeding up iterative development cycles and improving the overall development and testing experiences. The usefulness of the Java EE dynamic class redefinition is severely curtailed, however, by the restriction that the shape of the class – its declared fields and methods – cannot change. The purpose of FastSwap is to remove this restriction in WLS, allowing the dynamic redefinition of classes with new shapes to facilitate iterative development.

With FastSwap, Java classes are redefined in-place without reloading the ClassLoader, thereby having the decided advantage of fast turnaround times. This means that you do not have to wait for an application to redeploy and then navigate back to wherever you were in the Web page flow. Instead, you can make your changes, auto compile, and then see the effects immediately.

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.

Note:

You can configure a JDBC TLOG store to persist transaction logs to a database, which provides the following benefits:

* Leverages replication and HA characteristics of the underlying database.

* Simplifies disaster recovery by allowing the easy synchronization of the state of the database and TLOGs.

* Improved Transaction Recovery service migration as the transaction logs to do not need to be migrated (copied) to a new location.

* You can configure a JDBC TLOG store to persist transaction logs to a database, which allows you to leverage replication and HA characteristics of the underlying database, simplify disaster recovery, and improve Transaction Recovery service migration.

incorrect:

not B: Read-only, One-phase Commit Optimization requires Oracle DB 11.1.0.7.3PSU or above.