1z0-599 Practice Test

JNDI

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.

the WEB-INF subdirectory for a WAR file

the META-INF subdirectory for an EAR file, or EJB-JAR

 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 METAINF/
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

weblogic-application.xml

The WebLogic Server-specific deployment descriptor weblogic.xml.
If your Web application does not contain a weblogic.xml deployment descriptor, WebLogic
Server automatically selects the default values of the deployment descriptor elements.
Note:
A Web archive (WAR file) contains the files that make up a Web application. A WAR file is
deployed as a unit on one or more WebLogic Server instances. 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.
Reference: weblogic.xml Deployment Descriptor Elements

Configure a Work Manager for premium users with a higher fair-share-request-class.

fair-share-request-class—Specifies the average thread-use time required to
process requests. The default fair share value is 50.
For example, assume that WebLogic Server is running two modules. The Work Manager
for ModuleA specifies a fair-share-request-class of 80 and the Work Manager
for ModuleB specifies a fair-share-request-class of 20.
During a period of sufficient demand, with a steady stream of requests for each module
such that the number requests exceed the number of threads, WebLogic Server will
allocate 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.
* Example:
<work-manager>
<name>lowpriority_workmanager</name>
<fair-share-request-class>
<name>low_priority</name>
<fair-share>10</fair-share>
</fair-share-request-class>
</work-manager>
<work-manager>
<name>highpriority_workmanager</name>
<fair-share-request-class>
<name>high_priority</name>
<fair-share>100</fair-share>
</fair-share-request-class>
</work-manager>
Note:
* A request class expresses a scheduling guideline that WebLogic Server uses to allocate
threads to requests. Request classes help ensure that high priority work is scheduled
before less important work, even if the high priority work is submitted after the lower priority
work.
Incorrect:
Not C: response-time-request-class—Specifies a response time goal in milliseconds
Response time goals are not applied to individual requests. Instead, WebLogic Server
computes a tolerable waiting time for requests with that class by subtracting the observed
average thread use time from the response time goal, and schedules requests so that the
average wait for requests with the class is proportional to its tolerable waiting time.
Not A, D: Not related to thread constraints.
For example, assume that WebLogic Server is running two modules. The Work Manager
for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB
specifies a fair-share-request-class of 20.

SAF Client

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.
Reference: Programming JMS for Oracle WebLogic Server, Using WebLogic JMS SAF
Client