To manage work in your applications, you define one or more of the following Work Manager components:

Fair Share Request Class:

Response Time Request Class:

Min Threads Constraint:

Max Threads Constraint:

Capacity Constraint

Context Request Class:

Note:

* max-threads-constraint—This constraint limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined.

A max-threads-constraint can be defined in terms of a the availability of resource that requests depend upon, such as a connection pool.

A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the server does not schedule requests of this type until the number of concurrent executions falls below the limit. The server then schedules work based on the fair share or response time goal.

* WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput.

Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components.

* WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic Server prioritizes work based on rules you define, and run-time metrics, including the actual time it takes to execute a request and the rate at which requests are entering and leaving the pool.

The common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count. For example, if historical throughput statistics indicate that a higher thread count increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, WebLogic decreases the thread count. This new strategy makes it easier for administrators to allocate processing resources and manage performance, avoiding the effort and complexity involved in configuring, monitoring, and tuning custom executes queues.

D: auto-kill-if-failed

Specifies whether the Node Manager should automatically kill

this server (the managed server) if its health state is failed.

(Interface=weblogic.management.configuration.ServerMBean Attribute=getAutoKillIfFailed)

When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

E: When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

A: Oracle Smart Update is a standalone Java application that is automatically installed in the Middleware home utils/bsu directory. Smart Update simplifies the process of applying patches to your WebLogic Server installation. When support makes a patch available for an installed version of WebLogic Server, you download the patch from My Oracle Support and then use Oracle Smart Update to apply it to your installation. Smart Update organizes all available updates for you, and has several features that allow a great deal of customizing in the way various patches are applied and managed in your environment.

B: As part of a new Enterprise Manager system, the installation wizard does the following:

* Oracle My Oracle Support Management Plug-In

etc.

C: Applying patch from server start script:

After downloading the patch (jar file) follow the below steps:

- Stop your server.

- Then take the path of the folder which has the CRxxxxxx_xxxmpx.jar file and copy it in the CLASSPATH of setDomainEnv.cmd which is in

( < bea home > /user_projects/domains/ < your domain name > /bin/setDomainEnv.cmd)

For example, the script would look something like this:

set CLASSPATH=%PRE_CLASSPATH%;%WEBLOGIC_CLASSPATH%; C:\extra\my_projects\doc\CR\CR218639_920mp3.jar;C:\extra\my_projects\doc \CR\ CR360676_920mp3.jar;C:\extra\my_projects\doc\CR\CR367966_920mp3.jar; C:\extra\my_projects\doc\CR\CR368155_920mp3.jar;C:\extra\my_projects\doc\CR\CR370311_920mp3.jar

- Re-start your server.

- You should see the patch applied in the stdout file.

C: Message Unit-of-Order is a WebLogic Server value-added feature that enables a stand-alone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created.

D Transactions required for parallel processing.

Incorrect:

A: Many applications need an even more restricted notion of a group than provided by the Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic JMS provides the Unit-of-Work (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, an JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete.

Note:

* WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names:

weblogic.jms.ConnectionFactory

weblogic.jms.XAConnectionFactory

Note:

* Apache Maven is a software tool for building and managing Java-based projects. WebLogic Server provides support for Maven through the provisioning of plug-ins that enable you to perform various operations on WebLogic Server from within a Maven environment.

* Continuous Integration is a software engineering practice which attempts to improve quality and reduce time to deliver software by applying small, frequent quality control efforts. It is characterized by these key practices:

Use of a version control system

All developers commit to the ‘HEAD’ (main code line) every day

The product is built on every commit

The build must be automated and fast

Automated deployment to a production-like environment

Automated testing

Results of all builds are published (so everyone can see who broke the build)

Deliverables are easily available (for developers, testers, other stakeholders)

Note:

*

* When to Use Work Managers

Following are guildelines to help you determine when you might want to use Work Managers to customize thread management:

/ The default fair share is not sufficient.

This usually ocurrs in situations where one application needs to be given higher priority over another.

/ A response time goal is required.

/ A minimum thread constraint needs to be specified to avoid server deadlock