Oracle 1z0-599 Oracle WebLogic Server 12c Essentials Exam Practice Test

A Node Manager process is not associated with a specific WebLogic domain but with a

machine. You can use the same Node Manager process to control server instances in

any WebLogic Server domain, as long as the server instances reside on the same

machine as the Node Manager process. Node Manager must run on each computer

that hosts WebLogic Server instances—whether Administration Server or Managed

Server—that you want to control with Node Manager.

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

Note:

Note:

* Persistent messages are saved in the persistent store on the sending side until they are successfully forwarded to and acknowledged by the receiving side.

Note:

* It is recommended that you shutdown WebLogic Server instances through the Administration Console.

* If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.

Using JNDI, a JMS client can obtain access to a JMS provider by first looking up a ConnectionFactory. The ConnectionFactory is used to create JMS connections, which can then be used for sending and receiving messages. Destination objects, which represent virtual channels (topics and queues) in JMS, are also obtained via JNDI and are used by the JMS client. The directory service can be configured by the system administrator to provide JMS administered objects so that the JMS clients don't need to use proprietary code to access a JMS provider.

Note:

* The Java Naming and Directory Interface (JNDI) is part of the Java platform, providing applications based on Java technology with a unified interface to multiple naming and directory services.

C: Message Unit-of-Order is a WebLogic Server value-added feature that enables a stand-alone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created.

D Transactions required for parallel processing.

Incorrect:

A: Many applications need an even more restricted notion of a group than provided by the Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic JMSprovides the Unit-of-Work (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, an JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete.

Note:

* WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names:

weblogic.jms.ConnectionFactory

weblogic.jms.XAConnectionFactory

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.

• 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 12cR1 + Oracle Coherence row.

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

* When you create a data source using the Administration Console, the Administration Console automatically sets the Test Table Name attribute for a data source based on the DBMS that youselect. The Test Table Name attribute is used in connection testing which is optionally performed periodically or when you create or reserve a connection, depending on how you configure the testing options. For database tests to succeed, the database user used to create database connections in the data source must have access to the database table. If not, you should either grant access to the user (make this change in the DBMS) or change the Test Table Name attribute to the name of a table to which the user does have access (make this change in the WebLogic Server Administration Console).

* To manually test a connection from a data source, you can use the Test Data Source feature on the JDBC Data Source: Monitoring: Testing page in the Administration Console (see “ Test JDBC data sources”) or the testPool() method in the JDBCDataSourceRuntimMBean. To test a database connection from a data source, Test Reserved Connections must be enabled and Test Table Name must be defined in the data source configuration. Both are defined by default if you create the data source using the Administration Console.

When you test a data source, WebLogic Server reserves a connection, tests it using the query defined in Test Table Name, and then releases the connection.