A.

JMS Persistent Store

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.

D.

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

A.

the WEB-INF subdirectory for a WAR file

B.

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

D.

Use flag -version when redeploying the application. This will switch on the Side By Side
deployment feature and preserve existing sessions.

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 Web application's persistent 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.
Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c,
Redeploying Applications in a Production Environment

B.

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.

B.

You need to install and configure only one instance of Node Manager for all products,
regardless of the WebLogic version number.

Note:
* 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.
* In managing multiple servers, Node Manager uses multiple configuration files and outputs
log files to multiple directories.
* nodemanager.domains
This file contains mappings between the names of domains managed by Node Manager
and their corresponding directories.
* Node Manager in the WebLogic Server Environment

Description of Figure 2-1 follows
Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

C.

Oracle WebLogic Server clusters; Oracle Database RAC

The WebLogic Server JDBC subsystem has supported Oracle RAC since
WLS
version 8.1 SP5, originally developed for Oracle9i RAC. This support is based on a
particular type of data source configuration, called a multi data source. A multi data
source is a data source abstraction over one or more individual data sources. It
serves JDBC connections from each of the member data sources according to a
specified policy2. A RAC multi data source configuration requires that each
member data source obtain connections to a particular RAC instance, as illustrated
in the following diagram of a three-node RAC cluster configuration.

Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application
Clusters(RAC)

A.

Java

B.

C++

C.

NET