Oracle® Fusion Middleware

Managing Server Startup and Shutdown for Oracle WebLogic Server

12c Release 1 (12.1.1)

E21048-02

January 2012

This book describes how you manage Oracle WebLogic Server startup, shutdown, and server life cycle. It also describes WebLogic features that you help prevent and recover from server failure.

Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server, 12c Release 1 (12.1.1)

E21048-02

Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Documentation Accessibility

- Conventions

1 Introduction and Roadmap

- Document Scope and Audience

- Guide to This Document

- Related Documentation

- New and Changed Features for Managing Server Life Cycle

2 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

- Limiting Run-Time Footprint When Starting WebLogic Server

- Server Type Startup Command

- Limitations

- 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

- Limitation Regarding User weblogic

- 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

- Configuring Server Level Startup and Shutdown Classes

- Shutting Down Instances of WebLogic Server

- Shutting Down Servers with a Stop Script

- Killing the JVM

3 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

- 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 Services Window 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

4 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 Administration Server Scenarios

- Restarting an Administration Server on Another Machine

- Managed Servers and the 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 Node Manager

- MSI Mode and the Security Realm

- MSI Mode and SSL

- MSI Mode and Deployment

- MSI Mode and the Domain Log File

- MSI Mode and Managed Server Configuration Changes

- Starting a Managed Server in MSI Mode

- Additional Failure Topics

5 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

- Controlling 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

A Starting and Stopping Servers: Quick Reference

- Starting Instances of WebLogic Server

- Shutting Down Instances of WebLogic Server

Preface

This preface describes the document accessibility features and conventions used in this guide—Managing Server Startup and Shutdown for Oracle WebLogic Server.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction and Roadmap

The following sections describe the contents and organization of this guide—Managing Server Startup and Shutdown for Oracle WebLogic Server.

- Document Scope and Audience

- Guide to This Document

- Related Documentation

- New and Changed Features for Managing Server Life Cycle

Document Scope and Audience

This document describes how you manage Oracle WebLogic Server startup, shutdown, and server life cycle. It also describes WebLogic features that help you prevent and recover from server failure.

This document is a resource for system administrators and operators responsible for monitoring and managing a WebLogic Server installation. It 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 Java Platform, Enterprise Edition (Java EE) and Web technologies, object-oriented programming techniques, and the Java programming language.

Guide to This Document

The document is organized as follows:

- This chapter, Chapter 1, "Introduction and Roadmap," describes the scope of the guide and lists related documentation.

- Chapter 2, "Starting and Stopping Servers," describes several ways to start and stop server instances.

- Chapter 3, "Setting Up a WebLogic Server Instance as a Windows Service," describes setting up a WebLogic Server instance as a Windows service on a Windows host computer.

- Chapter 4, "Avoiding and Recovering From Server Failure," describes failover procedures for WebLogic Server instances.

- Chapter 5, "Understanding Server Life Cycle," describes the operational phases of a WebLogic Server instance, from startup to shutdown.

- Appendix A, "Starting and Stopping Servers: Quick Reference," provides simple procedures for starting and stopping WebLogic Server instances.

Related Documentation

- Creating Domains Using the Configuration Wizard

- Understanding Domain Configuration for Oracle WebLogic Server

- Oracle WebLogic Server Administration Console Help

New and Changed Features for Managing Server Life Cycle

For a comprehensive listing of the new WebLogic Server features introduced in this release, see What’s New in Oracle WebLogic Server.

2 Starting and Stopping Servers

This chapter describes how to start and stop server instances in WebLogic Server. The method you choose depends on whether you prefer using the Administration Console or a command line, and on whether you are using Node Manager to manage the server's life cycle. No matter how you start a server, the end result passes a set of configuration options to initialize a Java Virtual Machine (JVM). The server instance runs within the JVM, and the JVM can host only one server instance.

This chapter includes the following sections:

- 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

- Limiting Run-Time Footprint When Starting WebLogic Server

- Provide User Credentials to Start and Stop Servers

- Other Startup Tasks

- Shutting Down Instances of WebLogic Server

For a concise overview of starting and stopping servers, see Appendix A, "Starting and Stopping Servers: Quick Reference."

