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

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

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.

Note:

* Types of Security Roles: Global Roles and Scoped Roles

There are two types of security roles in WebLogic Server:

/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource

/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.

Incorrect:

Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gainingaccess to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

C: Message Unit-of-Order is a WebLogic Server value-added feature that enables a stand-alone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created.

D Transactions required for parallel processing.

Incorrect:

A: Many applications need an even more restricted notion of a group than provided by the Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic JMSprovides the Unit-of-Work (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, an JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete.

Note:

* WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names:

weblogic.jms.ConnectionFactory

weblogic.jms.XAConnectionFactory

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.

Note:

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

* In managing multiple servers, Node Manager uses multiple configuration files and outputs log files to multiple directories.

* nodemanager.domains

This file contains mappings between the names of domains managed by Node Manager and their corresponding directories.

* Node Manager in the WebLogic Server Environment

Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

Note:

* Rolling Upgrade is the process of upgrading a running WebLogic Server cluster with a patch, maintenance pack, or minor release without shutting down the entire cluster or domain. During the rolling upgrade of a cluster, each server in the cluster is individually upgraded and restarted while the other servers in the cluster continue to host your application.

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.

* When you create a data source using the Administration Console, the Administration Console automatically sets the Test Table Name attribute for a data source based on the DBMS that youselect. The Test Table Name attribute is used in connection testing which is optionally performed periodically or when you create or reserve a connection, depending on how you configure the testing options. For database tests to succeed, the database user used to create database connections in the data source must have access to the database table. If not, you should either grant access to the user (make this change in the DBMS) or change the Test Table Name attribute to the name of a table to which the user does have access (make this change in the WebLogic Server Administration Console).

* To manually test a connection from a data source, you can use the Test Data Source feature on the JDBC Data Source: Monitoring: Testing page in the Administration Console (see “ Test JDBC data sources”) or the testPool() method in the JDBCDataSourceRuntimMBean. To test a database connection from a data source, Test Reserved Connections must be enabled and Test Table Name must be defined in the data source configuration. Both are defined by default if you create the data source using the Administration Console.

When you test a data source, WebLogic Server reserves a connection, tests it using the query defined in Test Table Name, and then releases the connection.