![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section describes the inheritance of properties and permissions. For more information on wildcards, refer to Wildcards. For more information on destination properties, refer to Destination Properties. For more information on permissions, refer to Chapter 8, Authentication and Permissions.All destination properties are inheritable for both topics and queues. This means that a property set for a "wildcarded" destination is inherited by all destinations with matching names.For example, if you have the following in your topics.conf file:Topics foo.bar and foo.bob are secure topics because they inherit secure from their parent, foo.*. If your EMS server were to dynamically create a foo.new topic, it too would have the secure property.The properties inherited from a parent are in addition to the properties defined for the child destination.For example, if you have the following in your topics.conf file:In the above example, there is no way to make topic foo.* secure without making foo.bar secure. In other words, EMS does not offer the ability to remove inherited properties. However, for properties that are assigned values, you can override the value established in a parent.For example, if you have the following in your queues.conf file:foo.bar traceInheritance of permissions is similar to inheritance of properties. If the parent has a permission, then the child inherits that permission. For example, if Bob belongs to GroupA, and GroupA has publish permission on a topic, then Bob has publish permission on that topic.All rules for wildcards apply to inheritance of permissions. For example, if a user has permission to publish on topic foo.*, the user also has permission to publish on foo.bar and foo.new.For more information on wildcards, refer to Wildcards. For more information on permissions, refer to User Permissions.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |