Skip navigation.

Configuring WebLogic Server Environments

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

Introduction and Roadmap

This section describes the contents and organization of this guide—Configuring WebLogic Server Environments.


Document Scope and Audience

This document describes how you design, configure, and manage WebLogic Server® environments. It is a resource for system administrators and operators responsible for implementing a WebLogic Server installation. This document is relevant to all phases of a software project, from development through test and production phases.

It is assumed that the reader is familiar with J2EE and Web technologies, object-oriented programming techniques, and the Java programming language.


Guide to This Document

The document is organized as follows:


Related Documentation


New and Changed Features in WebLogic Server Environments

The following sections describe key changes and improvements to WebLogic Server:

Server Self-Tuning for Production Environments

New self-tuning capabilities simplify the process of configuring WebLogic Server for production environments with service level requirements that vary over time or by application. Self-tuning helps prevent deadlocks during periods of peak demand. Self-tuning features are also useful if your WebLogic Server environment hosts multiple applications with different performance and availability requirements—for example, allowing you to allocate a greater percentage of resources to a user-facing order processing application than to a back-end inventory management application.

The new queue strategy enables administrators to allocate processing resources and manage performance more effectively, by avoiding the effort and complexity involved in configuring, monitoring, and tuning custom executes queues.

Key self-tuning features in WebLogic Server include:

For more information, see Using Work Managers to Optimize Scheduled Work.

New Overload Protection Increases Availability

WebLogic Server 9.0 has improved capabilities for detecting when system load increases to the point that application performance and stability might be at risk. These new features, referred to as overload protection, are key to avoiding, and minimizing the negative effects of overload.

New overload features protect a server instance from out-of-memory (OOM) exceptions, execute queue overloads, increasing the availability of a server or a cluster.

For more information, see Avoiding and Managing Overload.

Network Channels Can Manage Traffic Between Server Instances

In addition to managing external network traffic, network channels can now manage network traffic between server instances. Other new and improved configuration and control options for network channels include:

For more information, see Configuring Network Resources.

System-Wide Persistent Store

The WebLogic Persistent Store is a built-in, high-performance storage solution for WebLogic Server subsystems and services that require persistence, especially subsystem that require the creation and deletion of short-lived data objects, such as transactional messages for JMS Servers. Each server instance in a domain has a default persistent store that requires no configuration and that can be used simultaneously by subsystems that do not require explicit selection of a particular store, but can use the system's default storage. These subsystems include JMS Servers, Web Services, EJB Timer services, Store-and-Forward services, and the JTA Transaction Log (TLOG). Optionally, administrators can configure dedicated file-based stores or JDBC-accessible stores to suit their environment.

For more information, see Using the WebLogic Persistent Store.


Skip navigation bar  Back to Top Previous Next