bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search

Configuring and Managing WebLogic Server

 Previous Next Contents Index View as PDF  

Overview of WebLogic System Administration

Introduction to System Administration

WebLogic Server Domains

System Administration Infrastructure

The Administration Server and Managed Servers

Failover for the Administration Server

Failover for Managed Servers

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

Java Utilities

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

Mail

Starting and Using the Administration Console

Browser Support for the Administration Console

Starting the Administration Console

Using the Administration Console

Using WebLogic Server with Web Servers

Monitoring

Licenses

Overview of WebLogic Server Domains

What Is a Domain?

Contents of a Domain

Administration Server

Managed Servers and Clustered Managed Servers

Resources and Services

Common Domain Types

Domain Restrictions

Domain Directory and config.xml

Domain Directories Structure

A Server's Root Directory

Overview of Node Manager

Introduction to Node Manager

Node Manager Architecture and Environment

Node Manager Runs on Machines that Host Managed Servers

Node Manager Should Run as a Service

Node Manager is Domain-Independent

Node Manager Clients

Node Manager Uses SSL

Native Support for Node Manager

Node Manager Capabilities

Start Managed Servers

Suspend or Stop Managed Servers

Shutdown Failed Managed Servers

Restart of Crashed and Failed Managed Servers

Prerequisites for Automatic Restart of Managed Servers

Configuring, Starting, and Stopping Node Manager

Configuring Node Manager

Default Configuration

Configuration Checklist

Set Up the Node Manager Hosts File

Reconfigure Startup Service

Update nodemanager.properties

Configure a Machine to Use Node Manager

Configure Managed Server Startup Arguments

Ensure Administration Server Address is Defined

Configure SSL for Node Manager

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

Managed Server Log Files

Node Manager Log Files

Correcting Common Problems

Node Manager and Managed Server States

Setting Up a WebLogic Server Instance as a Windows Service

Setting Up a Windows Service

Using a Non-Default JVM with a Windows Service

Verifying the Setup

Using the Control Panel to Stop or Restart the Service

Removing a Server as a Windows Service

Changing Startup Credentials for a Server Set Up as a Windows Service

Viewing Messages for a Server Set Up as a Windows Service

The WebLogic Server Windows Service Program (beasvc.exe)

Server Lifecycle

Lifecycle Overview

WebLogic Server States

Getting Server State

Understanding Server State

SHUTDOWN

STARTING

STANDBY

RESUMING

RUNNING

SUSPENDING

SHUTDOWN

FAILED

UNKNOWN

States Defined by Node Manager

Lifecycle Commands

Start

Graceful Shutdown

Graceful Shutdown Sequence

Controlling Graceful Shutdown

In-Flight Work Processing

Forced Shutdown

Configuring WebLogic Server Web Components

Overview

HTTP Parameters

Configuring the Listen Port

Web Applications

Web Applications and Clustering

Designating a Default Web Application

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)

Protecting System Administration Operations

Operations Available to Each Role

Default Group Associations

Protected User Interfaces

Overlapping Permissions for System Administration MBeans and Policies on Resources

Resources and Policies

Working with Policies

Maintaining a Consistent Security Scheme

Permissions for Starting and Shutting Down a WebLogic Server

Permissions for Using the weblogic.Server Command

Permissions for Using the Node Manager

Shutting Down a WebLogic Server

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

Machines 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

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 are 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?

WebLogic Server and the Channel Selection Process

Prioritizing Outgoing Connections

Handling Channel Failures

Upgrading Quality of Service Levels for RMI

Standard WebLogic Server Channels

The Default Network Channel

Administrative Channel

Configuring a Channel

Configuring Channels: Facts and Rules

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

 

Back to Top Previous Next