Most Recent Oracle 1Z0-599 Exam Questions & Answers

Note:

* A multi data source can be thought of as a pool of data sources. Multi data sources are best used for failover or load balancing between nodes of a highly available database system, such as redundant databases or Oracle Real Application Clusters (Oracle RAC).

* (not B) A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service, which may include multiple Oracle RAC clusters

* High Availability Storage Solutions

If you have applications that need access to persistent stores that reside on remote machines after the migration of a JMS server or JTA transaction log, then you should implement one of the following highly-available storage solutions:

/ File-based stores (default or custom)---Implement a hardware solution, such as a dual-ported SCSI disk or Storage Area Network (SAN) to make a file store available from shareable disks or remote machines.

/ JDBC-accessible stores---Configure a JDBC store or JDBC TLOG store and use JDBC to access this store, which can be on yet another server. Applications can then take advantage of any high-availability or failover solutions offered by your database vendor. In addition, JDBC stores support GridLink data sources and multi data sources, which provide failover between nodes of a highly available database system, such as Oracle Real Application Clusters (Oracle RAC).

http://my-java-planet.blogspot.com/2014/04/which-weblogic-optimization-allows-one.html

-DserverType={'wls' | 'wlx'}

Specifies the Server Type, which determines the set of services that are started in the server runtime.

The default is 'wls', which starts all WebLogic Server services, including EJB, JMS, Connector, Clustering, Deployment, and Management.

The 'wlx' option starts a server instance that excludes the following services, making for a lighter weight runtime footprint:

* (not D) Enterprise JavaBeans (EJB)

* (not B, not E) Java EE Connecter Architecture (JCA)

* (not C) Java Message Service (JMS)

A:

* The WEB-INF directory contains the deployment descriptors for the Web application (web.xml and weblogic.xml) and two subdirectories for storing compiled Java classes and library JAR files.

* Web Application - WEB-INF/web.xml ( WEB-INF/weblogic.xml )

The WEB-INF directory is a vital component of your web application. Web application wont run without it.It contains a heirarcy in which you'll find the necessary configuration information for your web application, and all the class files for your servlets and classes that are called up by your JSPs.

WEB-INF folder contains all the class files for your servlets and classes that are called up by your JSPs

B:

Enterprise Application - META-INF/application.xml (META-INF/weblogic-application.xml) and META-INF/ejb-jar.xml ( META-INF/weblogic-ejb-jar.xml )

Generally comprises of EJBs. Bussiness Tier of an application and EJB basically handels the Bussiness logic of application (distributed objects)

META-INF/application.xml containes Mappings and security roles etc.whereas META-INF/ejb-jar.xml containes ejb classes , session beans mapping etc.,

The META-INF directory is related to .jar files, It contains the manifest file which has list of jars.

A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml (The context root of a web application determines which URLs weblogic will delegate to your web application.

Note:

* Deployment descriptors are xml documents that describe runtime behaviour for the deployment unit. The XML file contains information such as the context root of the web application and the mapping of the portable names of an application's resources to the application Server's resources

. 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.