ConfigurationMBean
, DescriptorBean
, javax.management.DynamicMBean
, javax.management.MBeanRegistration
, javax.management.NotificationBroadcaster
, SettableBean
, TargetInfoMBean
, WebLogicMBean
SingletonServiceAppScopedMBean
public interface SubDeploymentMBean extends TargetInfoMBean
Modules in an EAR
JMS resources within a app scoped JMS module in an EAR
DEFAULT_EMPTY_BYTE_ARRAY
Modifier and Type | Method | Description |
---|---|---|
java.lang.String |
getName() |
Unique identifier for this bean instance.
|
SubDeploymentMBean[] |
getSubDeployments() |
The subdeployment groups within this JMS module.
|
SubDeploymentMBean |
lookupSubDeployment(java.lang.String name) |
freezeCurrentValue, getId, getInheritedProperties, getNotes, isDynamicallyCreated, isInherited, isSet, restoreDefaultValue, setComments, setDefaultedMBean, setNotes, setPersistenceEnabled, unSet
addPropertyChangeListener, createChildCopyIncludingObsolete, getParentBean, isEditable, removePropertyChangeListener
getAttribute, getAttributes, invoke, setAttribute, setAttributes
postDeregister, postRegister, preDeregister, preRegister
addNotificationListener, getNotificationInfo, removeNotificationListener
addTarget, getCompatibilityName, getTargets, removeTarget, setCompatibilityName, setModuleType, setName, setTargets
getMBeanInfo, getObjectName, getParent, getType, isCachingDisabled, isRegistered, setParent
java.lang.String getName()
For modules within an EAR, the name should be the URI of the module as defined in the META-INF/application.xml deployment descriptor. There is an exception to this for web applications. See below.
For web modules in an EAR, the name should always equal the context root of that webapp, because the URI is not always unique
getName
in interface ConfigurationMBean
getName
in interface TargetInfoMBean
getName
in interface WebLogicMBean
SubDeploymentMBean[] getSubDeployments()
The subdeployment groups within this JMS module. Subdeployments enable you to deploy some resources in a JMS module to a JMS server and other JMS resources to a server instance or cluster.
Standalone queues or topics can only be targeted to a single JMS server. Whereas, connection factories, uniform distributed destinations (UDDs), and foreign servers can be targeted to one or more JMS servers, one or more server instances, or to a cluster. Therefore, standalone queues or topics cannot be associated with a subdeployment if other members of the subdeployment are targeted to multiple JMS servers. However, UDDs can be associated with such subdeployments since the purpose of UDDs is to distribute its members to multiple JMS servers in a domain.
SubDeploymentMBean lookupSubDeployment(java.lang.String name)
name
-