AC: WebLogic Server migration framework provides infrastructure and facilities to perform the

manual or automatic migration of JMS-related services and the JTA Transaction Recovery Service.

D: WebLogic Server supports the automatic migration of user-defined singleton services.

Automatic singleton service migration allows the automatic health monitoring and migration of

singleton services. A singleton service is a service operating within a cluster that is available on only

one server at any given time.

JMSDeliveryMode specifies PERSISTENT or NON_PERSISTENT messaging.

A: Using the Automatic Migration option requires setting a cluster’s Migration Basis policy to either

Database or Consensus leasing.

C: Setting Migration Basis to Consensus leasing means that the member servers maintain leasing

information in-memory, which removes the requirement of having a high-availability database to use

leasing. This version of leasing requires that you use Node Manager to control servers within the

cluster.

The primary goals in exporting a deployment configuration are:

* To expose the external resources requirements of the application as null variables in a deployment

plan.

Any external resources required by the application are subject to change when the application is

deployed to a different environment. For example, the JNDI names of datasources used in your

development environment may be different from those used in testing or production. Exposing those

JNDI names as variables makes it easy for deployers to use available resources or create required

resources when deploying the application.

* To expose additional configurable properties, such as tuning parameters, as variables in a

deployment plan.

Java-based Node Manager runs within a Java Virtual Machine (JVM) process. It is recommended that

you run it as a Windows service on Windows platforms and as an operating system service on UNIX

platforms.

For UNIX and Linux systems, WebLogic Server provides a script-based version of Node Manager.

AB: The Select a Template Configuration Source window prompts you to choose the application template or domain directory from which you want to create an extension template. D: The Import SQL Scripts window prompts you to add SQL scripts for each database that you expect to be used with the domains created from this template.

This thread is considered Stuck by WebLogic because it's been running for over the time defined in MaxStuckThreadTime (600 seconds by default). Weblogic Server waits for this time to be reached before marking a thread as stuck if the thread is still working after this time. Example: [STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' id=73 idx=0x128 nid=13410 prio=1 alive, in native, daemon

In a given domain, you can create multiple diagnostic system modules with distinct configurations.

You can target multiple diagnostic system modules to any given server or cluster.

Note: To configure and use the Instrumentation, Harvester, and Watch and Notification components

at the server level, you must first create a system resource called a diagnostic system module, which

will contain the configurations for all those components. The configuration of diagnostic system

module is defined in a resource descriptor. A resource descriptor can be either configured or

external.

:

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.