1z0-102 Oracle Weblogic Server 11g: System Administration I Questions and Answers

The WEB-INF directory contains the deployment descriptors for the Web application (web.xml (C) and weblogic.xml) and two subdirectories for storing compiled Java classes (B) and library JAR files. These subdirectories are respectively named classes and lib. JSP taglibs are stored in the WEB-INF directory at the top level of the staging directory. The Java classes include servlets, helper classes and, if desired, precompiled JSPs.

A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, SAF agents, or a cluster).

For example, you can group a connection factory with stand-alone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.

A: All servers in a domain run either in development mode or production mode.

F: If you want to create a new domain, you can use the Configuration Wizard (or WLST or Unpack command).

A: Steps to Deploy Application using Administration Console

• Start the Admin Server and Managed Server.
• Navigate to Administration console https://localhost:7001/console and login.
• Navigate to Domain Environment –> Deployments. Lock the console.
• Etc.

E: To enable the administration port for your domain:

• If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
• Shutdown all Managed Servers in the domain. You cannot enable the administration port dynamically on a Managed Server.
• Ensure that all servers in the domain are properly configured to use SSL.
• In the left pane of the Console, under Domain Structure, select the domain name.
• Select Configuration > General and select the Enable Administration Port check box to enable the SSL administration port for this domain.
• In the Administration Port field, enter the SSL port number that server instances in the domain use as the administration port. You can override an individual server instance's administration port assignment on the Advanced options portion of the Configuration: General page for the server instance.
• Click Save.
• To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Note: If you want to use the Administration Console to make configuration changes, you must first click the Lock & Edit button in the Change Center. When you click Lock & Edit, you obtain a lock on the editable hierarchy of Configuration MBeans for all servers in the domain (the edit tree).

As you make configuration changes using the Administration Console, you click Save (or in some cases Finish) on the appropriate pages. This does not cause the changes to take effect immediately; instead, when you click Save, you are saving the change to the edit tree and to the DOMAIN_NAME/pending/config.xml file and related configuration files. The changes take effect when you click Activate Changes in the Change Center. At that point, the configuration changes are distributed to each of the servers in the domain. If the changes are acceptable to each of the servers, then they take effect. (Note, however, that some changes require a server to be restarted.) If any server cannot accept a change, then all of the changes are rolled back from all of the servers in the domain. The changes are left in a pending state; you can then either edit the pending changes to resolve the problem or revert the pending changes.

B: When in-memory replication is enabled for a web application, WebLogic Server copies session state from one server in the cluster (primary) to one other server in the same cluster (secondary). The replica on the secondary server is kept up-to-date so that it may be used if the primary server fails.

E: To utilize in-memory replication for HTTP session states, you must access the WebLogic Server cluster using either a collection of Web servers with identically configured WebLogic proxy plug-ins, or load balancing hardware.

If you choose to use load balancing hardware instead of a proxy plug-in, it must support a compatible passive or active cookie persistence mechanism, and SSL persistence.

Note 1: In its default configuration, WebLogic Server uses client-side cookies to keep track of the primary and secondary server that host the client's servlet session state. If client browsers have disabled cookie usage, WebLogic Server can also keep track of primary and secondary servers using URL rewriting. With URL rewriting, both locations of the client session state are embedded into the URLs passed between the client and proxy server. To support this feature, you must ensure that URL rewriting is enabled on the WebLogic Server cluster.

Note 2: To support automatic failover for servlet and JSP HTTP session states, WebLogic Server replicates the session state in memory. WebLogic 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. The process of copying a session state from one server instance to another is called in-memory replication.

A: The embedded LDAP server contains user, group, group membership, security role, security policy, and credential map information.

C: The credential (usually a password) used to connect to the embedded LDAP server. If this password has not been set, WebLogic Server generates a password at startup, initializes the attribute, and saves the configuration to the config.xml file. If you want to connect to the embedded LDAP server using an external LDAP browser and the embedded LDAP administrator account (cn=Admin), change this attribute from the generated value.

E: You can use either the WebLogic Auditing provider or a custom Auditing provider in a security realm. Although an Auditing provider is configured per security realm, each server writes auditing data to its own log file in the server directory. By default, all auditing information recorded by the WebLogic Auditing provider is saved in the following file:

WL_HOME\yourdomain\yourserver\DefaultAuditRecorder.log.

