StartupClassMBean (Java API Reference for Oracle WebLogic Server)

Class

Use

Tree

Help

Oracle Fusion Middleware
Java API Reference for Oracle WebLogic Server
12c (12.2.1)

Part Number E55141-01
P4 Change 1723563 on 2015/10/09

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

weblogic.management.configuration
Interface StartupClassMBean

All Superinterfaces:: ClassDeploymentMBean, ConfigurationMBean, DeploymentMBean, DescriptorBean, DynamicMBean, MBeanRegistration, NotificationBroadcaster, SettableBean, WebLogicMBean

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.

Field Summary

Fields inherited from interface weblogic.management.configuration.DeploymentMBean
`DEFAULT_ORDER, MAX_ORDER, MIN_ORDER`

Fields inherited from interface weblogic.management.configuration.ConfigurationMBean
`DEFAULT_EMPTY_BYTE_ARRAY`

Method Summary
`abstract boolean`	`getFailureIsFatal()` Specifies whether a failure in this startup class prevents the targeted server(s) from starting.
`abstract boolean`	`getLoadAfterAppsRunning()` Specifies whether the targeted servers load and run this startup class after applications and EJBs are running.
`abstract 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.
`abstract 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.
`abstract void`	`setFailureIsFatal(boolean flag)` Sets the value of the FailureIsFatal attribute.
`abstract void`	`setLoadAfterAppsRunning(boolean flag)` Sets the value of the LoadAfterAppsRunning attribute.
`abstract void`	`setLoadBeforeAppActivation(boolean flag)` Sets the value of the LoadBeforeAppActivation attribute.
`abstract void`	`setLoadBeforeAppDeployments(boolean flag)` Sets the value of the LoadBeforeAppDeployments attribute.

Methods inherited from interface weblogic.management.configuration.ClassDeploymentMBean
`getArguments, getClassName, setArguments, setClassName`

Methods inherited from interface weblogic.management.configuration.DeploymentMBean
`addTarget, getDeploymentOrder, getTargets, removeTarget, setDeploymentOrder, setTargets`

Methods inherited from interface weblogic.management.configuration.ConfigurationMBean
`freezeCurrentValue, getId, getInheritedProperties, getName, getNotes, isDynamicallyCreated, isInherited, isSet, restoreDefaultValue, setComments, setDefaultedMBean, setName, setNotes, setPersistenceEnabled, unSet`

Methods inherited from interface weblogic.management.WebLogicMBean
`getMBeanInfo, getObjectName, getParent, getType, isCachingDisabled, isRegistered, setParent`

Methods inherited from interface javax.management.DynamicMBean
`getAttribute, getAttributes, invoke, setAttribute, setAttributes`

Methods inherited from interface javax.management.MBeanRegistration
`postDeregister, postRegister, preDeregister, preRegister`

Methods inherited from interface javax.management.NotificationBroadcaster
`addNotificationListener, getNotificationInfo, removeNotificationListener`

Methods inherited from interface weblogic.descriptor.DescriptorBean
`addPropertyChangeListener, createChildCopyIncludingObsolete, getParentBean, isEditable, removePropertyChangeListener`

Method Detail

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

setFailureIsFatal

void setFailureIsFatal(boolean flag)

Sets the value of the FailureIsFatal attribute.

Parameters:: flag - The new failureIsFatal value
See Also:: StartupClassMBean.getFailureIsFatal()

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

setLoadBeforeAppDeployments

void setLoadBeforeAppDeployments(boolean flag)

Sets the value of the LoadBeforeAppDeployments attribute.

Parameters:: flag - The new loadBeforeAppDeployments value
See Also:: StartupClassMBean.getLoadBeforeAppDeployments()

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

setLoadBeforeAppActivation

void setLoadBeforeAppActivation(boolean flag)

Sets the value of the LoadBeforeAppActivation attribute.

See Also:: StartupClassMBean.getLoadBeforeAppActivation()

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.

Since:: 10.3.3.0
See Also:: DeploymentMBean

setLoadAfterAppsRunning

void setLoadAfterAppsRunning(boolean flag)

Sets the value of the LoadAfterAppsRunning attribute.

See Also:: StartupClassMBean.getLoadAfterAppsRunning()

Overview

Package