|
Administration Console Online Help
|
Startup Class --> Configuration
Tasks Related Topics Attributes
Overview
The Startup Class—>Configuration tab defines a named configuration for a startup class. You use this tab while creating a new configuration or modifying an existing one.
By default, startup classes are loaded and executed after all other types of modules have been deployed. You can configure a class to load and execute after the server deploys JDBC connection pools and before it deploys Web applications and EJBs.
If you are creating a new configuration, you must enter information on the Configuration tab and click Apply before you can access other tabs. Once you create a configuration, you cannot change its name. Instead, you must create a new configuration under a different name.
You can create multiple named configurations for any given startup class. For each configuration that you create, WebLogic Server uses a managed bean (MBean) to configure the startup class and persist the configuration.
Tasks
Configuring a Server to Use a Startup or Shutdown Class: Main Steps
Modify an Existing Startup or Shutdown Configuration
Delete a Startup or Shutdown Class Configuration
Related Topics
Starting and Stopping Servers
Attributes
Table 5-3
|
Attribute Label
|
Description
|
Value Constraints
|
|
Name
|
An alpha-numeric value that identifies the startup class configuration. This name attribute is for your identification purposes only.
After you have created a startup class configuration, you cannot change its name. Instead, delete the configuration and create a new one with a new name.
MBean: weblogic.management.
configuration.
StartupClassMBean
Attribute: Name
|
|
|
ClassName
|
The fully qualified name of the Java class that you have created and compiled. The class must be on the server's classpath.
MBean: weblogic.management.
configuration.
StartupClassMBean
Attribute: ClassName
|
Required: yes
|
|
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: weblogic.management.
configuration.
StartupClassMBean
Attribute: DeploymentOrder
|
Minimum: MIN_ORDER
Maximum: MAX_ORDER
Default: DEFAULT_ORDER
Dynamic: yes
|
|
Arguments
|
Arguments that the server uses to initialize a class. Separate multiple arguments with a comma. For example:
attribute1=value1,attribute2=value2
Do not use spaces to separate the arguments; use only a comma.
MBean: weblogic.management.
configuration.
StartupClassMBean
Attribute: Arguments
|
|
|
Failure is fatal
|
Determines whether a failure in this startup class prevents a server from starting. If this check box is cleared and the startup class fails, the server continues its startup process.
MBean: weblogic.management.
configuration.
StartupClassMBean
Attribute: FailureIsFatal
|
Default: false
Valid values:
|
|
Run before application deployments
|
Determines whether a startup class is loaded and run before the server deploys applications and EJBs. If you specify true for this option, the server loads the class after it deploys JDBC connection pools and before it deploys Web applications and EJBs.
If you specify false, the server loads the class after all other types of modules have been deployed.
MBean: weblogic.management.
configuration.
StartupClassMBean
Attribute: LoadBeforeAppDeployments
|
Default: false
Valid values:
|