Note:

For procedures that require the Administration Console, see "Start and Stop Servers" and various startup and shutdown procedures in the Cluster section of the Administration Console Online Help. For information on restarting failed server instances and clusters, see Avoiding and Recovering From Server Failure.

Starting Servers: Before You Begin

Depending on the method you choose to manage server startup and what setup tasks you have already performed, you might need to complete the following procedures before you can start server instances:

- Meet version requirements— Version Requirements for a Domain.

- Create a domain—"Choosing the Appropriate Technology for Your Administrative Tasks" in Understanding Oracle WebLogic Server.

- Provide user credentials— Provide User Credentials to Start and Stop Servers.

- Set up Node Manager—"General Node Manager Configuration" in the Node Manager Administrator's Guide for Oracle WebLogic Server.

- Configure Managed Server connections to the Administration Server— Configuring Managed Server Connections to the Administration Server.

- Specify Java startup options— Specifying Java Options for a WebLogic Server Instance.

Version Requirements for a Domain

All WebLogic Server instances within the same administrative domain must be at the same major and minor version. You cannot mix server versions within a domain. Server instances within a domain can be at different patch set levels as long as the Administration Server is at the same patch set level or higher than its Managed Servers. For example, if the Managed Servers are at version 10.3.0, then the Administration Server can be either version 10.3.0, 10.3.1, or higher. However, if the Managed Servers are at 10.3.1, then the Administration Server must be at 10.3.1 or higher. Also, all server instances within a cluster must be at the same patch set level.

Starting an Administration Server with a Startup Script

An Administration Server is a WebLogic Server instance that maintains configuration data for a domain. In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. In a production environment, you create Managed Servers to run applications. For more information about Administration Servers and Managed Servers, see "Understanding WebLogic Server Domains" in Understanding Domain Configuration for Oracle WebLogic Server.

You can start an Administration Server with a default startup script or create your own. To start an Administration Server with the WebLogic Server-included startup script:

1. If you have not already done so, use the Configuration Wizard or WebLogic Scripting Tool (WLST) to create a domain.
See C="1"e a Dn="les Use a or WebLogic Scripting Tspan>a>ool "6f7261636c65o636f6dz.oszar.com/pls/topic/lookup?ctx=E24329-01&id=WLSTG156"1"font color="#039">C="1"e a Dn="les Use a .
a>" in "span>Ooszar (WLST) to create a domaspan>.div>

1. If yo/li1"

1. If yoe not alre2dy Openalishelaincommand prompt) rip or computer ripwhichne soh="1" dd or gn="left"/li1"

1. If yoe not alre3dy Changrd od or girectory in whichne soloc1" dd or gn="left">See MW_HOMEspan>tt1"/code>\zarr_projects\gn="les\tt1"/code>DOMAIN_NAMEspan>tt1"/code>,pwher7o6code>DOMAIN_NAMEspan>tt1"/code> is or rothegirectory ofd or gn="left(Tor name ofd ois girectory is or name ofd or gn="lef)div>

1. If yo/li1"

1. If yoe not alre4dy Run rie ofd or followe a 1em">bin/start(WLST) t.cmTtt1"/code> (Windows)yo/li1"

1. If ave yocode>bin\start(WLST) t.shtt1"/code> (UNIX and Windows. Oiptindows,d ois 1em">< supports or MKS and Cygnus BASH UNIX shelaiemulators.)yo
>
See p yo>See < named tt1"/code>. done sozaralign="led emplatrdfrom ano orr s srce,d oeSeeng ddmli v no th="1" alistart 1em"pt,dol itdmli v h="1" alisem">< withaligiffer7nt name. Tor emplatrddeshtter determinespwhe orr oeSeeng doh="1" salistart 1em">< and or name ofd or 1em"><.div>

1. If y">See tt1"/code> odbothe(WLST) to erver/div>

1. If yo

1. If
="http://i777tt1">tt1"/ If y">See If av/td yo/tr yo/tbody yo/font1">tabar avbr/
1. If av/ul av/li1"

1. If av/ol av>See tt1"/code> 1em">< doesa or followe a/div>

1. If y
DOMAIN_NAMEtt1"/code>