Introduction and Roadmap
Document Scope and Audience
Guide to This Document
Related Documentation
New and Changed Features for Managing Server Life Cycle
Starting and Stopping Servers
Starting Servers: Before You Begin
Version Requirements for a Domain
Starting an Administration Server with a Startup Script
Starting an Administration Server from the Windows Start Menu
Starting an Administration Server with the java weblogic.Server Command
Starting an Administration Server Using WLST and Node Manager
Starting an Administration Server Using WLST Without Node Manager
Starting Managed Servers with a Startup Script
Starting Managed Servers from the Administration Console
Starting Managed Servers and Clusters with WLST and Node Manager
Starting Managed Servers with the java weblogic.Server Command
Starting a Managed Server When the Administration Server Is Unavailable
Provide User Credentials to Start and Stop Servers
Specifying an Initial Administrative User for a Domain
Boot Identity Files
Creating a Boot Identity File for an Administration Server
Using java weblogic.Server to Create a Boot Identity File for an Administration Server
Creating Boot Identity Files for Managed Servers
How a Server Uses a Boot Identity File at Startup
Removing Boot Identity Files After Startup
Specifying User Credentials for Starting a Server with Node Manager
Other Startup Tasks
Making Java Classfiles Globally Available
Configuring Managed Server Connections to the Administration Server
Specifying Java Options for a WebLogic Server Instance
Changing the JVM That Runs Servers
Shutting Down Instances of WebLogic Server
Shutting Down Servers with a Stop Script
Killing the JVM
Using Node Manager to Control Servers
Overview of Node Manager
Java-based and Script-based Node Manager
Determining Which Node Manager Version to Use
Accessing Node Manager
What You Can Do with Node Manager
Start, Shut Down, and Restart an Administration Server
Start, Shut Down, Suspend, and Restart Managed Servers
Restart Administration and Managed Servers
Monitor Servers and View Log Data
How Node Manager Works in the WebLogic Server Environment
Diagram of Node Manager and Servers
How Node Manager Starts an Administration Server
How Node Manager Starts a Managed Server
How Node Manager Restarts an Administration Server
How Node Manager Restarts a Managed Server
How Node Manager Shuts Down a Server Instance
Node Manager and System Crash Recovery
Node Manager Configuration and Log Files
General Node Manager Configuration
Configuring Your Computer to Run Node Manager
Controlling and Configuring Node Manager Using WLST
Using nmConnect() in a Production Environment
Specifying Node Manager Username and Password
Configuring a Machine to Use Node Manager
Configuring nodemanager.domains File
Configuring Remote Startup Arguments
Setting Server Startup Properties
Setting Startup Properties Using Administration Utilities
Ensuring Administration Server Address Is Defined
Setting Node Manager Environment Variables
Configuring Java-based Node Manager
Reconfigure Startup Service for Windows Installations
Configuring Java-based Node Manager Security
Remote Server Start Security for Java-based Node Manager
Reviewing nodemanager.properties
Deprecated Node Manager Properties
Configuring Node Manager to Use Start and Stop Scripts
Using SSL With Java-based Node Manager
Configuring Node Manager on Multiple Machines
Configuring Node Manager as an xinetd Service
Configuring Script-based Node Manager
Creating a Node Manager User
Overriding the Default SSH Port
Configuring Script-based Node Manager Security
Security for WebLogic Server Scripts
Remote Server Start Security for Script-based Node Manager
Generating and Distributing Key Value Pairs
Starting Node Manager and Servers
Running Node Manager as a Startup Service
Starting Java-based Node Manager Using Scripts
Command Syntax for Starting Java-based Node Manager
Running Script-based Node Manager
Stopping Node Manager
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
Java Class that Shuts Down a Server Instance
Redirecting Standard Out and Standard Error to a File
Changing the Default Rotation Criteria
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
Avoiding and Recovering From Server Failure
Failure Prevention and Recovery Features
Overload Protection
Failover for Clustered Services
Automatic Restart for Failed Server Instances
Server-Level Migration
Service-Level Migration
Managed Server Independence Mode
Directory and File Backups for Failure Recovery
Back Up Domain Configuration Directory
Back Up LDAP Repository
Back Up SerializedSystemIni.dat and Security Certificates
WebLogic Server Exit Codes and Restarting After Failure
Restarting a Failed Administration Server
Restarting an Administration Server
Restarting an Administration Server on the Same Machine
Restarting an Administration Server on Another Machine
Managed Servers and Re-started Administration Server
Restarting a Failed Managed Server
Starting a Managed Server When the Administration Server Is Accessible
Starting a Managed Server When the Administration Server Is Not Accessible
Understanding Managed Server Independence Mode
MSI Mode and the Security Realm
MSI Mode and the Domain Log File
MSI Mode and Managed Server Configuration Changes
Starting a Managed Server in MSI Mode
Additional Failure Topics
Understanding Server Life Cycle
Diagram of the Server Life Cycle
Getting and Using Server State
Understanding Server States in the Server Life Cycle
SHUTDOWN State
STARTING State
STANDBY State
ADMIN State
RESUMING State
RUNNING State
SUSPENDING State
FORCE_SUSPENDING State
SHUTTING_DOWN State
FAILED State
Using Server Life Cycle Commands
Start
Start in Standby
Start in Admin
Resume
Graceful Suspend
Force Suspend
Graceful Shutdown
Shutdown Operations and Application Undeployment
Force Shutdown
Processing In-Flight Work During Suspend and Shutdown
RMI Subsystem
Web Container
Timer Service
Application Service
EJB Container
JMS Service
JDBC Service
Transaction Service
Starting and Stopping Servers: Quick Reference
Starting Instances of WebLogic Server
Shutting Down Instances of WebLogic Server