Oracle 1z0-599 - Oracle WebLogic Server 12c Essentials

The following principles encourage RESTful applications to be simple, lightweight, and fast:

* Resource identification through URI

* Uniform interface: Resources are manipulated using a fixed set of four create, read, update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource, which can be then deleted by using DELETE. GET retrieves the current state of a resource in some representation. POST transfers a new state onto a resource. See Responding to HTTP Methods and Requests for more information.

* Self-descriptive messages

* Stateful interactions through hyperlinks

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.

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.

JCA Adapter

This product is a wrapper to the WebLogic Tuxedo Connector (WTC) found as part of the WebLogic Server (WLS) product. WTC can only be used on WebLogic, but the JCA adapter allows deploying WTC capabilities on other Java Application Servers that support the Java EE JCA specification.

Note:

* Tuxedo (Transactions for Unix, Extended for Distributed Operations) is a middleware platform used to manage distributed transaction processing in distributed computing environments. Tuxedo is a transaction processing system or transaction-oriented middleware, or enterprise application server for a variety of systems and programming languages. Developed by AT&T in the 1980s, it became a software product of Oracle Corporation in 2008.

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:

lowpriority_workmanager

low_priority

10

highpriority_workmanager

high_priority

100

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.

Note:

* When you configure multiple Authentication providers, use the JAAS Control Flag for each provider to control how the Authentication providers are used in the login sequence.

 You can choose the following the JAAS Control Flag settings, among others:

REQUIRED—The Authentication provider is always called, and the user must always pass its authentication test. Regardless of whether authentication succeeds or fails, authentication still continues down the list of providers.

SUFFICIENT—The user is not required to pass the authentication test of the Authentication provider. If authentication succeeds, no subsequent Authentication providers are executed. If authentication fails, authentication continues down the list of providers.

OPTIONAL—The user is allowed to pass or fail the authentication test of this Authentication provider. However, if all Authentication providers configured in a security realm have the JAAS Control Flag set to OPTIONAL, the user must pass the authentication test of one of the configured providers.

* Example:

Setting the Order of Providers

Re-order the OAM Identity Asserter, OID Authenticator, and Default Authenticator by ensuring that the control flag for each authenticator is set as follows:

OAMAuthenticator (REQUIRED)

OracleInternetDirectoryAuthenticator (SUFFICIENT)

DefaultAuthenticator (SUFFICIENT)

wls-maven-plugin—Delivered in WebLogic Server 12c, provides enhanced

functionality to install, start and stop servers, create domains, execute WLST

scripts, and compile and deploy applications.

B: Java EE Enterprise Web Services is supported.

E: New or enhanced WebLogic 12c features include

JAVA EE 6 support all kinds of JEE6 specifications are implemented like :

JSF 2.0,Java Servlets 3.0 JPA 2.0 and EJB 3.1.

Managed Beans 1.0

F: WebLogic 12c also supports supports Java SE 7 (and Java SE 6).

Java language optimizations and Internationalization

Client and server support

SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security

Converged Java VM:JRockit and HotSpot are incorporated with the best features from both. Oracle’s Publisher Seminar 2011 during OOW

Incorrect:

not C: