Free Practice Questions for Oracle 1z0-599 Exam

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.

* Built on top of Oracle Coherence (Coherence), Coherence*Web:

/ brings Coherence data grid's data scalability, availability, reliability, and performance to in-memory session management and storage.

/ can be deployed to many mainstream application servers such as Oracle GlassFish Server, Oracle WebLogic Server, IBM WebSphere, Tomcat, and so on

* Coherence*Web enables HTTP session sharing and management across different Web applications, domains, and heterogeneous application servers. Session data can be stored in data caches outside of the application server, thus freeing application server heap space and enabling server restarts without losing session data.

Use the Administration Console to:

* (A) Configure, start, and stop WebLogic Server instances

* Configure WebLogic Server clusters

* (D) Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS)

* Configure security parameters, including managing users, groups, and roles

* Configure and deploy your applications

* Monitor server and application performance

* View server and domain log files

* View application deployment descriptors

* (F) Edit selected run-time application deployment descriptor elements

* (B) Control (start, stop, and restart) standalone Coherence cache servers

* (B) Create and configure Coherence clusters

Incorrect:

Not C: The separate Domain Template Builder is used for creating Domain Templates.

The JRockit JVM is included in all Oracle WebLogic products – Oracle WebLogic Server Standard Edition, Oracle WebLogic Enterprise Edition, WebLogic Suite, and Oracle WebLogic Application Grid. JRockit will also be used across the Oracle Fusion Middleware and Oracle Applications product families, with the certification process happening over the coming months. For current status, see the certification matrices available from Oracle Metalink.

C: The saviour of having to type in the username and password each and every time that you start a server. A very useful little file to have, particularly if you have multiple managed servers.

By default, this appears in the Admin Servers security directory ($DOMAIN_HOME/servers/AdminServer/security) when a domain is created in development mode and is called boot.properties. The file is only created for the admin server, not for any additional servers; simply copying the security directory over is enough. The password is encrypted for the domain, so it can only be used for servers within that domain.

In production mode, the boot.properties file doesn’t exist.

D: Development mode enables a WebLogic Server instance to automatically deploy and update applications that are in the domain_name/autodeploy directory (where domain_name is the name of a WebLogic Server domain). Production mode disables the auto-deployment feature and prevents any applications you place in the autodeploy directory after you switch to production mode from being deployed.

Note:

* By default, a WebLogic Server domain runs in development mode.

* You can run a WebLogic Server domain in two different modes: development and production. Only development mode allows you use the auto-deployment feature

Note:

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.

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