Configuring WebLogic Server Environments
|
 |
 |
|
 |
 |
Introduction and Roadmap
This section describes the contents and organization of this guide—Configuring WebLogic Server Environments.
- Document Scope and Audience
- Guide to This Document
- Related Documentation
- New and Changed Features in 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:
- This chapter, Introduction and Roadmap, describes the scope of this guide and lists related documentation.
- Using Work Managers to Optimize Scheduled Work, describes the WebLogic Server execution model and the process of configuring application access to the execute queue.
- Avoiding and Managing Overload, describes detecting, avoiding, and recovering from overload conditions.
- Configuring Network Resources, describes optimizing your WebLogic Server domain for your network.
- Configuring Web Server Functionality, describes using WebLogic Server as a Web server.
- Using the WebLogic Persistent Store, describes configuring and monitoring the persistent store, a built-in, high-performance storage solution for WebLogic Server subsystems and services that require persistence.
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 Overload Protection Increases Availability
- Network Channels Can Manage Traffic Between Server Instances
- System-Wide Persistent Store
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:
- Workload management—Administrators can define scheduling policies and constraints at the domain level, application level, and module level.
- Automatic thread count tuning—A thread pool can maximize throughput by automatically changing its size, based on throughput history and queue size.
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:
- SSL behaviors configurable on a per-channel basis.
- Dynamic configuration and starting of channels without re-booting the server instance.
- New capabilities for closing and restarting a channel.
- Replication channel for replication traffic among server instances in a WebLogic Server cluster.
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.
