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

The WLST life cycle shutdown command gracefully shuts down a running server instance or cluster.

B: The Administration Server uses the machine definition in conjunction with the Node Manager application to start remote WebLogic Server instances.

E: By default, WebLogic Server attempts to create session state replicas on a different machine than the one that hosts the primary session state. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered servers to be used for storing session state replicas.

Using the WebLogic Server Console, you can define unique machine names that will host individual server instances. These machine names can be associated with new WebLogic Server instances to identify where the servers reside in your system.

Machine names are generally used to indicate servers that run on the same machine.

Note #1: If your EJBs will run on a WebLogic Server cluster, Oracle recommends that you deploy them homogeneously—to each Managed Server in the cluster. Alternatively, you can deploy an EJB to only to a single server in the cluster (that is, “pin” a module to a server). This type of deployment is less common, and should be used only in special circumstances where pinned services are required.

Note #2: When you deploy an EJB, you specify the servers and clusters to which the EJB deployment is targeted. After you have deployed an EJB, you can update the servers and clusters to which it is targeted.

To set target servers and clusters for a deployed EJB:

• If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
• In the left pane of the Administration Console, select Deployments.

The right pane lists the EJBs and other modules that you have deployed, or tried to deploy.

• In the right pane, click the desired EJB.
• Select the Targets tab.

Servers and clusters in the domain are displayed.

• Select the check box next to the individual servers and/or clusters to which you wish to deploy the EJB and click Save.

By default, the Administration Console deploys an EJB to all server instances in the cluster (the "All servers in the cluster" option). To deploy the EJB to selected servers in a cluster, select "Part of the cluster", and then select the individual server instances to which you want to deploy the EJB.

• To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart

B:

A reference to a shared Java EE library. Enclose all other elements within library-ref.

Note: A Java EE application can reference a registered shared Java EE library using entries in the application’s weblogic-application.xml deployment descriptor.

Elements include:

library-ref

library-name

D:

Specifies the Work Manager that is associated with the application.

Note: The weblogic-application.xml file is the BEA WebLogic Server-specific deployment descriptor extension for the application.xml deployment descriptor from Sun Microsystems. This is where you configure features such as shared Java EE libraries referenced in the application and EJB caching.

The file is located in the META-INF subdirectory of the application archive.

You can configure WebLogic Server to make backup copies of the configuration files. This facilitates recovery in cases where configuration changes need to be reversed or the unlikely case that configuration files become corrupted. When the Administration Server starts up, it saves a JAR file named config-booted.jar that contains the configuration files. When you make changes to the configuration files, the old files are saved in the configArchive directory under the domain directory, in a JAR file with a sequentially-numbered name like config-1.jar.

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

By default, when you start a server instance in production mode, the server rotates its local log file whenever the file grows to 5000 kilobytes in size. It does not rotate the local server log file when you start the server.

You can change these default settings for log file rotation. For example, you can change the file size at which the server rotates the log file or you can configure a server to rotate log files based on a time interval. You can also specify the maximum number of rotated files that can accumulate. After the number of log files reaches this number, subsequent file rotations delete the oldest log file and create a new log file with the latest suffix.

The backup of the embedded LDAP server is enabled for a domain at a time. See step 2) in Note below.

In order for a cluster to provide high availability it must be able to recover from service failures.

In clusters that utilize Web servers with WebLogic proxy plug-ins, the proxy plug-in handles failover transparently to the client. If a server fails, the plug-in locates the replicated HTTP session state on a secondary server and redirects the client's request accordingly.

A: If necessary, create a JMS server to target the JMS module.

F: Target the JMS Server to a weblogic server

Note: The major components of the WebLogic JMS Server architecture:

* JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

* JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jms.xsd schema.

* Client JMS applications that either produce messages to destinations or consume messages from destinations.

* JNDI (Java Naming and Directory Interface), which provides a resource lookup facility. JMS resources such as connection factories and destinations are configured with a JNDI name. The runtime implementations of these resources are then bound into JNDI using the given names.

* WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

B: The administration server must be running.

Note: A WebLogic Server administration domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain.

D:

Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.

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.