weblogic.management.configuration
Interface StartupClassMBean

All Superinterfaces:

ClassDeploymentMBean, ConfigurationMBean, DeploymentMBean

public interface StartupClassMBean
extends ClassDeploymentMBean

Provides methods that configure startup classes. A startup class is a Java program that is automatically loaded and executed when a WebLogic Server instance is started or restarted. 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.

Deprecation of MBeanHome and Type-Safe Interfaces

This is a type-safe interface for a WebLogic Server MBean, which you can import into your client classes and access through weblogic.management.MBeanHome. As of 9.0, the MBeanHome interface and all type-safe interfaces for WebLogic Server MBeans are deprecated. Instead, client classes that interact with WebLogic Server MBeans should use standard JMX design patterns in which clients use the javax.management.MBeanServerConnection interface to discover MBeans, attributes, and attribute types at runtime. For more information, see "Developing Manageable Applications with JMX."

Access limited to the following security roles:

Deployer

getFailureIsFatal

boolean getFailureIsFatal()

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.

Returns:

The failureIsFatal value

Default Value:

false

setFailureIsFatal

void setFailureIsFatal(boolean flag)

Sets the value of the FailureIsFatal attribute.

Parameters:

flag - The new failureIsFatal value

See Also:

StartupClassMBean.getFailureIsFatal()

Default Value:

false

getLoadBeforeAppDeployments

boolean getLoadBeforeAppDeployments()

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.

Returns:

The loadBeforeAppDeployments value

See Also:

DeploymentMBean

Default Value:

false

setLoadBeforeAppDeployments

void setLoadBeforeAppDeployments(boolean flag)

Sets the value of the LoadBeforeAppDeployments attribute.

Parameters:

flag - The new loadBeforeAppDeployments value

See Also:

StartupClassMBean.getLoadBeforeAppDeployments()

Default Value:

false

getLoadBeforeAppActivation

boolean getLoadBeforeAppActivation()

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.

See Also:

DeploymentMBean

Default Value:

false

setLoadBeforeAppActivation

void setLoadBeforeAppActivation(boolean flag)

Sets the value of the LoadBeforeAppActivation attribute.

See Also:

StartupClassMBean.getLoadBeforeAppActivation()

Default Value:

false

getLoadAfterAppsRunning

boolean getLoadAfterAppsRunning()

Specifies whether the targeted servers load and run this startup class after applications and EJBs are running.

If you enable this feature for a startup class, a server loads and runs the startup class after 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 applications are running and ready to service client requests.

If you do not enable this feature, LoadBeforeAppDeployments or LoadBeforeAppActivation, a server instance loads startup classes when applications go to the admin state.

See Also:

DeploymentMBean

Default Value:

false

setLoadAfterAppsRunning

void setLoadAfterAppsRunning(boolean flag)

Sets the value of the LoadAfterAppsRunning attribute.

See Also:

StartupClassMBean.getLoadAfterAppsRunning()

Default Value:

false