JMS Topic Subscriber input connector

This connector enables StreamServer to receive messages from a named topic in a publish-subscribe messaging system.

Connector settings
Setting	Description
java.naming.factory.initial	Specifies the JNDI provider class to use. See JNDI Settings. You can use the drop-down list to select a provider (see below) or type in the full JNDI class name if you want to use another provider. File system JNDI (Sun) File based JNDI directory provided by Sun. Full JNDI class name: com.sun.jndi.fscontext.RefFSContextFactory LDAP (Sun) LDAP based JNDI directory. Full JNDI class name: com.sun.jndi.ldap.LdapCtxFactory
java.naming.provider.url	The path to the JNDI directory. See JNDI Settings.
Context	The JNDI context. If you leave this empty, the initial context will be used. It is possible to specify nested JNDI directories. To do this you use this setting to specify the name, within the initial context of the JNDI directory, to actually use.
Connection factory	The JNDI name of the connection factory to use. See Connection factory.
Authentication	The authentication profile (user name and password) to use to access the JMS provider. See Authentication profiles in the Profile configurations documentation
Topic	The JNDI name of the topic to use.
Selector	You can use a message selector to apply filters to the received messages. A message selector is a string that contains an expression. The syntax of the expression is based on a subset of the SQL92 conditional expression syntax. Example: Type = ’Invoice’ OR Type = ’Order’ This message selector selects messages where Type is set to either Invoice or Order.
Durable subscriber name	If you specify a durable subscriber name, the subscription will become durable with the supplied name. See Durable subscriptions.
Polling interval	Opens the Scheduler Configuration dialog where you specify when and how often to retrieve messages. See Scheduling actions in the Design Center documentation for more information about scheduling.
Time-out	Specifies a time-out (seconds) for the connector. StreamServer uses job-end sequences in the input data to determine when all data in an input job is received. If there are no job-end sequences in the input data, StreamServer will not know when to stop waiting for more input. To prevent this from happening, you can define a time-out for the input connector.