> Overview
> TIBCO Enterprise Message Service can exchange messages with TIBCO SmartSockets.
> Scope

> ● | EMS can import and export messages to an external system through an EMS topic.

> ● | EMS can import messages from an external system to an EMS queue (but queues cannot export).

> Figure 24 SmartSockets Transports in the EMS Server
> Message Translation
> EMS and SmartSockets use different formats for messages and their data. When tibemsd imports or exports a messages, it translates the message and its data to the appropriate format; for details, see Message Translation.
> Configuration
> tibemsd uses definitions and parameters in three configuration files to guide the exchange of messages with SmartSockets.
> Enabling
> The parameter tibss_transports (in the configuration file tibemsd.conf) globally enables or disables message exchange with SmartSockets. The default value is disabled. To use these transports, you must explicitly set this parameter to enabled.
> The parameter tibss_config_dir (in the configuration file tibemsd.conf) specifies the location of SmartSockets files needed by the SmartSockets client within tibemsd.
> Transports
> Transport definitions (in the configuration file transports.conf) specify the communication protocol between EMS and the external system; for details, see Configuring Transports for SmartSockets.
> Destinations
> Destination definitions (in the configuration files topics.conf and queues.conf) can set the import and export properties to specify one or more transports:

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

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

> For details, see Topics, and Queues.
> Starting the Servers
> We recommend starting the SmartSockets RTserver before starting tibemsd.

Copyright © TIBCO Software Inc. All Rights Reserved.