1z0-599 Sample Questions Answers

This document provides a complete reference for the elements in 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.

The Clone WebLogic Domain option launches a wizard that enables you to clone a WebLogic Domain from an existing reference domain that is already discovered with Cloud Control. It allows you to clone the Middleware Home and its binaries, and the domain configuration.

*If you selected the Cloning a WebLogic Domain option, the Middleware Provisioning: Domain Configuration page appears. This page contains a set of links to several pages where you can enter the properties that are most likely to be reconfigured like domain name, listen addresses for the administration server and managed servers, Node Manager/Machine configuration, and JDBC data sources.

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:

Note:

*

* When to Use Work Managers

Following are guildelines to help you determine when you might want to use Work Managers to customize thread management:

/ The default fair share is not sufficient.

This usually ocurrs in situations where one application needs to be given higher priority over another.

/ A response time goal is required.

/ A minimum thread constraint needs to be specified to avoid server deadlock

Note:

* iAS: Oracle Application Server

* Oracle WebLogic Server SmartUpgrade is one several Oracle software tools that can help you upgrade your entire Oracle Application Server or Oracle WebLogic Server environment to Oracle Fusion Middleware 11g.

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

Oracle WebLogic Server Logging Last Resource (LLR) An additional option for XA transactions is Oracle WebLogic Server’s Logging Last Resource (LLR) transaction optimization through JDBC data sources. LLR is a performance enhancement option that enables one non-XA resource to participate in a distributed transaction with the same ACID guarantee asXA. In a distributed transaction with an LLR participant, the Oracle WebLogic Server transaction

An internal application may be configured to always use a minimum version of the same library. Applications that require no specific version can be configured to use the latest version of the library.

Note:

* Specification-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the specification version of the shared Java EE library. Referencing applications can optionally specify a required Specification-Version for a library; if the exact specification version is not available, deployment of the referencing application fails.

The Specification-Version uses the following format:

Major/minor version format, with version and revision numbers separated by periods (such as "9.0.1.1")

Referencing applications can be configured to require either an exact version of the shared Java EE library, a minimum version, or the latest available version.

* Implementation-Version (a manifest Attributes for Java EE Libraries)

An optional String value that defines the code implementation version of the shared

Java EE library. You can provide an Implementation-Version only if you have

also defined a Specification-Version.

* Extension-Name (a manifest Attributes for Java EE Libraries)

An optional string value that identifies the name of the shared Java EE library. Referencing applications must use the exact Extension-Name value to use the library.

As a best practice, always specify an Extension-Name value for each library. If you do not specify an extension name, one is derived from the deployment name of the library. Default deployment names are different for archive and exploded archive deployments, and they can be set to arbitrary values in the deployment command.

* After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console.

WAN HTTP Session State Replication

Resources in a wide area network (WAN) are frequently spread across separate geographical regions. In addition to requiring network traffic to cross long distances, these resources are often separated by multiple routers and other network bottle necks. Network communication in a WAN generally has higher latency and slower interconnect.

Slower network performance within a WAN makes it difficult to use a synchronous replication mechanism like the one used within a MAN. WebLogic Server provides failover across clusters in WAN by using an asynchronous data replication scheme.

Note:

HTTP Session State Replication

Weblogic Server uses two methods for replicating HTTP session state across clusters:

in-memory replication

* Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

* JDBC-based persistence

In JDBC-based persistence, WebLogic Server maintains the HTTP session state of a servlet or JSP using file-based or JDBC-based persistence.

JDBC-based persistence is also used for HTTP session state replication within a Wide Area Network (WAN). 

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

B: WLST enables you to create a new domain or update an existing domain without connecting to a running WebLogic Server (that is, using WLST offline)—supporting the same functionality as the Configuration Wizard.

E: With WLST you can

Creating a Domain (Offline)

Updating an Existing Domain (Offline)

Creating a Domain Template (Offline)

Exporting Diagnostic Data (Offline)

Stepping Through a Sample Script: Creating a Domain Using WLST Offline

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.

A: Oracle Smart Update is a standalone Java application that is automatically installed in the Middleware home utils/bsu directory. Smart Update simplifies the process of applying patches to your WebLogic Server installation. When support makes a patch available for an installed version of WebLogic Server, you download the patch from My Oracle Support and then use Oracle Smart Update to apply it to your installation. Smart Update organizes all available updates for you, and has several features that allow a great deal of customizing in the way various patches are applied and managed in your environment.

B: As part of a new Enterprise Manager system, the installation wizard does the following:

* Oracle My Oracle Support Management Plug-In

etc.

C: Applying patch from server start script:

After downloading the patch (jar file) follow the below steps:

- Stop your server.

- Then take the path of the folder which has the CRxxxxxx_xxxmpx.jar file and copy it in the CLASSPATH of setDomainEnv.cmd which is in

(/user_projects/domains//bin/setDomainEnv.cmd)

For example, the script would look something like this:

set CLASSPATH=%PRE_CLASSPATH%;%WEBLOGIC_CLASSPATH%; C:\extra\my_projects\doc\CR\CR218639_920mp3.jar;C:\extra\my_projects\doc \CR\ CR360676_920mp3.jar;C:\extra\my_projects\doc\CR\CR367966_920mp3.jar; C:\extra\my_projects\doc\CR\CR368155_920mp3.jar;C:\extra\my_projects\doc\CR\CR370311_920mp3.jar

- Re-start your server.

- You should see the patch applied in the stdout file.

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.

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

Using the Domain Template Builder to Create Domain Templates

To create a domain, start the Configuration Wizard and choose a domain configuration template.

A: a WebLogic domain can be created by using the Configuration Wizard in graphical mode.

B: WLST enables you to create a new domain or update an existing domain

D: A domain template is a JAR file that contains domain configuration documents, applications, security data, startup scripts, and other information needed to create a domain.

JMS queue    A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary to what the name queue suggests, messages have to be delivered in the order sent A JMS queue only guarantees that each message is processed only once.

WebLogic Server uses the standard J2EE web.xml deployment descriptor for defining a Web Application. Some applications also require the WebLogic-specific deployment descriptor, weblogic.xml. You use these deployment descriptors to define components and operating parameters for a Web Application. Deployment descriptors are standard text files, formatted using XML notation. You package them in the Web Application.

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)

Support Workbench is a feature where, on identification of a problem, targeted diagnostics data is dumped in a well-known format and location, for further analysis by administrators, Oracle Support and development. In case of Support Workbench for FMW, this feature works for Weblogic Server Targets.