Download Oracle Weblogic Server 11g: System Administration I.1z0-102.TestKing.2018-08-24.60q.vcex

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 PortIdentify the address and port you will dedicate to multicast communications for your cluster. References:

D: When a Managed Server starts, it contacts the Administration Server to retrieve its configuration information. If a Managed Server is unable to connect to the specified Administration Server during startup, it can retrieve its configuration directly by reading a copy of the config.xml file and other files located on the Managed Server's own file system.E: One instance of WebLogic Server in each domain acts as an Administration Server. The Administration Server provides a central point for managing a WebLogic Server domain.F: For a typical production system, BEA recommends that you deploy your applications only on Managed Servers. This practice allows you to dedicate the Administration Server to configuration and monitoring of the domain, while one or more Managed Servers service your applications.References:

Node Manager enables you to perform these tasks:Start and stop remote Managed Servers. (A) Monitor the self-reported health of Managed Servers and automatically kill server instances whose health state is "failed". Automatically restart Managed Servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot. (D)

When you create a JDBC resource (data source or multi data source) using the Administration Console or using the WebLogic Scripting Tool (WLST), WebLogic Server creates a JDBC module in the config/jdbc subdirectory of the domain directory, and adds a reference to the module in the domain’s config.xml file. References:

To configure the migratable target servers for JMS-related service migration:If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center). In the Domain Structure tree, expand Environment, then select Migratable Targets. On the Summary of Migratable Targets page, click New. On the Create a new Migratable Target page:In Name, enter a name for the migratable target. In Cluster, select a configured cluster for the migratable target. References:

Servicing only administrative requests: Specifies that WebLogic Server make the application available in Administration Mode only.While in Administration mode, the application can be accessed only by internal clients through a configured Administration port. References:

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:If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center). In the left pane of the Administration Console, select Deployments. In the right pane, click the desired EJB module. Select the Configuration > General tab. Selected deployment descriptor elements for the EJB are listed. Enter new values for the elements you want change, and click Save. 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 References:

A: Each connection in a data source has its own individual cache of prepared and callable statements used on the connection. However, you configure statement cache options per data source. That is, the statement cache for each connection in a data source uses the statement cache options specified for the data source, but each connection caches it's own statements.E: When Test Connections On Reserve is enabled, when your application requests a connection from the data source, WebLogic Server tests the connection using the query specified in Test Table Name before giving the connection to the application.Testing reserved connections can cause a delay in satisfying connection requests, but it makes sure that the connection is viable when the application gets the connection. References:

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. References:

Applications look up the data source on the JNDI tree or in the local application context (B) and then reserve a database connection with the getConnection (E) method. Data sources and their connection pools provide connection management processes that help keep your system running and performant. B: JNDI Name - Enter the JNDI path to where this JDBC data source will be bound. Applications look up the data source on the JNDI tree by this name when reserving a connection.Note: If you've done any work with JDBC DataSources in a Web application, you already understand the basic process: create an initial JNDI (Java Naming and Directory Interface) context, then use the context to perform a "lookup" to retrieve your DataSource.References: