Resolution:
WIth one exception RTserver does not have the capability to do any message filtering based upon message type or content. It should be left to the receiving client to determine if, when subscribing on a subject and receiving a message on that subject, whether or not the message received should be processed or discarded based upon message type or content.

The exception would be if RTserver is using the Basic Security feature of SmartSockets. (See the SmartSockets User's Guide, Chapter 3 Publish Subscribe, Section "Security"). The security option Sd_Basic_Admin_Msg_Types would have to be defined in the file sdbasic.cm. ( See the SmartSockets User's Guide, Chapter 8 Options Reference, Sd_Basic_Admin_Msg_Types option for details).

TIBCO does offer a product called RTGateway that provides a content inspector (a filter_list which is a string that lists the message type names or numbers the content inspector should filter). However, RTGateway was designed primarily to bridge server clouds and the content inspector was more of a secondary feature of the product. RTGateway is not recommended to be deployed in a single server cloud to restrict or filter messages. Every message published would have to go through RTGateway which would result in severe performance degradation.

For content based filtering, the TIBCO Business Works product has a plug in that allows parsing of SmartSockets messages which then allows user defined action based upon message content.

Is there a way for RTserver to restrict or filter a list of message types?