Parameter | Description |
Destination Type | This property is populated based on the Adapter for JMS connection associated with this notification. For connections associated with queues, the value will be QUEUE. For connections associated with topics, the value will be TOPIC. |
Destination JNDI Name | The JNDI name of the queue or topic you want the notification to monitor for messages. Provide a Queue Name if the Destination Type is QUEUE. Provide a Topic Name if the Destination Type is TOPIC. |
Message Selector | The SQL-92 compliant message selector expression used for filtering messages. |
Connection Client ID | This parameter is only used if the Run as True Listener option is selected. This field only applies to topics.The unique connection ID to use when connecting to a JMS provider topic.If the connection factory has a default Client ID, the notification will use the default, not the value specified in this parameter. Note: Do not change this field after you have saved the notification; doing so could potentially cause orphaned durable subscriptions on the JMS destination. Note: If you need to use a Client ID for the notifications, it is better to specify it along with the other notification parameters using Designer, and not while creating the connection factory or the Adapter for JMS connections. When the Client ID is specified in the connection factory or JMS connections, only one connection can be created through this connection factory or connection. This limits the Adapter for JMS from leveraging the connection pool. |
Durable Subscription Name | The unique subscription name to use when creating durable subscriptions. If this field is left blank, the adapter will use the name of the notification for the value of this field. Note: Do not change this field after you have saved the notification because doing so could potentially cause orphaned durable subscriptions on the JMS destination. |
Maximum Messages | This field only applies when the notification does not have the Run as True Listener option enabled. The value of this field specifies the maximum number of messages to retrieve every time the notification polls the JMS destination for messages.By default the value is -1, which indicates that the notification retrieves all available messages from the queue or topic every time it polls the JMS destination. Note: Do not set the maximum messages to zero because the notification will not retrieve any messages. |
Receive Timeout | The notification will wait for as many milliseconds as are indicated in this field. Provide a value as follows: 1 or greater: The number of milliseconds the notification will wait. 0: The notification will not wait if there are no messages on the queue or topic. -1:The notification will wait indefinitely to receive messages. This is the default. |
Run as True Listener | If this option is enabled, the notification will not poll for messages. Instead, it listens to the JMS destination and publishes the associated notification as soon as a message arrives in the JMS destination. If you disable the associated connection, this notification will continue to run (see
Disabling Adapter Connections). |
Exactly Once Notification | If this option is enabled, Integration Server ignores duplicate messages from this notification if published. Note: This option applies only if you are publishing a document with the notification. |
Use Durable Subscription | If this option is enabled, the notification creates durable subscriptions for the topic. |
notificationField Names and notificationField Types | This table shows the structure of the publishable document type associated with the notification. |
Notification Service | If you want the notification to directly invoke a service rather than publishing a document to Integration Server (which you could then use with an Integration Server trigger to invoke a service), provide the name of a service in this field.If you provide a service name here, the input signature for the service must be constructed the same way as an input signature for a service that is invoked by a trigger. However, the service cannot use any of the _env fields in the signature. See the Publish-Subscribe Developer’s Guide. Important: This option provides the only way to use notifications for JMS providers whose implementation of the JMS message interface 'javax.jms.Message' does not implement the Serializable interface. This option must be used by the Web Application Server JMS providers. |