Configuring and Managing WebLogic Server
- Overview
- Introduction to System Administration
- WebLogic Server Domains
- System Administration Infrastructure
- The Administration Server and Managed Servers
- Recovery of a Failed Administration Server
- Managed Server Independence
- Domain-Wide Administration Port
- Service Packs and WebLogic Server Instances
- System Administration Tools
- Security Protections for System Administration Tools
- System Administration Console
- Command-Line Interface
- JMX
- Configuration Wizard
- Configuration Template Builder
- Java Utilities
- Ant Tasks
- Node Manager
- SNMP
- Logs
- Editing config.xml
- Resources You Can Manage in a WebLogic Server Domain
- Servers
- Clusters
- Machines
- Network Channels
- JDBC
- JMS
- WebLogic Messaging Bridge
- Web Servers and Web Components
- Applications
- Application Formats
- Editing and Creating Deployment Descriptors with WebLogic Builder
- Startup and Shutdown Classes
- JNDI
- Transactions
- XML
- Security
- WebLogic Tuxedo Connector
- Jolt
- Starting the Administration Console
- Using WebLogic Server with Web Servers
- Monitoring
- Licenses
- Overview of WebLogic Server Domains
- What Is a Domain?
- Contents of a Domain
- Production and Development Modes
- Creating a New Domain
- Creating a Domain Using the Configuration Wizard
- Creating a Domain Using the weblogic.Server Command
- Creating a Domain Using Ant Tasks
- Administration Server
- Role of the Administration Server
- What Happens If the Administration Server Fails?
- Managed Servers and Clustered Managed Servers
- Resources and Services
- Common Domain Types
- Domain Restrictions
- Directory Structure
- The config.xml file
- Domain Directory Structure
- A Server's Root Directory
- Specifying a Server Root Directory
- Server Root Directory for an Administration Server
- Server Root Directory for a Managed Server Started with Node Manager
- Server Root Directory for a Managed Server Not Started with Node Manager
- Creating and Configuring Domains Using the Configuration Wizard
- Starting the Configuration Wizard
- Starting in a GUI Environment
- Starting in a Text-Based Environment
- Choosing a Domain Configuration Template
- BEA Templates
- Additional Templates
- Completing the Remaining Steps of the Configuration Wizard
- Example: Creating a Domain with a Single Server Instance
- Example: Creating a Domain with Administration Server and Clustered Managed Servers
- Overview of Node Manager
- Node Manager Environment
- Run Node Manager on Each Machine that Hosts Managed Servers
- Run Node Manager as an Operating System Service
- Node Manager is Domain-Independent
- Invoking Node Manager
- Node Manager Uses SSL
- Native Support for Node Manager
- Node Manager Capabilities
- Start Managed Servers
- Suspend or Stop Managed Servers
- Shut Down Failed Managed Servers
- Restart of Crashed and Failed Managed Servers
- Prerequisites for Automatic Restart of Managed Servers
- Node Manager Communications for Lifecycle Operations
- Node Manager Communications to Start a Managed Server
- Node Manager Communications to Shut Down a Managed Server
- Node Manager Communications to Restart a Managed Server
- Node Manager Communications to Re-establish Communications After a Failure
- Configuring, Starting, and Stopping Node Manager
- Configuring Node Manager
- Default Configuration (Development Environment)
- Configuration Checklist (Production Environment)
- Set Up the Node Manager Hosts File
- Reconfigure Startup Service
- Configure a Machine to Use Node Manager
- Configure Managed Server Startup Arguments
- Ensure Administration Server Address is Defined
- Configure SSL for Node Manager
- Review nodemanager.properties
- Configure Monitoring, Shutdown, and Restart for Managed Servers
- Starting and Stopping Node Manager
- Starting Node Manager as a Service
- Starting Node Manager with Commands or Scripts
- Command Syntax for Starting Node Manager
- Node Manager Environment Variables
- Node Manager Properties
- Server Properties
- Stopping Node Manager
- Troubleshooting Node Manager
- Node Manager Log Files
- Managed Server Log Files
- Node Manager Client Logs
- Correcting Common Problems
- Node Manager and Managed Server States
- Setting Up a WebLogic Server Instance as a Windows Service
- Setting Up a Windows Service: Main Steps
- Creating a Server-Specific Script
- Configuring a Connection to the Administration Server
- Requiring Managed Servers to Start After Administration Servers
- Enabling Graceful Shutdowns from the Windows Control Panel
- Redirecting Standard Out and Standard Error to a File
- Adding Classes to the Classpath
- Run the Server-Specific Script
- Verifying the Setup
- Verifying the User Account Under Which the Service Runs
- Using the Control Panel to Stop or Restart a Server Instance
- Removing a Server as a Windows Service
- Changing Startup Credentials for a Server Set Up as a Windows Service
- Server Life Cycle
- Life Cycle Overview
- Understanding WebLogic Server States
- Getting Server State
- Understanding Server State
- SHUTDOWN
- STARTING
- STANDBY
- RESUMING
- RUNNING
- SUSPENDING
- SHUTDOWN
- FAILED
- UNKNOWN
- States Defined by Node Manager
- Life Cycle Commands
- Start
- Graceful Shutdown
- Graceful Shutdown Sequence
- Controlling Graceful Shutdown
- In-Flight Work Processing
- Shutdown Operations and Application Undeployment
- Forced Shutdown
- Configuring Web Server Functionality for WebLogic Server
- Overview of Configuring Web Server Components
- HTTP Parameters
- Configuring the Listen Port
- Configuring the Listen Ports from the Administration Console
- Web Applications
- Web Applications and Clustering
- Designating a Default Web Application
- Virtual Directory Mapping
- Configuring Virtual Hosting
- Virtual Hosting and the Default Web Application
- Setting Up a Virtual Host
- How WebLogic Server Resolves HTTP Requests
- Setting Up HTTP Access Logs
- Log Rotation
- Common Log Format
- Setting Up HTTP Access Logs by Using Extended Log Format
- Creating the Fields Directive
- Supported Field identifiers
- Creating Custom Field Identifiers
- Preventing POST Denial-of-Service Attacks
- Setting Up WebLogic Server for HTTP Tunneling
- Configuring the HTTP Tunneling Connection
- Connecting to WebLogic Server from the Client
- Using Native I/O for Serving Static Files (Windows Only)
- Monitoring a WebLogic Server Domain
- Facilities for Monitoring WebLogic Server
- Administration Console
- Server Self-Health Monitoring
- Obtaining Server Health Programmatically
- Messages and Log Files
- Monitoring WebLogic Server Using the Administration Console
- Domain Monitoring Pages
- Other Domain Monitoring Links
- Server Monitoring Pages
- Other Server Monitoring Links
- Clusters Monitoring Pages
- Machine Monitoring Pages
- Deployments Monitoring Pages
- Services Monitoring Pages
- Recovering Failed Servers
- WebLogic Server Failure Recovery Features
- Automatic Restart for Managed Servers
- Managed Server Independence Mode
- MSI Mode and the Managed Servers Root Directory
- MSI Mode and the Security Realm
- MSI Mode and SSL
- MSI Mode and Deployment
- MSI Mode and Managed Server Configuration Changes
- MSI Mode and Node Manager
- MSI Mode and Configuration File Replication
- MSI Mode and Restored Communication with an Administration Server
- Backing Up Configuration and Security Data
- Backing up config.xml
- WebLogic Server Archives Previous Versions of config.xml
- WebLogic Server Archives config.xml during Server Startup
- Backing Up Security Data
- Backing Up the WebLogic LDAP Repository
- Backing Up SerializedSystemIni.dat and Security Certificates
- Restarting Failed Server Instances
- Restarting an Administration Server
- Restarting an Administration Server When Managed Servers Not Running
- Restarting an Administration Server When Managed Servers Are Running
- Restarting Managed Servers
- Starting a Managed Server When the Administration Server Is Accessible
- Starting a Managed Server When the Administration Server Is Not Accessible
- Additional Failure Topics
- Configuring Network Resources
- Overview of Network Configuration
- New Network Configuration Features in WebLogic Server
- Understanding Network Channels
- What Is a Channel?
- Rules for Configuring Channels
- Custom Channels Can Inherit Default Channel Attributes
- Why Use Network Channels?
- Handling Channel Failures
- Upgrading Quality of Service Levels for RMI
- Standard WebLogic Server Channels
- The Default Network Channel
- Administration Port and Administrative Channel
- Configuring a Channel
- Configuring Channels: Facts and Rules
- Channels and Server Instances
- Configuration Changes are Not Dynamic
- Channels and Protocols
- Reserved Names
- Channels, Proxy Servers, and Firewalls
- Configuring Network Channels with a Cluster
- Create the Cluster
- Create and Assign the Network Channel
- Starting and Stopping Servers: Quick Reference
- Starting Instances of WebLogic Server
- Shutting Down Instances of WebLogic Server