JCA Adapter

This product is a wrapper to the WebLogic Tuxedo Connector (WTC) found as part of the WebLogic Server (WLS) product. WTC can only be used on WebLogic, but the JCA adapter allows deploying WTC capabilities on other Java Application Servers that support the Java EE JCA specification.

Note:

* Tuxedo (Transactions for Unix, Extended for Distributed Operations) is a middleware platform used to manage distributed transaction processing in distributed computing environments. Tuxedo is a transaction processing system or transaction-oriented middleware, or enterprise application server for a variety of systems and programming languages. Developed by AT & T in the 1980s, it became a software product of Oracle Corporation in 2008.

fair-share-request-class—Specifies the average thread-use time required to process requests. The default fair share value is 50.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.

During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will allocate 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.

* Example:

< work-manager >

< name > lowpriority_workmanager < /name >

< fair-share-request-class >

< name > low_priority < /name >

< fair-share > 10 < /fair-share >

< /fair-share-request-class >

< /work-manager >

< work-manager >

< name > highpriority_workmanager < /name >

< fair-share-request-class >

< name > high_priority < /name >

< fair-share > 100 < /fair-share >

< /fair-share-request-class >

< /work-manager >

Note:

* A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work.

Incorrect:

Not C: response-time-request-class—Specifies a response time goal in milliseconds. Response time goals are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for requests with that class by subtracting the observed average thread use time from the response time goal, and schedules requests so that the average wait for requests with the class is proportional to its tolerable waiting time.

Not A, D: Not related to thread constraints.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

Restrictions on Production Redeployment Updates

WebLogic Server can host a maximum of two different versions of an application at one time.

Note:

* When you redeploy a new version of an application, you cannot change:

An application's deployment targets

An application's security model

A Web applications persistent store settings

To change any of the above features, you must first undeploy the active version of the application.

Incorrect:

* (not A)

Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability* to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application.

* (not C) Not dependant on whether the application is JRockit or Hotspot.

* (not E)

The production redeployment strategy is supported for:

Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).

Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.

All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.

Production redeployment is not supported for:

Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.

Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Applications that obtain JDBC data sources via the Driver Manager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.

Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.

WebLogic Administrators typically use the Administration Console or the WebLogic Scripting Tool (WLST) to create and deploy (target) JDBC modules.

Note:

* (not A) Domain template—defines the full set of resources within a domain, including

infrastructure components, applications, services, security options, and general

environment and operating system options.

* Extension template—defines the applications and services that you can add to an

existing domain, including product component functionality and resources such as

JDBC or JMS.

* (not B) Each domain describes its configuration in an XML document that is located in the domain’s configuration directory. At run time, each WebLogic Server instance in a given domain creates an in-memory representation of the configuration described in this document.

The central configuration file for a domain is   DOMAIN_NAME /config/config.xml . This file specifies the name of the domain and the configuration of each server instance, cluster, resource, and service in the domain. The file includes references to additional XML files that are stored in subdirectories of the DOMAIN_NAME /config   directory. These included files are used to describe major subsystems of WebLogic Server.

When an application that references a shared library or package is deployed, WebLogic Server checks the names and version string requirements against the libraries registered with the server. If an exact match for a library or package name is not found, or if the version requirements are not met, the application deployment fails.

If WebLogic Server finds a name and version string match for all of the libraries referenced in the application, the server adds the libraries' classes to the classpath of the referencing application and merges deployment descriptors from both the application and libraries in memory. The resulting deployed application appears as if the referenced libraries were bundled with the application itself.

Note:

As a best practice, your development team should always include version string information for a library or optional package in the manifest file for the deployment. See Editing Manifest Entries for Shared Libraries in Developing Applications for Oracle WebLogic Server for more information.

If you are deploying a library or package that does not include version string information, you can specify it at the command line using one or both of the following options:

libspecver—Defines a specification version for the library or package.

libimplver—Specifies an implementation version for the library or package.

The WebLogic Server Management Pack EE greatly improves application

performance by providing unique functionality to automatically detect performance

bottlenecks; quickly diagnose these performance problems, and identify their root

cause. Key application performance management features of the pack include the

following:

* (A) Manage multiple farms and WebLogic Domains centrally

* Monitor Oracle Coherence Cluster – including all nodes within a cluster, all

caches, services, connection managers and connections

* Monitor middleware availability and performance out-of-box; track such data

historically, and receive notifications of potential problems

* Obtain real-time, in-depth JVM diagnostics without instrumentation overhead

* Trace transactions across containers as well as to the database

* (E) Analyze call paths and dependencies via graphical, architecture views

* (E) Automatically discover and model dependencies between Java components,

frameworks, and web services