Cloud Application Foundation 1z0-102 Syllabus Exam Questions Answers

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.

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.

To Deploy the EAR File to the Production Server

See step 8 below.

Open the WebLogic Server console for the target server running in production mode.

• On the left-hand side Change Center pane, click Lock & Edit.
• On the left-hand side Domain Structure pane, click Deployments.
• On the right-hand content pane, click Install.Browse to the directory where the EAR file resides, mark the radio button next to the EAR file you want to deploy, and click Next.
• Confirm that the radio button next to Install this deployment as an application is marked and click Next.
• Click Finish.
• On the left-hand side Change Center pane, click Activate Changes.
• On the right-hand content pane, mark the radio button next to the EAR just deployed.
• Click Start to view the dropdown list and select Servicing all requests.
• In the content pane of the new page, click Yes.

Although running Node Manager as an operating system service is recommended, you can also start Node Manager manually at the command prompt or with a script.

Use startNodeManager.cmd on Windows systems and startNodeManager.sh on UNIX systems.