|
|
Select to prevent this channel from sending messages to JMS providers. |
|
|
Displays options that are global to all messages. |
|
|
How long messages should live after they reach a destination. Specify the time duration in milliseconds. This setting is global for all sent messages.
A value of 0 specifies that the message lives indefinitely. |
|
|
Specifies the message priority.
0-4 indicates normal delivery 5-9 indicates expedited delivery
Specifying expedited delivery can result in “out-of-order” message processing. This setting is global for all sent messages. |
|
|
Specifies the default message type as text or bytes. This setting is global for all sent messages. |
|
|
Specifies whether to display parameters that show the properties sent with messages.
Message properties can be used to prevent message loopback or to pass application-specific information in messages.
These properties are global for all sent messages. |
|
|
Message property names beginning with “JMS” must match those defined by the JMS specification or third-party providers.
Property names fall into three general categories:
1. Standard JMS properties. They usually begin with JMS or JMSX. 2. Provider-specific properties. They usually begin with JMS_. 3. Application-specific. Anything else. |
|
|
Message property value. |
|
|
Displays options global to all destinations. |
|
|
Specifies whether all destinations are queues or topics by default. This setting is global for all destinations. |
|
|
Specifies whether the JMS message envelope should be omitted from received messages. This setting is global to all destinations. |
|
|
Specifies how long a channel should wait to receive a response to a sent message. The default value is 10 seconds. Permitted values can range from 1-25.
This setting is global to all destinations. |
|
|
Specifies how destinations filter received messages.
This setting is global to all destinations. |
|
|
Specifies a custom message selector to filter received messages. Message selectors are like SQL WHERE clauses, such as JMSCorrelationID LIKE '%01=whatever%'.
The % wildcard character can be used to disregard content before or after the part of a header or property value you're interested in filtering on. When used in tandem with a message filter, the message selector is appended to the end of the filter by using an AND operator. |
|
|
Specifies the identifier for this destination by which it is known in the Identity Manager namespace. This name is also the durable subscription name for topics. This value must be unique per channel (Subscriber/Publisher). |
|
|
Displays additional options for this selected destination. |
|
|
|
|
|
Specifies the identifier for this destination that is known in the JNDI namespace. This might not be the name the destination is known by to the broker. This value does not need to be unique. |
|
|
Specifies whether this destination is a queue or a topic. |
|
|
Specifies whether the destination is used to send or receive messages. |
|
|
Specifies whether messages are sent as text or bytes. |
|
|
Specifies whether to display message properties sent with messages. Message properties can be used to prevent message loopback or pass provider or application-specific information along with messages. |
|
|
Message property names beginning with JMS must match those defined by the JMS specification or third-party providers. Property names fall into three general categories:
-
Standard JMS properties. They usually begin with JMS or JMSX.
-
Provider-specific properties. They begin with JMS_.
-
Application-specific. Anything else.
|
|
|
Message property value. |
|
|
Specifies the identifier by which this destination is known in the Identity Manager namespace. This name is also the durable subscription name for topics. This value must be unique per channel (Subscriber/Publisher). |
|
|
Displays additional options for this selected destination. |
|
|
Specifies the identifier by which this destination is known in the JNDI namespace. This might or might not be the name the destination is known by to the message broker.
This value does not need to be unique. |
|
|
Specifies whether the destination is a queue or a topic. |
|
|
Specifies whether the destination is used to send or receive messages. |
|
|
Specifies whether messages should be sent as text or bytes. |
|
|
Displays options that specify the message properties sent with messages. Message properties can be used to prevent message loopback or pass provider or application-specific information along with messages. |
|
|
Message property names beginning with JMS must match those defined by the JMS specification or third-party providers. Property names fall into three general categories:
-
Standard JMS properties. They usually begin with JMS or JMSX.
-
Provider-specific properties. They begin with JMS_.
-
Application-specific. Anything else.
|
|
|
Message property value. |
|
|
Specifies whether the JMS message envelope is omitted from messages received by this destination. |
|
|
Specifies how long a channel should wait to receive a response to a sent message. The default value is 10 seconds. Permitted values can range from 1-25. |
|
|
Specifies how the destination receives filtered messages. |
|
|
Specifies a custom message selector to filter received messages. Message selectors are like SQL WHERE clauses (for example, JMSCorrelationID = whatever. When used in tandem with a message filter, the message selector is appended to the end of the filter by using an AND operator. |
|
|
Specifies the identifier by which this destination is known in the Identity Manager namespace. This name is also the durable subscription name for topics. This value must be unique per channel (Subscriber/Publisher). |
|
|
Displays additional options for this destination. |
|
|
Specifies the identifier by which this destination is known in the JNDI namespace. This might or might not be the name the destination is known by to the message broker.
This value does not need to be unique. |
|
|
Specifies whether the destination is a queue or a topic. |
|
|
Specifies whether the destination is used to send or receive messages. |
|
|
Specifies whether messages should be sent as text or bytes. |
|
|
Displays options that specify the message properties sent with messages. Message properties can be used to prevent message loopback or pass provider/application-specific information along with messages. |
|
|
Message property names beginning with JMS must match those defined by the JMS specification or third-party providers. Property names fall into three general categories:
-
Standard JMS properties. They usually begin with JMS or JMSX.
-
Provider-specific properties. They begin with JMS_.
-
Application-specific. Anything else.
|
|
|
Message property value. |