1Z0-134 Practice Questions

Thank you for your visit.

When using automatic service migration, the Node Manager is required to get health monitoring

information about the member servers involved, as follows:

* Consensus leasing – Node Manager must be running on every machine hosting managed servers

within the cluster.

* Database leasing – Node Manager must be running on every machine hosting managed servers

within the cluster only if pre/post-migration scripts are defined. If pre/post-migrations are not

defined, then Node manager is not required.

Optionally, you can define parameters for Java Message Service (JMS) in the Extension Template. Optionally, you can customize the Java Database Connectivity (JDBC) settings in the Extension Template. You can review and modify, if desired, the list of applications to be included in your extension template.

A Coherence cluster can contain any number of managed Coherence servers. The servers can be

standalone managed servers or can be part of a WebLogic Server cluster that is associated with a

Coherence cluster.

* storage-disabled – a managed Coherence server that is not responsible for storing data and is used

to host Coherence applications (cache clients). A Coherence application GAR is packaged within an

EAR and deployed on storage-disabled managed Coherence servers.

* storage-enabled – a managed Coherence server that is responsible for storing data in the cluster.

Coherence applications are packaged as Grid ARchives (GAR) and deployed on storage-enabled

managed Coherence servers.

The pwd command displays the current location in the configuration or runtime bean hierarchy.

This command is useful when you have turned off the prompt display of the path information using

the prompt command.

:

:

One server instance in a cluster that contains migratable servers acts as the cluster master and

orchestrates the process of automatic server migration, in the event of failure.

Any Managed Server in a cluster can serve as the cluster master, whether it hosts pinned services or

not.

Note: Any server instance in the cluster can serve as the cluster master. When you start a cluster that

contains migratable servers, the first server to join the cluster becomes the cluster master and starts

up the cluster manager service. If a cluster does not include at least one migratable server, it does

not require a cluster master, and the cluster master service does not start up.

Note: WebLogic Server provides three different options for staging files: stage mode, nostage mode,

and external_stage mode.

* In stage mode, the Administration Server copies the deployment files from their original location

on the Administration Server machine to the staging directories of each target server.

* In nostage mode, the Administration Server does not copy the archive files from their source

location. Instead, each target server must access the archive files from a single source directory for

deployment. The staging directory of target servers is ignored for nostage deployments.

* External_stage mode is similar to stage mode, in that target servers deploy using local copies of the

deployment files. However, the Administration Server does not automatically copy the deployment

files to targeted servers in external_stage mode; instead, you must copy the files to the staging

directory of each target server before deployment.

A Node Manager client can be local or remote to the Node Managers with which it communicates.

You access either version of Node Manager—the Java version or the script-based (SSH) version—

from the following clients:

A: an administration server

B: WLST commands and scripts—WLST offline serves as a Node Manager command-line interface

that can run in the absence of a running Administration Server.