Understanding secured topics

A secured topic can only be published by a publisher who is a member of a specific Windows security group. This restriction applies to the entire topic space under the secured topic, including all subtopics.

Attempts to publish to a topic in a secured topic space by a publisher who is not a member of the specified group are ignored by the PubSub system.

Secured topics are typically associated with a particular system or service, as seen in the examples below.

Where:

• <system> is the system name (for example, west or north).

• <service> is the service name (for example, RealTime, Historical, ISPS).

  Note: By convention, system names match the case used in the system configuration and the service names are always lowercase (using the invariant locale).

  <system>.arbitration

  <system>.common

  <system>.common.adlds.ep

  <system>.isps

  <system>.mocEventLog.Install

  <system>.nmc

  <system>.notify.adminpager

  <system>.<service>.arb

  <system>.<service>.health

  <system>.<service>.healthmon

  <system>.<service>.processmonitor

  <system>.<service>.wmimonitor