Oracle 1z0-102 Oracle Weblogic Server 11g: System Administration I Exam Practice Test

A: The Configure the Administration Server window prompts you to define the configuration information for the Administration Server, including:

Administration Server name

Listen address

Nonsecure and secure (optional) listen ports

B: The Configure Managed Servers window prompts you to define the configuration information for one or more Managed Servers, including:

Managed Server name

Listen address

Nonsecure and secure (optional) listen ports

E: The Configure Clusters window prompts you to define the configuration information for one or more clusters, including:

Cluster name

Multicast address and port

Cluster address that identifies the Managed Servers in the cluster

Frontend host if you are using a proxy server or a firewall.

Frontend HTTP port if you are using a proxy server or a firewall.

The pool size has decreased from a maximum 20 to 10.

The workload has been 20. Now it is 10. The workload was higher.

Note: Current Capacity: The current count of JDBC connections in the connection pool in the data source.

Current Capacity High Count: Highest number of database connections available or in use (current capacity) in this instance of the data source since the data source was deployed.

Note:

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 WebLogic domain can be composed of a number of WebLogic instances, and

several of these servers may be grouped into clusters. For instance, you could set up a

cluster of WebLogic servers, all of which host your web application and related

resources. This cluster of servers could be fronted by a load balancer that distributes

requests evenly across all the members of the cluster. The load balancer could itself be

another WebLogic instance. All server instances must belong to the same WebLogic

domain. Thus, a WebLogic cluster is a group of servers working together with services,

such as clustered JNDI, to provide support for failover and load balancing. A domain

may in turn have a number of WebLogic instances, several groups of which can be

placed into different clusters.

-targetstarget_list (for the redeploy command) is not specified here.

It is used to specify the targets on which to distribute, deploy, or redeploy the application or module.

If you do not specify a target list with the -deploy command, the target defaults to:

* the Administration Server instance for new deployments (not the case here)

* the application's current targets for deployed applications (the case in this scenario)

Note:

Syntax:

java [SSL Arguments] weblogic.Deployer [Connection Arguments]

[User Credentials Arguments] COMMAND-NAME command-options

[Common Arguments]

Connection Arguments

The -adminurl value must specify the listen address and listen port of the Administration Server.

-usernameusername. The Administrator username. If you supply the -username option but you do not supply a corresponding -password option, weblogic.Deployer prompts you for the password.

-redeploy.redeploys a running application or part of a running application.

-name deployment_name. Specifies the deployment name of a deployed application or module. The -name option can be omitted, in which case the name is taken from the -source fileargument.

Note: weblogic.Deployer is a Java-based deployment tool that provides a command-line interface to the WebLogic Server deployment API. weblogic.Deployer is intended for administrators and developers who want to perform interactive, command-line based deployment operations.

A: If an object is clustered, failover and load balancing for that object is available.

In a WebLogic Server cluster, application processing can continue when a server instance fails. You “cluster” application components by deploying them on multiple server instances in the cluster—so, if a server instance on which a component is running fails, another server instance on which that component is deployed can continue application processing.

The choice to cluster WebLogic Server instances is transparent to application developers and clients.

B: A clustered application or application component is one that is available on multiple WebLogic Server instances in a cluster. If an object is clustered, failover and load balancing for that object is available. Deploy objects homogeneously—to every server instance in your cluster—to simplify cluster administration, maintenance, and troubleshooting.

Web applications can consist of different types of objects, including Enterprise Java Beans (EJBs), servlets, and Java Server Pages (JSPs).

Note: Load balancing and failover for EJBs and RMI objects is handled using replica-aware stubs, which can locate instances of the object throughout the cluster.

C: Cluster Multicast Address and Port

Identify the address and port you will dedicate to multicast communications for your cluster.

B: For efficient security management, BEA recommends adding users to groups. A group is a collection of users who usually have something in common, such as working in the same department in a company.

C: Example of group nesting:

