1z0-134 Exam Dumps - Oracle WebLogic Server 12c: Advanced Administrator II

Example: The following example displays information about the current MBean, cmo.

wls:/mydomain/serverConfig> cmo.getType()

‘Domain’

C: A callback handler used to control the failover and failback within a multi data source must include an implementation of the weblogic.jdbc.extensions.ConnectionPoolFailoverCallback interface.

D: You can register a callback handler with WebLogic Server that controls when a multi data source with the Failover algorithm fails over connection requests from one JDBC data source in the multi data source to the next data source in the list.

For persistent messaging, you must configure a custom persistent store that is targeted to the same migratable target as the JMS service. Unless you are using pre/post migration scripts to move the store data across migrated servers, the custom store must be configured such that all the candidate servers in the migratable target have access to it.

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.

With CLIENT_ACKNOWLEDGE the Session object relies on the application to call an acknowledge method on a received message. Once the method is called, the session acknowledges all messages received since the last acknowledge.

Starting the Domain Template Builder on UNIX Platforms

A simple way to failover a client connected to a failed distributed destination is to write reconnect logic in the client code to connect to the distributed destination after catching onException.

A: When using the create command with WLST online you must be connected to an Administration Server.

B: Child types must be created under an instance of their parent type.

C: Syntax: create(name, childMBeanType, [baseProviderType])

The Create command creates a configuration bean of the specified type for the current bean.

B: Distributing an application copies deployment files to target servers and places the application in a prepared state. You can then start the application in Administration mode, which restricts access to the application to a configured Administration channel so you can perform final testing without opening the application to external client connections or disrupting connected clients.

C: Distributing an application prepares it for deployment by copying its deployment files to all target servers and validating it. After you distribute an application, you can start it in Administration mode, which restricts access to the application to a configured Administration channel and allows you to distribute the application to a production environment (or distribute a new version of an application) without opening the application to external client connections.

E: While in Administration mode, you can connect to an application only via a configured Administration channel. This allows you to perform final (“sanity”) checking of the application directly in the production environment without disrupting clients. After performing final testing, you can either undeploy the application to make further changes, or start the application to make it generally available to clients.

WebLogic JMS calculates the JMSExpiration value as the sum of the application's time-to-live and the current GMT. If the application specifies time-to-live as 0, JMSExpiration is set to 0, which means the message never expires.

In Managed Server Independence mode, a Managed Server looks in its root directory for the following files:

* msi-config.xml—a replica of the domain's config.xml.(Even if the domain's configuration file is named something other than config.xml, a Managed Server in MSI mode always looks for a configuration file named msi-config.xml.)

* SerializedSystemIni.dat

* boot.properties—an optional file that contains an encrypted version of your username and password.

Note: When a Managed Server starts, it tries to contact the Administration Server to retrieve its configuration information. If a Managed Server cannot connect to the Administration Server during startup, it can retrieve its configuration by reading configuration and security files directly. A Managed Server that starts in this way is running in Managed Server Independence (MSI) mode