Fusion Middleware Control Help for WebLogic Server

Previous Next Open TOC in new window
Content starts here

Topic: Configuration: General

Configuration Options     

Use this page to define the general configuration parameters for this topic, such as selecting a destination key for sorting messages as they arrive on the topic.

You can configure topics explicitly or you can configure a JMS template to define and manage multiple topics with similar attribute settings.

Configuration Options

Name Description
Name

The name of this JMS topic.

MBean Attribute:
WebLogicMBean.Name

Changes take effect after you redeploy the module or restart the server.

Scope

The scope in which this JMS topic was created.

JNDI Name

The global JNDI name used to look up the destination within the JNDI namespace.

In a clustered environment, this name is propagated to the entire cluster. If you want the JNDI name to be bound only on the local server, and not propagated to the rest of the cluster, then use the Local JNDI Name parameter.

If not specified, the destination name will not be advertised through the global JNDI namespace.

MBean Attribute (Does not apply to application modules) :
DestinationBean.JNDIName

Template

The JMS template from which the destination is derived. A template provides an efficient means of defining multiple destinations with similar configuration values.

If a JMS template is specified, destination parameters that are set to their default values will instead inherit their values from the JMS template at run-time. However, if a JMS template is not defined, then the configuration values for the destination must be specified as part of the destination.

Although you can dynamically modify the configuration of a JMS template, the configuration values on a destination are static.

MBean Attribute (Does not apply to application modules) :
DestinationBean.Template

Changes take effect after you redeploy the module or restart the server.

Targeting Policy

Specifies whether this JMS resource defaults to the parent module's targeting or uses the subdeployment targeting mechanism.

When set to true, this resource implicitly inherits the targeting of its parent module. When set to false, this resource gets targeted based its subdeployment's targets, if one is specified.

MBean Attribute (Does not apply to application modules) :
DestinationBean.DefaultTargetingEnabled

Changes take effect after you redeploy the module or restart the server.

Subdeployment

Gets the name of the sub-deployment to use when targeting this entity

Entities are targeted using a sub-deployment with this name. The targets of the sub-deployment will be the targets of this entity.

MBean Attribute (Does not apply to application modules) :
DestinationBean.SubDeploymentName

Changes take effect after you redeploy the module or restart the server.


Back to Top