Create A New Startup Class
/management/weblogic/{version}/edit/startupClasses
Add a new startup class to this collection.
Request
- application/json
-
version: string
The version of the WebLogic REST interface.
-
X-Requested-By: string
The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Must contain a populated startup class model.
object
-
arguments(optional):
string
Arguments that a server uses to initialize a class.
Separate multiple arguments with a comma. For example:
first=MyFirstName,last=MyLastName
-
className(optional):
string
The fully qualified name of a class to load and run. The class must be on the server's classpath.
For example,
mycompany.mypackage.myclass
Constraints
- legal null
-
deploymentOrder(optional):
integer(int32)
Minimum Value:
0
Maximum Value:2147483647
Default Value:1000
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.
-
dynamicallyCreated(optional):
boolean
Read Only:
true
Default Value:false
Return whether the MBean was created dynamically or is persisted to config.xml
-
failureIsFatal(optional):
boolean
Default Value:
false
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.
-
id(optional):
integer(int64)
Read Only:
true
Return the unique id of this MBean instance
-
loadAfterAppsRunning(optional):
boolean
Default Value:
false
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.
-
loadBeforeAppActivation(optional):
boolean
Default Value:
false
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.
-
loadBeforeAppDeployments(optional):
boolean
Default Value:
false
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.
-
name(optional):
string
Read Only:
true
The user-specified name of this MBean instance.
This name is included as one of the key properties in the MBean's
javax.management.ObjectName
Name=user-specified-name
Constraints
- legal null
-
notes(optional):
string
Optional information that you can include to describe this configuration.
WebLogic Server saves this note in the domain's configuration file (
config.xml
) as XML PCDATA. All left angle brackets (<) are converted to the xml entity<. Carriage returns/line feeds are preserved.)>
Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.
-
tags(optional):
array Items
Title:
Items
Return all tags on this Configuration MBean
-
targets(optional):
array Target References
Title:
Target References
Contains the array of target references.You must select a target on which an MBean will be deployed from this list of the targets in the current domain on which this item can be deployed. Targets must be either servers or clusters. The deployment will only occur once if deployments overlap.
-
type(optional):
string
Read Only:
true
Returns the type of the MBean.
Constraints
- unharvestable
array
Target References
You must select a target on which an MBean will be deployed from this list of the targets in the current domain on which this item can be deployed. Targets must be either servers or clusters. The deployment will only occur once if deployments overlap.
-
Array of:
object Target Reference
Title:
Target Reference
Contains the target reference.
object
Target Reference
-
identity(optional):
array Identity
Title:
Identity
DOC TEAM TBD - describe an identity - it's a reference to another WLS REST resource.
array
Identity
-
Admin: basic
Type:
basic
Description:A user in the Admin security role.