Startup Classes: Configuration
Configuration Options Related Tasks Related Topics
Use this page to modify the configuration of a startup class.
The options on this page determine when servers load and run this startup class.
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.
Name Description 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.
The fully qualified name of a class to load and run. The class must be on the server's classpath.
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.
Arguments that a server uses to initialize a class.
Separate multiple arguments with a comma. For example:
Failure is Fatal
Specifies whether a failure in this startup class prevents the targeted server(s) from starting.
If you specify that failure is not fatal, if the startup class fails, the server continues its startup process.
Run Before Application Deployments
Specifies whether the targeted servers load and run this startup class before activating JMS and JDBC services and before starting deployment for applications and EJBs.
If you enable this feature for a startup class, a server loads and runs the startup class before the deployment prepare phase. At this point, JMS and JDBC services are not yet available. (Deployment for applications and EJBs consists of three phases: prepare, admin and activate.)
If you do not enable this feature, LoadBeforeAppActivation or LoadAfterAppsRunning, a server instance loads startup classes when applications go to the admin state.
Run Before Application Activations
Specifies whether the targeted servers load and run this startup class after activating JMS and JDBC services and before activating applications and EJBs.
If you enable this feature for a startup class, a server loads and runs the startup class before the activate phase. At this point, JMS and JDBC services are available. (Deployment for applications and EJBs consists of three phases: prepare, admin and activate.)
Enable this feature if the startup class needs to be invoked after JDBC connection pools are available but before the applications are activated and ready to service client requests.
If you do not enable this feature, LoadBeforeAppDeployments or LoadAfterAppsRunning, a server instance loads startup classes when applications go to the admin state.
- Use custom classes to configure servers
- Configure startup classes
- Configure shutdown classes
- Deploy startup and shutdown classes
- Add startup and shutdown classes to the classpath