By writing a custom Auditing provider, however, you can send the records containing audit information to any one of various output repositories, such as an LDAP server, database, or a simple file.

A, C: 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.

The Administration Console user interface includes the following panels.

* Breadcrumb Navigation

A series of links that show the path you have taken through the Administration Console's pages.

* Change Center

This is the starting point for using the Administration Console to make changes in WebLogic Server.

* Domain Structure

This panel is a tree you can use to navigate to pages in the Administration Console.

* How do I...

This panel includes links to online help tasks that are relevant to the current Console page.

* Tool Bar

The tool bar at the top of the Console.

* System Status

The System Status panel reports on the number of information, error, and warning messages that have been logged.

H: To help automate the task of configuring a domain, you can record your configuration actions in the Administration Console as a series of WebLogic Scripting Tool (WLST) commands and then use WLST to replay the commands.

For details see: Administration Console Online Help, Record WLST Scripts

They deploy command is used to deploy an application to a WebLogic Server instance. (A)

The deploy command returns a WLSTProgress object that you can access to check the status of the command. (E)

Note:

Syntax

deploy(appName, path, [targets], [stageMode], [planPath], [options])

* appName

Name of the application or standalone J2EE module to be deployed.

* targets

Optional. Comma-separated list of the target. Each target may be qualified with a J2EE module name (for example, module1@server1) enabling you to deploy different modules of the application archive on different servers. This argument defaults to the server to which WLST is currently connected.

Note 2: The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances and domains.

The Logging Last Resource option:

Enables a non-XA JDBC connection to participate in distributed transactions using the Logging Last Resource (LLR) transaction optimization. Recommended in place of Emulate Two-Phase Commit.

With this option, the transaction branch in which the connection is used is processed as the last resource in the transaction and is processed as a one-phase commit operation. The result of the operation is written in a log file on the resource itself, and the result determines the success or failure of the prepare phase of the transaction. This option offers some performance benefits with greater data safety than Emulate Two-Phase Commit.

Note: The transaction protocol for a JDBC data source determines how connections from the data source are handled during transaction processing. Transactions within a JDBC data source are either global (XA) and non-global (local).

A: WebLogic Server instances in a cluster communicate with one another using two basic network technologies:

* IP sockets, which are the conduits for peer-to-peer communication between clustered server instances.

* IP unicast or multicast, which server instances use to broadcast availability of services and heartbeats that indicate continued availability.

E: In many deployments, clustered server instances reside within a single subnet, ensuring multicast messages are reliably transmitted. However, you may want to distribute a WebLogic Server cluster across multiple subnets in a Wide Area Network (WAN) to increase redundancy, or to distribute clustered server instances over a larger geographical area.

A (not B): For any given WebLogic Server instance, you can override the default filter and create a log filter that causes a different set of messages to be written to the domain log file.

Note:

To create and configure a log filter:

• If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (not B) (see Use the Change Center).
• In the left pane of the Console, select the name of the active domain in the Domain Structure panel.
• On the Configuration: Log Filters page, click New.
• On the Create a New Log Filter page, enter a value to identify the filter in the Name field.
• Click Finish.

The new log filter appears in the Log Filters table.

• To configure a filter expression, in the Log Filters table, click the log filter name.
• On the Configuration page, in the Filter Expression text box, enter criteria for qualifying messages.

A filter expression defines simple filtering rules to limit the volume of log messages written to a particular log destination.

See D) below.

• Click Save.

The filter and filter expression are listed in the Log Filters table.

D: Log Filter Configuration

Use this page to define a custom log filter to restrict the set of messages that one or more servers send to a message destination, such as the domain log, standard out, server log file, or memory buffer of recent log events.

You can click Edit to type or paste in an expression directly, using WLDF Query Language syntax (see Related Topics, below); or you can click Add Expression to construct an expression by choosing items from lists.

Once you create a filter, you cannot change its name. Instead, you must create a new filter under a different name.

File persistence use less memory than in-memory replication, and does not need access rights to the company's database.

Note:

You use session persistence to permanently store data from an HTTP session object to enable failover and load balancing across a cluster of WebLogic Servers. When your applications stores data in an HTTP session object, the data must be serializable.

There are five different implementations of session persistence:

* Memory (single-server, non-replicated)

* File system persistence

* JDBC persistence

* Cookie-based session persistence

* In-memory replication (across a cluster)