Defines an instance of the persistent store on the specified target that will keep its persistent objects in files on the filesystem. It may be used by JMS and by other subsystems.
If you use the getMBeanInfo
operation in MBeanTypeServiceMBean, supply the following value as this MBean's fully qualified interface name:
weblogic.management.configuration.FileStoreMBean
Since 9.0.0.0
Because this MBean extends or implements DeploymentMBean, you can also access this MBean by retrieving DeploymentMBeans. The following attributes contain DeploymentMBeans and its subtypes:
|
Because this MBean extends or implements PersistentStoreMBean, you can also access this MBean by retrieving PersistentStoreMBeans. The following attributes contain PersistentStoreMBeans and its subtypes:
This section describes attributes that contain child MBeans. For more information about the MBean hierarchy, refer to WebLogic Server MBean Data Model.
|
The server instance that is targetted to a store.
Factory Methods | No explicit creator method. The child shares the lifecycle of its parent. |
Privileges | Read/Write |
Type | TargetMBean[] |
This section describes the following attributes:
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.
Privileges | Read/Write |
Type | int |
Default Value | 1000 |
Minimum value | 0 |
Maximum value | 2147483647 |
The path name to the file system directory where the file store maintains its data files.
This attribute is not dynamically configurable.
Privileges | Read/Write |
Type | java.lang.String |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
The name used by subsystems to refer to different stores on different servers using the same name.
For example, an EJB that uses the timer service may refer to its store using the logical name, and this name may be valid on multiple servers in the same cluster, even if each server has a store with a different physical name.
Multiple stores in the same domain or the same cluster may share the same logical name. However, a given logical name may not be assigned to more than one store on the same server.
Privileges | Read/Write |
Type | java.lang.String |
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
Privileges | Read/Write |
Type | java.lang.String |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
Optional information that you can include to describe this configuration.
WebLogic Sever 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.
If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.
Privileges | Read/Write |
Type | java.lang.String |
Return the immediate parent for this MBean
Privileges | Read/Write |
Type | |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
The disk write policy that determines how the file store writes data to disk.
This policy also affects the JMS file store's performance, scalability, and reliability. The valid policy options are:
Direct-Write
File store writes are written directly to disk. This policy is supported on Solaris, HP-UX, and Windows. On Windows systems, this option generally performs faster than the Cache-Flush option writes.
Disabled
Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be more than 100 times faster than the other policies, but power outages or operating system failures can cause lost and/or duplicate messages.
Cache-Flush
Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.
Privileges | Read/Write |
Type | java.lang.String |
Default Value | Direct-Write |
Legal Values |
|
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
Returns the type of the MBean.
Privileges | Read only |
Type | java.lang.String |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
Overrides the name of the XAResource that this store registers with JTA.
You should not normally set this attribute. Its purpose is to allow the name of the XAResource to be overridden when a store has been upgraded from an older release and the store contained prepared transactions. The generated name should be used in all other cases.
Privileges | Read only |
Type | java.lang.String |
Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
This section describes the following operations:
Targets a server instance to a store.
Operation Name | "addTarget" |
Parameters | Object [] {
}
where: |
Signature | String [] {
"weblogic.management.configuration.TargetMBean" } |
Returns |
boolean
|
javax.management.InvalidAttributeValueException
weblogic.management.DistributedManagementException
If the specified attribute has not been set explicitly, and if the attribute has a default value, this operation forces the MBean to persist the default value.
Unless you use this operation, the default value is not saved and is subject to change if you update to a newer release of WebLogic Server. Invoking this operation isolates this MBean from the effects of such changes.
To insure that you are freezing the default value, invoke the
restoreDefaultValue
operation before you invoke
this.
This operation has no effect if you invoke it on an attribute that does not provide a default value or on an attribute for which some other value has been set.
Deprecated.
Operation Name | "freezeCurrentValue" |
Parameters | Object [] {
attributeName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
void
|
javax.management.AttributeNotFoundException
javax.management.MBeanException
Returns true if the specified attribute has been set explicitly in this MBean instance.
Operation Name | "isSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
boolean
|
Untargets a server instance from a store.
Operation Name | "removeTarget" |
Parameters | Object [] {
}
where: |
Signature | String [] {
"weblogic.management.configuration.TargetMBean" } |
Returns |
boolean
|
javax.management.InvalidAttributeValueException
weblogic.management.DistributedManagementException
If the specified attribute has a default value, this operation removes any value that has been set explicitly and causes the attribute to use the default value.
Default values are subject to change if you update to a newer
release of WebLogic Server. To prevent the value from changing if
you update to a newer release, invoke the
freezeCurrentValue
operation.
This operation has no effect if you invoke it on an attribute that does not provide a default value or on an attribute that is already using the default.
Deprecated.
Operation Name | "restoreDefaultValue" |
Parameters | Object [] {
attributeName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
void
|
javax.management.AttributeNotFoundException
Restore the given property to its default value.
Operation Name | "unSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
void
|