| |
SAF Imported Destinations: Configuration: General
Configuration Options Related Tasks Related Topics
Use this page to configure SAF imported destinations properties. SAF imported destinations are collections of SAF queues and topics that locally represent JMS queues or topics on a remote server or cluster. Each collection of imported destinations is associated with a remote SAF context. They can also share the same JNDI prefix, time-to-live default (message expiration time), and SAF error handling policy.
Configuration Options
Name Description Name The name of this SAF imported destination.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.NameChanges take effect after you redeploy the module or restart the server.
JNDI Prefix Specifies the string that will prefix the local JNDI name of a remote destination.
Any change to this prefix affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.JNDIPrefixRemote SAF Context Specifies the remote context used for the imported destinations.
Changing the remote context name affects both stored messages and incoming messages.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.SAFRemoteContextSAF Error Handling Specifies the error handling configuration used for the imported destinations.
Any change to this parameter affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.SAFErrorHandlingChanges take effect after you redeploy the module or restart the server.
Enable SAF Default Time-to-Live Controls whether the Time-to-Live (expiration time) value set on imported JMS messages will be overridden by the value specified in the
SAF Default Time-to-Livefield.Any change to this parameter affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.UseSAFTimeToLiveDefaultSAF Default Time-to-Live Specifies the default Time-to-Live value (expiration time), in milliseconds, for imported JMS messages. The expiration time set on JMS messages will override this value unless the
SAF Default Time-to-Live Enabledfield is switched on, which then overrides the expiration time in JMS messages on imported destinations.Any change to this value affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.TimeToLiveDefaultMinimum value:
-1Message Unit-of-Order Routing Specifies the type of routing used to find a SAF agent when using the message Unit-of-Order feature.
Hashindicates that message producers use the hash code of a message Unit-of-Order to find a SAF agent.
PathServiceindicates that message producers use the Path Service to find a SAF agent.MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.UnitOfOrderRoutingChanges take effect after you redeploy the module or restart the server.
Default Targeting Enabled 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) :
SAFImportedDestinationsBean.DefaultTargetingEnabledChanges take effect after you redeploy the module or restart the server.
Exactly-once Load Balancing Policy Controls the load balancing behavior when the SAF service forwards messages to a distributed destination with the
Exactly-Oncequality of service (QOS).The valid values are:
Per-Member- The default value. All active members of the target distributed destination (DD) will be the candidates for load balancing. If there are multiple members of the same DD running on a WebLogic server JVM, these members will all receive forwarded messages.
Per-JVM- On each WebLogic server JVM, only one of the active members of the target distributed destination(DD) will be the candidate for load balancing. When the DD has members associated with the instances of a cluster-targeted JMS server, the load balancing algorithm will bias to the "preferred member", which has natural affinity or preference to a particular JVM. Otherwise, the algorithm will bias to the member whose name is lexicographically smallest among all candidate members on the same JVM.Notes:
When each JVM hosts only one member of a DD, the two options behave the same.
You can override the
Exactly Once Load Balancing Policyon SAF Imported Destinations Beans defined in all JMS modules or a particular JMS module by specifying the system propertiesweblogic.jms.saf.ExactlyOnceLoadBalancingPolicyorweblogic.jms.saf.ExactlyOnceLoadBalancingPolicy.MODULENAMEon every WebLogic Server in a cluster (the latter property takes precedence over the former). If a SAF Imported Destinations is overridden by one of these system properties, then the host WebLogic Server will log an Info message BEA-281034 with the name of the SAF Imported Destinations, the system property, and the system property value once the first SAF message is forwarded.The setting does not apply to the SAF configurations that use the
At-Last-OnceorAt-Most-OnceQOS. Neither does it apply to forwarding messages to a "standalone" destination, or forwarding unit-of-order messages.The setting is honored in both server store-and-forward and client store-and-forward.
For a similar setting that controls the load balancing of messages on a local distributed Imported Destination, see the Producer Load Balancing Policy attribute on Connection Factory Load Balancing Params Bean.
MBean Attribute (Does not apply to application modules) :
SAFImportedDestinationsBean.ExactlyOnceLoadBalancingPolicyChanges take effect after you redeploy the module or restart the server.
|