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.

A: A domain is the basic administration unit for WebLogic Server instances.

D: To define a WebLogic Server cluster there must be a domain:

Note: Before you start the Managed Servers in a domain, start the Administration Server. When you start a standalone or clustered Managed Server, it contacts the Administration Server for its configuration information. In this way, the Administration Server operates as the central control entity for the configuration of the entire domain.

C: auto deployment is not allowed in production mode only development mode.

Note 1:

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

To configure all servers in a domain to run in production mode:

1. 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, under Domain Structure, select the domain name.

2. Select Configuration > General and select the Production Mode check box.

3. Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.

4. Shut down any servers that are currently running.

5. Invoke the domain's startWebLogic script.

The Administration Server starts in the new mode.

6. If the domain contains Managed Servers, start the Managed Servers.

Result

As each Managed Server starts, it refers to the mode of the Administration Server to determine its runtime mode.

Note 2: Once you have changed to production mode, whether by using a start command argument, the Console, or WLST, you cannot change back to development mode without restarting the server.

By default auto deployment is turned off in Production Mode (however it can be later turned on).

Incorrect:

E: if you want to go back to development mode you must change the config.xml file and restart the admin server. The window shown below shows from developemnt to production NOT production to development is allowed.

This is in development mode and you can change to production mode but in production mode this attribute states the word true.

Node Manager security relies on a one-way SSL connection between the client and server.

A cluster must include at least one server.

A clustered is administered through an administration server, but the cluster consists of managed servers only.

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.

If you install the WebLogic Server Examples component, the default user weblogic is created that has permission to start and stop WebLogic Server. The default password is welcome1. If you change the password of the weblogic user, WebLogic Server does not automatically update this password in the boot.properties file, which is located in the DOMAIN_NAME/servers/AdminServer/security directory.

If you change the password for user weblogic, you can use either of the following workarounds so that you can continue to boot a WebLogic Server instance via that username and its new password:

* Remove the boot.properties file. Subsequently each time you start WebLogic Server, you are prompted for the username and password. The changed password for the weblogic user will be accepted.

* Modify the existing boot.properties file, changing the username and password as follows:

username=weblogic

password=welcome1

Subsequently during the server startup process, the boot.properties file is encrypted again.

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.

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.

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.

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.

Note: You can use the Administration Console to configure selected deployment descriptor element values for an EJB that is deployed as an exploded application.

To configure editable deployment descriptor values for an EJB that is deployed as an exploded application:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

2. In the left pane of the Administration Console, select Deployments.

3. In the right pane, click the desired EJB module.

4. Select the Configuration > General tab.

Selected deployment descriptor elements for the EJB are listed.

5. Enter new values for the elements you want change, and click Save.

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

D: In WebLogic Server, you configure database connectivity by adding data sources to your WebLogic domain. WebLogic JDBC data sources provide database access and database connection management. Each data source contains a pool of database connections that are created when the data source is created and at server startup. Applications reserve a database connection from the data source by looking up the data source on the JNDI tree or in the local application context and then calling getConnection().

E: Each data source that you configure contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications lookup a data source on the JNDI tree or in the local application context (java:comp/env), depending on how you configure and deploy the object, and then request a database connection. When finished with the connection, the application calls connection.close(), which returns the connection to the connection pool in the data source.

B: To proxy requests by path, use the Location block and the SetHandler statement.

When to use

Use to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use and . An exception is , which is an easy way to apply a configuration to the entire server.

For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, port, or query string may be included. For proxy requests, the URL to be matched is of the form scheme://servername/path, and you must include the prefix.

E: Add an IfModule block that defines one of the following:

For a non-clustered WebLogic Server instance:

The WebLogicHost and WebLogicPort parameters.

For a cluster of WebLogic Servers instances:

The WebLogicCluster parameter.

If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter.

For example:

WebLogicCluster w1s1.com:7001,w1s2.com:7001,w1s3.com:7001

Note #1: The ... section is used to mark directives that are conditional on the presence of a specific module. The directives within an section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.

The test in the section directive can be one of two forms:

module name

!module name

Note #2:

Directive

Description:Applies the enclosed directives only to matching URLs

Syntax: ...

Context:server config, virtual host

Status:Core

Module:core

The directive limits the scope of the enclosed directives by URL. It is similar to the directive, and starts a subsection which is terminated with a directive. sections are processed in the order they appear in the configuration file, after the sections and .htaccess files are read, and after the sections.

sections operate completely outside the filesystem. This has several consequences. Most importantly, directives should not be used to control access to filesystem locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented.

MS Connection Factory: Configuration: Default Delivery

Use this page to define the default delivery configuration parameters for this JMS connection factory, such as the default delivery mode, default time to live, etc.

B: Go to Start Menu->All programs->weblogic10gR3->Tools->Domain Template Builder

D: The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.F: 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.

Incorrect answer: