> Topics
> Topics can both export and import messages. Accordingly, you can configure topic definitions (in the configuration file topics.conf) with import and export properties that specify one or more external transports:
> import

> ● | import instructs tibemsd to import messages that arrive on those transports from SmartSockets, and deliver them to the EMS destination.

> export

> ● | export instructs tibemsd to take messages that arrive on the EMS destination, and export them to SmartSockets via those transports.

> | The EMS server never re-exports an imported message on the same topic.

> (For general information about topics.conf syntax and semantics, see topics.conf on page 229. You can also configure topics using the administration tool command addprop topic.)
> Example
> For example, the following tibemsadmin commands configure the topic myTopics.news to import and export messages on three transports.
> addprop topic myTopics.news import="SS01,SS02"
> addprop topic myTopics.news export="SS01,SS02,SS03"
> SmartSockets messages with subject /myTopics/news arrive at tibemsd over the transports SS01 and SS02. EMS clients can receive those messages by subscribing to myTopics.news.
> EMS messages sent to myTopics.news are exported to SmartSockets over all three transports—SS01, SS02 and SS03. SmartSockets clients of the corresponding RTservers can receive those messages by subscribing to /myTopics/news.
> Import Only when Subscribers Exist
> When a topic specifies import on a connected transport, tibemsd imports messages only when the topic has registered subscribers.
> Wildcards
> Wildcards in the import and export properties obey EMS syntax and semantics (not SmartSockets syntax and semantics); see Destination Name—Syntax and Semantics.

Copyright © TIBCO Software Inc. All Rights Reserved.