Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Shutdown Classes: Configuration

Configuration Options     Related Tasks     Related Topics

Use this page to modify the configuration of a shutdown class.

A server loads and runs a shutdown class as part of a graceful shutdown.

You can create multiple named configurations for any given shutdown class. For each configuration that you create, WebLogic Server uses a managed bean (MBean) to configure the shutdown class and persist the configuration.

Configuration Options

Name Description
Name

An alpha-numeric value that identifies the shutdown class configuration. This name is for your identification purposes only.

After you have created a shutdown class configuration, you cannot change its name. Instead, delete the configuration and create a new one with a new name.

MBean Attribute:
ShutdownClassMBean.Name

Changes take effect after you redeploy the module or restart the server.

Class Name

The fully qualified name of a class to load and run. The class must be on the server's classpath.

For example, mycompany.mypackage.myclass

MBean Attribute:
ShutdownClassMBean.ClassName

Changes take effect after you redeploy the module or restart the server.

Deployment Order

A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type.

For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.

Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.

MBean Attribute:
ShutdownClassMBean.DeploymentOrder

Minimum value: 0

Maximum value: 2147483647

Arguments

Arguments that a server uses to initialize a class.

Separate multiple arguments with a comma. For example:
first=MyFirstName,last=MyLastName

MBean Attribute:
ShutdownClassMBean.Arguments

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics


Back to Top