1z0-599 Exam Dumps - Oracle Application Server Questions and Answers

Session Affinity Policy

Web applications where a user session has back-to-back online transaction processing (OLTP) have better performance when repeated operations against the same set of records are processed by the same RAC instance. Business applications such as online shopping and online banking are typical examples of this pattern.

A GridLink data source uses the Session Affinity policy to ensure all the data base operations for a web session, including transactions, are directed to the same Oracle RAC instance of a RAC cluster.

Note:

The context is stored in the HTTP session. It is up to the application how windows (within a browser or across browsers) are mapped to HTTP sessions.

Note 2:

* GridLink Affinity

WebLogic Server GridLink affinity policies are designed to improve application performance by maximizing RAC cluster utilization. A GridLink data source monitors RAC load balancing advisories (LBAs) using the AffEnabled attribute to determine if RAC affinity is enabled for a RAC cluster. The first connection request is load balanced using Runtime Connection Load-Balancing (RCLB) and is assigned an Affinity context. All subsequent connection requests are routed to the same Oracle RAC instance using the Affinity context of the first connection until the session ends or the transaction completes.

* Session Affinity

Reference; Configuring and Managing JDBC Data Sources for Oracle Weblogic server 12c, Using GridLink Data Sources

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

* Oracle GoldenGate

Oracle GoldenGate is Oracle’s strategic product for data distribution and data integration. It is a highperformance software application that uses log-based bidirectional data replication for real-time capture, transformation, routing, and delivery of database transactions across heterogeneous systems.

Note:

* Oracle Active Data Guard

Oracle Active Data Guard 11g is an option of Oracle Database Enterprise Edition that extends basic Data Guard functionality. It allows a physical standby database to be open as read-only while changes are applied to it from the primary database. This increases performance and return on investment by offloading ad-hoc queries, Web-based access, reporting, and backups from the primary database while also providing disaster protection.

* Disaster recovery (DR) procedures ensure rapid recovery or continuation of a technology

infrastructure after a natural or human-induced disaster. Oracle WebLogic Server 12c supports

advanced disaster recovery and business continuity. Organizations can store transaction logs in an Oracle database instead of a file system, providing a highly available storage mechanism to improve the speed and reliability of disaster recovery operations. This permits them to utilize Oracle Active Data Guard or Oracle GoldenGate replication technology to move DR state information across data centers. Oracle’s enhanced DR architecture enables more effective recovery scenarios. Support for Oracle Exalogic and Oracle Exadata engineered systems ensures tremendous scalability for IT operations of any size.

* Oracle WebLogic Server 12c places transaction logs on the database tier to improve the speed, reliability and availability of disaster recovery operations.

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

Auto-deployment is intended for use with a single server target in a development environment.

Note:

* If auto-deployment is enabled, when an application is copied into the \autodeploy directory of the Administration Server, the Administration Server detects the presence of the new application and deploys it automatically (if the Administration Server is running). If WebLogic Server is not running when you copy the application to the \autodeploy directory, the application is deployed the next time the WebLogic Server Administration Server is started. Auto-deployment deploys only to the Administration Server.

* Limitations of Auto-Deployment

Auto-deployed applications are very convenient in a development environment, but there are some limitations:

There is no configuration in config.xml for an auto-deployed application. Therefore, in the Administration Console, there are no notes or target pages associated with an auto-deployed application because there is no backing configuration for that information.

You cannot associate an auto-deployed application with a deployment plan since auto-deployed applications do not support any configuration operations which would be reflected in a deployment plan.

You cannot set up security policies or roles for auto-deployed applications.

You cannot undeploy or redeploy auto-deployed applications using WebLogic Server tools.

Reference; Developing Applications for Oracle WebLogic Server 12c, Auto-Deploying Applications in Development Domains

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.

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.

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.

* WebLogic Server supports Fast Connection Failover, a Oracle feature which provides an application independent method to implement RAC event notifications, such a detection and cleanup of invalid connections, load balancing of available connections, and work redistribution on active RAC instances.

* A GridLink data source uses Fast Connection Failover and responds to Oracle RAC

events using ONS. This ensures that the connection pool in the GridLink data source

contains valid connections (including reserved connections) without the need to poll

and test connections