Every user is a member of the everyone group.

The users group is nested within the everyone group.

Note: Security Providers - are modules that provide security service to application to protect Weblogic resource. Types of security providers in WebLogic Server are

Authentication Provider, Authorization Provider, Auditing Providers, Credential Mapping Provider, Identity Assertion Provider, Principal Validation Provider, Adjudication Providers, Role Mapping Providers, Certificate Lookup and Validation Providers, Keystore Providers and Realm Adapter providers

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.

C: Choose the Startup Mode

Specify the startup mode for your domain.

Either Development or Production

D: The Create WebLogic Domain window prompts you to specify the name and pathname for the domain, and initiate its creation.

E: The Configure Administrator Username and Password window prompts you to specify a username and password to be used for starting the Administration Server.

B: Attribute label: Cluster

The cluster to which this server belongs. If set, the server will listen for cluster multicast events.

This is a configurable attribute.

C: Attribute label: Machine

The WebLogic Server host computer (machine) on which this server is meant to run.

This is a configurable attribute.

D: Server --> Configuration --> Cluster

A WebLogic Server cluster is a group of servers that work together to provide a more scalable, more reliable application platform than a single server.

Use this page to specify a server's primary and secondary replication group, cluster weight, and the interface address used to handle multicast traffic.

Attribute label: Replication Group

Description: Defines preferred clustered instances considered for hosting replicas of the primary HTTP session states created on the server.

C: To assign server instances to a cluster:

• If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit .
• In the left pane of the Console, expand Environment and select Clusters.
• Select the cluster to which you want to assign servers.
• Select Servers and click Add.
• To add an existing server to a cluster:

Note: You cannot change the cluster of the Administation Server using the Administration Console. You cannot change the cluster or machine of a running server.

• uk.co.certification.simulator.questionpool.PList@5bf1db00
• To create a new server as part of a cluster:

The new server appears in the list of servers and is added as a member of the current cluster.

• To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Incorrect answer:

Not A. See screenshot below.

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

Administrator machine:

The Choose the Administration Server window prompts you to designate a server as the Administration Server. This window is displayed automatically only if the selected template includes multiple servers that are not assigned to clusters.

• From the list of Available Servers, select the server that you want to designate as the Administration Server. The Administration Server cannot be assigned to a cluster.

To choose the Administration Server:The Server Details area displays detailed information about the selected server. By default, the currently assigned Administration Server is selected.

• Select Next to proceed to the next configuration window.

The Configure the Administration Server and Configure Managed Server(s) windows are updated to reflect your changes.

Managed machine:

The minimum requirement for your domain is a single Administration Server on a single machine. In addition, however, you have the option of configuring other resources to be managed by the Administration Server and distributing them across multiple machines. Specifically, you can:

* Add, change, or delete Managed Servers

* Add, change, or delete clusters

* Group Managed Servers into clusters, or change current groupings

* Assign servers to machines, or change current assignments

Note: The Managed Servers, Clusters, and Machines Options window prompts you to specify whether you want to distribute your WebLogic configuration across Managed Servers, clusters, and physical machines

Note 2:

The Configure Managed Servers window prompts you to provide the configuration information for one or more Managed Servers. Production environments typically deploy one or more Managed Servers, in addition to the Administration Server, to host enterprise applications.

D: You were able to log in to the web application that is deployed through WebLogic.

In WebLogic Server, Authentication providers are used to prove the identity of users or system processes.

This implies that your account exists in an authentication provider.

E: Extra security is needed to use the publish link. This could be explained by a security policy attached the publish Link URL.

MedRec-Spring is not installed by default when you install WebLogic Server. You must choose Custom installation, then select Server Examples from the Choose Products and Component page.

Note: MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.

MedRec demonstrates WebLogic Server and Java EE features, and highlights Oracle-recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Server. A Spring version of the application is accessible from the WL_HOME\samples\domains\medrec-spring directory.