WebLogic Server Configuration Reference
By default, startup classes are loaded and executed after all other server subsystems have initialized and after the server deploys modules. For any startup class, you can override the default and specify that the server loads and executes it and before it deploys JDBC connection pools and before it deploys Web applications and EJBs.
FailureIsFatal=( "true" | "false" )
LoadBeforeAppActivation=( "true" | "false" )
LoadBeforeAppDeployments=( "true" | "false" )
Targets="list of Target names"
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.
Determines whether a failure in this startup class prevents a server from starting. If this check box is cleared (or if you use an API to specify a value of
LoadBeforeAppDeployments should be used when the startup class needs to be invoked before the applications are even prepared for deployment. Please note that connection pools are not yet created at this stage.
LoadBeforeAppActivation should be used when the startup class needs to be invoked after the connections pools are available but before the applications are activated and ready to service client requests.
Determines whether a startup class is loaded and run before the server creates JMS and JDBC services or deploys applications and EJBs. If you specify true for this option, the server loads and runs the class before the prepare() phase in the 2-phase depoloyment model. At this point, JMS and JDBC services are not yet available, and no applications or EJBs have been deployed.