Pass the Oracle Application Server 1z0-599 Questions and answers with CertsForce

A, B: With Active GridLink for RAC, WebLogic instances are isolated from RAC configuration changes, and DBAs only need to contend with a single data source rather than multiple data sources.

D: Active GridLink for RAC distributes work based on different backend node capacities, automatically detecting and adapting to overworked nodes and hangs. It enables smart load balancing across RAC nodes. This makes it easier to route traffic around node failures, enhancing availability and performance.

A:

* Troubleshooting Slow Response Time from the Client and Low Database Usage

These symptoms are usually caused by a bottleneck upstream of the database, perhaps in the JDBC connectionpooling. Monitor the active JDBC connections in the WebLogic Console and watch for excessive waiters and wait times; increase the pool size, if necessary.

* Attribute: Maximum Capacity

Maximum number of physical database connections that this connection pool can contain. Different JDBC Drivers and database servers may limit the number of possible physical connections.

C: Attribute: Statement Cache Size

The algorithm used to maintain the statement cache:

LRU - After the statementCacheSize is met, the Least Recently Used statement is removed when a new statement is used.

Fixed - The first statementCacheSize number of statements is stored and stay fixed in the cache. No new statements are cached unless the cache is manually cleared.

E: If the queue appears starved but adding execute threads does not improve performance,

there may be resource contention. Because CPU utilization is low, the threads are probably

spending much of their time waiting for some resource, quite often a database connection.

Use the JDBC monitoring facilities in the console to check for high levels of waiters or long

wait times. Adding connections to the JDBC connection pool may be all that is required to

fix the problem.

Note:

* If you had a JDBC connection pool where the Initial Capacity and Maximum Capacity attributes were different, you might want to create a gauge monitor to monitor the maximum and minimum number of connections.

By setting the Threshold Low value to be one less than the Initial Capacity, your gauge monitor trapcould monitor the ActiveConnectionsCurrentCount attribute of the JDBCDataSourceRuntime MBean and alert you whenever the number of active connections are less than the Initial Capacity (which might indicate database connectivity problems).

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

When an application that references a shared library or package is deployed, WebLogic Server checks the names and version string requirements against the libraries registered with the server. If an exact match for a library or package name is not found, or if the version requirements are not met, the application deployment fails.

If WebLogic Server finds a name and version string match for all of the libraries referenced in the application, the server adds the libraries' classes to the classpath of the referencing application and merges deployment descriptors from both the application and libraries in memory. The resulting deployed application appears as if the referenced libraries were bundled with the application itself.

Note:

As a best practice, your development team should always include version string information for a library or optional package in the manifest file for the deployment. See Editing Manifest Entries for Shared Libraries in Developing Applications for Oracle WebLogic Server for more information.

If you are deploying a library or package that does not include version string information, you can specify it at the command line using one or both of the following options:

libspecver—Defines a specification version for the library or package.

libimplver—Specifies an implementation version for the library or package.

WebLogic Administrators typically use the Administration Console or the WebLogic Scripting Tool (WLST) to create and deploy (target) JDBC modules.

Note:

* (not A) Domain template—defines the full set of resources within a domain, including

infrastructure components, applications, services, security options, and general

environment and operating system options.

* Extension template—defines the applications and services that you can add to an

existing domain, including product component functionality and resources such as

JDBC or JMS.

* (not B)Each domain describes its configuration in an XML document that is located in the domain’s configuration directory. At run time, each WebLogic Server instance in a given domain creates an in-memory representation of the configuration described in this document.

The central configuration file for a domain is DOMAIN_NAME/config/config.xml. This file specifies the name of the domain and the configuration of each server instance, cluster, resource, and service in the domain. The file includes references to additional XML files that are stored in subdirectories of theDOMAIN_NAME/config directory. These included files are used to describe major subsystems of WebLogic Server.